Current section: Blog LaptopCompass
Find my laptop

Blog

The Intel IPU6 webcam problem on Linux, and which laptops dodge it

If you buy a 2024 or 2025 Intel Core Ultra laptop and run Linux, assume the webcam does not work until you have checked the specific model. That assumption is correct more often than not, and here is why.

Intel moved the laptop camera off the old, boring path. A traditional laptop webcam is a UVC device: USB Video Class, a standardised interface the uvcvideo kernel driver has handled for over a decade with nothing to configure. On Tiger Lake and newer, Intel routed the MIPI camera sensor through the on-die Image Processing Unit, IPU6 on Meteor Lake and Lunar Lake, IPU7 on the very newest parts. The raw sensor is not a plug-and-play video device. It needs the IPU6/IPU7 kernel driver, sensor bridge drivers, the proprietary Intel IPU firmware and processing binaries, and libcamera plus a pipewire/v4l2 shim so that ordinary apps see a normal camera. On Windows this is one Intel driver package. On Linux it is a stack that was not in the mainline kernel when these laptops shipped.

The kernel and userspace timeline

The fix arrived in pieces, not in one release. Kernel 6.10 brought intel-ipu6 into the mainline kernel, but a webcam needs more than a driver. Through kernel 6.13 the IPU6 sensor bridge and several specific sensor drivers landed, which is why several of our model notes use “kernel 6.13” as the practical floor for Lunar Lake cameras to have a chance. The IPU7 work for the newest 2025 parts continued after that, through the 6.17 and 6.18 cycle, and even on a current kernel some IPU7 sensors still need pieces that are not all upstream.

The other half is userspace. Even with the kernel driver present, the camera shows up through libcamera’s software ISP, not as a classic /dev/video0 UVC device. You need a recent libcamera, the pipewire/libcamera glue, and apps that go through PipeWire. A stock Ubuntu 24.04 LTS install does not have that plumbing, which is why an LTS user on Lunar Lake hits a dead camera even when a newer Fedora on the same hardware works.

Which models hit it, which dodge it

The pattern in our database is consistent.

ModelCamera pathLinux camera state
Dell XPS 13 9350Intel IPU7, OV02C10broken, Dell BIOS bug no kernel fully fixes
ThinkPad X1 Carbon Gen 13Intel IPU7needs kernel 6.13+ and libcamera, broken on stock LTS
ThinkPad T14 Gen 5 (AMD)normal UVCworks, dodges the IPU6 mess entirely
Framework 13 (AMD 7040)UVCworks (Wayland unverified in our notes)
Star Labs StarBook Mk VIIUVCworks out of the box

The Dell XPS 13 9350 is the cautionary case and worth its own sentence. Its camera is not just the generic IPU7 plumbing problem. Dell shipped a BIOS bug specific to the OV02C10 sensor that no kernel or firmware update fully fixes, tracked in Launchpad bug 2131016. Our Arch note on that machine says the camera is still dead even with the kernel 6.18 IPU7 drivers. Everything else on the XPS works, which makes it more frustrating, not less. The ThinkPad X1 Carbon Gen 13 is the better-behaved IPU7 case: broken on the stock 24.04 stack, gets to a tweak state on Fedora 42 with a 6.13-plus kernel.

The dodge is not subtle. Every model that simply works uses a normal UVC webcam, and in this database that lines up with the AMD machines and the Linux-first vendor builds. The ThinkPad T14 Gen 5 (AMD) note states it plainly: the AMD model uses a normal UVC webcam so it dodges the Intel IPU6 mess. The StarBook Mk VII is an Intel chip but a vendor that ships Linux, and its camera works because the rest of the firmware is sane.

The recommendation

If a working webcam on day one matters to you and you are running Linux, the safe filter is: prefer an AMD Core, or an Intel machine from a Linux-first vendor, and check the model’s kernel floor before you buy. For mainstream Intel Core Ultra laptops from Dell, Lenovo and the rest, treat the webcam as the open question. It may work on a current Fedora with kernel 6.13 or newer and libcamera. It may also be a model-specific firmware bug, like the XPS 13 9350, that no kernel fixes at all. The cheapest way around the entire problem is still to buy AMD and let the boring old UVC driver do its job.