FYI: Compatibility issue with ubuntu 20.04LTS on raspberry4b and kernel 6.8.0.1004 ?

[pstestos]

OS: ubuntu 20.04LTS hardware: raspberry 4b 8gb, usbstick: HMIP-RFUSB/eQ-3 HmIP-RFUSB as well as own creation of HM-MOD-RPI-PCB/HB-RF-USB software: docker container raspberryMatic 3.75.7.20240420

I've had the problem that RaspberryMatic was not running after upgrading my prerelease ubuntu 20.04LTS to the current version. As described in https://github.com/jens-maus/RaspberryMatic/issues/2748#issuecomment-2117818293 I've had problems with the driver.

The kernel that worked was 6.8.0.1001 the kernel that did not work was 6.8.1004

I did not see any errors. I could compile the kernel module and that worked fine. lsmod showed me eq3 and hm modules only weird thing was that the /dev/mmd_* devices were missing.

I could only get around that problem by reverting back to a previous state ( zfs got my back ) So now I'm back to the old kernel but the new RaspberryMatic version and everything works fine.

As I rolled back, I currently can't replicate it any more but everything works fine again with raspberryMatic 3.75.7.20240420

[pstestos]

I could replicate the problem on a different raspberry pi and different usb-stick with the newest ubuntu 24.4. Installing the dkms module will create the /dev/rawuart and /dev/eq3loop but not /dev/mm*

[alexreinert]

Both devices are not created on the init of the kernel module, but on startup of the multimacd process, so there is no issue. If it isnot working together with RaspberryMatic, please use the issue tracker of RaspberryMatic.

[pstestos]

Thank you for your clarification. I started looking into it as RaspberryMatic was failing after updating the os. I updated RaspberryMatic after if was failing with the new os and that did not work, so I downgraded the os and kept the newer version of RaspberryMatic which now works. But maybe they introduced something that only gets triggred with the new os even though it's running in a docker container.

[schacka]

Hello everyone and thanks for the great project! I can confirm the error:

Starting multimacd: ..........ERROR
Starting rfd: ERROR: /dev/mmd_bidcos missing, no BidCos-RF hardware found
Starting HMIPServer: ERROR: /dev/mmd_hmip missing

It occurs on a RaspberryPi4 with Ubuntu Server 24.04, Kernel 6.8.1004, Docker 26.1.3 and RPI-RF-MOD on GPIO. Changing to 23.10 and everything runs fine. The kernel module eq3_charloop is loaded in both cases without problems (bt disabled). Only on 6.8.1004 the /dev/mmd* devices are not created within the docker container.

The error does not occur on a device with a 6.8.1004 kernel and RPI-RF-MOD via HB-RF-ETH.

[alexreinert]

Sorry, but I cannot help you on RaspberryMatic issues, themodules are working just fine using piVCCU or debmatic. Maybe you should open an issue at the RaspberryMatic project.

[schacka]

Hi Alex, i don't thinks its just a RaspberryMatic issue but as @pstestos said, something new with loading your module inside a docker environment. Nevertheless, thank you so much for your work! Proud owner of 3 HB-RF-ETH :)

[alexreinert]

It is. As said, the dev nodes are not created on startup of the kernel module, but on start of the multimacd process as the names are dynamic regarding to the keernel module. Inside a docker container the container needs to create them inside the container by itself.