Fedora Account System
Red Hat Associate
Red Hat Customer
System is a Lenovo W541 with internal Intel Haswell Moble graphics, kernel is 4.0.4-202.fc21.x86_64. During boot nothing is displayed on laptop display nor any attached monitor. But it should display the disk encryption password text input. By appearances the system is immediately hung during boot. However if you go to the alternate text console you'll see the password prompt. Oddly it has 4 characters already filled in (based on the number of asterisks shown after the text prompt). If you backspace over the initial characters and fill in the correct password the system boots and eventually switches to a graphical display.
That does't sound like a kernel problem. It sounds more like something in the initramfs is misconfigured. Do you have any error logs in dmesg or the journal?
I'm not sure it's a kernel issue either but I wasn't sure who is responsible so early in the boot process. I'm attaching the output of dmesg and journalctl, there are some errors and warnings in the logs but since I'm not sure exactly what I'm looking for I don't know if they are relevant or not.
Created attachment 1038123 [details] dmesg log
Created attachment 1038124 [details] journalctl log
(In reply to John Dennis from comment #4) > Created attachment 1038124 [details] > journalctl log Jun 12 09:28:32 localhost.localdomain systemd-cryptsetup[402]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/218325a8-e1a7-4ed5-ad99-022fad01afbb. Does it help, if you add "plymouth.enable=0" to the kernel cmdline?
re comment #5 > Does it help, if you add "plymouth.enable=0" to the kernel cmdline? Somewhat. With plymouth.enable=0 I get a text prompt on the built-in laptop display, there are no initial characters that need to be backspaced. However there is still no GUI and the text prompt does not appear on the primary (attached) display. Prior to receiving my laptop refresh (W541) my old T420s (also running F21) would display the password prompt on both the laptop display and the attached monitor in GUI mode.
reassigning to plymouth
the version of plymouth in fedora is pretty ancient right now and doesn't support optimus hardware very well. you could rd.driver.blacklist=nouveau nouveau.modeset=0 on the kernel command line and see if that fixes things.
Re comment #8 Good news, bad news ... Good news. Using the above boot options successfully caused the GUI disk decryption dialog to display. Bad news. Using the above boot options seems to have screwed up my monitor settings, looks like the timing or some other mode setting is off, the image was offset on the monitor and possibly scaled wrong, it was a little hard to tell. I view this as an experiment, the above boot options fix the GUI dialog can't be used otherwise because once booted the screens are messed up.
FWIW, I discovered the W541 has a Nvidia card in it. The system reports (via the System applet) it's using the internal Intel Haswell graphics. Looking at the x.org journal messages it appears as if it's the intel driver that's being used, but it's not entirely clear to me I'm reading those messages correctly. I presume nouveau is the Nvidia driver (yes/no?). I don't know how it's determined which graphics are going to be used, nor whether what the system applet reports is correct. I only bring this up because I wonder if there is some conflict occurring because of the multiple graphics devices.
Also seen with fresh install of Fedora 23 on W541.
Also affects my new W541 with Fedora 23.
Been seeing this for some time on F23, Thinkpad T440 w/Intel drivers. Happy to provide more debugging info.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.