Files
xps16-camera-fix-fedora/CAMERA-GUIDE.md
T
2026-10-29 12:10:33 +02:00

16 KiB
Raw Blame History

Built-in Camera Fix for Intel IPU6 Laptops on Fedora

As of 2026-10-29

The built-in camera on the Dell XPS 16 (DA16250) works on Fedora 44 after three fixes. Fix 1 moves libcamera's image processing off the NVIDIA GPU. Fix 2 corrects the upside-down sensor in the kernel. Fix 3 lets browsers use PipeWire cameras. Fixes 1 and 3 apply to most laptops with an Intel IPU6 camera; fix 2 depends on the laptop model.

This guide sits in the xps16-camera-fix-fedora repository, next to the files the fixes need:

xps16-camera-fix-fedora/
├── CAMERA-GUIDE.md                  this guide
├── README.md                        short summary
├── fix-camera.sh                    starts Claude Code with a prompt that follows this guide
├── install.sh                       builds and installs the patched module (Fix 2)
└── ipu-bridge/
    ├── ipu-bridge.c                 Fedora's 7.2 source plus one entry for the DA16250
    ├── Makefile
    └── dell-xps16-da16250.patch     the 7-line change, for reference

At a glance

Find your symptom, then go to the section in the last column.

Symptom Cause Where to look
Camera is listed, but the picture is black or frozen libcamera's GPU image processing uses the NVIDIA driver, which fails on every frame Fix 1
Picture is upside down in every app Firmware says the sensor is upright, and your kernel doesn't know your model is an exception Fix 2
Brave, Chrome or Chromium finds no camera The browser opens /dev/video* directly, and those nodes only carry raw sensor data Fix 3
Firefox finds no camera Firefox's PipeWire camera setting is off Fix 3
Jagged, grainy picture in Kamoso Kamoso always asks for 640×480, a 3× downscale with no smoothing Fix 3 (use Snapshot)
Upside down only in COSMIC Camera Bug in COSMIC Camera 1.3.7: it rotates a second time after libcamera already did Fix 3 (use Snapshot)
A Flatpak camera app shows black, but Snapshot works The app bundles its own libcamera, so the WirePlumber setting doesn't reach it Fix 1 (Flatpak apps)
Grainy, muddy picture in a dim room Exposure and gain are both at maximum Image quality
Device or resource busy Another app is using the camera; only one can at a time Close the other app or browser tab

Does this apply to you

This guide is for laptops whose camera connects through an Intel IPU6 image processor, not over USB. It was tested on a Dell XPS 16 DA16250 (Core Ultra 9 285H, OmniVision OV02C10 sensor, RTX 5070) with Fedora 44, kernels 7.2.11 and 7.2.13, libcamera 0.7.2, PipeWire 1.6.9 and WirePlumber 0.5.18.

Run these checks in a terminal, top to bottom.

  1. Camera type. A "Multimedia controller … IPU" line means a MIPI camera, so this guide applies. 8086:7d19 is the IPU6 in Meteor Lake and Arrow Lake. No line: you probably have a USB webcam, which works without this guide.

    lspci -nn | grep -i ipu
    
  2. Kernel drivers. Both intel_ipu6 and ipu_bridge should be listed.

    lsmod | grep -E 'intel_ipu6|ipu_bridge'
    
  3. Sensor found. Look for a sensor name besides the "Intel IPU6 CSI2" lines (ours: ov02c10 23-0036). If there are only CSI2 lines, the sensor driver is missing, which this guide doesn't cover.

    grep . /sys/class/video4linux/v4l-subdev*/name
    
  4. Userspace packages. All three should be installed.

    rpm -q libcamera libcamera-ipa pipewire-plugin-libcamera
    
  5. PipeWire sees it. Under Video → Sources you should see "Built-in Front Camera".

    wpctl status
    
  6. NVIDIA GPU. Any output means you will probably need Fix 1.

    lspci | grep -i nvidia
    
  7. Laptop model. Fix 2 needs the exact string.

    cat /sys/class/dmi/id/product_name
    

Lunar Lake laptops (Core Ultra 200V) use a newer IPU7 with a different kernel driver. This guide was not tested on them.

How it works

The camera passes through five layers, and each fix targets one of them.

Layer Component What it does Fix
Hardware OV02C10 sensor Mounted at 180°, but the firmware says 0°
Hardware IPU6 image unit Receives raw Bayer frames over CSI-2
Kernel ipu-bridge Reads the firmware tables and reports the sensor rotation Fix 2: add your model
Kernel ov02c10 driver Exposure, gain, hardware horizontal/vertical flip
Kernel intel_ipu6_isys Provides the /dev/video* nodes, with raw Bayer data only
libcamera (inside WirePlumber) Software ISP Turns raw data into a color picture on the GPU Fix 1: use Intel (Mesa), not NVIDIA
libcamera (inside WirePlumber) Exposure, color, orientation Sets sensor gain and exposure, and turns on the flips for 180°
PipeWire PipeWire + WirePlumber Offers "Built-in Front Camera" to apps, with the camera portal for Flatpaks
Apps Snapshot, browsers, Kamoso Ask PipeWire for the camera at some resolution Fix 3: browser PipeWire flag

The kernel delivers only raw sensor data. libcamera turns it into a picture, and PipeWire hands that picture to apps. Apps that open /dev/video* directly skip libcamera and get only raw data, which is why browsers need the PipeWire flag.

Fix 1: black image on laptops with an NVIDIA GPU

On Intel + NVIDIA laptops, tell WirePlumber to use the Intel GPU's driver (Mesa) for camera processing. This takes one file in your home folder and needs no sudo.

Why it breaks. The IPU6 delivers raw Bayer data, and libcamera's software ISP turns it into a color picture on the GPU through EGL. The system hands out NVIDIA's EGL driver first, and with it every frame fails. Using the Intel GPU also keeps the NVIDIA GPU asleep while the camera is on.

Confirm the symptom. Open the camera in any app first, because these lines only appear after a stream starts:

journalctl --user -b -u wireplumber | grep -E "EGL_VENDOR|GL_RENDERER|debayerGPU|FATAL"

The broken case looks like this:

EGL: EGL_VENDOR: NVIDIA
ERROR eGL egl.cpp:134 glFrameBufferTexture2D error 36054
ERROR Debayer debayer_egl.cpp:639 debayerGPU failed
FATAL default pipeline_handler.cpp:398 assertion "data->queuedRequests_.empty()" failed in stop()

Apply the fix. Restarting WirePlumber can interrupt audio for a moment.

mkdir -p ~/.config/systemd/user/wireplumber.service.d
cat > ~/.config/systemd/user/wireplumber.service.d/camera-softisp-mesa.conf <<'EOF'
[Service]
Environment=__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json
EOF
systemctl --user daemon-reload
systemctl --user restart wireplumber

Check it worked. Open the camera again and rerun the journalctl command. You should see EGL_VENDOR: Mesa Project, a GL_RENDERER line naming your Intel GPU, and no debayerGPU failed. On the test laptop the stream ran at about 28 frames per second.

If the Intel route fails. Replace the Environment= line with Environment=LIBCAMERA_SOFTISP_MODE=cpu and restart WirePlumber. The CPU path works, but at small sizes it crops the middle of the image instead of scaling it: at 640×480 you get a zoomed-in view.

Flatpak apps that bundle libcamera. Some camera apps, such as COSMIC Camera, ship their own libcamera and bypass WirePlumber, so they need the same setting. The Mesa file sits at a different path inside the sandbox:

flatpak override --user --env=__EGL_VENDOR_LIBRARY_FILENAMES=/usr/lib/x86_64-linux-gnu/GL/glvnd/egl_vendor.d/50_mesa.json <app-id>

Undo it with flatpak override --user --reset <app-id>. Snapshot and the browsers go through PipeWire and don't need this.

Fix 2: upside-down image

Add your laptop to the kernel's list of upside-down sensors. Mainline Linux already lists the XPS 16 DA16250, but Fedora's 7.2 kernels don't yet. The fix is a patched ipu-bridge module that rebuilds itself on every kernel update.

Why it breaks. The laptop firmware (ACPI) tells the kernel the sensor is mounted at 0°, but it is mounted at 180°. The ipu-bridge module keeps a list of models whose firmware gets this wrong and reports 180° for them. libcamera then flips the image in the sensor itself, at no cost.

Check 1: the rotation the system reports.

ID=$(wpctl status | grep -m1 "Built-in Front Camera" | grep -oE "[0-9]+" | head -1)
pw-cli info $ID | grep api.libcamera.rotation

"0" on an upside-down camera means you need this fix. "180" means it is already handled.

Check 2: whether your kernel knows your model.

M=$(modinfo -n ipu_bridge)
case $M in *.xz) xzcat "$M" ;; *) cat "$M" ;; esac | strings | grep -F "$(cat /sys/class/dmi/id/product_name)"

If your model name prints, the kernel already has the fix. If nothing prints, install the patched module.

Install it (XPS 16 DA16250, Fedora 7.2 kernels).

  1. Install the build tools: sudo dnf install kernel-devel-$(uname -r) gcc make.
  2. Check Secure Boot with mokutil --sb-state (see below if it is enabled).
  3. In this folder, run sudo ./install.sh, then reboot.
  4. Repeat Check 1. It should print "180".

What install.sh does.

  • Stops on any model other than the DA16250 (it compares the DMI product name).
  • If the stock module already has the entry, removes any override for that kernel instead of building.
  • Builds the module against the running kernel and checks that it was built for that kernel version.
  • Compares every string in the stock module with the new one. Any difference besides the new entry stops the install, so a newer Fedora module is never replaced with an older copy.
  • Installs to /lib/modules/<kernel>/updates/ipu-bridge.ko, which takes priority over the stock module, and runs depmod.
  • Adds a kernel-install hook that repeats all this for each new kernel, logging to /var/log/ipu-bridge-da16250.log. The hook never fails a kernel install. On the test laptop it rebuilt the module by itself when kernel 7.2.13 arrived.

The kernel will mark itself "tainted" because the module is unsigned and built outside the kernel tree. This is only a label.

Secure Boot. With Secure Boot on, Fedora refuses unsigned modules, and the script does not sign. You would need to sign the module with a key enrolled in MOK, such as the akmods key if you use akmod-nvidia. This was not tested.

A different laptop model. First check whether mainline Linux already lists your model (link in Sources). If not, change two places:

  1. Note your model string (cat /sys/class/dmi/id/product_name) and your sensor's ACPI ID from the command below. The test laptop prints ov02c10 23-0036 OVTI02C1.
  2. In ipu-bridge/ipu-bridge.c, copy the DA16250 entry in upside_down_sensor_dmi_ids[]. Put your model string in DMI_PRODUCT_NAME and your sensor ID in .driver_data.
  3. In install.sh, set QUIRK to your model string.
for s in /sys/class/video4linux/v4l-subdev*; do echo "$(cat $s/name)  $(cat $s/device/firmware_node/hid 2>/dev/null)"; done

The bundled ipu-bridge.c matches Fedora's 7.2 kernels. On another kernel series the script stops at the string comparison, and the source needs refreshing from that kernel first.

Undo. Run sudo ./install.sh --uninstall, then reboot.

Fix 3: apps and browsers

Only apps that get the camera through PipeWire can use it. Browsers need one setting; for a camera app, use GNOME Snapshot.

Browsers.

  • Brave, Chrome, Chromium: open brave://flags/#enable-webrtc-pipewire-camera (or chrome://flags/…), set "PipeWire Camera support" to Enabled, and relaunch. In Meet or Jitsi, choose "Built-in Front Camera". The desktop asks once whether the browser may use the camera.
  • Firefox: in about:config, media.webrtc.camera.allow-pipewire must be true.

With the flag on, USB webcams go through PipeWire too. PipeWire passes their frames through unchanged, and a USB webcam may show up twice in the list.

Camera apps. The resolution an app asks for decides the quality, because the image is shrunk from the sensor's 1928×1092 without smoothing.

App Asks for Result on the test laptop
GNOME Snapshot (org.gnome.Snapshot) 1920×1080 Works, upright, full quality. Recommended.
Brave with Google Meet 1280×720 Works, good quality.
Kamoso 640×480, no setting to change it Upright, but jagged and grainy. Photos are also 640×480.
COSMIC Camera 1.3.7 1920×1080 Upside down: it rotates again after libcamera already did. It also bundles its own libcamera, so it needs the Flatpak setting from Fix 1.

Install Snapshot with flatpak install --user flathub org.gnome.Snapshot. To see what an app asked for, open it and run:

journalctl --user -b | grep "configuring streams" | tail -3

Only one app can use the camera at a time. If an app shows nothing, close any other camera app or video-call tab.

Image quality

Expect a usable but basic picture: grainy and muddy in a dim room. More light on your face helps more than any setting.

  • Low light. In the test room, auto-exposure hit both limits: the longest exposure possible at 30 fps, and 15.5× analogue gain. The image was still about half its target brightness. Maximum gain is where the grain comes from.
  • Basic processing. Linux uses libcamera's software ISP, which has no noise reduction, no lens-shading correction and no calibrated color for this sensor. Windows uses Intel's hardware ISP with tuned processing.
  • Slow brightness changes. libcamera 0.7.2 has no exposure model for the OV02C10, so auto-exposure moves in small steps. The picture takes 10 seconds or more to settle after the camera opens.
  • Resolution. Use 1280×720 or higher. At 640×480 the image is shrunk about 3× without smoothing, which makes edges jagged.

Let Claude Code do it

Claude Code can run the checks, read the logs and adapt the files for your model. You only run the sudo step yourself.

  1. Install Claude Code if you don't have it: curl -fsSL https://claude.ai/install.sh | bash.
  2. Run ./fix-camera.sh from this folder, or double-click it in your file manager. It opens a terminal if needed and starts Claude Code with a prompt that walks through this guide. The prompt is at the top of the script.
  3. Claude Code asks before it runs commands or edits files. When it hands you a sudo command, run it in a separate terminal, then reboot.

Some file managers open scripts in a text editor when you double-click them. In that case, right-click the file and choose the option to run or execute it, or start it from a terminal.

What gets installed and how to undo it

Everything is reversible. Fix 1 and Fix 3 stay in your user account; only Fix 2 touches the system.

Change Location Root Undo
WirePlumber setting (Fix 1) ~/.config/systemd/user/wireplumber.service.d/camera-softisp-mesa.conf No Delete the file, then systemctl --user daemon-reload && systemctl --user restart wireplumber
Flatpak app setting (Fix 1, only for apps that bundle libcamera) The app's flatpak override --user entry No flatpak override --user --reset <app-id>
Patched module (Fix 2) /lib/modules/<kernel>/updates/ipu-bridge.ko, one per kernel Yes sudo ./install.sh --uninstall, then reboot
Kernel-install hook (Fix 2) /etc/kernel/install.d/90-ipu-bridge-da16250.install Yes Removed by --uninstall
Copy of the script and source the hook uses (Fix 2) /usr/local/src/ipu-bridge-da16250/ Yes Removed by --uninstall
Hook log (Fix 2) /var/log/ipu-bridge-da16250.log Yes Not removed by --uninstall; delete it with sudo rm
Browser flag (Fix 3) The browser's flags page No Set the flag back to Default

Sources

Checked on 29 October 2026.

  • Mainline ipu-bridge.c: its upside-down list includes the XPS 16 DA16250. Search it for your own model.
  • Stable 7.2.y ipu-bridge.c: the 7.2 series as of 7.2.13, without the DA16250 entry.
  • Fedora f44 kernel patch: Fedora's own ipu-bridge changes (it adds the DA14250, not the DA16250). The bundled ipu-bridge.c is stable 7.2 plus these changes plus the DA16250 entry.