I am reporting an issue with the integrated camera on an Intel Lunar Lake laptop running Fedora 43. The system has an Intel IPU7 and an integrated MIPI camera. The IPU7 driver loads correctly, firmware is found and the camera sensor is detected by the kernel. However, the camera is not usable in userspace. libcamera does not detect any available camera devices. I followed the guidance described in Hans de Goede’s blog post about Intel MIPI cameras on Linux: https://hansdegoede.dreamwidth.org/31089.html and here: https://bugzilla.redhat.com/show_bug.cgi?id=2413656#c1, but they do not resolve the issue on Lunar Lake / IPU7. This looks like kernel support is present, but the libcamera userspace stack is still incomplete for IPU7 on Fedora, resulting in no functional camera pipeline. Runnig: systemctl --user restart pipewire systemctl --user restart wireplumber had no effect - the issue persists. Hardware Platform: Intel Lunar Lake IPU: Intel IPU7 Camera sensor: OVTI02C1 (detected by kernel) Laptop: Dell XPS 13 9350 model 04PF4P (custom Lunar Lake build) Software Fedora 43 Kernel: 6.17.11-300.fc43.x86_64 libcamera: 0.5.2 Reproducible: Always Steps to Reproduce: 1. Install Fedora 43 on an Intel Lunar Lake laptop with IPU7 and integrated MIPI camera. 2. Make sure the system is fully updated, including the kernel and libcamera. 3. Open a terminal. 4. Run dmesg | grep -i ipu to verify that the kernel detects the camera sensor (OVTI02C1). 5. Run ls /dev/media* to confirm /dev/media0 exists. 6. Run qcam. Actual Results: No camera is detected by libcamera or camera applications. qcam [0:21:42.668085008] [7852] INFO Camera camera_manager.cpp:330 libcamera v0.5.2 [0:21:42.687731328] [7865] INFO SimplePipeline simple.cpp:1687 No sensor found for /dev/media0 No camera detected Expected Results: The integrated camera should be detected by libcamera and usable in applications.
Created attachment 2118799 [details] journalctl -b 0 -k
Created attachment 2118812 [details] dmesg -w
Created attachment 2118813 [details] lsusb
Created attachment 2118814 [details] i2c-devices
Created attachment 2118815 [details] spi-devices
Created attachment 2118816 [details] grep-ipu
Created attachment 2118817 [details] v4l2-ctl--listdevices
Looking at your journalctl -k output it looks like you never did the: sudo insmod intel_cvs.ko command from the workaround instructions. If everything is setup properly this should result in a line like this in the journactl -k / dmesg output: Oct 10 12:51:20 saturn kernel: Intel CVS driver i2c-INTC10E0:00: cvs_i2c_probe:Transfer of ownership success which is not in your logs. Note the workaround instructions where missing a note about secureboot needing to be disabled to load the out of tree kernel module. I've added new updated workaround instructions to bug 2413656 comment 2. If you've secureboot enabled and run the: sudo insmod intel_cvs.ko command then you should see the following in your kernel logs: de nov. 08 09:53:09 patufet kernel: Loading of unsigned module is rejected which is also not there.
Hi Hans! Thank you so much for your reply and advise! I did followed all of the steps and I repeated that twice yesterday and again today just to be sure, but the camera is not working - libcamera applications continue to fall back to SimplePipeline and report: No sensor found for /dev/media0 I also do not see the expected messages in journalctl that are mentioned in this bug. When I run sudo insmod intel_cvs.ko I do not get Intel CVS driver i2c-INTC10E0:00: cvs_i2c_probe:Transfer of ownership success in the journalctl - I am not sure why. The secure boot is disabled - I restarted the laptop and running all of the above instructions have no effect. I am attaching another joutnalctl + a screenshot of the terminal where I ran again the commands today. I would apprecite any help here, as I don't understand why this is not working or what am I missing. Please let me know if there are specific debug flags or logs I should collect.
Created attachment 2118937 [details] journalctl-1
Created attachment 2118938 [details] terminal-screenshot
Adding also the teminal output during make vision-drivers in the attached files.
Created attachment 2118940 [details] make-vision-drivers-terminal-screenshot
It looks like these errors are the problem: Dec 16 11:23:39 fedora kernel: Intel CVS driver i2c-INTC10DE:00: magic number in dev response not supported Dec 16 11:23:39 fedora kernel: Intel CVS driver i2c-INTC10DE:00: cvs_find_magic_num_support:Device protocol is 1.0 Dec 16 11:23:39 fedora kernel: Intel CVS driver i2c-INTC10DE:00: cvs_common_probe:set_host_identifier cmd failed Dec 16 11:23:39 fedora kernel: Intel CVS driver i2c-INTC10DE:00: probe with driver Intel CVS driver failed with error -5 I suggest that you file a bug report at the intel vision drivers git repository: https://github.com/intel/vision-drivers/issues
Thank you Hans for your help! I filed an issue: https://github.com/intel/vision-drivers/issues/31