Hide Forgot
Description of problem: An attempt to load the Fedora 20 via grub2, ends up with a hung bootscreen. The last line in 'dracut' log is something like: "Reached target Basic System." Also, there is an error before, like: "Device 'efifb0' doesn't have function release(). It's broken and must be fixed." Version-Release number of selected component (if applicable): 3.10.11-301 How reproducible: Always, on two different workstations. Steps to Reproduce: 1. Boot PC. 2. Select entry in grub2. 3. Enter the passphrase to unlock encrypted mounts.
I believe you mean 3.11.10-301. Does your grub2 config file have an initrd line listed for this kernel? If so, is the corresponding initramfs file present in /boot and of similar size to the other initramfs files there?
Yes, the initramfs file is here - almost the same size: -rw-------. 1 root root 12M Dec 5 19:27 initramfs-3.11.10-300.fc20.x86_64.img -rw-------. 1 root root 12M Dec 13 10:19 initramfs-3.11.10-301.fc20.x86_64.img Also, I'm suprised, but there is no config in /boot/grub2 - but there is one in /boot/efi/EFI/fedora. It has initrd line for my kernels. I'm a little bit confused about EFI, since I have turned it off in BIOS Setup before doing Fedora fresh install. But the second workstation (I can't access it right now) doesn't have EFI for sure. Also, want to mention, that the previous kernel 3.11.10-300 loads without problems.
The problem has gone with update to kernel-3.12.5-302. Don't know what should I do with this bug now.
Ok. Thanks for letting us know. We'll close it out for now.
The problem has returned with kernels 3.12.7-8 It doesn't even get to the passphrase input screen. The only thing I can think of is a way I've installed these kernels. As non-sudo user: $ yum check-update $ pkcon update $ reboot
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.