Description of problem: I updated my kernel from 4.19.8 to 4.19.10 and it has broken my system. Rolling back to kernel 4.19.8 seems to resolve the issue. Version-Release number of selected component (if applicable): kernel-4.19.10-200.fc28 How reproducible: Always Steps to Reproduce: 1. Install kernel-4.19.10-200.fc28 2. Reboot 3. Observe blank screen after grub Actual results: The screen is blank after grub, does not ask for the password for LUKS decryption Expected results: Successful boot asks for the password for LUKS decryption Additional info: I am using a LUKS LVM encryption for my root and home partition, while /boot and /boot/efi are not encrypted. The boot appears fails before asking my password to unencrypt my system on 4.19.10. Please let me know if there are any logs I can post to help.
You might be able to get some boot messages by tapping the ESC key while booting. Alternatively, if "rhgb quiet" is on the kernel command-line, you could remove those options from grub. (press "e" and use the down arrow key to scroll to the "linux" line; use the right arrow key to get to the end of the line and then backspace over the options; press "ctrl-x" to boot). And could you attach the output from this command when booted from 4.19.8: $ journalctl -b --no-hostname > journalctl-1.log # review the file for anything you don't want posted
(In reply to Jeremy Newton from comment #0) > 1. Install kernel-4.19.10-200.fc28 > ... while /boot and /boot/efi are not encrypted. If you have an AMD system, you could seeing: Bug 1661024 - 4.19.8-300.fc29.x86_64 -> 4.19.9-300.fc29.x86_64 update results in black screen (missing GPU firmware) If so, update linux-firmware and rebuild the initramfs: # dnf update linux-firmware # dracut --kver 4.19.10-200.fc28 --force Documentation: "man dracut".
I did what you said, but it looks like the problem still exists. It seems the issue is now that the password prompt never comes up. Granted, if I type it and hit enter, it'll boot, but there's no visual feedback. I reproduced the issue with 4.19.12 as well, I'll update the bug name accordingly.
Also note, here's my graphics renderer string: AMD Radeon R7 Graphics (CARRIZO / DRM 3.27.0 / 4.19.12-200.fc28.x86_64, LLVM 6.0.1)
(In reply to Jeremy Newton from comment #3) > I did what you said, but it looks like the problem still exists. It seems > the issue is now that the password prompt never comes up. Granted, if I type > it and hit enter, it'll boot, but there's no visual feedback. > > I reproduced the issue with 4.19.12 as well, I'll update the bug name > accordingly. Thanks for testing and for your followup reports. The black-screen-but-can-login-anyway symptom sounds very similar to what Turgut reports in Bug 1661417, Comment 13. Turgut's workaround is to tap the power button twice (apparently with a small delay between taps). Could you try that? And kernel 4.19.13 is available: bugfix update in Fedora 28 for kernel and kernel-headers https://bodhi.fedoraproject.org/updates/FEDORA-2019-b968817096 Update with: # dnf update kernel --enablerepo=updates-testing --refresh If that doesn't solve the problem, please attach this log file: $ journalctl -b --no-hostname > journalctl-1.log
Can you get a text-mode LUKS passphrase prompt by pressing the ESC key?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Hmm currently 4.19.16-200 works well but always falls back to the text-mode prompt, which I guess works for me. Thanks!
Hello Same issue as described here happens for version: "Linux <hostname> 5.4.13-201.fc31.x86_64 #1 SMP Tue Jan 21 17:21:47 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Is there a way to debug what is happening during reboot (not clean shutdown and boot) of the system? Thank you Best regards Marco Nunes