Find the answer to your Linux question:
Results 1 to 4 of 4
Here is the situation: I just compiled and installed the new kernel - 2.6.2. I added it to the lilo.conf file, and now it loads this kernel by default. When ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2004
    Posts
    9

    Problems with starting the computer with 2.6.2 kernel.


    Here is the situation:

    I just compiled and installed the new kernel - 2.6.2. I added it to the lilo.conf file, and now it loads this kernel by default. When I choose another kernel out of the lilo list, everything works fine. But when the 2.6.2 is chosen, nothing works.

    Here is what happens:

    After lilo, right after the line "Loading 2.6.2................................",
    and just before the PCI probing begins (the hardware probing), everything goes blank!

    I think the computer just suspends. I cannot even turn off the computer in a regular way. I have to take the battery out of my laptop to shut it off!

    What could be making this happen?

    Thanks,
    Vladimir

  2. #2
    Linux Engineer
    Join Date
    Nov 2002
    Location
    Queens, NY
    Posts
    1,319
    I would investigate this problem with dmesg and /var/log/messages. Because you can boot with other kernels, try to use your latest 2.6 kernel. After it freezes, reboot into a working kernel. Then scroll through /var/log/messages and /var/log/dmesg (if you have this file) and see what you find. Most likely, I'm thinking that it's a misconfigured hardware problem.
    The best things in life are free.

  3. #3
    Just Joined!
    Join Date
    Feb 2004
    Posts
    9
    It doesn't even get to that point. There is nothing in that file that specifies the failed bootup.
    The "BREAKLINE" point is w.here I marked the messages file before I rebooted with the 2.6.2 kernel. But, as you see, there are only log entries for the 2.4.20...., the one I loaded after the failed 2.6.2.


    Feb 6 06:53:53 odessa gconfd (vova-3742): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
    Feb 6 09:07:17 odessa su(pam_unix)[4237]: session opened for user root by vova(uid=500) [b]BREAKLINE

    Feb 6 09:10:35 odessa syslogd 1.4.1: restart. Feb 6 09:10:35 odessa syslog: syslogd startup succeeded
    Feb 6 09:10:35 odessa syslog: klogd startup succeeded Feb 6 09:10:35 odessa kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Feb 6 09:10:35 odessa kernel: Linux version 2.4.20-28.9 (bhcompile@porky.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Dec 18 13:45:22 EST 2003
    Feb 6 09:10:35 odessa kernel: BIOS-provided physical RAM map: Feb 6 09:10:35 odessa kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    [/b]

  4. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    That won't work - since the user-level system never started booting, no syslogd was ever started that could log the messages to a file.

    Some questions: Does the screen really go blank, or can you see the last messages? Did you ever try with 2.6.0 or 2.6.1? What did you choose under Bus Options in the kernel config, what power management options did you enable, and not least, did you choose the right CPU type?

Posting Permissions

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