On Sun, 2004-12-05 at 22:31, Mary Gardiner wrote: > 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:
Building a new initrd is usually just a matter of calling mkinitrd(8) with an output file and the kernel version you want to build it for. /usr/sbin/mkinitrd is a bash script, so if it's still broken, maybe tinkering with it to hardwire the kernel module path might be a go. -- Pete -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
