Kernel 2.4.23 compiling error

vincebs · 12-13-2003, 02:27 AM

Hello all,

Can anyone help me fix this compiling problem? I first tried compiling 2.6.0-test10 but apparently that failed as I kept getting unresolved symbols errors.

So I decided to compile 2.4.23 instead. All was well until I rebooted and got this error:

Code:

VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00

Hmm, I must have accidentally compiled by ext3 filesystem as a module, I thought. But upon make xconfig 'ing again, I realized that it was already set to be compiled into the kernel. Just in case, I also selected ext2 to be compiled into the kernel as well. Then I deleted the 2.4.23 files in /boot and in /lib/modules and re-compiled. And rebooted. But it still did not work. Same error.

I checked my grub.conf file:

Code:

default=2
timeout=4
splashimage=...

title Red Hat Linux (2.4.23)
        root (hd0,1)
        kernel /vmlinuz-2.4.23 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.23.img
title Red Hat Linux (2.4.20-8)
        root (hd0,1)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.20-8.img
...

The second option seems to boot just fine. But not the first one.

Could it have anything to do with the hdd=ide-scsi option? Although I don't have a SCSI hard disk, would it still matter? I only compiled generic SCSI support in my new kernel configuration.

jailbait · 12-13-2003, 11:05 AM

"Could it have anything to do with the hdd=ide-scsi option? Although I don't have a SCSI hard disk, would it still matter? I only compiled generic SCSI support in my new kernel configuration."

If you specify hdd=ide-scsi then you need ide-scsi in your kernel. However I do not think that is the boot error. You can fix it by taking hdd=ide-scsi out of your grub kernel 2.4.23 line.

"VFS: Cannot open root device "LABEL=/" or 00:00"

You may not have compiled LVM support in your kernel. Try changing :
kernel /vmlinuz-2.4.23 ro root=LABEL=/ hdd=ide-scsi
to
kernel /vmlinuz-2.4.23 ro root=/dev/hdxy
where /dev/hdxy is the partition where your root partition is located.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

vincebs · 12-13-2003, 04:03 PM

Thanks, that worked! Will I lose any functionality by not loading LVM?

Now, I have another problem: It's not loading my modules!

I think it may have something to do with me messing up my modprobe file a while ago. I updated module-init-tools without using the "make moveold" command. Now whenever I run modprobe I get this error:
Kernel requires old modprobe, but couldn't run modprobe.old: No such file or directory

Is this the source of my woes:

Code:

Dec 13 16:46:54 CPE00207805d97a-CM000a7369e75e ifup: Determining IP information
for eth0...
Dec 13 16:46:56 CPE00207805d97a-CM000a7369e75e dhclient: socket: Protocol not available - make sure <27>Dec 13 16:46:56 dhclient: CONFIG_PACKET (Packet socket)
and CONFIG_FILTER
Dec 13 16:46:58 CPE00207805d97a-CM000a7369e75e crond: crond startup succeeded
Dec 13 16:46:58 CPE00207805d97a-CM000a7369e75e xfs: xfs startup succeeded
Dec 13 16:46:59 CPE00207805d97a-CM000a7369e75e anacron: anacron startup succeeded
Dec 13 16:46:59 CPE00207805d97a-CM000a7369e75e rhnsd[1087]: Red Hat Network Services Daemon starting up.
Dec 13 16:46:59 CPE00207805d97a-CM000a7369e75e rhnsd: rhnsd startup succeeded
Dec 13 16:46:59 CPE00207805d97a-CM000a7369e75e xfs: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
Dec 13 16:47:00 CPE00207805d97a-CM000a7369e75e modprobe: modprobe: Can't locate
module char-major-10-134
Dec 13 16:47:02 CPE00207805d97a-CM000a7369e75e modprobe: modprobe: Can't locate
module char-major-13
Dec 13 16:47:13 CPE00207805d97a-CM000a7369e75e gdm(pam_unix)[1142]: session opened for user root by (uid=0)
Dec 13 16:47:15 CPE00207805d97a-CM000a7369e75e gconfd (root-1219): starting (version 2.2.0), pid 1219 user 'root'
Dec 13 16:47:15 CPE00207805d97a-CM000a7369e75e gconfd (root-1219): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Dec 13 16:47:15 CPE00207805d97a-CM000a7369e75e gconfd (root-1219): Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Dec 13 16:47:15 CPE00207805d97a-CM000a7369e75e gconfd (root-1219): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Dec 13 16:47:19 CPE00207805d97a-CM000a7369e75e modprobe: modprobe: Can't locate
module block-major-11
Dec 13 16:47:20 CPE00207805d97a-CM000a7369e75e modprobe: modprobe: Can't locate
module block-major-11
Dec 13 16:47:20 CPE00207805d97a-CM000a7369e75e kernel: cdrom: This disc doesn't
have any tracks I recognize!

My network card isn't working under the new kernel either despite including the required tulip module.

jailbait · 12-13-2003, 04:59 PM

"Will I lose any functionality by not loading LVM?"

LVM allows you to find a disk by its LABEL. Without LVM you can only find it by its device address, i.e. /dev/hda4. If you have LVM in your kernel compile you should make it y if you want to use it at boot.

"I think it may have something to do with me messing up my modprobe file a while ago. I updated module-init-tools without using the "make moveold" command. Now whenever I run modprobe I get this error:
Kernel requires old modprobe, but couldn't run modprobe.old: No such file or directory"

I think that you need to update /etc/modules.conf. The details for your configuration are beyond me. I always do it by messing around with my old modules.conf until I get the error messages out. Do you have an old /etc/modules.conf available in backup someplace? Or you could try making the problem modules y in your kernel compile. That should solve the problem although you may end up with a bloated bootable kernel.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

vincebs · 12-14-2003, 01:57 AM

Well I can't test it anymore because whenever I run modprobe, I get this error:

Kernel requires old modprobe, but couldn't run modprobe.old: No such file or directory

Plus I don't see anything wrong with my modules.conf:

alias eth0 tulip
alias usb-controller usb-uhci
alias sound-slot-0 es1371
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :