2.4.0 root fs problem

[reeze]

Recently I compiled 2.4.0 for a 486. I've set it up in lilo:

root=/dev/hda1

image=/vmlinuz
label=Linux
read-only
restricted

and then ran lilo. When I try to boot the kernel though I get this error:

Kernel panic: VFS: Unable to mount root fs on 03:01

even if I enter, this at the lilo prompt:
linux root=/dev/hda1

For some reason the kernel thinks the root fs is 301 (???).

rdev /vmlinux ..returns:
root device /dev/hda1

but if I do a:
file /boot/vmlinuz-2.4.0
it returns:

Linux kernel x86 boot .... , root_dev=0x301, ...

oh and I'm running debian, not that, that really matters, thanks for any help you can give me.

-reeze

[sans-hubris]

I have no idea what your problem is, but let me take a crack at it. Make sure that you have the boot map file defined in lilo.conf. Make sure you run lilo. Also make sure that you define where the boot sector is ("install=/boot/boot.b").

[The King Ant]

03:01 is the device ID number of hda1. If you cd to the /dev directory, and then "ls -la | grep -i hda | more", look in the 2 columns after the username/groupname columns. That's the device ID.

Is /vmlinuz a symlink to /boot/vmlinuz-2.4.0?

Are you sure that /dev/hda1 is your linux / partition?

I would double check that you have ext2 support compiled into your new kernel.

Can you post some more of you lilo.conf file? Maybe all of it?

[reeze]

from ndogg

Make sure that you have the boot map file defined in lilo.conf. Make sure you run lilo. Also make sure that you define where the boot sector is ("install=/boot/boot.b").

I have that line in lilo.conf , and I can boot the 2.2.17 kernel, it is only the 2.4.0 kernel that cant find the root fs. I was wondering if I need a different boot sector file for 2.4.0 . There are 3 files in /usr/src/linux/arch/i386/boot/ with names:

bbootsect
bbootsect.o
bbootsect.s

I dont know if one of these are supposed to be moved to /boot/boot.b.


Is /vmlinuz a symlink to /boot/vmlinuz-2.4.0?

what else would it be linked too? /proc/foobar ?

Are you sure that /dev/hda1 is your linux / partition?

well it is when I boot the 2.2.17 kernel, so yes I'm sure.

I would double check that you have ext2 support compiled into your new kernel.

Its there, how would I run linux without ext2 support, umsdos.. lmao

Can you post some more of you lilo.conf file? Maybe all of it?


boot=/dev/hda
root=/dev/hda1

install=/boot/boot.b
map=/boot/map

password=xxxxxxxx

delay=200
default=linux

image=/vmlinux
label=Linux
read-only
restricted

image=/vmlinuz.old
label=linux-2.2.17
read-only



thats it --^

--reeze.

[The King Ant]

Your /boot/boot.b is fine. That file is a part of lilo, and it is usually automatically updated when you run the lilo command.

It really doesn't look like this is a problem with your lilo setup. It looks like there might be something wrong with how your 2.4 kernel is setup that it isn't able to read from that drive.

You should have these things marked as "Y" in the Kernel config file:
ATA/IDE/MFM/RLL support --> IDE, ATA and ATAPI Block devices
--> Enhanced IDE...
--> Include IDE/ATA-2...
--> Generic PCI IDE...
--> Sharing PCI...
--> Generic PCI bus-master...

[reeze]

ok, I had the old drive selected because it is a 486 and has old hardware, but I will try it with the enhanced driver.

It takes about 2 hours to do the full compile....

[reeze]

Thanks for all the help _The King Ant_ .

It was just a matter of selecting the new enhanced drivers over the old ones. This is the first problem I've brought to LNO and it got fixed right away. I like this place.

--reeze.

[The King Ant]

Wooowww, cool. You're quite welcome. Have fun with your new kernel.