Paul Johnson wrote:
On Thu, Nov 20, 2008 at 2:42 PM, Mikkel L. Ellertson
<mikkel@xxxxxxxxxxxxxxxx> wrote:
Paul Johnson wrote:
When the kernel is updated, the Fedora 9 framework will rebuild a new
initrd and it will NOT have the special modules in it. On fedora
systems, I found no simpler solution than to edit the new-kernel
script and change the modules that were assumed. Otherwise, the boot
up will fail just like you have been seeing. On Ubuntu linux, I've
learned that the required modules can be configured in
/etc/modprobe.conf or someplace similar, and the initrd builder takes
notice of it.
...
Sorry if this appears pedantic. I'm a teacher :)
Well, my solution is even more so ...
I got tired of fighting it. My requirements are to build a bootable
disk in a VM and have it run on any i686 based platform. Exceptions are
SAN based ...
In my post install I do this:
# make sure drivers are in the initrd image
kernel=`ls /boot/vmli* | tail -1 | awk -F\- '{printf("%s-%s\n", $2,$3)}'`
initrd="/boot/initrd-${kernel}.img"
rm $initrd
/sbin/mkinitrd --preload=ehci-hcd --preload=ahci --preload=libata
--preload=jbd --preload=ohci-hcd --preload=uhci-hcd
--preload=scsi_wait_scan --preload=usb-storage --preload=scsi_mod
--preload=sd_mod --preload=pata_amd --preload=ata_generic
--preload=pata_cs5536 --preload=pata_acpi $initrd $kernel
THAT will boot. :)
Good Luck!
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
