Find the answer to your Linux question:
Results 1 to 6 of 6
Hello. I have two internal HDD-s on Linux. The LiveCD will only boot from VESA-mode. One HDD is booting fine. But the second one, gives a boot message, and has ...
  1. #1
    Just Joined!
    Join Date
    Dec 2007
    Posts
    86

    [SOLVED] Boot-Problem with own custom made PC.

    Hello.

    I have two internal HDD-s on Linux.

    The LiveCD will only boot from VESA-mode.

    One HDD is booting fine.
    But the second one, gives a boot message, and has a behavior,same as the LivCD without VESA-modus: Booting stops just before the splashy would come.

    This is what reads:

    "Starting K Display Manager: kdm.

    Press....., for graphical login screen.

    "Name of my PC" login:_
    Password:_

    Last login: .....................on tty1

    "my_user"@"my_Printer": $_

    Linux "my_printer" 2.6.22-1-mepis - smp
    1 SMP PREEMPT"


    Do you have any ideas?...

  2. #2
    Linux Engineer GNU-Fan's Avatar
    Join Date
    Mar 2008
    Posts
    935
    I assume you have run a diagnosis tool for hardware defects on that harddisk, so that we can rule that one out, didn't you?

  3. #3
    Just Joined!
    Join Date
    Dec 2007
    Posts
    86
    Thank you.
    No, I haven't done that check.
    I could do a file consistency check (fsck): If the HDD would be defect, it would state as such.

    But I will first try to give in the command /etc./init.d/kdm, when I get prompted by the console.

    (I was able to change my password, by using passwd: but that did not change anything.)

    /////////////////////////////////////////////
    /////////////////////////////////////


    Comparing the two kdm.log files of both HDD's (sda1 does boot with spashy; sdb1 does not boot with splashy):


    sdb1
    -------------


    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux MuMo6 2.6.22-1-mepis-smp #1 SMP PREEMPT Sun Dec 2 19:15:40 EST 2007 i686
    Build Date: 04 September 2007
    Before reporting problems, check X.Org Wiki - Home
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 12 03:21:21 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (WW) VESA: No matching Device section for instance (BusID PCI:2:0:0) found
    (WW) VESA: No matching Device section for instance (BusID PCI:5:0:0) found
    (EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes { include "xfree86+aliases(qwertz)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+de" };
    xkb_geometry { include "pc(pc105)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+ch" };
    xkb_geometry { include "pc(pc104)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    SetClientVersion: 0 9
    SetGrabKeysState - disabled
    SetGrabKeysState - enabled

    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux MuMo6 2.6.22-1-mepis-smp #1 SMP PREEMPT Sun Dec 2 19:15:40 EST 2007 i686
    Build Date: 04 September 2007
    Before reporting problems, check X.Org Wiki - Home
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 12 06:47:17 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (WW) VESA: No matching Device section for instance (BusID PCI:2:0:0) found
    (WW) VESA: No matching Device section for instance (BusID PCI:5:0:0) found
    (EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes { include "xfree86+aliases(qwertz)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+de" };
    xkb_geometry { include "pc(pc105)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+ch" };
    xkb_geometry { include "pc(pc104)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    find_mesa_visual returned NULL for visualID = 0x0025
    xkb_types { include "&#37;" };
    xkb_compatibility { include "%" };
    xkb_symbols { include "%" };
    xkb_geometry { include "%" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Missing KeyNames section in a Keymap file
    > Description of Keymap not compiled
    Errors from xkbcomp are not fatal to the X server
    (EE) Error loading keymap /var/lib/xkb/server-0.xkm




    --------------------------------------------
    --------------------------------------------

    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux MuMo6 2.6.22-1-mepis-smp #1 SMP PREEMPT Sun Dec 2 19:15:40 EST 2007 i686
    Build Date: 04 September 2007
    Before reporting problems, check X.Org Wiki - Home
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 16 14:39:24 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (EE) Failed to load module "nvidia" (module does not exist, 0)
    (EE) No devices detected.

    Fatal server error:
    no screens found


    ------------------------------------
    --------------------------------
    ---------------------------------------


    sda1
    -----------


    ************************************************** ******************************
    Note that your system uses syslog. All of kdm's internally generated messages
    (i.e., not from libraries and external programs/scripts it uses) go to the
    daemon.* syslog facility; check your syslog configuration to find out to which
    file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
    ************************************************** ******************************


    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux MuMo6 2.6.22-1-mepis-smp #1 SMP PREEMPT Sun Dec 2 19:15:40 EST 2007 i686
    Build Date: 04 September 2007
    Before reporting problems, check X.Org Wiki - Home
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 15 23:49:12 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (WW) VESA: No matching Device section for instance (BusID PCI:1:0:0) found
    (WW) VESA: No matching Device section for instance (BusID PCI:5:0:0) found
    (EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes { include "xfree86+aliases(qwertz)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+de" };
    xkb_geometry { include "pc(pc105)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+ch" };
    xkb_geometry { include "pc(pc104)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    SetClientVersion: 0 9
    SetGrabKeysState - disabled
    SetGrabKeysState - enabled
    (EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes { include "xfree86+aliases(qwertz)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+de" };
    xkb_geometry { include "pc(pc105)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+ch" };
    xkb_geometry { include "pc(pc104)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    (EE) AIGLX: Screen 0 is not DRI capable
    xkb_keycodes { include "xfree86+aliases(qwertz)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+de" };
    xkb_geometry { include "pc(pc105)" };
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server



    ---------------------------------------
    ------------------------------------
    -------------------------------
    ---------------------------

    Final conclusion / problem:


    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Missing KeyNames section in a Keymap file
    > Description of Keymap not compiled
    Errors from xkbcomp are not fatal to the X server
    (EE) Error loading keymap /var/lib/xkb/server-0.xkm


    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 16 14:39:24 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (EE) Failed to load module "nvidia" (module does not exist, 0)
    (EE) No devices detected.

    Fatal server error:
    no screens found




    Final question:

    How solve the problem?

  4. #4
    Just Joined!
    Join Date
    Dec 2007
    Posts
    86
    Please help.

  5. #5
    Linux Engineer GNU-Fan's Avatar
    Join Date
    Mar 2008
    Posts
    935
    The keyboard error is not fatal, meaning it doesn't prevent X11 from coming up. (KDM depends on that.)

    But the missing module for your NVIDIA card is indeed fatal.
    In the /etc/X11/xorg.conf file, change the line
    Code:
    Section "Device"
    ...
            Driver          "nvidia"
    ...
    EndSection
    to
    Code:
    Section "Device"
    ...
            Driver          "nv"
    ...
    EndSection

  6. #6
    Just Joined!
    Join Date
    Dec 2007
    Posts
    86
    Hello and thanks.
    I comparred that file in sda1 and sdb1, and saw that sda1 had "vesa", and that sdb1 had "nvidia", so I decided to copy and paste the "vesa-file", and replace the "nvidia-file".

    Because the "vesa-file" was working, and the "nvidia-file" not: Only common sense...

    I will see, what happens, now.

    So, all devices shall boot via the "vesa"-driver.

    Fingers crossed!


    Edit:

    Hello GNU-Fan

    Thank you sooo... much, for your help!

    sdb1 is booting like a charm. Everything back to normal, and perfect. Big hug for you. Good help, and good hint.

    I notice, that the LiveCD only boots via VESA, and I noticed, that sda1 does, as well, so I concluded, that all discs must boot via VESA. However, it workes, for sdb1, as well, with the VESA-driver.

    Using the relevant error log, and asking for advice in this forum, plus a bit of common sense: That is how I solved my problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...