generic_raw_uart driver not loaded after reboot

[blatthew]

Describe the issue you are experiencing

When rebooting HA Yellow the generic_raw_uart driver does not seem to load anymore. The issue I am experiencing is that i have no rf-module available in raspberrymatic (HmIP-RFUSB).

lsmod on a freshly booted system leads to
lsmod |grep uart
hci_uart               49152  1
btbcm                  24576  1 hci_uart
bluetooth             593920  29 hci_uart,btbcm,bnep,rfcomm

lsusb

 lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 1a40:0101

when i modprobe the driver:
generic_raw_uart: loading out-of-tree module taints kernel.

lsmod | grep uart
generic_raw_uart       45056  0
hci_uart               49152  1
btbcm                  24576  1 hci_uart
bluetooth             593920  29 hci_uart,btbcm,bnep,rfcomm

If I take out the usb module and plug it back in:

[ 1323.946866] usb 1-1.2: new full-speed USB device number 4 using dwc2
[ 1324.168989] usb 1-1.2: New USB device found, idVendor=1b1f, idProduct=c020, bcdDevice= 1.00
[ 1324.169022] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1324.169039] usb 1-1.2: Product: eQ-3 HmIP-RFUSB
[ 1324.169061] usb 1-1.2: Manufacturer: Silicon Labs
[ 1324.169074] usb 1-1.2: SerialNumber: 3014F711A000041F299ECF1F
[ 1324.172015] usb 1-1.2: Found eQ-3 HmIP-RFUSB with serial 3014F711A000041F299ECF1F at usb-fe980000.usb-1.2
[ 1324.172377] raw-uart raw-uart: Reset radio module
[ 1324.172398] raw-uart raw-uart: Registered new raw-uart device using underlying device eQ-3 [email protected].
[ 1324.703956] usb 1-1.2: USB disconnect, device number 4

The problem then seems to be that i dont have character device /dev/raw-uart:

ll /dev/r
ram0    ram1    ram10   ram11   ram12   ram13   ram14   ram15   ram2    ram3    ram4    ram5    ram6    ram7    ram8    ram9    random  rfkill  rtc     rtc0

Thanks for your help in advance.

Describe the behavior you expected

It used to work just fine In the sense that I could reboot HA Yellow and the HmIP-RFUSB would be recogniced by raspberymatic.

Steps to reproduce the issue

1. Reboot Systerm

...

What is the version this bug report is based on?

3.71.12.20231014

Which base platform are you running?

ha-addon (HomeAssistant Add-on)

Which HomeMatic/homematicIP radio module are you using?

HmIP-RFUSB

Anything in the logs that might be useful for us?

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: onboard, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.1, OK
Identifying Homematic RF-Hardware: HmRF: n/a, HmIP: n/a, OK
Updating Homematic RF-Hardware: no GPIO/USB connected RF-hardware found
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting sshd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: not required
Starting rfd: no BidCos-RF hardware found
Starting HMIPServer: .....OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.71.12.20231014 (raspmatic_oci_arm64)

Additional information

Hardware: HA-Yellow
HA-OS: 11.0
HA-Version: 2023.10.3

[blatthew]

After updating to
HA-OS: 11.1
Core: 2023.11.0
Raspberrymatic: 3.71.12.20231020

I still have the same behaviour. Does anyone know why i dont have a char device "raw-uart" after loading the driver?

[jens-maus]

Sorry, but I just tried to reproduce this issue with my HomeAssistant yellow test installation and cannot reproduce it. Here connecting a HmIP-RFUSB to one of the USB ports and then rebooting latest HomeAssistantOS (11.1) works perfectly. See here:

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: onboard, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.0, OK
Identifying Homematic RF-Hardware: ....HmRF: HMIP-RFUSB/eQ-3 [email protected], HmIP: HMIP-RFUSB/eQ-3 [email protected], OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.4.18, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: .......OK
Starting rfd: .OK
Starting HMIPServer: ..............OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.71.12.20231020 (raspmatic_oci_arm64)

Thus, the HmIP-RFUSB is perfectly recognized and integrated in the RaspberryMatic HA addon. Thus, this must be something on your end.

[blatthew]

Hi Jens
Thanks for getting back. Do you have any recommendations on how to procede?
It did work well for me for a long time. I dont know if one of the OS updates caused this behavior or what did. I think the root issue is that i dont have a raw-uart device in /dev...
Do you know whether it can be created manually?
Thanks

[blatthew]

I have done a fresh install of home assistant yellow and the problem no longer exists.
Thank you