I switched back to an earlier btrfs snapshot of the rootfs to check that.īut after the upgrade, rvice was not started, although activated. It turns out NetworkManager was already installed and also activated.
#Yacreader raspberry pi update#
No rpi-update, just apt update & apt full-upgrade Rpi-update might enable NetworkManager instead of dhcpcd but that is non-standard. NetworkManager is not enabled by default and is classed as beta at the moment, If a run an update there, it will also fail I guess. On another Pi which is a clone network/VLAN wise, rvice is not installed. Or maybe remove it completely, as it must have been installed/activated by the upgrade.
Workaround is to disable rvice, then rvice gets started as usual. rvice isn't started and rvice fails, that is the conclusion.
#Yacreader raspberry pi serial#
Via serial console I see that NetworkManager has a problem with my VLAN configuration. Update/upgrade I did yesterday breaks network availability on my RasPiOS64 installation. ID-1: /dev/sda type: USB vendor: SanDisk model: Ultra USB 3.0 Message: No ARM data found for this feature. Unloaded: fbdev resolution: 1920x1080~60Hz Info: Quad Core Model N/A speed: 1800 MHz min/max: 600/1800 MHzĭevice-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/Aĭevice-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/Aĭevice-3: bcm2711-vc5 driver: vc4_drm v: N/Aĭisplay: wayland server: X.Org 1.20.11 driver: loaded: modesetting Type: ARM Device System: Raspberry Pi 4 Model B Rev 1.4 details: BCM2835 Host: raspberrypi Kernel: 5.15.61-v8+ aarch64 bits: 64 Desktop: GNOME HDMI audio is not working on rPi4-8, but works on rPi-400 Another possibility is something is still broken and I'm just on a run of luck not hitting it One other possibility is something was broken in the previous kernel which was fixed in 5.15.61-v8+.
#Yacreader raspberry pi 64 Bit#
It is no longer occurring and the last change I made before it didn't happen again was "gpu_mem=128" - I had left this at default for 64 bit Bullseye because of the changes in graphics memory allocation and all seemed to run fine up until now. At first I thought it was my overclock settings but it also happened after disabling all overclocking. In the last week or so I also saw multiple GUI lockups requiring a reboot on a Pi 400 running fully up to date 64 bit Raspberry Pi OS - all seemed to occur when playing videos in Chromium. Version on Raspberry Pi OS is still 1.57-rpt2 while in Debian stable Software section I see 1.53-1~deb11u1 and Security section already advises to upgrade to 1.52-1~deb11u1. I experience the same with 64 bit and up to date.Īlso wondering if we are badly missing security patches on Chromium. Keyboard and mouse does not respond during these occasions and a hard-reset is required. Chromium still causes irrevertable system freezes/lockups, especially on pages with embedded videos and animations.
0 kommentar(er)
