Tom Schutter wrote:
You need a line:I am having trouble setting up Debian woody on a IOpener. I am setting up the IDE drive on another machine, and then hooking it up to the IOpener and attempting to boot. When I attempt to boot with the drive in the IOpener, I get: VFS: Cannot open root device "301" or 03:01 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:01I have tried to add root=/dev/hda1 to the boot prompt with no success. I can boot fine to the drive when it is hooked up to my desktop machine. "uname -a" gives: Linux newman 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown lilo.conf looks like this (with comments removed): lba32 boot=/dev/hda root=/dev/hda1 install=/boot/boot-menu.b map=/boot/map delay=20 prompt vga=ask default=Linux image=/vmlinuz label=Linux read-only "fdisk -l" gives: Disk /dev/hda: 128 heads, 63 sectors, 525 cylinders Units = cylinders of 8064 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 484 1951456+ 83 Linux /dev/hda2 485 525 165312 82 Linux swap "lilo -q -v" gives: LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2001 John Coffman Released 05-Feb-2002 and compiled at 20:57:26 on Apr 13 2002. MAX_IMAGES = 27 Reading boot sector from /dev/hda Global settings: Delay before booting: 2.0 seconds No command-line timeout Always enter boot prompt Boot-time BIOS data saved Non-RAID installation Serial line access is disabled No message for boot prompt No default boot command line Images: Linux * No password Boot command-line won't be locked No single-key activation VGA mode: ASK Kernel is loaded "high", at 0x00100000 No initial RAM disk No fallback Options: "ro root=301" Interesting, there is where the "root=301" comes from. But why is it there? What should I specify in lilo.conf?
initrd=/boot/initrd.img-2.4.19-bf2.4
in the image section of your lilo.conf[assuming initrd.img-2.4.19-bf2.4 exists, it should or something very similarly named]. Also, it is my understanding that 2.4.19-bf2.4 is only supposed to be used for installation and you should install a 'real' kernel once you have your system up and running. apt-cache search kernel-image and apt-get install the one that looks appropriate for your system. This is not to say though that this kernel shouldn't work indefinately...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]