Hello, This issue appears on a Dell Precision computer with Quadro P400 (GP107GL) graphics card and the nVidia akmod from rpmfusion. I think this machine first saw Fedora 35 or 34 and it has been upgraded in place since then. I haven't had any problems on other systems with cards of the same family, though not exactly the same. A few months ago, KMS stopped working. Plymouth displayed some ugly graphics I hadn't seen since we first got plymouth in Fedora and the solution was to remove a couple of options from the boot command line. After the root and LUKS options, I used to have: rhgb quiet initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau when I changed that to "rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" and after asking dracut to rebuild everything, things went back to normal. KMS worked and the LUKS password prompt appeared as it should. After upgrading the kernel to 6.9.4-200.fc40, I get a completely black screen and I can tell from the HDD activity LED that the process reaches the point where I need to give the LUKS password. I've done this blindly many times, so there's no surprise there. What is surprising, is that the password does not seem to be input. The keyboard is working, CAPS lock and NUM lock turn on and off and sending a Ctrl+Alt+Del does reboot the computer. There are no boot logs from these attempts, I guess because the disks never get unlocked. If I remove the rhgb quiet options (so booting with only rd.driver.blacklist=nouveau modprobe.blacklist=nouveau) I can see the point where the encrypted partitions have to be mounted, though I am not being asked for a password. The password prompt appears as soon as I start typing. From there on, things work as expected. I also tried adding back the two options I had removed in the past (so rhgb quiet initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau). With these, I only get a message from grub that it's passing things along and I need to rely on the HDD light to tell when I've reached the point where I have to type the password. It is accepted and I get the ugly plymouth graphics until gdm starts. With kernels up to 6.8.12-300.fc40 and with the options "rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" there is no problem. Reproducible: Always
I have just installed kernel-6.9.5-200.fc40 and the problem is still there.
Same with kernel-6.9.6-200.fc40.
I still need to remove "rhgb quiet" in order to input the password with kernel-6.9.7-200.fc40.
Hello, Is this still an issue? Is there a fix? I am currently facing this issue as well on Fedora 40 on kernel versions 6.9.5 and 6.9.4. Here is a link to my post on the Fedora Discussion Forums: https://discussion.fedoraproject.org/t/trouble-getting-a-luks-passphrase-prompt-on-fedora-40-kernel-v6-9-4-during-boot/121653 I also find that removing the 'rhgb quiet' option from the 'linux' command in my /etc/default/grub file will display the prompt in the end after all the system boot messages have been printed. Please note that I have to press ENTER or something else after all the boot messages have been printed to get the prompt. Some people suggest disabling the 'Multi-monitor' option in my BIOS for this to work. First, I do not see such an option on my motherboard's UEFI interface (ASUS TUF B650 Plus WIFI). Second, I'm not sure I want to change a BIOS/UEFI setting just for this. I am not sure what changes in the fedora linux kernel would have caused this issue because I do not have this issue with kernel version 6.8.11-300.fc40.x86_64. I hope there is some documentation/help regarding this.
I ended up changing the "Multi-Display" setting as well, which according to Dell "should have no effect on other operating systems" (other than windows 7 and later). Just switched it back for the fun of testing and with kernel 6.9.9-200.fc40 the issue is still there. Oh, well.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.