Bug 2337628 - IPU6 camera on Dell Precision 5480 laptop not working
Summary: IPU6 camera on Dell Precision 5480 laptop not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-14 16:57 UTC by cmatic
Modified: 2025-05-26 11:13 UTC (History)
16 users (show)

Fixed In Version: kernel-6.14.6-300.fc42
Clone Of:
Environment:
Last Closed: 2025-05-26 11:13:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
"journalctl -b 0 -k" (148.51 KB, text/plain)
2025-01-14 16:57 UTC, cmatic
no flags Details
journalctl -b 0 -k (193.67 KB, text/plain)
2025-05-26 08:38 UTC, cmatic
no flags Details
ls -l /sys/bus/spi/devices/ (291 bytes, text/plain)
2025-05-26 08:39 UTC, cmatic
no flags Details
ls -l /sys/bus/i2c/devices/ (2.92 KB, text/plain)
2025-05-26 08:39 UTC, cmatic
no flags Details
lsusb (1.29 KB, text/plain)
2025-05-26 08:39 UTC, cmatic
no flags Details

Description cmatic 2025-01-14 16:57:00 UTC
Webcam on my laptop is not recongnized :

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 002 Device 002: ID 0951:16b0 Kingston Technology Dell USBBus 002 Device 003: ID 1d5c:5500 Fresco Logic Frescologic USB3.1Gen2 HUBBus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet AdapterBus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 003 Device 003: ID 0b0e:0305 GN Netcom Jabra EVOLVE Link MSBus 003 Device 005: ID 8086:0b63 Intel Corp. USB BridgeBus 003 Device 008: ID 27c6:63cc Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISCBus 003 Device 010: ID 8087:0033 Intel Corp. AX211 BluetoothBus 003 Device 016: ID 1d5c:5510 Fresco Logic Frescologic USB2.0 HUBBus 003 Device 017: ID 413c:c010 Dell Computer Corp. Dell DA310Bus 003 Device 018: ID 248a:ff0f Maxxter Wireless ReceiverBus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

 sudo dmesg | grep ipu6
[   33.274074] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[   33.274274] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   33.355645] intel-ipu6 0000:00:05.0: FW version: 20230925

 uname -a
Linux localhost-live 6.11.4-301.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 20 15:02:33 UTC 2024 x86_64 GNU/Linux

sudo LIBCAMERA_LOG_LEVELS=0 cam --list
[0:22:42.360528137] [7940] DEBUG IPAModule ipa_module.cpp:333 ipa_ipu3.so: IPA module /usr/lib64/libcamera/ipa_ipu3.so is signed[0:22:42.360610490] [7940] DEBUG IPAManager ipa_manager.cpp:235 Loaded IPA module '/usr/lib64/libcamera/ipa_ipu3.so'[0:22:42.360662735] [7940] DEBUG IPAModule ipa_module.cpp:333 ipa_soft_simple.so: IPA module /usr/lib64/libcamera/ipa_soft_simple.so is signed[0:22:42.360687930] [7940] DEBUG IPAManager ipa_manager.cpp:235 Loaded IPA module '/usr/lib64/libcamera/ipa_soft_simple.so'[0:22:42.360698328] [7940]  INFO Camera camera_manager.cpp:325 libcamera v0.3.2[0:22:42.360888830] [7943] DEBUG Camera camera_manager.cpp:73 Starting camera manager[0:22:42.361334196] [7943] DEBUG Camera camera_manager.cpp:138 Found registered pipeline handler 'ipu3'[0:22:42.361361362] [7943] DEBUG Camera camera_manager.cpp:138 Found registered pipeline handler 'simple'[0:22:42.361373152] [7943] DEBUG Camera camera_manager.cpp:138 Found registered pipeline handler 'uvcvideo'
Available cameras:

ls /sys/bus/i2c/devices
i2c-0  i2c-1  i2c-10  i2c-11  i2c-12  i2c-13  i2c-14  i2c-15  i2c-16  i2c-18  i2c-19  i2c-2  i2c-20  i2c-3  i2c-4  i2c-5  i2c-6  i2c-7  i2c-8  i2c-9  i2c-OVTI01AB:00  i2c-VEN_0488:00  i2c-WACF3233:00

find /sys/devices -name modalias | xargs grep -h acpi | grep -Ev 'PNP|LNX' | sort -u

acpi:ACPI0003:acpi:ACPI0007:acpi:ACPI000C:acpi:ACPI000E:acpi:INT3472:acpi:INTC1009:acpi:INTC100A:acpi:INTC100B:acpi:INTC100C:acpi:INTC100D:acpi:INTC1055:acpi:INTC1078:acpi:INTC10A0:acpi:INTC10A1:acpi:NVDA0820:acpi:OVTI01A0:acpi:OVTI01AB:acpi:STM0176:MSFT0101:platform:acpi-cpufreq



Reproducible: Always

Comment 1 cmatic 2025-01-14 16:57:55 UTC
Created attachment 2065974 [details]
"journalctl -b 0 -k"

Comment 2 cmatic 2025-01-22 08:52:10 UTC
Working with kernel 6.6 and drivers from intel (https://github.com/intel/ipu6-drivers) :

sudo dmesg | grep ipu6
[   13.882427] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[   13.882574] intel-ipu6 0000:00:05.0: Device 0xa75d (rev: 0x0)
[   13.882872] intel-ipu6 0000:00:05.0: physical base address 0x628e000000
[   13.882874] intel-ipu6 0000:00:05.0: mapped as: 0x000000003ced395f
[   13.883609] intel-ipu6 0000:00:05.0: IPU in secure mode
[   13.883612] intel-ipu6 0000:00:05.0: IPU secure touch = 0x0
[   13.883613] intel-ipu6 0000:00:05.0: IPU camera mask = 0x0
[   13.900974] intel-ipu6 0000:00:05.0: IPC reset done
[   13.900992] intel-ipu6 0000:00:05.0: cpd file name: intel/ipu6ep_fw.bin
[   13.902332] intel-ipu6 0000:00:05.0: FW version: 20230925
[   13.903096] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[   13.927201] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[   14.000820] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[   14.000907] intel-ipu6 0000:00:05.0: IPU6-v3 driver version 1.0
[   14.302676] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8
[   14.302944] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0
[   15.651163] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16
[   15.651186] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
[   16.724479] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16
[   16.724491] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
[   17.751963] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16
[   17.751983] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
[   18.773385] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16
[   18.773396] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
[   19.794314] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed -16
[   19.794326] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
[   23.922468] intel-ipu6-isys intel-ipu6-isys0: bind ov01a10 17-0036 nlanes is 1 port is 2
[   23.922904] intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed.

Comment 3 Hans de Goede 2025-05-23 22:43:49 UTC
Thank you for reporting this bug.

The problem seems to be these messages:

Jan 14 16:19:41 fedora kernel: vsc-tp spi-INTC1009:00: wait rom failed ret: -110
Jan 14 16:19:41 fedora kernel: intel_vsc intel_vsc: hw_reset failed ret = -110
Jan 14 16:19:42 fedora kernel: vsc-tp spi-INTC1009:00: wait rom failed ret: -110
Jan 14 16:19:42 fedora kernel: intel_vsc intel_vsc: hw_reset failed ret = -110
Jan 14 16:19:42 fedora kernel: vsc-tp spi-INTC1009:00: wait rom failed ret: -110
Jan 14 16:19:42 fedora kernel: intel_vsc intel_vsc: hw_reset failed ret = -110

Which should be fixed in recent kernels.

cmatic, can you please try updating to a Fedora kernel >= kernel-6.14.6-300.fc42 and then try again ?

If things still do not work, please collect and attach the logs described here:

https://fedoraproject.org/wiki/Changes/X86_MIPI_CameraHwEnablement#How_To_Test

Comment 4 cmatic 2025-05-26 08:37:44 UTC
Thank you for your response. 
On the new kernel the camera is well recognized but the image flashes constantly.

Comment 5 cmatic 2025-05-26 08:38:40 UTC
Created attachment 2091579 [details]
journalctl -b 0 -k

Comment 6 cmatic 2025-05-26 08:39:08 UTC
Created attachment 2091580 [details]
ls -l /sys/bus/spi/devices/

Comment 7 cmatic 2025-05-26 08:39:26 UTC
Created attachment 2091581 [details]
ls -l /sys/bus/i2c/devices/

Comment 8 cmatic 2025-05-26 08:39:42 UTC
Created attachment 2091582 [details]
lsusb

Comment 9 Hans de Goede 2025-05-26 08:49:57 UTC
(In reply to cmatic from comment #4)
> Thank you for your response. 
> On the new kernel the camera is well recognized but the image flashes
> constantly.

That is libcamera's autoexposure algorithm oscilating, this is a known issue which I need to look into. This is happening to lots of users so I'll prioritize looking into this.

Comment 10 Cristian Le 2025-05-26 08:52:32 UTC
Thanks for the info. Is there another bug to follow for that? We could probably mark this one as solved and migrate to the other bug if it exists.

Comment 11 Hans de Goede 2025-05-26 08:57:15 UTC
There is no other bug yet, but opening one is a good idea, so I've just done so.

Since the oscilating problem is not specific to the Dell Precision 5480 I'm closing this bug.

Comment 12 Hans de Goede 2025-05-26 09:05:49 UTC
Note the new bug is bug 2368538 .

Comment 13 Hans de Goede 2025-05-26 09:07:39 UTC
I just realized this only works because you have the usbio drivers from rpmfusion, this does not work with a stock Fedora kernel yet, re-opening.

Comment 14 Cristian Le 2025-05-26 09:19:25 UTC
Which package should I check from the rpmfusion? I had tested previously with various packages disabled, and now I have removed both `ipu6-camera-hal` and `akmod-intel-ipu6` and it still functions properly.

Comment 15 cmatic 2025-05-26 10:11:11 UTC
I don't think i have  installed usbio driver from rpmfusion : 

dnf list --installed | grep rpmfusion

akmod-nvidia.x86_64                                  3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
akmod-v4l2loopback.x86_64                            0.14.0-1.fc42                        rpmfusion-free
kmod-v4l2loopback.x86_64                             0.14.0-1.fc42                        rpmfusion-free
mplayer.x86_64                                       1.5.1-0.17.20250127svn.fc42          rpmfusion-free
mplayer-common.x86_64                                1.5.1-0.17.20250127svn.fc42          rpmfusion-free
nvidia-modprobe.x86_64                               3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64                           3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                               3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
rpmfusion-free-release.noarch                        42-1                                 rpmfusion-free
rpmfusion-nonfree-release.noarch                     42-1                                 rpmfusion-nonfree
steam.i686                                           1.0.0.83-1.fc42                      rpmfusion-nonfree-steam
v4l2loopback.x86_64                                  0.14.0-1.fc42                        rpmfusion-free
xorg-x11-drv-nvidia.x86_64                           3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64                      3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.i686                   3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64                 3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64                   3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.i686                        3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64                      3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64                     3:570.153.02-1.fc42                  rpmfusion-nonfree-nvidia-driver

Comment 16 Hans de Goede 2025-05-26 11:13:00 UTC
You're right I somehow mistakenly thought this laptop is using the usbio expander, but it is not, so lets close this.


Note You need to log in before you can comment on or make changes to this bug.