BDC Recording doesn't proceed after Information Message

Hi,
I need to upload Vendor Master Data. I've recorded a BDC transaction and I came across an Information message in the final stages of the transaction.
The activity I recorded after the information message is saving the transaction. However hen I processed the recording it stops at the place where  the Information message popped up.( though the SAVE action( okcode =UPDA) is recorded). Spo each time I need to Save manually though I recorded it.
How can I make the recording to proceed even after the Information message is displayed( Note: Information message is not seen when processing the recording).
Any immediate inputs in the regard will be of great help.
Regards,
Siva

Rich,
  Thanks for your reply.
  The real scenario is like this.
  There is an error before the Information message expecting a Tax code value which we need to live with. During recording we fill the required field where the error occured and proceed by pressing ENTER. All these are recorded. The Information Popup is very next screen after pressing ENTER. So I beliecve all these were recorded and still it is not executing the final SAVE Process.
A piece of code for your reference.
('KNVI-TAXKD' is the place where error occured. We entered a value and proceed with ENTER key.)
The point to be noted is though the OK Code is there for SAVE (=UPDA)it is not getting saved. Please resolve this if you could able to.
perform fill_bdc_data using:
             'X'      'SAPLWR09'        '0320',
              space    'BDC_CURSOR'      'KNVI-TAXKD',
              space    'BDC_OKCODE'      '/00',
<b>              space    'KNVI-TAXKD'      '0'.</b>
perform fill_bdc_data using:
              'X'      'SAPMF02K'        '0310',
              space    'BDC_CURSOR'      'LFM1-WAERS',
              space    'BDC_OKCODE'      '/00'.
perform fill_bdc_data using:
              'X'      'SAPMF02K'        '0320',
              space    'BDC_CURSOR'      'RF02K-LIFNR',
<b>              space    'BDC_OKCODE'      '=UPDA'.</b>

Similar Messages

  • How to display the information message in the end in BDC

    Dear All,
    I have been submitting a BDC for FB01, in a dialog program of mine.
    The BDC gets executed successfully but it does not display the 'Documnet No....generated' information message in the end.
    I have even written the following code in the BDC, after call transaction, to accomplish this, by assigning the value of genno (variable) to sy-msgv1, but it's not working.
    call transaction 'FB01' using bdcdata1 mode 'E'.
      message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      genno = sy-msgv1.

    Hi,
    try this its easy .
    create an internal table e_report for sucess with the fields you want to display .like the same for F_tab for failure .
    so finally u will be having the success record in e_report and the failure in f_itab.
    call transaction 'FB09' using bdcdata MODE 'N' MESSAGES INTO IT_ERROR.
    IF sy-subrc eq 0.
      E_report-status = 'Sucessfully Updated'.
      e_report-belnr = itab-belnr.
      e_report-year = fiscalyear.
      APPEND E_report.
    else .
       F_tab = itab.
       F_tab-year = fiscalyear.
       F_tab-status = 'FAILED'.
       APPEND F_tab.
    finally print this
    sort e_report by  belnr ascending.
    LOOP AT E_report.
        at FIRST .
           WRITE:/'**********SUCCESSFUL RECORDS ARE **********'.
           FORMAT COLOR 6.
           WRITE:/ 'Document Numer',20 'Year',35'Status',54 ''.
        ENDAT.
        FORMAT COLOR 3.
        write:/ E_report-belnr,20 E_report-year ,35 E_report-status.
        FORMAT COLOR OFF.
       at LAST.
         write:/ 'Total No.Of Successful Records:',sy-tabix.
         FORMAT COLOR OFF.
       ENDAT.
       RESERVE 20 LINES.
    ENDLOOP.
      IF F_tab is initial.
           FORMAT COLOR 1.
           WRITE:/ ' NO Errored Files'.
           FORMAT COLOR OFF.
      ENDIF.
    WRITE:/ SY-ULINE.
    new-PAGE.   " to display in a  new page
    sort f_tab by  belnr ascending.
    LOOP AT F_tab.
        at FIRST .
           WRITE:/'**********FAILED RECORDS ARE **********'.
           FORMAT COLOR 6.
           WRITE:/ 'Document Numer',20 'Year',35'Status',54 ''.
        ENDAT.
           FORMAT COLOR 5.
           WRITE:/ f_tab-belnr ,20 F_tab-year, 35 F_tab-status.
        at LAST.
         write:/ 'Total No.Of Failed Records:',sy-tabix.
        ENDAT.
    ENDLOOP.
    ENDIF.
    if they want to display in the excel sheet pass the internal table to the F.M.
    plz motivate me.
      by rewards.
    thanks
    vinoth

  • Capturing warning message in BDC recording

    Hi all,
    I want to capture a warning message that is getting popped during BDC recording. When BDC is ran in background, it is stopping at that point and further processing is stopped with the display of this warning message.
    Can anybody help me in capturing this warning message?
    Thanksm
    Archana

    Hi Avinash,
    I am trying to change the profit center using this BDC. So, when i change it, this warning is displayed and it goes inside one more window and coreects the new profit center added in the previous window. So, this warning message is necessary to be displayed. But my problem is that because of this message my BDC is also not proceeding further.
    Hi Bhavesh,
    The warning message is getting displayed as a pop-up. I am not getting any information about the screen number. I know the prgram for that but no the screen number. And can you please tell me what that piece of code does? So that i can try it out in my BDC.
    Thanks,
    Archana

  • Want to output Error message in BDC recording(PA30)

    Hi all,
    Currently iam working on upload program,whic is done by BDC recording with transaction PA30.while loading the data to different infotypes,iam checking one condition
    in particular infotype,after that i need to give the error message(Type E) and i data should not get uploaded for that infotype,and it has to go to next infotype.i want to log this error also,how can i do this?

    The ERROR message will stop the processing of the program,  the message will need to be either an I(information) or a W(warning) message into for the program to continue processing.
    Log the message by writing it to an internal table.
    IF SOME_CONDITION = 'X'.
    MESSAGE W001(00) with 'Hey, here is a message'.
    itab-pernr = p_pernr.
    itab-msgid = '00'.
    itab-msgno = '001'.
    append itab.
    ENDIF.
    CALL TRANSACTION 'PA30'........
    Regards,
    Rich HEilman

  • Suppressing Information Message in BDC

    Hi all,
    I want to avoid the Information Messages comming during Recording while doing a BDC in no-screen mode.
    Please help me.
    Thanks & Regards
    GK

    Hi ,
    Thanks for he quick response.
    The information message is comming in the form of a pop-up window. I can for now do write a line of code to avoid this.
    In case in future if that pop-up message does not come, then my output will again get effected.
    Thanks
    GK

  • Can we show information messages after triggring IDOC's in background

    Hi friends,
    Iam executing one custom transaction for sales cycle in background, in that iam trigging IDOC's, user are getting the messages like
    1. Idoc No: 0000014254 despatched to client -
    2. 1Output  were processed.
    3. 1 IDOC's selected.
    user has to enter 3 times while the transaction is running in background.
    But requirement is "can i set all 3 information messages after trigging IDOC's to background.
    any body suggest the solution.
    regards,
    vamsy krishna.

    Nope nope, I don't work for Apple - I'm just a Level 3 Discussions pleb...! ;-))
    I'd been in touch with the senior tiers of Apple Support on the phone to diagnose the chkdsk incidents of 2004-2005.
    Following that, I also negotiated (part-)resolution to the Smart Playlist issue.
    Since Updater 2006-01-10 (part-)fixed the Smart Playlist problem, but seemed to introduce some other issues for folks, I've been continuing to pass feedback from my Level 2 contact who is handling investigation of the latest problems. In turn, he is working with US Engineering to handle this issue.
    So no, I'm not Apple, but I (and some others) pass commentary to and fro between Discussions and Level 2 Support, and by by-passing Front Line phone support, it helps us to get serious issues investigated and resolved more quickly. I find that such an approach for serious problems works well to help the Community.
    I'm not sure if my message gives hope - but I do hope that having reported this on up to Level 2, and having been told that US Engineering have teams watching Discussions, that maybe we can expect some attention from Apple R&D on this matter. However, the official line is for individuals to contact Apple directly themselves via the phone and website feedback, so US Engineering have an idea of the number of people affected. The more people who report to Apple directly, the more likely the problem is to be noticed, and hence the priority for investigation and resolution increases. I can start an unofficial ball rolling, as I have done, but we cannot keep the momentum up unless users use these official routes to let Apple know they are affected.
    Sorry it's all a bit foggy, but it's the best I've got! Hope this little explanation helps to clarify things a bit more. Feel free to post back if you'd like to discuss this further. Best for now.
    Kind regards,
    Gopha.

  • HT1430 my iphone 4 turn off after appearing message "temprature high, need to be cool down after than doesn't becoming turn on"

    my iphone 4 turn off after appearing message 'temprature high, need to be cool down' after that does not getting turn on by anyhow.

    Hello vijaypatel,
    Thanks for the question. The following article outlines the temperature warning that you experienced:
    iPhone, iPad, and iPod touch (4th generation): Keeping device within acceptable operating temperatures
    http://support.apple.com/kb/HT2101
    If the iPhone is no longer powering on, we will need to isolate this issue to determine if it is hardware related.
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/TS2802
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    - Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    - Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion.
    Learn about LCIs and corrosion.
    - Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    - After at least 15 minutes, if:
                   - The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
                   - The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
                   - Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    - If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
                   - If the display turns on, go to step 4.
                   - If the display remains black, go to next step.
    - Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to
    restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    - If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    Thanks,
    Matt M.

  • Error  message B1 357-Status records with status 51 after status 53

    Hi All,
    somebody  knows  why  is  can  be  caused this  message:
    ''Error  message B1 357-Status records with status 51 after status 53''
    Thanks and  best  regards
    L

    Dear Luis,
    Please Check
    Status records with status 51 after status 53
    Best Regards,
    Amit

  • Is there anyone who can help me? my Photoshop CC is keep crashing, it doesn't show any error message. Suddenly " program stop responding" after few seconds of launch.

    Is there anyone who can help me? my Photoshop CC is keep crashing, it doesn't show any error message. Suddenly " program stop responding" after few seconds of launch.

    If Photoshop crashes the should be a System crash report generated by your OS. For example Windows

  • Popup dialog or information message after planning functions run

    Hi Guru,
              Anyone who encounter an issue on BPS where a popup dialog or information message appear with SQL statements (one line of statement per dialog). When I debug it the message was raise by form write_sql_log_begin/end.
    Thanks,
    Irish

    MODULE m_pai INPUT.
    CASE fcode.
        WHEN 'ENT'.
            PERFORM f_force_enter.
            LOOP AT git_tab INTO gwa_tab.
                  PERFORM f_update_it9090 USING l_tabix.
            ENDLOOP.
      ENDCASE.
      CLEAR fcode.
    ENDMODULE.      
    FORM f_update_it9090 USING fu_tabix.
    PERFORM f_read_9090 TABLES lit_p9090 USING fu_tab CHANGING lwa_p9090.
        IF lwa_p9090-pernr IS NOT INITIAL.
      ELSE.
          CONCATENATE fu_tab-pernr text-014 '.' INTO l_text SEPARATED BY space.
          <b>MESSAGE i004 WITH l_text.</b>
          g_final_flag = 'X'.
        ENDIF.
    ENDFORM.          
    FORM f_force_enter.
      CALL METHOD g_alv->check_changed_data
        IMPORTING
          e_valid = g_valid.
    ENDFORM.
    Therefore, when this code is run the statement highlighted in BOLD behaves differently when 'Enter' is strike before save and when 'Enter' is not strike before save.  The f_force_enter subroutine is invoke to cause data_changed method to be invoke to capture relevant data before proceeding to other processing.

  • Handling popups in bdc recording

    Hi,
    I am doing bdc recording for a transaction, and there is a popup screen to be handled by the user, but when i am doing recording it is not recording the popup menus. can you please tel me how i can handle popups in BDC recording.
    It is very urgent.
    Thank you.

    Hi Ameen,
    Award points if useful...
    Step by Step approach to ceate simple BDC session program using reusable template.
    This step by step approach can be used to create a Simple BDC program i.e for a transaction which does not have any table control / looping at screen table. The same can also be enhanced to develop a program for transactions involving table controls .
    1. Create a new program as executable program using SE38 transaction code.
    2. Copy the following template code into your program .
    ---- Start of Template -
    REPORT  NO STANDARD PAGE HEADING LINE-SIZE 200 LINE-COUNT 300.
    *-- DATA DECLARATION--
    *---Types
    DATA : BEGIN OF t_upload,
    FIELD1(10),
    FIELD2(2),
    FIELD3(18),
    FIELD4(35),
    END OF t_upload.
    *--- Tables
    DATA : BEGIN OF i_bdcdata OCCURS 0."to hold the transaction record
    INCLUDE STRUCTURE bdcdata.
    DATA: END OF i_bdcdata.
    DATA: i_upload LIKE STANDARD TABLE OF t_upload," to hold file data.
    i_upload1 LIKE STANDARD TABLE OF t_upload." to hold file data.
    *--- Work Areas
    DATA: wa_upload2 LIKE t_upload,
    wa_upload LIKE t_upload,
    wa_upload1 LIKE t_upload.
    *--- Variables
    DATA: v_count1(4) TYPE n,
    v_error TYPE c,
    v_session(12),
    v_field(21) TYPE c,
    v_message(60) type 'C'.
    *--Constants
    DATA: c_open TYPE c VALUE '(',
    c_close TYPE c VALUE ')',
    c_x TYPE c VALUE 'X'.
    *---Initialisation
    initialization.
    refresh : i_upload , i_upload1 ,i_bdcdata.
    -------Selection Screen Design -
    *Selection screen for input of upload file address
    SELECTION-SCREEN SKIP 2.
    SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
    PARAMETERS : p_file LIKE rlgrap-filename OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK blk1.
    ---AT SELECTION SCREEN -
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    *--For popup to select file.
    PERFORM give_help.
    -----START OF SELECTION -
    START-OF-SELECTION.
    *--Data upload using WS_Upload.
    PERFORM get_data.
    *-- OPEN SESSION
    PERFORM open_group.
    *--Insert transactions using BDCDATA table in the session.
    PERFORM do_transaction .
    *-- Close the session.
    PERFORM close_group.
    END-OF-SELECTION.
    *& Form f_get_data
    For data upload from external file.
    FORM get_data.
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
    filename = p_file
    filetype = 'DAT'
    TABLES
    data_tab = i_upload
    EXCEPTIONS
    conversion_error = 1
    file_open_error = 2
    file_read_error = 3
    invalid_type = 4
    no_batch = 5
    unknown_error = 6
    invalid_table_width = 7
    gui_refuse_filetransfer = 8
    customer_error = 9
    OTHERS = 10.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ELSE.
    DELETE I_UPLOAD INDEX 1.
    ENDIF.
    ENDFORM. " f_get_data
    *& Form F_open_group
    To open session in session management.
    FORM open_group.
    v_session = 'TCODE'.
    CALL FUNCTION 'BDC_OPEN_GROUP'
    EXPORTING
    client = sy-mandt
    group = v_session
    user = sy-uname
    keep = 'X'.
    ENDFORM. " F_open_group
    *& Form f_do_transaction
    Insert transactions in session after passing values to BDCDATA
    FORM do_transaction.
    LOOP AT i_upload INTO wa_upload .
    *---- insert your generated codes from recording at SHDB here
    *----- insertion ends
    perform bdc_transaction using 'TCODE'.
    REFRESH : I_BDCDATA.
    CLEAR : WA_UPLOAD.
    ENDIF.
    ENDLOOP.
    ENDFORM. " f_do_transaction
    *& Form bdc_dynpro
    For appending screen details to BDCDATA
    FORM bdc_dynpro USING program dynpro.
    CLEAR i_bdcdata.
    i_bdcdata-program = program.
    i_bdcdata-dynpro = dynpro.
    i_bdcdata-dynbegin = 'X'.
    APPEND i_bdcdata.
    CLEAR i_bdcdata.
    ENDFORM. "bdc_dynpro
    *& Form bdc_field
    For appending field details to bdcdata table
    FORM bdc_field USING fnam fval.
    CLEAR i_bdcdata.
    i_bdcdata-fnam = fnam.
    i_bdcdata-fval = fval.
    APPEND i_bdcdata.
    CLEAR i_bdcdata.
    ENDFORM. " bdc_field
    *& Form bdc_transaction
    For inserting Transaction in the session
    FORM bdc_transaction USING tcode.
    CALL FUNCTION 'BDC_INSERT'
    EXPORTING
    tcode = tcode
    TABLES
    dynprotab = i_bdcdata.
    ENDFORM. " bdc_transaction
    *& Form F_close_group
    For closing the session created in Session manager SM35
    FORM close_group.
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    concatenate 'Session ' v_session 'successfully created' into v_field.
    MESSAGE v_field type 'I'..
    CALL TRANSACTION 'SM35'.
    ENDFORM. "f_close_group
    *& Form f_give_help
    For user help to select file
    FORM give_help.
    CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
    mask = ',.,..'
    mode = 'O'
    IMPORTING
    filename = p_file
    EXCEPTIONS
    inv_winsys = 1
    no_batch = 2
    selection_cancel = 3
    selection_error = 4
    OTHERS = 5.
    IF sy-subrc <> 0 AND NOT sy-msgty IS INITIAL.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    ENDFORM. " f_give_help
    ---- End of Template -
    3.Go to the transaction SHDB in another session ( you can also give TCODE - OSHDB in transaction code window and hit enter ).
    4.Create you transaction recording in SHDB . Ensure your transaction recording takes care of input values to all the
    fields to which you intend to pass values in the BDC.
    5.Once your recording is done correctly create the program from recording in the SHDB transction . You will find the button to create program in SHDB . Choose the option of creating from file when you proceed through the subsequent steps.
    6. Define data type t_upload and structure wa_upload in the template program with fields of structure 'RECORD' from the program generated using SHDB recording ( replace the field1, field2 and so on as per your requirement). For your understanding you can remove the suffixes to the
    field name but keep the field size unchanged.
    7.Copy the coding existing between 'do' and 'enddo' statement from the generated program . Insert the copied code between the loop and endloop code of form 'Do_transaction '. Replace fields of structure 'RECORD' with respective fields of structure wa_upload.Insert constant values wherever possible in transaction recording.You can also handle customised data conversions here.
    8.Replace 'TCODE' in the template program with the transaction code you intend to process in this BDC.
    9.Please carry out further syntax check and resolve the related issues.
    This program will provide for input help to select upload file from local machine. The file needs to be in Tab delimited format and is assumed to have first row as column headers .
    On successful creation of session you will be prompted with a Information popup giving the name of session ,and will take you to the SM35 transaction to process your session.

  • I downloaded iOS7 but to install I accept the Terms and Conditions. I accepted many times but it doesn't proceed. Stocked.

    I downloaded iOS7 in my iphone4 but to install I need to accept the Terms and Conditions. I accepted many times but it doesn't proceed. Stocked.

    I updated the software on my iphone4 tonight and ran into this same endless loop - "itunes terms & conditions have been changed" - go to itunes, aceept - back to the "T&C have been changed message" with no ability to do anything in the app store until I accepted the new terms.
    While not a very direct solution, I was able to finally accept the terms in a way that seem to register with apple by making a purchase through iTunes on my computer. This forced me through updating my payment information and updating my iTunes software to the latest edition (which I had not yet taken the time to do).  After doing both of these, iTunes took me through the terms & conditions on two separate pages, but ultimately allowed me to purchase my song.  Once I completed these steps, it fixed the problem on my phone, so now I can update my apps and download new ones without running into that loop.
    Hope this helps!!!

  • ITunes won't open on my windows laptop, and it doesn't give any error message, help!

    iTunes store won't open on my windows laptop, no error message given

    Refer to this article to delete SC files:
    iTunes for Windows: Doesn't open after upgrading in Windows Vista or Windows 7
    http://support.apple.com/kb/TS2363
    Then proceed to repair your QuickTime:
    Control Panel  > Programs n Features > highlight Quicktime, click CHANGE then REPAIR

  • [SOLVED] Xorg doesn't start after upgrade to 1.17.1

    Archlinux i686
    Intel Core 2 Duo 6600
    01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] (rev a1)
    After following upgrades:
    [2015-02-26 03:27] [PACMAN] Running 'pacman -S mesa mesa-demos mesa-libgl'
    [2015-02-26 03:27] [ALPM] transaction started
    [2015-02-26 03:28] [ALPM] upgraded mesa (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-libgl (10.4.2-1 -> 10.4.5-1)
    [2015-02-26 03:28] [ALPM] upgraded mesa-demos (8.2.0-3 -> 8.2.0-4)
    [2015-02-26 03:28] [ALPM] transaction completed
    [2015-02-26 03:28] [PACMAN] Running 'pacman -S xorg-server xorg-server-common'
    [2015-02-26 03:29] [ALPM] transaction started
    [2015-02-26 03:29] [ALPM] removed xf86-video-vesa (2.3.2-5)
    [2015-02-26 03:29] [ALPM] removed xf86-video-nouveau (1.0.11-2)
    [2015-02-26 03:29] [ALPM] removed xf86-video-modesetting (0.9.0-2)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server-common (1.16.3-2 -> 1.17.1-3)
    [2015-02-26 03:29] [ALPM] upgraded xorg-server (1.16.3-2 -> 1.17.1-3)
    Xorg doesn't start after reboot and I found following kernel message:
    kernel: [drm:drm_mmap_locked] *ERROR* Could not find map
    and /var/log/Xorg.0.log looks like this:
    [ 5.591]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 5.591] X Protocol Version 11, Revision 0
    [ 5.591] Build Operating System: Linux 3.18.6-1-ARCH i686
    [ 5.591] Current Operating System: Linux emeria7 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:59:29 CET 2015 i686
    [ 5.591] Kernel command line: root=/dev/disk/by-label/archroot rw
    [ 5.591] Build Date: 22 February 2015 12:52:47PM
    [ 5.591]
    [ 5.592] Current version of pixman: 0.32.6
    [ 5.592] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 5.592] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 5.592] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 26 14:58:35 2015
    [ 5.597] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 5.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 5.598] (==) ServerLayout "ServerLayout0"
    [ 5.598] (==) No screen section available. Using defaults.
    [ 5.598] (**) |-->Screen "Default Screen Section" (0)
    [ 5.598] (**) | |-->Monitor "<default monitor>"
    [ 5.599] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 5.599] (**) | |-->Device "Device0"
    [ 5.599] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 5.599] (**) Option "BlankTime" "0"
    [ 5.599] (**) Option "StandbyTime" "0"
    [ 5.599] (**) Option "SuspendTime" "0"
    [ 5.599] (**) Option "OffTime" "0"
    [ 5.599] (==) Automatically adding devices
    [ 5.599] (==) Automatically enabling devices
    [ 5.599] (==) Automatically adding GPU devices
    [ 5.608] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 5.608] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 5.608] (**) Extension "Composite" is disabled
    [ 5.608] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 5.608] (II) Loader magic: 0x829e700
    [ 5.608] (II) Module ABI versions:
    [ 5.608] X.Org ANSI C Emulation: 0.4
    [ 5.608] X.Org Video Driver: 19.0
    [ 5.608] X.Org XInput driver : 21.0
    [ 5.608] X.Org Server Extension : 9.0
    [ 5.611] (EE) systemd-logind: failed to get session: PID 995 does not belong to any known session
    [ 5.611] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 5.612] (--) PCI:*(0:1:0:0) 10de:0291:107d:2a62 rev 161, Mem @ 0xfd000000/16777216, 0xc0000000/268435456, 0xfc000000/16777216, I/O @ 0x0000ac00/128, BIOS @ 0x????????/131072
    [ 5.612] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 5.613] (II) LoadModule: "glx"
    [ 5.616] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.632] (II) Module glx: vendor="X.Org Foundation"
    [ 5.632] compiled for 1.17.1, module version = 1.0.0
    [ 5.632] ABI class: X.Org Server Extension, version 9.0
    [ 5.632] (==) AIGLX enabled
    [ 5.632] (==) Matched nouveau as autoconfigured driver 0
    [ 5.632] (==) Matched nv as autoconfigured driver 1
    [ 5.632] (==) Matched nouveau as autoconfigured driver 2
    [ 5.632] (==) Matched nv as autoconfigured driver 3
    [ 5.632] (==) Matched modesetting as autoconfigured driver 4
    [ 5.632] (==) Matched fbdev as autoconfigured driver 5
    [ 5.632] (==) Matched vesa as autoconfigured driver 6
    [ 5.632] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.632] (II) LoadModule: "nouveau"
    [ 5.632] (WW) Warning, couldn't open module nouveau
    [ 5.632] (II) UnloadModule: "nouveau"
    [ 5.632] (II) Unloading nouveau
    [ 5.632] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "nv"
    [ 5.633] (WW) Warning, couldn't open module nv
    [ 5.633] (II) UnloadModule: "nv"
    [ 5.633] (II) Unloading nv
    [ 5.633] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 5.633] (II) LoadModule: "modesetting"
    [ 5.633] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 5.634] (II) Module modesetting: vendor="X.Org Foundation"
    [ 5.634] compiled for 1.17.1, module version = 1.17.1
    [ 5.634] Module class: X.Org Video Driver
    [ 5.634] ABI class: X.Org Video Driver, version 19.0
    [ 5.634] (II) LoadModule: "fbdev"
    [ 5.634] (WW) Warning, couldn't open module fbdev
    [ 5.634] (II) UnloadModule: "fbdev"
    [ 5.634] (II) Unloading fbdev
    [ 5.634] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 5.634] (II) LoadModule: "vesa"
    [ 5.634] (WW) Warning, couldn't open module vesa
    [ 5.634] (II) UnloadModule: "vesa"
    [ 5.634] (II) Unloading vesa
    [ 5.634] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 5.634] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 5.634] (++) using VT number 7
    [ 5.635] (II) modeset(0): using drv /dev/dri/card0
    [ 5.635] (II) modeset(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.636] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
    [ 5.636] (==) modeset(0): RGB weight 888
    [ 5.636] (==) modeset(0): Default visual is TrueColor
    [ 5.636] (II) Loading sub module "glamoregl"
    [ 5.636] (II) LoadModule: "glamoregl"
    [ 5.636] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 5.647] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 5.647] compiled for 1.17.1, module version = 1.0.0
    [ 5.647] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.647] (II) glamor: OpenGL accelerated X.org driver based.
    [ 5.772] (II) glamor: EGL version 1.4 (DRI2):
    [ 5.786] (II) modeset(0): glamor initialized
    [ 5.786] (II) Loading sub module "dri2"
    [ 5.786] (II) LoadModule: "dri2"
    [ 5.786] (II) Module "dri2" already built-in
    [ 5.843] (II) modeset(0): Output DVI-0 has no monitor section
    [ 5.896] (II) modeset(0): Output DVI-1 has no monitor section
    [ 5.950] (II) modeset(0): Output TV-0 has no monitor section
    [ 6.006] (II) modeset(0): EDID for output DVI-0
    [ 6.006] (II) modeset(0): Manufacturer: SAM Model: 76f Serial#: 1110590261
    [ 6.006] (II) modeset(0): Year: 2011 Week: 8
    [ 6.006] (II) modeset(0): EDID Version: 1.3
    [ 6.006] (II) modeset(0): Digital Display Input
    [ 6.006] (II) modeset(0): Max Image Size [cm]: horiz.: 51 vert.: 29
    [ 6.006] (II) modeset(0): Gamma: 2.20
    [ 6.006] (II) modeset(0): DPMS capabilities: Off
    [ 6.006] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 6.006] (II) modeset(0): First detailed timing is preferred mode
    [ 6.006] (II) modeset(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    [ 6.006] (II) modeset(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    [ 6.006] (II) modeset(0): Supported established timings:
    [ 6.006] (II) modeset(0): 720x400@70Hz
    [ 6.006] (II) modeset(0): 640x480@60Hz
    [ 6.006] (II) modeset(0): 640x480@67Hz
    [ 6.006] (II) modeset(0): 640x480@72Hz
    [ 6.006] (II) modeset(0): 640x480@75Hz
    [ 6.006] (II) modeset(0): 800x600@56Hz
    [ 6.006] (II) modeset(0): 800x600@60Hz
    [ 6.006] (II) modeset(0): 800x600@72Hz
    [ 6.006] (II) modeset(0): 800x600@75Hz
    [ 6.006] (II) modeset(0): 832x624@75Hz
    [ 6.006] (II) modeset(0): 1024x768@60Hz
    [ 6.006] (II) modeset(0): 1024x768@70Hz
    [ 6.006] (II) modeset(0): 1024x768@75Hz
    [ 6.006] (II) modeset(0): 1280x1024@75Hz
    [ 6.006] (II) modeset(0): 1152x864@75Hz
    [ 6.006] (II) modeset(0): Manufacturer's mask: 0
    [ 6.006] (II) modeset(0): Supported standard timings:
    [ 6.006] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 6.006] (II) modeset(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 6.006] (II) modeset(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 6.006] (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 6.006] (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 6.006] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 6.007] (II) modeset(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 6.007] (II) modeset(0): #7: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 148.5 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Ranges: V min: 50 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 175 MHz
    [ 6.007] (II) modeset(0): Monitor name: SMBX2331
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
    [ 6.007] (II) modeset(0): Supported detailed timing:
    [ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
    [ 6.007] (II) modeset(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 6.007] (II) modeset(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 6.007] (II) modeset(0): Number of EDID sections to follow: 1
    [ 6.007] (II) modeset(0): EDID (in hex):
    [ 6.007] (II) modeset(0): 00ffffffffffff004c2d6f0735433242
    [ 6.007] (II) modeset(0): 0815010380331d782aee91a3544c9926
    [ 6.007] (II) modeset(0): 0f5054bfef80714f8100814081809500
    [ 6.007] (II) modeset(0): 950fa940b300023a801871382d40582c
    [ 6.007] (II) modeset(0): 4500fd1e1100001e011d007251d01e20
    [ 6.007] (II) modeset(0): 6e285500fd1e1100001e000000fd0032
    [ 6.007] (II) modeset(0): 4b1f5111000a202020202020000000fc
    [ 6.007] (II) modeset(0): 00534d4258323333310a2020202001ee
    [ 6.007] (II) modeset(0): 02031cf14890041f0514131203230907
    [ 6.007] (II) modeset(0): 078301000066030c00100080011d80d0
    [ 6.007] (II) modeset(0): 721c1620102c2580fd1e1100009e011d
    [ 6.007] (II) modeset(0): 8018711c1620582c2500fd1e1100009e
    [ 6.007] (II) modeset(0): 011d00bc52d01e20b8285540fd1e1100
    [ 6.007] (II) modeset(0): 001e8c0ad090204031200c405500fd1e
    [ 6.007] (II) modeset(0): 110000188c0ad08a20e02d10103e9600
    [ 6.007] (II) modeset(0): fd1e110000180000000000000000004c
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
    [ 6.007] (II) modeset(0): Printing probed modes for output DVI-0
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 170.24 1024 1108 1220 1416 768 768 770 801 doublescan -hsync +vsync (120.2 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz d)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 6.008] (II) modeset(0): Modeline "960x720"x75.0 148.50 960 1032 1144 1320 720 720 722 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "960x720"x60.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x75.0 144.00 928 992 1104 1280 696 696 698 750 doublescan -hsync +vsync (112.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz d)
    [ 6.008] (II) modeset(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 101.25 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (93.8 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x70.0 94.50 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (87.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x65.0 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (81.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 6.008] (II) modeset(0): Modeline "700x525"x74.8 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (81.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 6.008] (II) modeset(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
    [ 6.008] (II) modeset(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz d)
    [ 6.008] (II) modeset(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
    [ 6.063] (II) modeset(0): EDID for output DVI-1
    [ 6.116] (II) modeset(0): EDID for output TV-0
    [ 6.116] (II) modeset(0): Output DVI-0 connected
    [ 6.116] (II) modeset(0): Output DVI-1 disconnected
    [ 6.116] (II) modeset(0): Output TV-0 disconnected
    [ 6.116] (II) modeset(0): Using exact sizes for initial modes
    [ 6.116] (II) modeset(0): Output DVI-0 using initial mode 1920x1080
    [ 6.116] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 6.116] (==) modeset(0): DPI set to (96, 96)
    [ 6.116] (II) Loading sub module "fb"
    [ 6.116] (II) LoadModule: "fb"
    [ 6.117] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 6.118] (II) Module fb: vendor="X.Org Foundation"
    [ 6.118] compiled for 1.17.1, module version = 1.0.0
    [ 6.118] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 6.118] (==) Depth 24 pixmap format is 32 bpp
    [ 6.462] (==) modeset(0): Backing store disabled
    [ 6.462] (==) modeset(0): Silken mouse enabled
    [ 6.464] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 6.535] (==) modeset(0): DPMS enabled
    [ 6.535] (WW) modeset(0): Option "EXANoComposite" is not used
    [ 6.535] (II) modeset(0): [DRI2] Setup complete
    [ 6.535] (II) modeset(0): [DRI2] DRI driver: nouveau
    [ 6.535] (II) modeset(0): [DRI2] VDPAU driver: nouveau
    [ 6.535] (--) RandR disabled
    [ 6.551] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context
    [ 6.551] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 6.551] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 6.551] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 6.551] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 6.551] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 6.551] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 6.551] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 6.552] (II) AIGLX: Loaded and initialized nouveau
    [ 6.552] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 6.559] (II) modeset(0): Setting screen physical size to 507 x 285
    [ 6.741] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 6.741] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.741] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.741] (II) LoadModule: "evdev"
    [ 6.741] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.744] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.744] compiled for 1.16.2, module version = 2.9.1
    [ 6.744] Module class: X.Org XInput Driver
    [ 6.744] ABI class: X.Org XInput driver, version 21.0
    [ 6.744] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.744] (**) Power Button: always reports core events
    [ 6.744] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 6.744] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.744] (--) evdev: Power Button: Found keys
    [ 6.744] (II) evdev: Power Button: Configuring as keyboard
    [ 6.744] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.744] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.744] (**) Option "xkb_rules" "evdev"
    [ 6.744] (**) Option "xkb_model" "pc104"
    [ 6.744] (**) Option "xkb_layout" "us"
    [ 6.744] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.780] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 6.780] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.780] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.780] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.780] (**) Power Button: always reports core events
    [ 6.780] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 6.780] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.780] (--) evdev: Power Button: Found keys
    [ 6.780] (II) evdev: Power Button: Configuring as keyboard
    [ 6.780] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
    [ 6.780] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 6.780] (**) Option "xkb_rules" "evdev"
    [ 6.780] (**) Option "xkb_model" "pc104"
    [ 6.780] (**) Option "xkb_layout" "us"
    [ 6.780] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.781] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 6.781] (II) No input driver specified, ignoring this device.
    [ 6.781] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event10)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.782] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
    [ 6.782] (II) No input driver specified, ignoring this device.
    [ 6.782] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event7)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event8)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.783] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event9)
    [ 6.783] (II) No input driver specified, ignoring this device.
    [ 6.783] (II) This device may have been added with another device file.
    [ 6.784] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 6.784] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc050
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
    [ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 6.784] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/0003:046D:C050.0001/input/input1/event1"
    [ 6.784] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 8)
    [ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [ 6.785] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 6.785] (II) No input driver specified, ignoring this device.
    [ 6.785] (II) This device may have been added with another device file.
    [ 6.785] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
    [ 6.785] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 6.785] (**) AT Translated Set 2 keyboard: always reports core events
    [ 6.785] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 6.785] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 6.785] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 6.785] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 6.785] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 6.785] (**) Option "xkb_rules" "evdev"
    [ 6.785] (**) Option "xkb_model" "pc104"
    [ 6.785] (**) Option "xkb_layout" "us"
    [ 6.785] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [ 6.803] (EE)
    [ 6.803] (EE) Backtrace:
    [ 6.803] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x132) [0x81df9e2]
    [ 6.804] (EE) 1: ? (?+0x132) [0xb7787cc5]
    [ 6.804] (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x4cd7) [0xb6e2a1c7]
    [ 6.806] (EE) 3: /usr/lib/xorg-server/Xorg (xf86_show_cursors+0x688) [0x80f9008]
    [ 6.806] (EE) 4: /usr/lib/xorg-server/Xorg (xf86DestroyCursorInfoRec+0xcf8) [0x8103fc8]
    [ 6.806] (EE) 5: /usr/lib/xorg-server/Xorg (RamDacHandleColormaps+0x67b) [0x810218b]
    [ 6.807] (EE) 6: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x25d) [0x81c648d]
    [ 6.808] (EE) 7: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x4c1) [0x81c6b31]
    [ 6.808] (EE) 8: /usr/lib/xorg-server/Xorg (CompositeRegisterImplicitRedirectionException+0x4199) [0x8114399]
    [ 6.809] (EE) 9: /usr/lib/xorg-server/Xorg (PanoramiXRenderReset+0x72a) [0x815915a]
    [ 6.810] (EE) 10: /usr/lib/xorg-server/Xorg (ConfineToShape+0x9f1) [0x80843b1]
    [ 6.810] (EE) 11: /usr/lib/xorg-server/Xorg (WindowHasNewCursor+0x3b) [0x8084f2b]
    [ 6.810] (EE) 12: /usr/lib/xorg-server/Xorg (ChangeWindowAttributes+0xb7c) [0x80aa9ec]
    [ 6.811] (EE) 13: /usr/lib/xorg-server/Xorg (ProcBadRequest+0x209) [0x8074a49]
    [ 6.811] (EE) 14: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x3a6) [0x807abf6]
    [ 6.811] (EE) 15: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x42f) [0x807edaf]
    [ 6.811] (EE) 16: /usr/lib/xorg-server/Xorg (miPolyFillRect+0x27f) [0x8068ddf]
    [ 6.814] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xde) [0xb72d864e]
    [ 6.814] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x21) [0x8068bd9]
    [ 6.814] (EE)
    [ 6.814] (EE) Segmentation fault at address 0x0
    [ 6.814] (EE)
    Fatal server error:
    [ 6.814] (EE) Caught signal 11 (Segmentation fault). Server aborting
    [ 6.814] (EE)
    [ 6.814] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 6.814] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 6.814] (EE)
    [ 6.815] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 6.817] (EE) Server terminated with error (1). Closing log file.
    Note the segfault in modesetting_drv.so!
    Any help?
    I tried to reinstall dependencies of xorg-server and mesa. And then I even went through with the whole system update which I postponed for a few weeks because of the KDE changes. Sadly even the whole system update didn't help.
    Is it possible that any old config files can cause this?
    EDIT:
    I tried kernel parameter "nouveau.modeset=0" but it didn't help.
    Last edited by cro (2015-02-26 16:33:19)

    Ok, I guess I solved it by reinstalling xf86-video-nouveau.
    Funny business! Why did the upgrade to xorg-server 1.17.1 force me to remove it when it is still needed??
    And why does that lead to mysterious error messages and segfault??
    I discovered it accidentally when I stumbled upon the fact that the package was still installed on my newer x86-64 Arch installation despite being on xorg-server 1.17.1.

  • [Solved] Network doesn't work after hibernate?

    Hello!  This is my first legit Linux install so excuse me if I'm a bit slow.  I installed Arch last night and everything went smoothly.  However, after I tested out hibernate on my machine, the network doesn't seem to work.  Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
    I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver.  Running "dmesg | grep e1000e" says that it is up.
    I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd.  I am using wicd so I did the following (or at least I think I am only using wicd):
    #rc.d stop network
    #rc.d stop dhcpcd
    #rc.d stop networkmanager
    Similarly, I put a ! in front of network in rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=()
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Vicious"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface=eth0
    address=
    netmask=
    broadcast=
    gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
    Restarting eth0 through wicd-cli still did not work.  I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
    I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work.  Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved?  But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work.  As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
    mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is.  Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
    fstab.conf:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
    /dev/sda1 / ext4 defaults,noatime,discard 0 1
    /dev/sda2 /home ext4 defaults,noatime,discard 0 2
    /dev/sdc1 /boot ext4 defaults 0 1
    /dev/sdc2 /var ext4 defaults 0 0
    /dev/sdc3 swap swap defaults 0 0
    /dev/sdc4 /media/data ext4 defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
    Is wicd causing these problems or did I configure something else improperly?  Would appreciate any help to get eth0 up again!
    Last edited by TheBigCow7 (2011-09-13 17:57:20)

    Ok, I think I've made some progress!  Hibernate definitely affects my network connection.  Could this be a kernel 3.0 problem?
    I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time.  e1000e seemed to be loading up ok.  I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
    Trying to use dhcpcd like the instructions here did not work.  By some chance, one attempt did work and while it did, I downloaded and installed dhclient.  After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
    Luckily though, I found that running "dhclient eth0" worked.  My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot.  Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
    Now, eth0 works after a boot.  However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before).  I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
    I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings). 
    Is this the correct/most efficient way to fix my DHCP problem?  Can I fix my "eth0 after hibernate" issue?  Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

Maybe you are looking for

  • HR-PA-Changes IT0000 & IT0001

    I have to changed wrong maintain IT0000 & IT0001 far away from earliest retro active allowed in SAP. For Exampe : Earliest Retro is on January 2005 Data in IT0001 as below: 01/01/1980 - 12/31/1990 as Position A. Data should be changed as below: 01/01

  • Unable to launch PS CC Mac OSX 10.9

    I have installed PS CC on 2 Max's with the same result on both The splash screen shows, the app opens for a couple of seconds then closes There is no error reported and I can not find an issue in a log. I have followed a multitude of information on d

  • NEF files - can't open in Bridge or PS CS3 but can see in camera

    Not sure if I'm in the right forum...first time here. I'm shooting the floods in Brisbane, Australia today and have been shooting with a Nikon D200 and with a Nikon D3. I have transferred the NEF files from the D200 easily (as I normally do) to Bridg

  • Cumulative Quantities in a BEx Query

    Hi Friends, I have to get the Cumulative Values for a Key Fig Actual Quantity in a BEx Query. The scenario is as follows: I have the following data in the cube: YearWeek       ActQuantity   200601                     35   200602                     4

  • Data table with fixed column with

    I have a data table bound to a row set , and I would like the table to have fixed column widths to avoid unpleasant display shifts when paging through it. The column component does not have too many properties I can work with (maybe this can be fixed