You are not logged in.
itayf wrote:Sorry to bring even more pessimism, after upgrading to 6.10, using using Dell XPS 13 Plus (9320) the camera doesn't even seem to be recognized.
Have anyone with that laptop got something else?
I'm using the same laptop, the camera isn't recognized too.
dmesg:
> sudo dmesg | grep ipu6 [ 1.764285] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 1.764485] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 1.764518] intel-ipu6 0000:00:05.0: Direct firmware load for intel/ipu/ipu6ep_fw.bin failed with error -2 [ 1.764521] intel-ipu6 0000:00:05.0: error -ENOENT: Requesting signed firmware intel/ipu/ipu6ep_fw.bin failed [ 1.764523] intel-ipu6 0000:00:05.0: probe with driver intel-ipu6 failed with error -2
I got the same error because the firmware was stored on an encrypted device. I fixed it by adding the complete path to the firmware in FILES array of mkinitcpio.conf (and generate again the image). I don't know wether it is a valid solution, but the firmware is now loaded.
Last edited by bdeloynes (2024-09-02 16:19:05)
Offline
Have you installed external intel driver package?
In my my dmesg (running on XPS 9320 6.10.7-arch1-1) i have only:
lvanni@XPS-LV:~$ sudo dmesg | grep ipu6
[ 16.820656] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 16.821391] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff
[ 16.829951] intel-ipu6 0000:00:05.0: FW version: 20230925
[ 16.830489] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff
[ 16.834005] intel-ipu6 0000:00:05.0: FW version: 20230925
.....
and my camera isn't working too.
Last edited by lvanni (2024-09-02 20:14:17)
Offline
According to this debian bug (https://bugs.debian.org/cgi-bin/bugrepo … ug=1074441), it seems that IPU6 is only fully functional with kernel 6.11. Is this the case for Archlinux?
I don't see how that issue is relevant, I have all those config flags set in my 6.10.5 kernel and still no camera, at least not in an XPS 13+
Offline
Have you installed external intel driver package?
In my my dmesg (running on XPS 9320 6.10.7-arch1-1) i have only:
lvanni@XPS-LV:~$ sudo dmesg | grep ipu6 [ 16.820656] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 16.821391] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 16.829951] intel-ipu6 0000:00:05.0: FW version: 20230925 [ 16.830489] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 16.834005] intel-ipu6 0000:00:05.0: FW version: 20230925 .....
and my camera isn't working too.
I have the same output but also the one with
deferred probe pending: intel-ipu6: IPU6 bridge init failed
Last edited by potuz (2024-09-04 14:31:44)
Offline
So I have been doing some research because I have the same problem where the camera is not recognized (running on Manjaro 6.10 on a Dell Precision 5490). It seems that dkms is failing when building the drivers. In fact if I run
sudo dkms autoinstall -k $(uname -r)
this is the output:
❯ sudo dkms autoinstall -k $(uname -r)
Sign command: /usr/lib/modules/6.10.6-10-MANJARO/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j22 KERNELRELEASE=6.10.6-10-MANJARO KERNELRELEASE=6.10.6-10-MANJARO KERNEL_SRC=/usr/lib/modules/6.10.6-10-MANJARO/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.10.6-10-MANJARO (x86_64)
Consult /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/make.log for more information.
dkms autoinstall on 6.10.6-10-MANJARO/x86_64 succeeded for v4l2loopback
dkms autoinstall on 6.10.6-10-MANJARO/x86_64 failed for ipu6-drivers(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
If I take a look at the log, this is what is shown:
make -C /lib/modules/6.10.6-10-MANJARO/build M=/var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build modules
make[1]: Entering directory '/usr/lib/modules/6.10.6-10-MANJARO/build'
CC [M] /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.o
In file included from /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu-buttress.h:9,
from /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.c:20:
/var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.h:75:23: error: field ‘buttress’ has incomplete type
75 | struct ipu_buttress buttress;
| ^~~~~~~~
make[5]: *** [scripts/Makefile.build:244: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.o] Error 1
make[4]: *** [scripts/Makefile.build:485: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6] Error 2
make[3]: *** [scripts/Makefile.build:485: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel] Error 2
make[2]: *** [/usr/lib/modules/6.10.6-10-MANJARO/build/Makefile:1934: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build] Error 2
make[1]: *** [Makefile:240: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.10.6-10-MANJARO/build'
make: *** [Makefile:121: all] Error 2
So there seems to be a problem with the driver itself. If you guys could try the same so we can see if that's actually the problem here it would be great!
Offline
So I have been doing some research because I have the same problem where the camera is not recognized (running on Manjaro 6.10 on a Dell Precision 5490). It seems that dkms is failing when building the drivers. In fact if I run
sudo dkms autoinstall -k $(uname -r)
this is the output:
❯ sudo dkms autoinstall -k $(uname -r) Sign command: /usr/lib/modules/6.10.6-10-MANJARO/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j22 KERNELRELEASE=6.10.6-10-MANJARO KERNELRELEASE=6.10.6-10-MANJARO KERNEL_SRC=/usr/lib/modules/6.10.6-10-MANJARO/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.10.6-10-MANJARO (x86_64) Consult /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/make.log for more information. dkms autoinstall on 6.10.6-10-MANJARO/x86_64 succeeded for v4l2loopback dkms autoinstall on 6.10.6-10-MANJARO/x86_64 failed for ipu6-drivers(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information.
If I take a look at the log, this is what is shown:
make -C /lib/modules/6.10.6-10-MANJARO/build M=/var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build modules make[1]: Entering directory '/usr/lib/modules/6.10.6-10-MANJARO/build' CC [M] /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.o In file included from /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu-buttress.h:9, from /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.c:20: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.h:75:23: error: field ‘buttress’ has incomplete type 75 | struct ipu_buttress buttress; | ^~~~~~~~ make[5]: *** [scripts/Makefile.build:244: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6/../ipu.o] Error 1 make[4]: *** [scripts/Makefile.build:485: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel/ipu6] Error 2 make[3]: *** [scripts/Makefile.build:485: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build/drivers/media/pci/intel] Error 2 make[2]: *** [/usr/lib/modules/6.10.6-10-MANJARO/build/Makefile:1934: /var/lib/dkms/ipu6-drivers/r165.cfb7af1e5/build] Error 2 make[1]: *** [Makefile:240: __sub-make] Error 2 make[1]: Leaving directory '/usr/lib/modules/6.10.6-10-MANJARO/build' make: *** [Makefile:121: all] Error 2
So there seems to be a problem with the driver itself. If you guys could try the same so we can see if that's actually the problem here it would be great!
I've tried on my archlinux system. I was not using dkms, I've installed it and run the sudo dkms autoinstall -k $(uname -r) command which exits immediately without any message.
I do not know if it is related, but since some days in the dmesg I got this error:
vsc-tp spi-INTC1094:00: probe with driver vsc-tp failed with error -22
That seems related to the ipu6 somehow.
Last edited by Xwang (2024-09-07 17:01:33)
Offline
Just adding 0.02 here, from a read of that Debian bug, I checked the config for 6.10.9-arch1-2 and it looks like Arch has everything needed enabled:
% for mod in `cat mod.txt`
do
zcat /proc/config.gz | grep $mod
done
CONFIG_INTEL_MEI_VSC_HW=m
CONFIG_INTEL_MEI_VSC_HW=m
CONFIG_INTEL_MEI_VSC=m
CONFIG_I2C_LJCA=m
CONFIG_SPI_LJCA=m
CONFIG_GPIO_LJCA=m
CONFIG_INTEL_VSC=m
CONFIG_IPU_BRIDGE=m
CONFIG_VIDEO_OV2740=m
CONFIG_USB_LJCA=m
CONFIG_VIDEO_INTEL_IPU6=m
I have a new Dell Latitude 7450 from work and the camera still doesn't work on it, even though everything looks like it's loaded properly and I see no firmware errors in dmesg etc.
Offline
According to this debian bug (https://bugs.debian.org/cgi-bin/bugrepo … ug=1074441), it seems that IPU6 is only fully functional with kernel 6.11. Is this the case for Archlinux?
I just enabled the repository core-testing and installed 6.11.0, but still no camera working.
> v4l2-ctl --all
Driver Info:
Driver name : isys
Card type : ipu6
Bus info :
Driver version : 6.11.0
Capabilities : 0xa4a00001
Video Capture
Metadata Capture
I/O MC
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x24a00001
Video Capture
Metadata Capture
I/O MC
Streaming
Extended Pix Format
Priority: 2
Video input : 0 (Intel IPU6 ISYS Capture 0: ok)
Format Video Capture:
Width/Height : 1920/1080
Pixel Format : 'BG12' (12-bit Bayer BGBG/GRGR)
Field : None
Bytes per Line : 3840
Size Image : 4151040
Colorspace : Raw
Transfer Function : Default (maps to None)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Full Range)
Flags :
Format Metadata Capture:
Sample Format : 'MET8' (8-bit Generic Metadata)
Buffer Size : 9600
I am on a HP Spectre x360 (16-aa0xxx).
However, something seems to have found a sensor at least.
> sudo dmesg | grep ipu6
[ 11.584332] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 11.584599] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x80000000 mask 0x0
[ 11.600419] intel-ipu6 0000:00:05.0: FW version: 20230925
[ 11.601608] intel-ipu6 0000:00:05.0: Found supported sensor OVTI08F4:00
[ 11.602266] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 11.604573] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 11.648034] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 11.698943] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 11.698954] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6
Offline
Hello,
New Dell Precision 5490 here, I just moved to Arch. I read your very interesting thread, understanding that the problem is not really over yet.
I installed linux-mainline, but I am a bit lost with the AUR packages about ipu6 and their git version: are these necessary for 6.11 or are they all integrated (included the "bin" package)?
Also, for what it's worth (since I might be missing a packages), on my end, there are no video devices and dmesg does not even mention a sensor.
Cheers,
-Benoit.
Offline
Hello everyone,
I wanted to share how I resolved a permission issue with my IPU6 webcam. Like some of you, I found that the camera only worked with `sudo` and not with my normal user. To fix this, I had to remove the `RestrictNamespaces` line from the systemd services.
This bug has been reported for WirePlumber; you can check the issue here: https://gitlab.freedesktop.org/pipewire … issues/466.
I hope this helps anyone facing the same problem!
Best regards,
Émilien
Offline
Where exactly did you remove this `RestrictNamespaces` line from? It does not appear in my `/usr/lib/systemd/user/wireplumber.service` . The issue you're linking to is closed, and there's this PR that removed this line more than a year ago: https://gitlab.freedesktop.org/pipewire … quests/511
Offline
Hi,
I'm a gentoo user
it's was in this file /usr/lib/systemd/user/pipewire.service
In my logs I was :
[0:03:34.163996549] [1965] ERROR Process process.cpp:312 Failed to unshare execution context: Ope>
Offline
ah, thanks for clarifying! I can confirm this exists on my Arch installation as well.
Offline
FYI, I just managed to get it working on openSUSE Tumbleweed on a XPS 13 9340 laptop using the out of tree drivers (https://github.com/intel/ipu6-drivers) with kernel 6.11.
If anyone is interested in replicating this setup with AUR packages, all sources are available here: https://build.opensuse.org/project/show … eira:xps13
Relevant packages are gstreamer-plugins-icamerasrc, intel-ipu6, ipu6-camera-bins, ipu6-camera-hal, v4l2-relayd
A lot of patches from Ubuntu are used. Since Dell officially supports these cameras on Ubuntu, I basically tried to match their sources:
https://git.launchpad.net/ubuntu/+source/ipu6-drivers
https://launchpad.net/~oem-solutions-gr … intel-ipu6
The kernel is the default tumbleweed kernel (from the devel project as 6.11 is not yet in the TW repos) with an additional patch from Ubuntu's kernel, which seems to be needed for ipu6-drivers:
https://gist.github.com/xTeixeira/36efa … 3d2d017671
For whatever reason the camera doesn't work with cheese, but works fine with OBS studio, chromium and firefox (needs "media.webrtc.camera.allow-pipewire" set to "false").
good luck!
Offline
The camera requires libcamera version >= 0.3.2 which was released Sep 24th. Its not yet available in the repos so I built my own package. This version fixes a buglet where ipu6 was not active.
After installing the updated libcamera (no other packages changed) " cam -l" now shows the camera and qcam sort of works but only if change the 'renderer'
i.e.
qcam -r gles
The image is super dark, but otherwise works - so not right yet but closer.
Offline
I've tried the command again on my Dell Latitude 9330 2in1 today after the update of libcamera to 0.3.2 and still I get the very similar messages as before (and still no camera available):
Firmware is :
pacman -Ql linux-firmware | grep ipu6
linux-firmware /usr/lib/firmware/intel/ipu/ipu6_fw.bin.zst
linux-firmware /usr/lib/firmware/intel/ipu/ipu6ep_fw.bin.zst
linux-firmware /usr/lib/firmware/intel/ipu/ipu6epadln_fw.bin.zst
linux-firmware /usr/lib/firmware/intel/ipu/ipu6epmtl_fw.bin.zst
linux-firmware /usr/lib/firmware/intel/ipu/ipu6se_fw.bin.zst
dmesg:
sudo dmesg | grep ipu6
[ 5.017375] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 5.017654] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff
[ 5.024057] intel-ipu6 0000:00:05.0: FW version: 20230925
[ 5.031892] intel-ipu6 0000:00:05.0: IPU6-v3[465d] hardware version 5
v4l2 somehow recognizes the camera, but no bus info is available:
v4l2-ctl --all
Driver Info:
Driver name : isys
Card type : ipu6
Bus info :
Driver version : 6.10.10
Capabilities : 0xa4a00001
Video Capture
Metadata Capture
I/O MC
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x24a00001
Video Capture
Metadata Capture
I/O MC
Streaming
Extended Pix Format
Priority: 2
Video input : 0 (Intel IPU6 ISYS Capture 0: ok)
Format Video Capture:
Width/Height : 1920/1080
Pixel Format : 'BG12' (12-bit Bayer BGBG/GRGR)
Field : None
Bytes per Line : 3840
Size Image : 4151040
Colorspace : Raw
Transfer Function : Default (maps to None)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Full Range)
Flags :
Format Metadata Capture:
Sample Format : 'MET8' (8-bit Generic Metadata)
Buffer Size : 9600
No camera is available in cam -l or using qcam
sudo cam -l
[0:03:08.520830382] [2948] ERROR IPAModule ipa_module.cpp:171 Symbol ipaModuleInfo not found
[0:03:08.520852855] [2948] ERROR IPAModule ipa_module.cpp:291 v4l2-compat.so: IPA module has no valid info
[0:03:08.520865144] [2948] INFO Camera camera_manager.cpp:325 libcamera v0.3.2
[0:03:08.530949599] [2949] INFO SimplePipeline simple.cpp:1548 No sensor found for /dev/media0
Available cameras:
Offline
I notice a couple of things maybe someone has ideas.
1) running 'cam -l' as user has a warning.
No static properties available for 'ov01a10'
WARN CameraSensorProperties camera_sensor_properties.cpp:295 Please consider updating
Running as root adds a suggestion to provide this via config instead of static c++ - where for my ov01a10 sensor the properties are indeed missing
(c++ file is src/libcamera/src/libcamera/sensor/camera_sensor_properties.cpp)
When run as root it offers:
Configuration file 'ov01a10.yaml' not found for IPA module 'simple', falling back to 'uncalibrated.yaml'
WARN IPASoft soft_simple.cpp:94 IPASoft: Failed to create camera sensor helper for ov01a10
2) There seems to be a permission problem for non-root on /dev/dmabuf :
ERROR DmaBufAllocator dma_buf_allocator.cpp:116 Could not open any dma-buf provider
ERROR SoftwareIsp software_isp.cpp:88 Failed to create DmaBufAllocator object
I tried fixing this by putting this rule into /etc/udev/rules.d/99-udmabuf-uaccess.rules
ACTION=="add", SUBSYSTEM=="misc", KERNEL=="udmabuf", TAG+="uaccess"
But even after running 'udevadm trigger' this had no effect - perhaps someone can suggest how to fix this.
cam must be run as non-root to do anything useful.
Ok so thats as far as my explorations have taken me - I did check that the kernel drivers seem to be there in 6.11+.
So libcamera and udev look to be the key.
According to my browsing libcamera issues - v4l2 is a software incomplete api wrapper to provide "some" v4l2 support - for all testing I suggest avoiding anything v4l related and stick with cam and qcam.
Edit: I also installed pipewire-libcamera which may be required as well.
Last edited by GeneArch (2024-09-29 15:06:52)
Offline
2) There seems to be a permission problem for non-root on /dev/dmabuf :
ERROR DmaBufAllocator dma_buf_allocator.cpp:116 Could not open any dma-buf provider ERROR SoftwareIsp software_isp.cpp:88 Failed to create DmaBufAllocator object
I tried fixing this by putting this rule into /etc/udev/rules.d/99-udmabuf-uaccess.rules
ACTION=="add", SUBSYSTEM=="misc", KERNEL=="udmabuf", TAG+="uaccess"
But even after running 'udevadm trigger' this had no effect - perhaps someone can suggest how to fix this.
cam must be run as non-root to do anything useful.
See https://github.com/systemd/systemd/comm … 5ffe357a57 for the relevant systemd fix. I applied that manually and ran
# udevadm control --reload-rules
# udevadm trigger
And now `cam -l` works as my regular user.
To get it to work in firefox I also had to enable media.webrtc.camera.allow-pipewire in about:config.
Offline
See https://hansdegoede.dreamwidth.org/28841.html → https://fedoraproject.org/wiki/Changes/ … ra_support. Hopefully this highlights the needed changes, should easily portable from Fedora.
Last edited by icar (2024-10-03 02:13:12)
Offline
..
See https://github.com/systemd/systemd/comm … 5ffe357a57 for the relevant systemd fix. I applied that manually and ranAnd now `cam -l` works as my regular user.
Excellent thanks @tavianator.
As an alternative to modifying the systemd provided rule (/usr/lib/udev/rules.d/70-xx) i changed my local rule file to /etc/udev/rules.d/69-xxx which works fine.
This can be removed once systemd updated rule makes it way into the Arch package.
thank you.
Last edited by GeneArch (2024-10-03 11:30:45)
Offline
I note that cheese does not work for me - I tried using 'cheese' and 'cheese -d xxx where xxx is /dev/video as suggested by v4l-ctl --list-devices. Fails with device not found.
Good progress but not sure what, aside from the (q)cam test tools would work.
Offline
You might have more luck with https://archlinux.org/packages/extra/x86_64/snapshot/
Offline
Thanks - tried - same problem - doesn't find the camera
Offline
Looks like it is not that straightforward: Fedora 41 will ship with a number of camera's supported and working in Firefox and Gnome Snapshot out of the box: https://hansdegoede.dreamwidth.org/28841.html
Maybe the Fedora patches can be useful to Arch devs as well?
Offline
Things finally work here with Gnome Snapshot after upgrading everything to the latest (I don't have any testing repo enabled). The one thing I was missing is the `pipewire-libcamera` package.
Firefox strangly still shows a list of ~20 cameras to choose from, and it seems like all of them do not work.
Offline