This one time, at band camp, Mary Gardiner wrote: >The initrd on a superficial check looked OK (ie, it's a mountable >filesystem, it has /dev). I can't answer the question about whether it >has the correct driver for my filesystem because Google and my offlist >correspondent both indicate that the drivers for SATA controllers all >changed names between 2.6.7 and 2.6.8 and hence I have very little idea >of what the correct driver actually calls itself. (This is in addition >to suddenly all becoming treated as SCSI devices.)
Ah :( >If the install process really is building only current modules into the >initrd, then that may explain the problem. If so though, I'm absolutely >stuck for solving it, short of building an initrd by hand. At the moment >I'm reasonably sure that it is *not* loading the correct driver, because >the boot sequence goes: OK, in that case your best bet is to fix the initrd by hand, which may be as easy as unzipping the image, mounting it, copying in the missing modules, and editing linuxrc, and as hard as mounting the image, copying everything somewhere else because the cramfs isn't writable, adding the modules, working out how the module loading works because linuxrc is a binary executable, and repacking the lot into a new cramfs. Hopefully it's closer to the former than the latter. My only advice is keep all your initrds in /boot until you have one that works, otherwise it'll really start to suck. I found grub was excellent for mucking around with bootloaders in this way, because I could just change the initrd at boot time without being worried about breaking the bootloader too. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
