ich laufe die Installation schon zum zweiten mal durch und habe ein Problem mit der Logausgabe und vollen zvram:
Also hier erstmal der Teil des Logs der auftaucht wenn ich pivccu3 installiere:
Code: Alles auswählen
sudo apt install pivccu3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
detect-radio-module dnsmasq-base liblxc1 lxc wait-sysfs-notify
Suggested packages:
lvm2 python3-lxc
Recommended packages:
dns-root-data apparmor debootstrap libpam-cgfs lxcfs lxc-templates uidmap
The following NEW packages will be installed:
detect-radio-module dnsmasq-base liblxc1 lxc pivccu3 wait-sysfs-notify
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 122 MB of archives.
After this operation, 15.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian bullseye/main armhf liblxc1 armhf 1:4.0.6-2 [294 kB]
Get:2 http://deb.debian.org/debian bullseye/main armhf dnsmasq-base armhf 2.85-1 [431 kB]
Get:3 http://deb.debian.org/debian bullseye/main armhf lxc armhf 1:4.0.6-2 [1,671 kB]
Get:4 https://www.pivccu.de/piVCCU stable/main armhf detect-radio-module armhf 1.0-5 [270 kB]
Get:5 https://www.pivccu.de/piVCCU stable/main armhf wait-sysfs-notify armhf 1.0-2 [3,436 B]
Get:6 https://www.pivccu.de/piVCCU stable/main armhf pivccu3 armhf 3.59.6-59 [119 MB]
Fetched 122 MB in 21s (5,742 kB/s)
Preconfiguring packages ...
Selecting previously unselected package detect-radio-module.
(Reading database ... 78960 files and directories currently installed.)
Preparing to unpack .../detect-radio-module_1.0-5_armhf.deb ...
Unpacking detect-radio-module (1.0-5) ...
Selecting previously unselected package wait-sysfs-notify.
Preparing to unpack .../wait-sysfs-notify_1.0-2_armhf.deb ...
Unpacking wait-sysfs-notify (1.0-2) ...
Selecting previously unselected package liblxc1:armhf.
Preparing to unpack .../liblxc1_1%3a4.0.6-2_armhf.deb ...
Unpacking liblxc1:armhf (1:4.0.6-2) ...
Selecting previously unselected package dnsmasq-base.
Preparing to unpack .../dnsmasq-base_2.85-1_armhf.deb ...
Unpacking dnsmasq-base (2.85-1) ...
Selecting previously unselected package lxc.
Preparing to unpack .../lxc_1%3a4.0.6-2_armhf.deb ...
Unpacking lxc (1:4.0.6-2) ...
Setting up detect-radio-module (1.0-5) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up wait-sysfs-notify (1.0-2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up liblxc1:armhf (1:4.0.6-2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up dnsmasq-base (2.85-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up lxc (1:4.0.6-2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-net.service → /lib/systemd/system/lxc-net.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc.service → /lib/systemd/system/lxc.service.
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Selecting previously unselected package pivccu3.
(Reading database ... 79216 files and directories currently installed.)
Preparing to unpack .../pivccu3_3.59.6-59_armhf.deb ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Unpacking pivccu3 (3.59.6-59) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up pivccu3 (3.59.6-59) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu.service → /lib/systemd/system/pivccu.service.
Created symlink /etc/systemd/system/pivccu.service.wants/monitor-hb-rf-eth.service → /lib/systemd/system/monitor-hb-rf-eth.service.
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for man-db (2.9.4-2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for dbus (1.12.20-2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for libc-bin (2.31-13+deb11u2) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
piVCCU: DTB rk3288-tinker.dtb was already patched
piVCCU: DTB rk3288-tinker-s.dtb was already patched
E: Write error - ~LZMAFILE (28: No space left on device)
Dann lasse ich mir den Speicher anzeigen: df -h
Code: Alles auswählen
# df -h
Filesystem Size Used Avail Use% Mounted on
udev 989M 0 989M 0% /dev
tmpfs 201M 16M 185M 8% /run
/dev/mmcblk0p1 15G 3.6G 11G 25% /
tmpfs 1001M 0 1001M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1001M 216K 1001M 1% /tmp
/dev/zram1 49M 48M 0 100% /var/log
tmpfs 201M 0 201M 0% /run/user/0
Code: Alles auswählen
sudo pivccu-info
piVCCU version: 3.59.6-59
Kernel modules: Available
Raw UART dev: Available
HMRF Hardware: RPI-RF-MOD
Connected via: GPIO (/dev/raw-uart)
Board serial: 58A992FB3B
Radio MAC: 0xFFFB3B
HMIP Hardware: RPI-RF-MOD
SGTIN: 3014F711A0001F5xxxxxxxxx
Radio MAC: 0xB3D162
State: RUNNING
PID: 4581
IP: 192.168.1.19
Link: vethpivccu
TX bytes: 3.65 MiB
RX bytes: 604.76 KiB
Total bytes: 4.24 MiB
Ich bekomme im ioBroker allerdings hm.rpc.0 nicht grün hat das etwas damit zu tun ? Ist die Installation wirklich durchgelaufen oder hat sie durch die Fehlermeldungen Lücken ?
Viele Grüße,
Marc