OV9281 DToverlay not loading kernel module

[zharr]

Yep, missing a bunch of I2C ones:

Code: [Select]

kernel/drivers/i2c/busses/i2c-robotfuzz-osif.ko:
kernel/drivers/i2c/busses/i2c-tiny-usb.ko:
kernel/drivers/i2c/muxes/i2c-mux-gpmux.ko: kernel/drivers/i2c/i2c-mux.ko kernel/drivers/mux/mux-core.ko
kernel/drivers/i2c/muxes/i2c-mux-pca954x.ko: kernel/drivers/i2c/i2c-mux.ko
kernel/drivers/i2c/muxes/i2c-mux-pinctrl.ko: kernel/drivers/i2c/i2c-mux.ko
kernel/drivers/i2c/i2c-mux.ko:my piCore 14 install only has.

Code: [Select]

kernel/drivers/i2c/algos/i2c-algo-bit.ko:
kernel/drivers/i2c/busses/i2c-bcm2708.ko:
kernel/drivers/i2c/busses/i2c-bcm2835.ko:
kernel/drivers/i2c/busses/i2c-gpio.ko: kernel/drivers/i2c/algos/i2c-algo-bit.ko
kernel/drivers/i2c/i2c-dev.ko:am I missing some critical packets in the upgrade? I am manually specifying which packets to install with a custom install script, so that is very much possible, though I would expect device-drivers for I2C to be in the base image

[Juanito]

Looking at piCore-16.x, all of the modules you mention as missing in piCore-14.x are in the base.

You could add them to the piCore-14.x analogy of /mnt/mmcblk0p1/modules-6.12.25-piCore-v7.gz?

[Paul_123]

mux drivers are rarely needed, and is likely not the cause of your problem

[zharr]

Well afaik the internal camera I2C is on a mux (I2C0 and I2C10). Even if the driver does not need that (and accesses it through VC somehow), I do need manual access to I2C10 in userspace for modifications to OV9281 registers.

Wrote a script that searches packages in repositories for files. And going through dependencies of modules, and trying to find them on the 14.x image, to see what's missing.
Made the following package from the modules:

Code: [Select]

#: unsquashfs -l i2c-modules-6.1.68-piCore-v7.tcz
squashfs-root
squashfs-root/lib
squashfs-root/lib/modules
squashfs-root/lib/modules/6.1.68-piCore-v7
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/busses
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/busses/i2c-robotfuzz-osif.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/busses/i2c-tiny-usb.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/i2c-mux.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/muxes
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/muxes/i2c-mux-gpmux.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/muxes/i2c-mux-pca954x.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/i2c/muxes/i2c-mux-pinctrl.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/mux
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/mux/mux-core.ko
squashfs-root/lib/modules/6.1.68-piCore-v7/kernel/drivers/mux/mux-gpio.ko
loaded it, then modprobed ov9281 - and it works! Well, /dev/video0 appears, will compile my program to see if anything else is missing.

I'd greatly appreciate if you could integrate that in the 14.x kernel - though it's easy enough to patch it back in in my setup scripts.

Also, unrelated, sorry: 15.x doesn't seem to supply armv6 packages, is Pi Zero 1 support dropped? Might try it out later, but I doubt it will work. Could switch straight to 15.x to see if everything works there (I do know the camera didn't work there either, I assume it's also missing the I2C mux packages)

[Paul_123]

Yes the pi0 is still supported, It’s all in the armhf folders.   We stoped creating 3 duplicate repos for the 32bit architectures.

FWIW, I’ll be spinning 16.0 release images today.

[zharr]

Ohh, I just didn't see any v6 package files, but I guess those are renamed to not have the v6 suffix? Gotta fix that in my setup scripts then, but glad to see!

Edit. Will be waiting for the 16.x images then and test!

[Paul_123]

Kernel name still has v6, just the main repo name changed.

[Rich]

Hi zharr

Ohh, I just didn't see any v6 package files, but I guess those are renamed to not have the v6 suffix? ...

I don't think the module extensions ever had a v6 suffix.
No suffix means v6. These are the modules in TC14 armv6:

Code: [Select]

ls -1 *6.1.68*.tcz
alsa-modules-6.1.68-piCore.tcz
ax25-6.1.68-piCore.tcz
bluetooth-6.1.68-piCore.tcz
cdrom-6.1.68-piCore.tcz
filesystems-6.1.68-piCore.tcz
graphics-6.1.68-piCore.tcz
ipv6-netfilter-6.1.68-piCore.tcz
media-rc-6.1.68-piCore.tcz
net-bridging-6.1.68-piCore.tcz
net-usb-6.1.68-piCore.tcz
ppp-modules-6.1.68-piCore.tcz
raid-dm-6.1.68-piCore.tcz
rtc-6.1.68-piCore.tcz
touchscreen-6.1.68-piCore.tcz
usb-gadget-6.1.68-piCore.tcz
usbip-6.1.68-piCore.tcz
usb-serial-6.1.68-piCore.tcz
v4l-dvb-6.1.68-piCore.tcz
w1-6.1.68-piCore.tcz
wireguard-6.1.68-piCore.tcz
wireless-6.1.68-piCore.tczNo v6 suffixes.

[Paul_123]

I don't think the module extensions ever had a v6 suffix.

I use armv6 on my build system, because blank does not work well in scripts   but yes, x.x.x-piCore are the armv6 kernel modules.