Topics created by Achilleas Kotsis

@cleve Because I never use precompiled modules on debian based systems if I can help it since dkms was introduced in the '00s, I like the flexibility of not having to match kernels with specific precompiled modules.
For example, right now on one of my systems:
unipi-kernel-modules : Depends: linux-image-rpi-v8 (= 1:6.12.20-1+rpt1~bpo12+1) but 1:6.6.74-1+rpt1 is to be installed

I have multiple rpi3 and rpi4 based neuron systems that I maintain, most are runing raspberry pi os bookworm aarch64. BTW unipi-kernel-modules-dkms=2.70~bookworm builds just fine until at least linux-image-6.6.74+rpt-rpi-v8

I see now that these are included in neuron-main tree, but it was never installed on my rpi because the install script failed.

The following packages have unmet dependencies: unipi-kernel-modules : Depends: raspberrypi-kernel (= 1:1.20221104-1) but 1:1.20230106-1 is to be installed E: Unable to correct problems, you have held broken packages. Cleaning temporary files Cleaning temporary files

I am guessing you need a better way of determining the platform, otherwise this is going to break each time a new rpi kernel is released before you have a chance to build the modules package...

If anyone needs a workaround, install like this:

wget -qO - https://repo.unipi.technology/debian/raspberry-install.sh | sed s/unipi-kernel-modules/unipi-kernel-modules-dkms/ | bash

Hello @Achilleas-Kotsis,
the issue is not with the unipi-kernel-module, but with the unipi-firmware 5.52. We have removed it from our repository and advise to downgrade to 5.50 (and flash it to the HW via /opt/unipi/tools/fwspi). We are working on the fix.

Thank you again for reporting this issue and have a nice day,
Martin

Hello @Achilleas-Kotsis,

I have tried to upgrade the system from a few older images (also with DKMS drivers) and this kind of behaviour did not occur. The issue seems to be coupled with the filesystem write operation and the following sync (should be invoked by umount command in the script).

Moreover, the .inc file should be updated formerly within the upgrade process (as the step of unipi-common package postinst script).

Can you retry the whole process with a new uSD card? This kind of problems sometimes occurs on corrupted cards as the write operation is not fully synced in fact.

Thank you