You are not logged in.
My laptop was working fine last night. I think I might have run a `pacman -Syu` last night before going to bed.
I have a Dell Pro 13 Premium PA13250 with Intel(R) Core(TM) Ultra 5 236V.
This morning when I tried to boot it up, I saw this text flash for 1 sec.
EFI stub: WARNING: [Firmware Bug] LoadOptions is an EFI_LOAD_OPTION descriptor
EFI stub: WARNING: [Firmware Bug] Using OptionalData as a workaround
Then the laptop screen went dark. The laptop is still on and the screen backlight is on, but the screen just displays black.
At first, I thought it might be a hardware issue... I did see something flash "EC Power Rail Error" a few times when I tried power cycling the laptop, but it hasn't come up again.
Then I saw this on the Gentoo forums, which seems similar: https://forums.gentoo.org/viewtopic-t-1 … art-0.html but I don't totally follow what the fix was...
I then checked to see if I could boot into anything. So I plugged in an Ubuntu USB I happened to have lying around and I was able to successfully boot into that. I'm on the Ubuntu ISO right now.
I was able to update my EFI stub to enable more logging. I used this command.
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux' \
--loader /vmlinuz-linux \
--unicode "initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot rw debug ignore_loglevel sysrq_always_enabled=1"
After rebooting, now I started seeing more logs.
xe 0000:00:02.0 [drm] Registered 3 planes with drm panic
[drm] Initialized xe 1.1.0 for 0000:00:02.0 on minor 0
ACPI: video Video Device [GFX0] (multi-head: yes rom: no post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYSBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
fbcon: xedrmfb (fb0) is primary device
Console: switching to colour frame buffer device 240x75
xe 0000:00:02.0 [drm] fb0: xedrmfb frame buffer device
Here's some lshw info
*-cpu
description: CPU
product: Intel(R) Core(TM) Ultra 5 236V
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.189.1
slot: U3E1
size: 400MHz
capacity: 4700MHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs
ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a rdseed adx smap clflushopt clwb intel_pt sha_ni xs
aveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni lam wbnoinvd dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku os
pke waitpkg gfni vaes vpclmulqdq rdpid bus_lock_detect movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities cpufreq
configuration: cores=8 enabledcores=8 microcode=287 threads=8
*-display
description: VGA compatible controller
product: Lunar Lake [Intel Graphics]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=xe latency=0 mode=1920x1200 resolution=1920,1200 visual=truecolor xres=1920 yres=1200
resources: iomemory:300-2ff iomemory:200-1ff irq:188 memory:3014000000-3014ffffff memory:2000000000-200fffffff memory:c0000-dffff
Last edited by 1ptb3b (2025-10-10 06:26:52)
Offline
Got the same warning on my Dell Vostro 5402 yesterday too. Though, it boots fine. Perhaps the newer kernel's EFI Stub has some new standards for the UEFI.
I created my boot entry with this command
sudo efibootmgr -c \
-d /dev/nvme0n1 -p 1 \
-L "Arch Linux" \
-l '\vmlinuz-linux' \
-u "initrd=\initramfs-linux.img root=PARTUUID=b13c8d6a-e9a7-466c-a5e7-ec411d4c308c rw quiet rootfstype=ext4 zswap.enabled=0 loglevel=0 rd.systemd.show_status=0 vt.global_cursor_default=0 splash keep_bootcon"
Here's my lshw
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: 1.33.1
date: 11/15/2024
size: 1MiB
capacity: 32MiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi
*-cpu
description: CPU
product: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.140.1
slot: CPU 1
size: 1971MHz
capacity: 4200MHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l2 cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2intersect md_clear ibt flush_l1d arch_capabilities cpufreq
configuration: cores=4 enabledcores=4 microcode=188 threads=8
*-display
description: VGA compatible controller
product: TigerLake-LP GT2 [Iris Xe Graphics]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
resources: iomemory:600-5ff iomemory:400-3ff irq:162 memory:601e000000-601effffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff
Offline
Interesting. I was able to install Guix Linux and boot all the way to a GNOME desktop.
After that, I tried doing a fresh Arch install without a desktop environment and with systemd-boot, but I ended up hitting the same error as my initial post. Still can't boot the system. Black screen.
The Arch installer was working fine though.
Last edited by 1ptb3b (2025-10-09 22:15:39)
Offline
I noticed a difference between my setup, and yours.
Since you have a newer graphics card, your kernel loads the xe graphics driver, which is still experimental. When my kernel loads i915, which works fine for me.
Try to blacklist the xe driver. There's a couple ways to do that, and one of them is adding this kernel argument to your EFIStub
modprobe.blacklist=xe
Full command would look something like this
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux' \
--loader /vmlinuz-linux \
--unicode "initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot rw debug ignore_loglevel sysrq_always_enabled=1 modprobe.blacklist=xe"
Let me know how that turned out for you
Offline
Strange... adding
modprobe.blacklist=xe
allowed me to boot into GNOME! Hurrah!
Except.
The system isn't working 100%... Weirdly, my audio is now broken. The graphics mostly work... Except there are no animations anywhere and GNOME says I can't turn on Night Light... I also can't dim my screen with the keyboard now...
The wifi works at least.
Here's some more info, in case it's helpful.
$ echo $XDG_SESSION_TYPE
wayland
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa (0xffffffff)
Device: llvmpipe (LLVM 20.1.8, 256 bits) (0xffffffff)
Version: 25.2.4
Accelerated: no
Video memory: 15580MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 0 MB, largest block: 0 MB
VBO free aux. memory - total: 12991 MB, largest block: 12991 MB
Texture free memory - total: 0 MB, largest block: 0 MB
Texture free aux. memory - total: 12991 MB, largest block: 12991 MB
Renderbuffer free memory - total: 0 MB, largest block: 0 MB
Renderbuffer free aux. memory - total: 12991 MB, largest block: 12991 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 0 MB
Total available memory: 15580 MB
Currently available dedicated video memory: 0 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 20.1.8, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 25.2.4-arch1.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.2.4-arch1.1
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.2.4-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
$ vainfo
Trying display: wayland
Trying display: x11
libva error: vaGetDriverNames() failed with unknown libva error
vaInitialize failed with error code -1 (unknown libva error),exit
$ pacman -Qs intel
local/ibus 1.5.32-1
Intelligent input bus for Linux/Unix
local/intel-gmmlib 22.8.1-1
Intel Graphics Memory Management Library
local/intel-gpu-tools 2.1-1
Tools for development and testing of the Intel DRM driver
local/intel-media-driver 25.3.4-1
Intel Media Driver for VAAPI
local/intel-ucode 20250812-1
Microcode update files for Intel CPUs
local/libva-utils 2.22.0-1
Intel VA-API Media Applications and Scripts for libva
local/libvpl 2.15.0-1
Intel Video Processing Library
local/linux-firmware-intel 20250917-1
Firmware files for Linux - Firmware for Intel devices
Last edited by 1ptb3b (2025-10-10 05:15:24)
Offline
Wait, I fixed it!
First, I installed `linux-lts`.
sudo pacman -S linux-lts
Then I created another boot entry:
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux LTS' \
--loader /vmlinuz-linux-lts \
--unicode "initrd=/initramfs-linux-lts.img cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot rw debug ignore_loglevel sysrq_always_enabled=1"
vainfo looks happy now.
$ vainfo
Trying display: wayland
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.3.4 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile1 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileVP9Profile3 : VAEntrypointVLD
VAProfileHEVCMain12 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointEncSlice
VAProfileHEVCMain422_12 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointEncSlice
VAProfileHEVCMain444_10 : VAEntrypointVLD
VAProfileHEVCMain444_10 : VAEntrypointEncSlice
VAProfileHEVCMain444_12 : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointEncSlice
VAProfileHEVCSccMain10 : VAEntrypointVLD
VAProfileHEVCSccMain10 : VAEntrypointEncSlice
VAProfileHEVCSccMain444 : VAEntrypointVLD
VAProfileHEVCSccMain444 : VAEntrypointEncSlice
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointEncSlice
VAProfileHEVCSccMain444_10 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointEncSlice
VAProfileVVCMain10 : VAEntrypointVLD
VAProfileVVCMultilayerMain10 : VAEntrypointVLD
and so does glxinfo
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) Graphics (LNL) (0x64a0)
Version: 25.2.4
Accelerated: yes
Video memory: 7792MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (LNL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.2.4-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.2.4-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.2.4-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Working kernel
$ uname -a
Linux pierogi 6.12.51-1-lts #1 SMP PREEMPT_DYNAMIC Mon, 06 Oct 2025 11:05:41 +0000 x86_64 GNU/Linux
Not working kernel
local/linux 6.17.1.arch1-1
The Linux kernel and modules
Uff. Not sure if I have to go back that far. Is there a way to pin the 6.16 kernel?
Last edited by 1ptb3b (2025-10-10 06:35:41)
Offline
Nice, if LTS works for you, stay there. It uses i915 driver, which works fine for now.
But if you wanna tackle the root cause of 6.17.1 kernel, read my text below.
When blacklisting the xe driver, I expected your kernel to fallback to i915 driver. But instead, it just didn't use any driver at all. Weird.
I guess we have to explicitly load i915.
Given that linux-lts is uninstalled, and linux is set as default.
Add i915 to initramfs.
sudo nano /etc/mkinitcpio.conf
MODULES=(i915)
Rebuild initramfs.
sudo mkinitcpio -p linux
Explicitly tell the kernel to load i915 by adding this as a kernel argument to EFIStub. For good measure.
modules-load=i915
And regarding about the pinning of 6.16.1.
Of course, you can freeze your kernel, but you'll be stuck with this version forever.
It involves manually downloading 6.16.1 with its headers from Arch archives with wget.
And blacklisting linux and linux-headers in /etc/pacman.conf to prevent them from updating
In that case, just stick to LTS. It's good enough.
Offline
These GPU modules usually have some shared initalisation code which is why blacklisting one or the other module nor changing the earlyness of their loader will likely change something. The "proper" way is to not blacklist either driver but set the relevant probing config as described in https://wiki.archlinux.org/title/Intel_ … _Xe_driver (but reversing the location of the ! if you want to load i915 in lieu of xe)
Offline
I guess we have to explicitly load i915.
Ooook, so I edited `/etc/mkinitcpio.conf` to add `MODULES=(i915)`. Then I ran `sudo mkinitcpio -P` to rebuild all the presets.
Then I created a new boot entry.
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux Explicit i915' \
--loader /vmlinuz-linux \
--unicode "initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:root:allow-discards root=/dev/mapper/root rw debug ignore_loglevel sysrq_always_enabled=1 modules-load=i915"
Also, I did not run a 'pacman -Rs linux-lts' to uninstall the LTS kernel. Not sure if that matters...
And then finally I rebooted! ... ... ... aaaaand I ended up hitting the error from post 1. No DE, black screen.
set the relevant probing config
OK, next up I tried this config.
$ lspci -nnd ::03xx
00:02.0 VGA compatible controller [0300]: Intel Corporation Lunar Lake [Intel Arc Graphics 130V / 140V] [8086:64a0] (rev 04)
I created another boot entry, swaping the "!" in the docs: https://wiki.archlinux.org/title/Intel_ … _Xe_driver
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux Force Probe' \
--loader /vmlinuz-linux \
--unicode 'initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:root:allow-discards root=/dev/mapper/root rw debug ignore_loglevel sysrq_always_enabled=1 i915.force_probe=64a0 xe.force_probe=!64a0'
and then rebooted and selected this entry. Aaaaand ... ... ... it booted into GNOME! Hurrah!
Except. Again. I have no animations. And it looks like I'm back to the state of post number 5: https://bbs.archlinux.org/viewtopic.php … 6#p2266836 where I had added "modprobe.blacklist=xe".
Offline
Try blacklisting xe AND explicitly loading i915.
Offline
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux blacklist and enable' \
--loader /vmlinuz-linux \
--unicode "initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:root:allow-discards root=/dev/mapper/root rw debug ignore_loglevel sysrq_always_enabled=1 modprobe.blacklist=xe modules-load=i915"
Same behavior as post 5 https://bbs.archlinux.org/viewtopic.php … 6#p2266836 (no animations)
Offline
I am out of options, sadly
Offline
I appreciate the brainstorming, thanks!
Last edited by 1ptb3b (2025-10-11 04:39:44)
Offline
Got the same warning on my Dell Vostro 5402 yesterday too. Though, it boots fine. Perhaps the newer kernel's EFI Stub has some new standards for the UEFI.
I created my boot entry with this command
sudo efibootmgr -c \ -d /dev/nvme0n1 -p 1 \ -L "Arch Linux" \ -l '\vmlinuz-linux' \ -u "initrd=\initramfs-linux.img root=PARTUUID=b13c8d6a-e9a7-466c-a5e7-ec411d4c308c rw quiet rootfstype=ext4 zswap.enabled=0 loglevel=0 rd.systemd.show_status=0 vt.global_cursor_default=0 splash keep_bootcon"
Wait! You're not using LUKS encryption! I am!
Uhh... some how I managed to boot into the system now. I entered my LUKS password on the black screen and mashed some buttons to get another TTY (Ctrl+Alt+F3, etc) nothing happened for a long time, then I pressed and held the power button to try to turn off the laptop... Then magically I got to the GDM screen!
I also updated the kernel hoping that 6.17.2 would fix my original issue... although, I don't think that fixed it... I think what's happening is that the black screen isn't showing the LUKS password prompt... but the rest of the system *is* still working.
$ uname -a
Linux 1ptb3b 6.17.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 12 Oct 2025 12:45:18 +0000 x86_64 GNU/Linux
Gonna try to document some more reproducible steps. brb.
Last edited by 1ptb3b (2025-10-14 23:19:14)
Offline
OK! Found a workaround.
1. Boot normal non-LTS kernel
2. When I get to the screen with "xe 0000:00:02.0 [drm] Registered 3 planes with drm panic" (or plain black screen if logs are disabled), enter LUKS password
3. Wait for screen to slightly dim, indicating that the password was accepted
4. Press the power button to suspend the laptop
5. Press the power button again to wake the laptop
6. Get presented with GDM!
7. ???
8. Profit!
During steps 2 to 5, there is no indication from the display that things are working. It seems like the laptop is hanging, but apparently it's not. It's just the graphics that are buggy.
Also, just to be clear, this is the boot entry I'm using:
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label 'Arch Linux' \
--loader /vmlinuz-linux \
--unicode "initrd=/initramfs-linux.img cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot rw debug ignore_loglevel sysrq_always_enabled=1"
and the kernel I booted is "6.17.2-arch1-1". The LTS kernel's graphics work better with my hardware, which I guess is too new.
Offline