Description of problem: After kernel-2.6.27.5-37.fc9 hit F9 updates, initramfs fails on missing loop kmod (builtin now) Version-Release number of selected component (if applicable): kernel-2.6.27.5-37.fc9.x86_64 mkinitrd-6.0.52-2.fc9.x86_64 How reproducible: always with F9 updates-newkey repo Steps to Reproduce: 1. run livecd-creator with a kickstart config which uses repo=updates-released-f9.newkey 2. boot resulting ISO 3. Actual results: initramfs errors out: http://apevec.fedorapeople.org/whereismyloop.png Expected results: livecd finishes boot normally Additional info: upstream mkliveinitrd fix http://git.fedorahosted.org/git/?p=mkinitrd;a=commitdiff;h=859493878a1916b86fecea3892e441e1894ccb10
Ugh -- Chuck, are we really pushing back all the module vs built-in changes to F9? If so, we're going to end up needing to figure out more than just this mkinitrd bit to backport :(
(In reply to comment #1) Right, F9 userspace assumes kmods in few more places: http://apevec.fedorapeople.org/whereismybridge.png
(In reply to comment #2) > (In reply to comment #1) > Right, F9 userspace assumes kmods in few more places: > http://apevec.fedorapeople.org/whereismybridge.png ignore that, it was oVirt Node image minimization which killed net/802
*** Bug 472198 has been marked as a duplicate of this bug. ***
From brief IRC discussion with Chuck, we shouldn't have had the modular->built-in changes in F9. So over to kernel
Changed loop driver back to modular in 2.6.27.6-46. On the missing stp.ko driver: I have one in my install. And the manifest for the RPM shows there's one too. Did you delete it somehow?
(In reply to comment #6) > On the missing stp.ko driver: I have one in my install. And the manifest for > the RPM shows there's one too. Did you delete it somehow? Yeah, see comment #3 - I've fixed our blacklist