Thanks for the suggestion. I tried this first in the grub file and had a slightly different result. I tried it in the /etc/fstab as well, but it didn't make any difference. I currently get:
VFS: Cannot open root device "ide/host0/bus0/target0/lun0/part7" or unknown-block (0,0)
Please append a correct "root=" boot option
Kernel Panic VFS: Unable to mount root fs on unknown-block(0,0)
Looks like I'm stuck. The 2.4 kernel doesn't seem to like my broadcom nic, and the 2.6.1 just stubbornly refuses to load.
BTW, I'm running on a Dell Inspiron 8500. I do have gentoo working perfectly on a Dell Inspiron 3800, so I'm not a complete newbie.
--Kurt
Martin Carpella wrote:
Kurt Guenther <[EMAIL PROTECTED]> writes:
Seems straightforward, but my grub.conf has:
title Gentoo (2.6.1-r1) root (hd0,4) kernel (hd0,4)/kernel-2.6.1-gentoo-r1 root=/dev/hda7
and I checked the /etc/fstab and it has
/dev/hda7 / ext3 noatime 0 1
I had a similar error once, I ended up using /dev/ide/host0/bus0/target0/lun0/part1 on that particular machine to get access to my /dev/hda1. Seemed, the symlink was created after the boot, so it was not there for the kernel to find. But I cannot recall if I was using it on the grub kernel-line or in /etc/fstab...
HTH, Martin
-- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
