On Wed, Dec 01, 2004 at 03:27:56PM +0100, Richard Atterer wrote: > On Wed, Dec 01, 2004 at 03:06:17AM -0800, Steve Langasek wrote: > > On Wed, Dec 01, 2004 at 12:01:29PM +0100, Richard Atterer wrote: > > > Obviously, you cannot load the SATA modules if you need the SATA code to > > > access the hard disc. > > > > Of course you can, that's what initial ramdisks are for. > > Initially, I also thought that, but I have been unable to get things to > work using the standard Debian kernel packages. > > After installing sarge, I uninstalled grub and installed lilo (just a > personal preference). Everything continued to work. > > I then installed kernel-image-2.6.8-1-686 2.6.8-10. (Actually, I tried > kernel-image-2.6.8-1-386 first, replacing the previous, working setup - > doh!) > > After that, a reboot resulted in lilo loading the kernel, the kernel > starting up, but panicking after a short while. I have verified that > lilo.conf is set up correctly, including the right initrd=... setting. > > The error messages output by the kernel are as follows: > > pivot_root: No such file or directory > /sbin/init: Cannot open /dev/console: no such file or directory > Kernel panic: Attempted to kill init!
That sounds like a bug in initrd-tools. SATA modules really do work in initrds; I have a machine set up this way right in front of me, which works out of the box. It would be a regression to jam them back into the kernel monolithic-style (for one, it would probably make it impossible to put the kernel on a floppy). > Do these messages this apply to the /dev inside the initrd?? FWIW, the > machine does not use udev or devfs. Those messages indicate that the init in the initrd can't figure out how to mount your real root partition. Cheers, -- Colin Watson [EMAIL PROTECTED]