OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
gpu-drivers high occasional DISPUTE

Brand-new Intel GPU does not probe: 'not properly supported by i915 in this kernel version'

omarchy-4archendeavouroscachyosmanjarointelmeteor-lakelunar-lakearclaptopdesktop
AUDITED Audited against its sources and confirmed accurate.
AUDIT NOTE

This tracks the Arch Intel graphics wiki almost line for line. Wiki line 308 carries the exact experimental warning the record paraphrases. Lines 310-326 give the same 8086:9a49 Tiger Lake example, the same i915.force_probe=!9a49 xe.force_probe=9a49 pairing, and the same /etc/modprobe.d/intel_xe.conf block with options i915 force_probe=!9a49 / options xe force_probe=9a49, matching the record's conf snippet verbatim. The require_force_probe / -ENODEV mechanism is accurate, as is the i915-through-Meteor-Lake vs xe-for-Lunar-Lake-and-later split and the 'both can bind on first-gen Xe, so you must exclude from i915 in the same breath' point. lspci -nnd ::03xx is valid syntax (pciutils accepts 'x' wildcards in the class field). Every package named exists: linux-firmware-intel (core 20260810), intel-media-driver (extra 26.2.4), mesa, vulkan-intel, and linux-mainline in AUR (7.2-1). The 'prefer a newer kernel, the driver message says so itself' ordering is the right advice rather than leading with the force. Two things I noted but that do not change the verdict: the sudo pacman -Syu linux ... line in step 2 will trip Omarchy's update guard (it has both -S and -u), though the reader has already been pointed at omarchy update on the line above. The sudo tee in step 3 truncates zz-local.conf rather than appending, so prefer tee -a if you already have parameters there.

RISK

Force-probing calls add_taint(TAINT_USER): the kernel is marked tainted, and Intel will not accept bug reports from that state. Unvalidated hardware can hang, corrupt the display, or fail to resume from suspend. Keep a snapshot or a second boot entry. Switching Tiger Lake / Rocket Lake / Alder Lake / Arc A-series to xe is explicitly experimental per the Arch wiki, with no stability or feature-parity guarantee. Have a way to revert (edit the entry at the Limine menu, or boot a snapshot) before you reboot. Getting the ! wrong on the i915 exclusion leaves both drivers fighting for the device and you get no display at all.

Symptom

On a just-released laptop (Meteor Lake, Lunar Lake, Arrow Lake, Panther Lake, Arc) there is no hardware acceleration at all: everything renders on llvmpipe, video playback pegs the CPU, and Hyprland may refuse to start with drm: Found no gpus to use, cannot continue. dmesg says exactly:


i915 0000:00:02.0: Your graphics device 7d55 is not properly supported by i915 in this
kernel version. To force driver probe anyway, use i915.force_probe=7d55
module parameter or CONFIG_DRM_I915_FORCE_PROBE=7d55 configuration option,
or (recommended) check for kernel updates.

or, for the newer driver:


xe 0000:00:02.0: Your graphics device 9a49 is not officially supported
by xe driver in this kernel version. To force Xe probe,
use xe.force_probe='9a49' and i915.force_probe='!9a49'
module parameters or CONFIG_DRM_XE_FORCE_PROBE='9a49' and
CONFIG_DRM_I915_FORCE_PROBE='!9a49' configuration options.

lspci -k shows the VGA controller with no Kernel driver in use: line at all.

Cause

Intel gates support for hardware it considers not yet validated behind a require_force_probe flag in the driver's device table. Until Intel clears it, the driver refuses -ENODEV on probe and prints the message above, and you fall back to simpledrm/efifb plus software rendering.

The second half of the problem is the i915-vs-xe split. Both drivers exist in the same kernel and both claim overlapping PCI IDs. i915 covers everything up to and including Alchemist/Meteor Lake. xe is the newer driver and is the only option for Lunar Lake, Battlemage and later. For first-generation Xe hardware (Tiger Lake, Rocket Lake, Alder Lake, Arc A-series) both drivers can bind, and the Arch wiki flags xe as *experimental* on those parts. Two drivers cannot own the same device, so switching to xe always requires excluding the ID from i915 at the same time.

Fix

**1. Get your PCI device ID.** It is the four hex digits after 8086:.


lspci -nnd ::03xx
# 00:02.0 VGA compatible controller [0300]: Intel Corporation ... [8086:7d55] (rev 08)

dmesg | grep -iE 'i915|xe ' | head -20
lspci -k -d ::03xx        # confirm no "Kernel driver in use"

**2. Prefer the real fix: a newer kernel.** The driver message says so itself. Before forcing anything, update and try the newest kernel available. On Arch-based systems that means linux at minimum, and linux-firmware for the GuC/HuC blobs the newer parts require.


omarchy update                                  # Omarchy 4
sudo pacman -Syu linux linux-headers linux-firmware linux-firmware-intel mesa vulkan-intel

If linux is still too old, linux-mainline (AUR) or CachyOS's kernels usually have it.

**3. Force the probe if you cannot wait.** Substitute your own ID for 7d55/9a49.

Stay on i915:


sudo tee /etc/limine-entry-tool.d/zz-local.conf >/dev/null <<'EOF'
KERNEL_CMDLINE[default]+=" i915.force_probe=7d55"
EOF
sudo limine-mkinitcpio && sudo limine-update && sudo reboot

Switch to xe (must exclude the ID from i915 in the same breath):


sudo tee /etc/limine-entry-tool.d/zz-local.conf >/dev/null <<'EOF'
KERNEL_CMDLINE[default]+=" i915.force_probe=!9a49 xe.force_probe=9a49"
EOF
sudo limine-mkinitcpio && sudo limine-update && sudo reboot

The modprobe.d equivalent (works only if the module is loaded from the initramfs *after* your config is included, and the cmdline is more reliable for early KMS):


# /etc/modprobe.d/intel_xe.conf
options i915 force_probe=!9a49
options xe   force_probe=9a49

On GRUB systems, put the same string in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run sudo grub-mkconfig -o /boot/grub/grub.cfg.

**4. Make sure the Mesa/Vulkan userspace is present too**, otherwise you get KMS but still no acceleration:


sudo pacman -S mesa vulkan-intel intel-media-driver

Verify

lspci -k -d ::03xx now shows Kernel driver in use: i915 (or xe). glxinfo -B | grep -i 'OpenGL renderer' names your Intel GPU instead of llvmpipe. vulkaninfo --summary lists an Intel device. dmesg | grep -i force shows Force probing unsupported Device ID 7d55, tainting kernel, confirming the parameter took effect.

Sources

intel-gpu-force-probe-required