[09:03] Hi I'm trying to get a official camera module v1.3 to work with a raspberry pi 4 8Gb on ubuntu server 20.04.3. I apt-src installed libcamera, added start_x=1 to the usercfg.txt file and vcgencmd get_camera returns "supported=1 detected=1". Yet qcam or cam don't list the camera. [09:04] if I add dtoverlay=ov5647 to usercfg.txt, the vcgencmd get_camera returns "supported=1 detected=0" [09:04] I switched between dtoverlay=vc4-kms-v3d and dtoverlay=vc4-fkms-v3d [09:04] but this didn't seem to make a difference [09:09] (coming over from #ubuntu-server with this question) [09:25] @waveform, may this be an issue with options that can't be included from usercfg.txt? [09:35] (arm64) [14:15] hi johk, sorry -- I'm on holiday this week so haven't been paying much attention to IRC :) what interface are you trying to use with the camera (I'm not familiar with cam/qcam?) [14:19] on a couple of your other question: no start_x=1 doesn't work in usercfg.txt, which is a big part of the reason I removed that config/syscfg/usercfg split in groovy as a terrible mistake -- full story over in https://waldorf.waveform.org.uk/2020/boot-configuration-with-pibootctl.html. As far as kms/fkms goes, the only thing to remember is that kms isn't *entirely* compatible with the "classic" mmal-based camera interfaces because it lets the [14:19] kernel stomp all over the GPU, while fkms leaves the GPU in the hands of the (camera) firmware [14:20] but other than that, the mmal-based camera interfaces work happily with either fkms or with no (f)kms overlay at all [14:21] however, that's the mmal-based camera interfaces and those are considered "legacy" by raspberry pi at this point; everything's meant to be moving to libcamera (which will use camera-specific device-tree overlays and do most things via the linux kernel), but that's likely to be a relatively slow and painful transition as there's little in the way of high-level libraries built on libcamera currently [14:28] waveform, note that this seems to be 20.04 (old kernel/fw)