reacocard wrote:
Steps that should replicate my setup:
Thanks for this! I finally have a working IPU6 cam on my 2024 XPS 16 (9640) https://wiki.archlinux.org/title/Dell_XPS_16_(9640) with 6.18.4-arch1-1 and the V4L2 loopback.
I've been able to get my webcam to work with libcamera, gstreamer, v4l2loopback, and chromium. I'll share the details here.
I'm not using the intel proprietary packages (intel-ipu6-dkms-git intel-ipu6-camera-bin intel-ipu6-camera-hal-git icamerasrc-git)
With the newest kernel I could immediately get a picture with qcam but I could not get it to work with either firefox or chromium.
With the following configuration I am finally able to use my webcam with nextcloud talk under chromium. The quality is not great, its greenish and a bit low on light. Its clearly missing calibration data. But its responsive and very usable.
laptop: Dell Latitude 7450
Kernel: 6.18.4-arch1-1
Sensor: INT3537
Camera name: hi556
dmesg |grep intel-ip6
intel-ipu6 0000:00:05.0: Found supported sensor INT3537:00recognised by libcamera as: (leaving out the warnings here)
cam -l
Available cameras:
1: 'hi556' (\_SB_.PC00.LNK1)Related packages I have installed:
local/pipewire-v4l2 1:1.4.9-2
local/v4l2loopback-dkms 0.15.3-1
local/v4l2loopback-utils 0.15.3-1
local/gst-plugin-libcamera 0.6.0-2
local/libcamera 0.6.0-2
local/libcamera-ipa 0.6.0-2
local/libcamera-tools 0.6.0-2
local/pipewire-libcamera 1:1.4.9-2
local/gstreamer 1.26.10-2
Create the following file:
cat /etc/modprobe.d/v4l2loopback.conf
options v4l2loopback video_nr=60 card_label="v4l2_hi556_loopback" exclusive_caps=1Now you've created a v4l2 loopback device /dev/video60
Use gstreamer to send the signal from your webcam to the v4l2loopback device:
gst-launch-1.0 libcamerasrc name="hi556" ! queue ! videoconvert ! video/x-raw,format=YUY2 ! v4l2sink name=v4l2sink-hi556 device=/dev/video60I noticed that adding any other video settings here, like the resolution, would result in no video output
if all goes well you should see a counter going up (counting seconds of video stream sent to v4l2 sink.
Test it with ffplay:
After this you should see a webcam device in chromium called: "v4l2_hi556_loopback" (don't let ffplay run in the background)
First I had "PipeWire Camera support" disabled in chrome://flags/
But now I've set it to "Default" again and its still working
Firefox does not see my v4l2loopback device for some reason.
obs works
edit
After using the camera for some time the image can start to flicker. And Gstreamer would show the following warnings:
WARNING: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink-hi556: A lot of buffers are being dropped.
Additional debug info:
../gstreamer/subprojects/gstreamer/libs/gst/base/gstbasesink.c(3146): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink-hi556:
There may be a timestamping problem, or this computer is too slow. edit2
Was able to stop the flickering. See https://bbs.archlinux.org/viewtopic.php … 2#p2301912
Last edited by merijn (Today 13:15:31)
merijn wrote:
I've been able to get my webcam to work with libcamera, gstreamer, v4l2loopback, and chromium. I'll share the details here.
I'm not using the intel proprietary packages (intel-ipu6-dkms-git intel-ipu6-camera-bin intel-ipu6-camera-hal-git icamerasrc-git)With the newest kernel I could immediately get a picture with qcam but I could not get it to work with either firefox or chromium.
With the following configuration I am finally able to use my webcam with nextcloud talk under chromium. The quality is not great, its greenish and a bit low on light. Its clearly missing calibration data. But its responsive and very usable.laptop: Dell Latitude 7450
Kernel: 6.18.4-arch1-1
Sensor: INT3537
Camera name: hi556dmesg |grep intel-ip6 intel-ipu6 0000:00:05.0: Found supported sensor INT3537:00recognised by libcamera as: (leaving out the warnings here)
cam -l Available cameras: 1: 'hi556' (\_SB_.PC00.LNK1)Related packages I have installed:
local/pipewire-v4l2 1:1.4.9-2
local/v4l2loopback-dkms 0.15.3-1
local/v4l2loopback-utils 0.15.3-1
local/gst-plugin-libcamera 0.6.0-2
local/libcamera 0.6.0-2
local/libcamera-ipa 0.6.0-2
local/libcamera-tools 0.6.0-2
local/pipewire-libcamera 1:1.4.9-2
local/gstreamer 1.26.10-2Create the following file:
cat /etc/modprobe.d/v4l2loopback.conf options v4l2loopback video_nr=60 card_label="v4l2_hi556_loopback" exclusive_caps=1Now you've created a v4l2 loopback device /dev/video60
Use gstreamer to send the signal from your webcam to the v4l2loopback device:
gst-launch-1.0 libcamerasrc name="hi556" ! queue ! videoconvert ! video/x-raw,format=YUY2 ! v4l2sink name=v4l2sink-hi556 device=/dev/video60I noticed that adding any other video settings here, like the resolution, would result in no video output
if all goes well you should see a counter going up (counting seconds of video stream sent to v4l2 sink.Test it with ffplay:
After this you should see a webcam device in chromium called: "v4l2_hi556_loopback" (don't let ffplay run in the background)
First I had "PipeWire Camera support" disabled in chrome://flags/
But now I've set it to "Default" again and its still working
Firefox does not see my v4l2loopback device for some reason.
obs worksedit
After using the camera for some time the image can start to flicker. And Gstreamer would show the following warnings:WARNING: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink-hi556: A lot of buffers are being dropped. Additional debug info: ../gstreamer/subprojects/gstreamer/libs/gst/base/gstbasesink.c(3146): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink-hi556: There may be a timestamping problem, or this computer is too slow.
Thanks for sharing. Its work on my Acer Swift SF314-512 with Debian sid.
Mod note: @duzhuo please refrain from unnecessary full-quotes. Thank you.
Inofficial first vice president of the Rust Evangelism Strike Force
Got my webcam fully working on the X1 Carbon Gen 11 (i7-1355U, OV2740 sensor, kernel 6.18) using the in-tree IPU6 driver + libcamera. The default uncalibrated profile looks pretty bad so I put together a CCM tuning file that helps. Couldn't find one anywhere online so posting it here.
Install packages:
sudo pacman -S libcamera libcamera-ipa libcamera-tools gst-plugin-libcamera pipewire-libcameraWirePlumber config — tells PipeWire to use libcamera instead of raw V4L2 (which only gives unusable bayer data):
mkdir -p ~/.config/wireplumber/wireplumber.conf.d# ~/.config/wireplumber/wireplumber.conf.d/99-libcamera.conf
wireplumber.profiles = {
main = {
monitor.v4l2 = disabled
monitor.libcamera = optional
}
}Firefox: set media.webrtc.camera.allow-pipewire to true in about:config, otherwise you get 30+ ipu6 entries in the camera dropdown instead of one usable device.
Tuning file — this is the main thing, without it libcamera falls back to uncalibrated.yaml and the image is washed out and green:
# /usr/share/libcamera/ipa/simple/ov2740.yaml
# SPDX-License-Identifier: CC0-1.0
%YAML 1.1
---
version: 1
algorithms:
- BlackLevel:
- Awb:
# - Agc:
- Adjust:
- Ccm:
ccms:
- ct: 6500
ccm: [ 2.25, -1.00, -0.25,
-0.45, 1.35, -0.20,
0.00, -0.60, 1.60 ]Boot race condition fix — WirePlumber often starts before the IPU6 driver is ready, so the camera doesn't show up until you manually restart it. This service handles it automatically:
# ~/.config/systemd/user/restart-wireplumber.service
[Unit]
Description=Restart WirePlumber to pick up libcamera device
After=wireplumber.service pipewire.service
[Service]
Type=oneshot
ExecStartPre=/usr/bin/sleep 5
ExecStart=/usr/bin/systemctl --user restart wireplumber
[Install]
WantedBy=default.targetsystemctl --user daemon-reload
systemctl --user enable restart-wireplumber.serviceReboot after all of the above.
Notes:
- Still not perfect — there's a slight green cast that seems to come from the debayer stage before the CCM runs. The values aren't properly calibrated, just eyeballed, so if anyone can refine them please share.
- pacman -Syu will probably overwrite the tuning yaml when libcamera updates, keep a backup.
Edit: Based on other comments, I also removed Agc, since it fixed the awful flickering I was getting whenever my surroundings were too bright. I'm also going without the Ccm now, since I find the default washed out looked is a lil better than the aggressive pink that comes when it's too bright.
Last edited by platelminto (2026-02-26 12:20:33)
@platelminto your config helped a lot, thanks!
the `Ccm` part didn't work for Carbon X1 Gen10 with ov2740 (purple tint),
disabling Agc stops the flickering!
Here's the config that works well for me:
# /usr/share/libcamera/ipa/simple/ov2740.yaml
# SPDX-License-Identifier: CC0-1.0
%YAML 1.1
---
version: 1
algorithms:
- BlackLevel:
- Awb:
# - Agc:
- Adjust:Configs working for Thinkpad X1 Nano Gen 3, thank you @platelminto
The Tuning file was my missing piece, as the image was constantly flickering and with a very intrusive green tint.
I also had to disable Agc. This is my CCM, which is a bit brighter but still has a slight green tint.:
- Ccm:
ccms:
- ct: 6500
ccm: [ 3.05, -1.40, -0.15,
-0.40, 2.70, -0.95,
0.00, -1.50, 3.60 ]Iruwen wrote:
Indeed, on 6.19rc3 with the Chromium PipeWire Camera support flag enabled at least https://webcamtests.com works to a degree, it's ugly but still. OVTI08F4/ov08x40 in a X1C G12.
/e: somehow after accessing the test page for a second time resolution increased and much of the noise disappeared, quality is kind of okay now.
https://i.ibb.co/wFmPCcqb/image.png
I'm running 6.19.6 with an OVTI08F4 here. Hopes were high that with 6.19 I would have ootb support for this sensor, but unfortunately this hasn't worked out in my case.
$ sudo dmesg | grep 0000:00:05
[ 0.412704] pci 0000:00:05.0: [8086:7d19] type 00 class 0x048000 PCIe Root Complex Integrated Endpoint
[ 0.412723] pci 0000:00:05.0: BAR 0 [mem 0x5020000000-0x5020ffffff 64bit]
[ 0.412729] pci 0000:00:05.0: enabling Extended Tags
[ 0.540007] pci 0000:00:05.0: Adding to iommu group 3
[ 10.256446] pci 0000:00:05.0: Setting to D3hot
[ 10.403382] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 10.412995] intel-ipu6 0000:00:05.0: Found supported sensor OVTI08F4:00
[ 10.413091] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 10.414191] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 10.461871] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 10.511117] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 10.511141] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6and
$ LIBCAMERA_LOG_LEVELS=0 cam --list
[0:37:18.816383767] [37620] DEBUG IPAModule ipa_module.cpp:333 ipa_ipu3.so: IPA module /usr/lib/libcamera/ipa/ipa_ipu3.so is signed
[0:37:18.816435750] [37620] DEBUG IPAManager ipa_manager.cpp:239 Loaded IPA module '/usr/lib/libcamera/ipa/ipa_ipu3.so'
[0:37:18.816466260] [37620] DEBUG IPAModule ipa_module.cpp:333 ipa_soft_simple.so: IPA module /usr/lib/libcamera/ipa/ipa_soft_simple.so is signed
[0:37:18.816483262] [37620] DEBUG IPAManager ipa_manager.cpp:239 Loaded IPA module '/usr/lib/libcamera/ipa/ipa_soft_simple.so'
[0:37:18.816507046] [37620] DEBUG IPAModule ipa_module.cpp:333 ipa_vimc.so: IPA module /usr/lib/libcamera/ipa/ipa_vimc.so is signed
[0:37:18.816522090] [37620] DEBUG IPAManager ipa_manager.cpp:239 Loaded IPA module '/usr/lib/libcamera/ipa/ipa_vimc.so'
[0:37:18.816528546] [37620] INFO Camera camera_manager.cpp:340 libcamera v0.7.0
[0:37:18.816662647] [37621] DEBUG Camera camera_manager.cpp:74 Starting camera manager
[0:37:18.827348539] [37621] DEBUG DeviceEnumerator device_enumerator.cpp:267 New media device "intel-ipu6" created from /dev/media0
[0:37:18.827375600] [37621] DEBUG DeviceEnumerator device_enumerator_udev.cpp:111 Defer media device /dev/media0 due to 48 missing dependencies
[0:37:18.832671069] [37621] DEBUG DeviceEnumerator device_enumerator_udev.cpp:346 All dependencies for media device /dev/media0 found
[0:37:18.832681867] [37621] DEBUG DeviceEnumerator device_enumerator.cpp:295 Added device /dev/media0: intel-ipu6
[0:37:18.833095075] [37621] DEBUG Camera camera_manager.cpp:143 Found registered pipeline handler 'virtual'
[0:37:18.833112174] [37621] DEBUG DmaBufAllocator dma_buf_allocator.cpp:106 Failed to open /dev/dma_heap/linux,cma: No such file or directory
[0:37:18.833124121] [37621] DEBUG DmaBufAllocator dma_buf_allocator.cpp:106 Failed to open /dev/dma_heap/reserved: No such file or directory
[0:37:18.833130155] [37621] DEBUG DmaBufAllocator dma_buf_allocator.cpp:106 Failed to open /dev/dma_heap/system: Permission denied
[0:37:18.833147850] [37621] DEBUG DmaBufAllocator dma_buf_allocator.cpp:112 Using /dev/udmabuf
[0:37:18.833159934] [37621] DEBUG Virtual virtual.cpp:385 Configuration file not found, skipping virtual cameras
[0:37:18.833166216] [37621] DEBUG Camera camera_manager.cpp:143 Found registered pipeline handler 'vimc'
[0:37:18.833181277] [37621] DEBUG Camera camera_manager.cpp:143 Found registered pipeline handler 'uvcvideo'
[0:37:18.833187114] [37621] DEBUG Camera camera_manager.cpp:143 Found registered pipeline handler 'simple'
[0:37:18.833195477] [37621] DEBUG DeviceEnumerator device_enumerator.cpp:355 Successful match for media device "intel-ipu6"
[0:37:18.833204564] [37621] INFO SimplePipeline simple.cpp:1899 No sensor found for /dev/media0
[0:37:18.833211496] [37621] DEBUG Camera camera_manager.cpp:143 Found registered pipeline handler 'ipu3'
Available cameras:Do I still need to install the DKMS AUR packages for this sensor?
For me, the service restarting wireplumber was necessary to get the camera working. I also needed to able Agc to get proper colors (ov02c10). So lovely to have this working!
How does one tune the CCM for their own sensor?
Last edited by marmistrz (2026-03-06 12:20:13)
My Dell XPS 16 ipu6 camera has been working with qcam since Linux kernel 6.16 landed last year, but the libcamera 0.6 --> 0.7 update last month broke it. I downgraded the affected packages but want to know a more permanent solution. Has anyone encountered this issue?
I noticed that setting /usr/share/libcamera/ipa/simple/ov01a10.yaml as follows on a dell xps 9320 seems to disable the camera's ability to adjust exposure automatiaclly based on light amount (often resulting in extremely dark images in sub-optimal conditions)
# SPDX-License-Identifier: CC0-1.0
%YAML 1.1
---
version: 1
algorithms:
- BlackLevel:
- Awb:
# - Agc:
- Adjust:
- Ccm:
ccms:
- ct: 6500
ccm: [ 2.25, -1.00, -0.25,
-0.45, 1.35, -0.20,
0.00, -0.60, 1.60 ]does anyone know a fix?
Update: somehow after the last firmware updates my camera (OVTI08F4) started to work. For now. Let's see if that is persistent, it had been occasionally detected earlier too, lottery style. What is new is that I no longer have countless of ipu6 instances when trying to access the camera with a browser, I can actually use the camera now.
@halogene: "countless of ipu6 instances": if your browser is Firefox, try setting media.webrtc.camera.allow-pipewire to true in about:config.
@all: FYI: I found this blog article to be very helpful to understand the difference between the old and new camera stack:
https://jetm.github.io/blog/posts/ipu6- … a-on-linux
It helped me to remove several unnecessary dependencies, and solve the suspend/resume problem.
However, it didn't help me to fix the "green tint" problem, because I don't have the right CCM parameters for my ov02e10 camera driver.
Maybe switching to libcamera-git might help, let's see...
alba4k wrote:
I noticed that setting /usr/share/libcamera/ipa/simple/ov01a10.yaml as follows on a dell xps 9320 seems to disable the camera's ability to adjust exposure automatiaclly based on light amount (often resulting in extremely dark images in sub-optimal conditions)
# SPDX-License-Identifier: CC0-1.0 %YAML 1.1 --- version: 1 algorithms: - BlackLevel: - Awb: # - Agc: - Adjust: - Ccm: ccms: - ct: 6500 ccm: [ 2.25, -1.00, -0.25, -0.45, 1.35, -0.20, 0.00, -0.60, 1.60 ]does anyone know a fix?
I have the same computer, I notice at least on firefox it seems to adjust my brightness but yeah, the quality is pretty rough even with some of those adjustments. Would love a better solution because this is by far my biggest hangup using arch/cachy atm.
dmoebius wrote:
@halogene: "countless of ipu6 instances": if your browser is Firefox, try setting media.webrtc.camera.allow-pipewire to true in about:config.
I already had that setting active, but it still showed all the ipu6 instances nevertheless (provided the camera got recognized at all sporadically).
Now since 6.19.8 it works reliably, so far. Albeit with terrible quality, but well.
peter.g wrote:
My Dell XPS 16 ipu6 camera has been working with qcam since Linux kernel 6.16 landed last year, but the libcamera 0.6 --> 0.7 update last month broke it. I downgraded the affected packages but want to know a more permanent solution. Has anyone encountered this issue?
For me the camera worked on March 6, but no longer does. And that was already 0.7.0. (ov02c10)
I'm puzzled
I have a Lenovo X1 Nano with a OV2740 Camera (https://wiki.archlinux.org/title/Lenovo … no_(Gen_2))
I was finally able to get the cam working with the help of Claude Code Agent, below a summary of what the LLM did in case its helpful to anyone
* [GUIDE] Getting IPU6 webcam working on Lenovo X1 Nano (and similar ThinkPads) for Zoom/Meet
*Hardware:* Lenovo X1 Nano | Sensor: OV2740 (ipu6) | Kernel: 6.19.11-arch1-1
The ipu6 camera doesn't expose a standard v4l2 capture device, so apps like Zoom and Google Meet
can't use it directly. The solution is to bridge libcamera → v4l2loopback using GStreamer.
* 1. Required packages
#+begin_src bash
sudo pacman -S gstreamer gst-plugins-base gst-plugins-good gst-plugin-libcamera v4l2loopback-dkms v4l-utils
#+end_src
* 2. Load v4l2loopback at boot
#+begin_src bash
echo "v4l2loopback" | sudo tee /etc/modules-load.d/v4l2loopback.conf
echo 'options v4l2loopback devices=1 video_nr=0 card_label="Dummy video device"' | sudo tee /etc/modprobe.d/v4l2loopback.conf
#+end_src
Reboot or load manually: ~sudo modprobe v4l2loopback devices=1 video_nr=0~
* 3. Verify libcamera detects the camera
#+begin_src bash
cam --list
#+end_src
Should show something like ~_SB_.PC00.LNK1~ (Internal front camera).
* 4. Create a systemd user service for the bridge
File: =~/.config/systemd/user/camera-bridge.service=
#+begin_src ini
[Unit]
Description=libcamera to v4l2loopback bridge
After=graphical-session.target
[Service]
ExecStart=gst-launch-1.0 libcamerasrc ! video/x-raw,width=1280,height=720,framerate=30/1 ! videoconvert ! video/x-raw,format=YUY2 ! v4l2sink device=/dev/video0 sync=false
Restart=on-failure
[Install]
WantedBy=graphical-session.target
#+end_src
Enable it:
#+begin_src bash
systemctl --user daemon-reload
systemctl --user enable --now camera-bridge.service
#+end_src
* 5. Select the device in Zoom/Meet
- In Zoom: Settings → Video → select *"Dummy video device (0x0000)"*
- In Google Meet: Settings → Video → same device.
* Notes
- ~sync=false~ in the pipeline is important — without it the stream may stall
- Only one app can use libcamera at a time — if another app (e.g. Kamoso) has the camera open, the bridge won't start
- ~v4l2-relayd~ does not work on this setup — use gst-launch directly
- To debug: ~systemctl --user status camera-bridge.service~
That's my fork of gc2607-v4l2-driver: https://github.com/adubovskoy/gc2607-v4l2-driver
It's for Huawei Matebook X Pro 2024. Tested and works.
I got the OV02C10 camera working on a Dell XPS 13 9340 with Arch Linux.
My setup:
Linux 7.0.3
KDE Plasma / Wayland
OVTI02C1:00 -> ov02c10AUR packages used:
intel-ipu6-dkms-git
intel-ipu6-camera-bin
intel-ipu6-camera-hal-git
icamerasrc-git
v4l2loopback-dkms
v4l2-relaydThe camera works through Intel IPU6 HAL + icamerasrc. I then bridge it to a normal webcam device with v4l2loopback.
I had to make several local changes.
1. In /etc/camera/ipu6epmtl/libcamhal_profile.xml, I limited availableSensors to:
2. In /etc/camera/ipu6epmtl/sensors/ov02c10-uf.xml, I hardcoded the media entity names for my machine:
ov02c10 17-0036
Intel IPU6 CSI2 4
Intel IPU6 ISYS Capture 323. I had to add uaccess for /dev/ipu-psys0. Without this, icamerasrc failed as a normal user with:
Failed to open PSYS, error: Permission deniedMy udev rule is:
SUBSYSTEM=="intel-ipu6-psys", TAG+="uaccess"4. After a reboot, the camera broke again because the sensor entity name changed:
ov02c10 17-0036 -> ov02c10 16-0036The CSI and capture entity names stayed the same, but the sensor subdev name changed. Since the HAL was doing exact matching, it failed to find the sensor subdev.
I fixed this with a small ipu6-camera-hal patch. See the PR below for details.
Related PR:
https://github.com/intel/ipu6-camera-hal/pull/173
Detailed notes are here, but they are written in Chinese:
https://soragoto.io/posts/xps13-9340/camera/
Maybe this helps other OV02C10 / XPS 13 9340 users.
A little update on my setup described in post: https://bbs.archlinux.org/viewtopic.php … 1#p2282711
I have been able to fix the flickering issue by making two changes
1: Change the gstreamer command I use to:
gst-launch-1.0 libcamerasrc name=hi556 ! video/x-raw,framerate=15/1 ! queue leaky=downstream max-size-buffers=2 ! videoconvert ! video/x-raw,format=NV12,framerate=15/1 ! v4l2sink name=v4l2sink-hi556 device=/dev/video60 sync=falsechanging the resolution somehow always resulted in a blank/white image. So I keep that the same.
2: Created a hi556 calibration file and disabled Agc. Also changed the contrast and gamma to slightly improve the overexposure.
cat /usr/share/libcamera/ipa/simple/hi556.yaml
%YAML 1.1
---
version: 1
algorithms:
- BlackLevel:
- Awb:
- Adjust:
- Agc:
enabled: false
controls:
- Contrast: 0.7 # reduces harsh highlights, default is 1.0
- Gamma: 2.0 # higher gamma darkens bright areas more than shadowsI'm now able to use my webcam for work. The image quality is still bad but its workable
Last edited by merijn (Today 13:28:50)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。