Description of problem: when a new kernel is installed grub2-mkconfig runs too early and the resulting config doesnt have the initrd in it causeing the machine to not boot. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: menuentry "GNU/Linux, with Linux 2.6.35.6-45.fc14.x86_64" --class gnu-linux --class gnu --class os { set gfxpayload=keep insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set 19572112-8049-4742-a295-9bf307f63fd2 echo Loading Linux 2.6.35.6-45.fc14.x86_64 ... linux /vmlinuz-2.6.35.6-45.fc14.x86_64 root=/dev/mapper/vg_athosian-lv_root ro quiet rhgb } Expected results: menuentry "GNU/Linux, with Linux 2.6.35.6-45.fc14.x86_64" --class gnu-linux --class gnu --class os { set gfxpayload=keep insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set 19572112-8049-4742-a295-9bf307f63fd2 echo Loading Linux 2.6.35.6-45.fc14.x86_64 ... linux /vmlinuz-2.6.35.6-45.fc14.x86_64 root=/dev/mapper/vg_athosian-lv_root ro quiet rhgb echo Loading initial ramdisk ... initrd /initramfs-2.6.35.6-45.fc14.x86_64.img } Additional info:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** This bug has been marked as a duplicate of bug 725185 ***