On Sat, October 15, 2005 11:49 am, rik-Xandros-test said: > Steve Holdoway wrote: > >>... this is all suspend/resume stuff, isn't it? Why not just get up and >>running first? Try just >> >> >>title Xandros Linux 3.0 (starter) >>root (hd0,8) >>kernel /boot/vmlinuz-2.6.9-x1 root=/dev/hda9 ro acpi=off >>initrd /boot/initrd-2.6.9-x1.gz
Just thinking on initrd's, as I only use them on one box... The idea of initrd is that it provides a tempoary root directory with stuff you need to complete the boot. It does this in a ram disk. I suspect this is why it cannot find /root - because a needed filesystem module is in the initrd. so try this (cribbed from my machine that uses initrd) kernel /boot/vmlinuz-2.6.9-x1 root=/dev/ram0 real_root=/dev/hda9 ro acpi=off (thats all one line) As you can probably see that starts the kernel with the ramdisk (/dev/ram0) as root, then later swithes to /dev/hda9 (real_root). Give it a try. >> >> >> > The boot process runs longer now, but stops in much the same way: > >>>Boot error message: >>> >>>sh : error opening /proc/software_suspend/do_resume : No such file or >>>directory >>> >>> > [still.] > > VFS : Cannot open root device "hda9" or unknown-block (0,0) > Please append a correct "root=" boot option > > [then] > >>>Kernel panic - not syncing : VFS : unable to mount root fs on >>>unknown-block (0,0) >>> >>> >>> >>> > Back at install-time (June), I gave up after these.. > >>>GRUB entry lines I have tried before: >>> >>>#root (hd0,8)/dev/hda9 >>>#systemmap /boot/System.map-2.6.9-x1 >>>#kernel /boot/vmlinuz-2.6.9-x1 root=(hd0,8) ro # rw single >>>#kernel (hd0,8)/boot/vmlinuz-2.6.9-x1 root=(hd0,8)/dev/hda9 >>> >>> >>> > Advisor (just left) concluded 'init.rd is not loading'. > >>>I have assumed map (Lilo) & systemmap (Grub) are not quite the same >>>reference, and so have left that out this last run (pending >>>clarification). >>> >>>Thanks for any help, >>>Rik >>> >
