heute habe ich es mal gewagt und habe meinen Raspberry Pi 4 - 8 GB von Buster 32 Bit auf Bullseye mit 64 Bit aktualisiert.
Allerdings mit dem Ergebnis, daß piVCCU leider nicht mehr nicht mehr startet.
Den Raspi-Kernel habe ich auch aktualisiert und auch 10 Minuten abgewartet.
Code: Alles auswählen
pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.65.6-73
Kernel modules: Not available
Raw UART dev: Not available
Rasp.Pi UART: Assigned to GPIO pins
HMRF Hardware: unknown
HMIP Hardware: unknown
State: STOPPEDCode: Alles auswählen
pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
Active: failed (Result: protocol) since Fri 2022-08-19 19:07:45 CEST; 16min ago
Process: 984 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
CPU: 34ms
Aug 19 19:07:45 raspberrypi systemd[1]: Starting piVCCU...
Aug 19 19:07:45 raspberrypi start_container.sh[987]: modprobe: FATAL: Module eq3_char_loop not found in directory /lib/modules/5.15.56-v8+
Aug 19 19:07:45 raspberrypi systemd[1]: pivccu.service: Can't open PID file /run/pivccu3.pid (yet?) after start: Operation not permitted
Aug 19 19:07:45 raspberrypi systemd[1]: pivccu.service: Failed with result 'protocol'.
Aug 19 19:07:45 raspberrypi systemd[1]: Failed to start piVCCU.
Code: Alles auswählen
pi@raspberrypi:~ $ systemctl start pivccu
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Legitimierung ist zum Starten von »pivccu.service« notwendig.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
Job for pivccu.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pivccu.service" and "journalctl -xe" for details.
pi@raspberrypi:~ $ Auch sudo dpkg-reconfigure pivccu-modules-dkms mal durchlaufen lassen. Leider ohne Erfolg.
Was mich etwas etwas erstaunt ist der Fehler "Could not load required kernel module eq3_char_loop." Habe aber keine Idee wie ich den Char_Loop nachschieben kann.
Code: Alles auswählen
pi@raspberrypi:/lib/modules $ ls
5.15.56+ 5.15.56-v7+ 5.15.56-v7l+ 5.15.56-v8+
pi@raspberrypi:/lib/modules $ cd 5.15.56-v8+/
pi@raspberrypi:/lib/modules/5.15.56-v8+ $ ls
kernel modules.alias modules.alias.bin modules.builtin modules.builtin.alias.bin modules.builtin.bin modules.builtin.modinfo modules.dep modules.dep.bin modules.devname modules.order modules.softdep modules.symbols modules.symbols.bin
pi@raspberrypi:/lib/modules/5.15.56-v8+ $ Code: Alles auswählen
pi@raspberrypi:/lib/modules/5.15.56-v7l+ $ sudo dpkg-reconfigure pivccu-modules-dkms
Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.
Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.
------------------------------
Deleting module version: 1.0.77
completely from the DKMS tree.
------------------------------
Done.
Error! The module/version combo: pivccu-1.0.77
is not located in the DKMS tree.
Creating symlink /var/lib/dkms/pivccu/1.0.77/source ->
/usr/src/pivccu-1.0.77
DKMS: add completed.
Error! echo
Your kernel headers for kernel 5.15.56-v8+ cannot be found at
/lib/modules/5.15.56-v8+/build or /lib/modules/5.15.56-v8+/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
pi@raspberrypi:/lib/modules/5.15.56-v7l+ $ sudo dpkg-reconfigure pivccu-modules-dkms
Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.
Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.
------------------------------
Deleting module version: 1.0.77
completely from the DKMS tree.
------------------------------
Done.
Error! The module/version combo: pivccu-1.0.77
is not located in the DKMS tree.
Creating symlink /var/lib/dkms/pivccu/1.0.77/source ->
/usr/src/pivccu-1.0.77
DKMS: add completed.
Error! echo
Your kernel headers for kernel 5.15.56-v8+ cannot be found at
/lib/modules/5.15.56-v8+/build or /lib/modules/5.15.56-v8+/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
pi@raspberrypi:/lib/modules/5.15.56-v7l+ $ Unter 32 Bit geht alles wunderbar.
Wäre klasse wenn jemand eine Idee hat wie man alles auf 64 Bit laufen lassen kann.
Grüße vom
Mark
