Fedora Account System
Red Hat Associate
Red Hat Customer
When I start my laptop for the first time, I see a black screen on plymouth's LUKS password screen. I can blindly type the password and get the loading screen to show for plymouth and then my user login screen. If I restart, I see the luks password screen just fine. I do have an NVIDIA Optimus graphics laptop, but I have uninstalled the NVIDIA driver and disabled nouveau to only depend on i915 and no luck. alex@razerblade15:~$ sudo journalctl -b 0 | grep -ie "drm\|i915\|plymouth" | grep 15: Oct 16 15:07:40 razerblade15 kernel: ACPI: bus type drm_connector registered Oct 16 15:07:40 razerblade15 kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic Oct 16 15:07:40 razerblade15 kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0 Oct 16 15:07:40 razerblade15 kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device Oct 16 15:07:41 razerblade15 systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen... Oct 16 15:07:41 razerblade15 systemd[1]: Received SIGRTMIN+20 from PID 538 (plymouthd). Oct 16 15:07:41 razerblade15 systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen. Oct 16 15:07:41 razerblade15 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid). Oct 16 15:07:41 razerblade15 systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch. Oct 16 15:07:41 razerblade15 systemd[1]: Started systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth. Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] Found alderlake_p (device ID 46a6) integrated display version 13.00 stepping D0 Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4 Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] Skipping intel_backlight registration Oct 16 15:07:42 razerblade15 kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 Oct 16 15:07:42 razerblade15 kernel: fbcon: i915drmfb (fb0) is primary device Oct 16 15:07:42 razerblade15 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Oct 16 15:07:50 razerblade15 systemd[1]: Starting plymouth-switch-root.service - Plymouth switch root service... Oct 16 15:07:50 razerblade15 systemd[1]: Finished plymouth-switch-root.service - Plymouth switch root service. Graphics: Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Razer USA driver: i915 v: kernel arch: Xe ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:46a6 class-ID: 0300 Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Razer USA driver: N/A arch: Ampere pcie: speed: 16 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300 Device-3: IMC Networks Integrated RGB Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-2:2 chip-ID: 13d3:5279 class-ID: 0e02 serial: 01.00.00 Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8 compositor: gnome-shell v: 48.5 driver: dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 4096x2304 s-dpi: 96 s-size: 1084x610mm (42.68x24.02") s-diag: 1244mm (48.97") Monitor-1: eDP-1 model: Sharp LQ156T1JW03 res: mode: 4096x2304 hz: 240 scale: 100% (1) dpi: 306 size: 340x190mm (13.39x7.48") diag: 395mm (15.5") modes: 2560x1440 API: OpenGL v: 4.6 vendor: intel mesa v: 25.1.9 glx-v: 1.4 es-v: 3.2 direct-render: yes renderer: Mesa Intel Iris Xe Graphics (ADL GT2) device-ID: 8086:46a6 API: EGL Message: EGL data requires eglinfo. Check --recommends. Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr Reproducible: Always Steps to Reproduce: 1. Shut down Laptop 2. Start PC 3. Wait til LUKS prompt Actual Results: Black screen at LUKS prompt Expected Results: I should see the LUKS prompt
Hi, it seems to be dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2455924#c13 Could you please check the suggestion in comment https://bugzilla.redhat.com/show_bug.cgi?id=2455924#c13 regarding the missing LUKS display? If that doesn't help, do you have any other experimental steps in mind to help us diagnose the blank screen during the password prompt? Thanks for your help!
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-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 '42'. 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 42 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 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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.