X1 Carbon Gen 13 LUKS Prompt Black Screen
System details
ThinkPad X1 Carbon Gen 13 - i915 - Omarchy 3.2.0
What's wrong?
Installed Omarchy on my ThinkPad X1 Carbon Gen 13. The system runs great, and the i915 driver works perfectly post-boot. However, I get a black screen right at the LUKS password prompt (Plymouth stage). I can blind-type my password and it boots fine, but I can't see the prompt. Using the kernel parameter nomodeset fixes the issue and shows the prompt, but I need Kernel Mode Setting (KMS) enabled for proper graphics performance. How do I get the display working at the LUKS prompt with the i915 driver loaded correctly enabled? Is there a standard Omarchy/Arch configuration step I'm missing to ensure Early KMS Start for Intel graphics on this hardware (e.g., specific mkinitcpio.conf configuration)? Thanks for any help!
I had the same issue a few months back on a vanilla Arch install (same Thinkpad). It started working one day after a kernel upgrade IIRC. You're not using an older kernel by any chance?
I think I'm using xe rather than i915 too. Try switching to that.
Hey @muzzwood
Kernel: 6.17.8-arch1-1
Graphics: Device-1: Intel Arrow Lake-U [Intel Graphics] driver: xe v: kernel Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9 compositor: Hyprland v: 0.52.1 driver: X: loaded: modesetting dri: iris
Tried with xe loaded like this:
KERNEL_CMDLINE[default]+="noquiet i915.force_probe=!7d41 xe.force_probe=7d41"
Same problem. LUKS Auth is ablack screen.
Just to add up:
Tried every possible firmeware update and newest Bios. Stays the same with i915 or xe. Just nomodeset works which then can't be overwritten with the driver post boot. :(
Hey there, I have the same issue with X1 Carbon G13.
Following this thread, I found that removing the kms hook from HOOKS in /etc/mkinitcpio.conf solves the problem (don't forget to run sudo mkinitcpio -P afterwards).
As I understand it, the kms hook tries to be "smart" and loads video drivers too early, which causes the black screen during the LUKS prompt. Removing this hook allows the driver to load after the LUKS stage, so the password prompt displays correctly without needing the nomodeset workaround.
P.S. I don't have plymouth installed though.
Oh yeah! That worked. Thank you so much!