RPI-RF-MOD wird nicht erkannt

Debian/Ubuntu basierte CCU

Moderator: Co-Administratoren

Antworten
DerHenry
Beiträge: 2
Registriert: 01.08.2022, 11:55
System: in Planung

RPI-RF-MOD wird nicht erkannt

Beitrag von DerHenry » 01.08.2022, 13:54

Guten Tag,

versuche seit eingen Tagen Debmatic unter Ubuntu Server 22.04 in Virtualbox ans laufen zu bekommen. Leider ohne Erfolg.
Verwende die HB-RF-USB-2 mit der RPI-RF-MOD.

Hier ein paar Ausgaben:

root@ubuntuserver2:~# uname -a
Linux ubuntuserver2 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

root@ubuntuserver2:~# debmatic-info
debmatic version: 3.65.6-94
Kernel modules: Available
Raw UART dev: Available
HMRF Hardware: unknown
HMIP Hardware: unknown

root@ubuntuserver2:~# sudo dpkg -s pivccu-modules-dkms
Package: pivccu-modules-dkms
Status: install ok installed
Priority: extra
Section: kernel
Maintainer: Alexander Reinert <alex@areinert.de>
Architecture: all
Version: 1.0.77
Provides: pivccu-kernel-modules
Pre-Depends: dkms, build-essential, bison, flex, debconf (>= 0.5) | debconf-2.0
Conflicts: pivccu
Conffiles:
/lib/systemd/system/pivccu-dkms.service b04311796976a57c2aa4c5d47cc5d175
Description: DKMS package for kernel modules needed for Homematic
This package contains the a DKMS package for kernel needed for Homematic.
Homepage: https://github.com/alexreinert/piVCCU

root@ubuntuserver2:~# ls -la /dev/raw-*
crw------- 1 root root 235, 0 Aug 1 11:34 /dev/raw-uart

root@ubuntuserver2:~# detect_radio_module --debug /dev/raw-uart
11:36:37.167162 Sending HM frame: fd 00 03 fe 00 01 14 1e
11:36:40.168455 Sending HM frame: fd 00 03 00 01 00 9e 03
11:36:43.169782 Sending HM frame: fd 00 03 fe 02 01 98 1d
11:36:46.170563 Sending HM frame: fd 00 03 00 03 00 12 00
11:36:49.173529 Sending HM frame: fd 00 03 fe 04 01 8c 1d
11:36:52.176623 Sending HM frame: fd 00 03 00 05 00 06 00
Error: Radio module was not detected

root@ubuntuserver2:~# dmesg | grep -e "usb\|oltage\|raw"
[ 0.629752] usbcore: registered new interface driver usbfs
[ 0.630567] usbcore: registered new interface driver hub
[ 0.631667] usbcore: registered new device driver usb
[ 0.869357] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15
[ 0.870690] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.871930] usb usb1: Product: OHCI PCI host controller
[ 0.872773] usb usb1: Manufacturer: Linux 5.15.0-43-generic ohci_hcd
[ 0.873697] usb usb1: SerialNumber: 0000:00:06.0
[ 1.347735] usb 1-1: new full-speed USB device number 2 using ohci-pci
[ 1.664437] usb 1-1: New USB device found, idVendor=80ee, idProduct=0021, bcdDevice= 1.00
[ 1.664852] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 1.665167] usb 1-1: Product: USB Tablet
[ 1.665389] usb 1-1: Manufacturer: VirtualBox
[ 2.099721] usb 1-2: new full-speed USB device number 3 using ohci-pci
[ 2.719003] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x1 has invalid maxpacket 512, setting to 64
[ 2.719429] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x82 has invalid maxpacket 512, setting to 64
[ 2.748302] usb 1-2: New USB device found, idVendor=0bda, idProduct=0129, bcdDevice=39.60
[ 2.748687] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.748981] usb 1-2: Product: USB2.0-CRW
[ 2.749188] usb 1-2: Manufacturer: Generic
[ 2.749398] usb 1-2: SerialNumber: 20100201396000000
[ 3.207713] usb 1-3: new full-speed USB device number 4 using ohci-pci
[ 3.752647] usb 1-3: New USB device found, idVendor=10c4, idProduct=8c07, bcdDevice= 1.01
[ 3.752684] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.752709] usb 1-3: Product: HB-RF-USB-2
[ 3.752724] usb 1-3: Manufacturer: Alexander Reinert
[ 3.752742] usb 1-3: SerialNumber: a481285b3cc1e8118ba76b713b0549ec
[ 3.770538] hid: raw HID events driver (C) Jiri Kosina
[ 3.789239] usbcore: registered new interface driver usbhid
[ 3.789377] usbhid: USB HID core driver
[ 3.792488] input: VirtualBox USB Tablet as /devices/pci0000:00/0000:00:06.0 usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input6
[ 3.796683] hid-generic 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-0000:00:06.0-1/input0
[ 3.847994] usbcore: registered new interface driver rtsx_usb
[ 8.762108] generic_raw_uart: loading out-of-tree module taints kernel.
[ 8.762188] generic_raw_uart: module verification failed: signature and/or required key missing - tainting kernel
[ 8.795729] usb 1-3: DKey: 6235383231383461 3131386531636333 3137623637616238 6365393435306233
[ 8.795737] usb 1-3: HKey: 7dcefb00aee173b3 a56a7ee67115ba07 b896e54ff0105397 d3859c7466e6fb0a
[ 8.795743] usb 1-3: SKey: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 8.795748] usb 1-3: SKey: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 8.795754] usb 1-3: PKey: f50048a8d7cc3f44 ae8460d13cf61d60 2dc161f5272a5876 88c996b27737fbae
[ 8.795760] usb 1-3: PKey: dd24b0aced521e88 cc457acb4b7c49a4 6745032ab2079847 becfb9f3af25d41f
[ 8.795765] usb 1-3: Could not verify device signature
[ 8.799125] usb 1-3: Found HB-RF-USB-2 with serial a481285b3cc1e8118ba76b713b0549ec at usb-0000:00:06.0-3
[ 8.865205] raw-uart raw-uart: Reset radio module
[ 8.991813] raw-uart raw-uart: Registered new raw-uart device using underlying device HB-RF-USB-2@usb-0000:00:06.0-3.
[ 9.009955] usbcore: registered new interface driver hb_rf_usb_2
[ 14.778194] raw-uart raw-uart: Reset radio module

root@ubuntuserver2:~# modinfo hb-rf-usb-2
filename: /lib/modules/5.15.0-43-generic/updates/dkms/hb_rf_usb_2.ko
alias: hb_rf_usb-2
author: Alexander Reinert <alex@areinert.de>
description: HB-RF-USB-2 raw uart driver for communication of debmatic and piVCCU with the HM-MOD-RPI-PCB and RPI-RF-MOD radio modules
version: 1.14
license: GPL
srcversion: 3C283625828CD3707030C78
alias: usb:v10C4p8D81d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1B1FpC020d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v10C4p8C07d*dc*dsc*dp*ic*isc*ip*in*
depends: generic_raw_uart
retpoline: Y
name: hb_rf_usb_2
vermagic: 5.15.0-43-generic SMP mod_unload modversions


Folgende Befehle habe ich schon versucht:
sudo dpkg-reconfigure pivccu-modules-dkms (danach reboot).

Vielen Dank schonmal!
Henry

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: RPI-RF-MOD wird nicht erkannt

Beitrag von deimos » 01.08.2022, 14:21

Hi,

hast du detect_radio_module aufgerufen während debmatic gestartet war? Dann ist es normal, dass nichts empfangen wird. In den Fall bitte debmatic stoppen und nochmal neu ausführen.

Viele Grüße
Alex

DerHenry
Beiträge: 2
Registriert: 01.08.2022, 11:55
System: in Planung

Re: RPI-RF-MOD wird nicht erkannt

Beitrag von DerHenry » 03.08.2022, 10:37

Hallo Alex,

danke für die schnelle Antwort. Habe den Fehler mittlerweile in einem defektem Funkmodul gefunden.
Danke für deine Bemühungen!.

Das Thema kann eigentlich gelöscht werden.

Viele Grüße
Henry

Antworten

Zurück zu „debmatic“