search

alexreinert / piVCCU

piVCCU is a project to install the original Homematic CCU3 firmware inside a virtualized container (lxc) on ARM based single board computers.
Apache License 2.0
300 stars 62 forks source link

Raspi 3B, bookworm 32-bit, pivccu3 stopped #508

Open DIY-Blub opened 10 months ago

DIY-Blub commented 10 months ago

Nachdem mein SmartPi in die Jahre gekommen ist, möchte ich das System komplett neu aufsetzen. Hab die WLAN Probleme mit der bridge scheinbar selbst gelöst, aber die pivccu3 läuft leider immer noch nicht. WLAN-Problem, vielleicht relevant: Problem beim WLAN war das keine Verbindung mehr mit dem Heimnetzwerk zustande kam. Zudem sind die Anleitungen nach raspberrypi.md & wlan.md etwas veraltet (inhaltlich als auch technisch, soweit ich das aus dem WWW verstanden habe)

Dennoch läuft alles gut an, jedoch stoppt pivccu nach wenigen Sekunden:

uname -a Linux smartpi 6.1.0-rpi4-rpi-v7 #1 SMP Raspbian 1:6.1.54-1+rpt2 (2023-10-05) armv7l GNU/Linux sudo pivccu-info 

piVCCU version: 3.71.12-85
OS:             Raspbian GNU/Linux 12 (bookworm)
Kernel:         6.1.0-rpi4-rpi-v7 armv7l
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
 Connected via: GPIO@3f201000.serial (/dev/raw-uart)
 Board serial:  PEQ0171168
 Radio MAC:     0x67085B
HMIP Hardware:  HM-MOD-RPI-PCB
 Connected via: GPIO@3f201000.serial (/dev/raw-uart)
 SGTIN:         3014F711A061A7D8A98C04A0
 Radio MAC:     0xBD5CDF
State:          STOPPED

journalctl -xeu pivccu.service

Okt 15 15:35:37 smartpi systemd[1]: Starting pivccu.service - piVCCU...
░░ Subject: A start job for unit pivccu.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit pivccu.service has begun execution.
░░ 
░░ The job identifier is 148.
Okt 15 15:35:45 smartpi start_container.sh[1834]: kernel.sched_rt_runtime_us = -1
Okt 15 15:35:45 smartpi systemd[1]: Started pivccu.service - piVCCU.
░░ Subject: A start job for unit pivccu.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit pivccu.service has finished successfully.
░░ 
░░ The job identifier is 148.
Okt 15 15:35:45 smartpi systemd[1]: pivccu.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit pivccu.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Okt 15 15:35:45 smartpi systemd[1]: pivccu.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit pivccu.service has entered the 'failed' state with result 'exit-code'.
Okt 15 15:35:45 smartpi systemd[1]: pivccu.service: Consumed 2.400s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit pivccu.service completed and consumed the indicated resources.

hab schon vieles versucht, zuletzt habe ich noch folgendes gemacht: sudo dpkg-reconfigure pivccu-modules-dkms

Disabled DKMS service ... Done
Remove obsolete kernel modules ... Done
Ensure non mixed processor architecure ... Done
Create kernel modules ... Done
Enable DKMS service ... Done

Neustart --> Resultat siehe journalctl

Weiß jemand was da ist oder hat jemand zumindest einen Tipp? :) (systemd[1]: pivccu.service: Failed with result 'exit-code'.)

DIY-Blub commented 10 months ago

Hier noch die Ausgabe von ifconfig

br0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.253.1  netmask 255.255.255.0  broadcast 192.168.253.255
        inet6 fe80::9c8d:3249:9a07:30d3  prefixlen 64  scopeid 0x20<link>
        ether 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 1  bytes 76 (76.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 1446 (1.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 448  bytes 38046 (37.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 448  bytes 38046 (37.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lxcbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 10.0.3.1  netmask 255.255.255.0  broadcast 10.0.3.255
        ether 00:16:3e:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.143  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::86f1:c0ee:acd4:149c  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:24:36:76  txqueuelen 1000  (Ethernet)
        RX packets 81  bytes 8480 (8.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 95  bytes 13265 (12.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Ich denke da passt doch noch nicht alles, br0 sollte nicht ether 00:00:00:00:00:00 sein. Bin halt echt kein Netzwerkadmin :(

DIY-Blub commented 9 months ago

@alexreinert Hast du eine Idee bzw. wirst du die WLAN-Anleitung adaptieren?

stale[bot] commented 4 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

DIY-Blub commented 4 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

push