Hannes

I do ran into the same problem today with my rock-3a running Armbian 24.2.1 Bookworm with Linux 6.6.16-current-rockchip64 It occurred after re-boot of the system because of the banner the message "Please reboot system do to kernel-updated" appeared. After that ethernet (was named "end0") did not come up anymore. When activating using "nmtui" the message comes: "Activation failed. Device could not be prepared for activation ..." (freely translated from German language). journalctl -x gives the following: (armbian-monitor -u already performed) Mar 14 10:51:01 cloud kernel: rk_gmac-dwmac fe010000.ethernet end0: __stmmac_open: Cannot attach to PHY (error: -19) Mar 14 10:51:01 cloud NetworkManager[745]: <info> [1710409861.7565] device (end0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed') Mar 14 10:51:01 cloud NetworkManager[745]: <warn> [1710409861.7579] device (end0): Activation: failed for connection 'Ethernet' Mar 14 10:51:01 cloud NetworkManager[745]: <info> [1710409861.7588] device (end0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') After all I updated the bootloader (using armbian-config) and it luckily resolved the problem ... Thx for reading this. Hope it helps others ...

Thx for your answer, Joekhoobyar. Yes, indeed, there are messages about "held BROKEN packages", but I did not put any packages on hold. Neither 'sudo apt-mark showhold' nor 'sudo apt-mark unhold' shows anything. What to do? I am a little bit of lost. What is the reason for this mismatch? How to get rid of it?

Thx folks for the upgrade instructions. Worked for me until I got this (when running the standard 'apt update && apt upgrade'): The following packages have been kept back: libffi-dev libsigrokdecode4 libssl-dev 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Then it turns out that the system has broken dependencies (or what ever may be the reason). For example if I try to update rock@nextcloud:/etc/apt/sources.list.d$ sudo apt -f install libpython3.11 Reading package lists... Done Building dependency tree... Done Some packages could not be installed [...] The following packages have unmet dependencies: libpython3.11 : Depends: libpython3.11-stdlib (= 3.11.2-6) but 3.11.7-2 is to be installed E: Unable to correct problems, you have held broken packages. But when I try updating to the required version of "libpython3.11-stdlib" it says that it's already installed: rock@nextcloud:/etc/apt/sources.list.d$ sudo apt -f install libpython3.11-stdlib Reading package lists... Done Building dependency tree... Done libpython3.11-stdlib is already the newest version (3.11.7-2). 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. And this is the case for other libraries, too. So I am not sure whether there is something wrong in gerenal ???!!!??? Info: I already tried cleaning apt and its corresponding /var/lib/apt/ dir several times. Please help ...

Sorry, but it does NOT help. There is only armbian-config launching, loading 58 modules and then it's done. After reboot it says Welcome to Armbian 23.02.2 Bullseye with Linux 6.1.11-rk35xx No end-user support: untested automated build WHAT has exactly to be done. I should -- at least -- expect to be asked what kernel I wanna install or that the messages "untested automated build" disappears.

Further investigation gives, that the running kernel (like already written in the title) is still "Linux rock-3a 5.19.10-rk35xx" whereas the updates installed the version 5.19.14: I already installed a newer update (5.19.16-rk35xx) but still the 5.19.10-Kernel is active, regardless of any reboots. The name/version of the subdir in /usr/lib/modules/ gives the correct installed version (latest is .16) and unfortunately a symlink to it does not resolve the problem: rock@rock-3a:/usr/lib/modules$ ll 0 lrwxrwxrwx 1 root root 14 22. Okt 21:49 5.19.10-rk35xx -> 5.19.16-rk35xx 4 drwxr-xr-x 3 root root 4096 22. Okt 22:04 5.19.16-rk35xx My question for now is: Where is that old initrd-image from which the kernel is loaded? How could it load if already removed by the update process (see first log)? And why is it installing "linux-image-edge-rk35xx" instead of a "stable" version? If I wanna have an "on-the-egde"-kernel then I expect do have a switch somewhere to activate it but not to have the latest "egde"-version as a default option. Am I too naive to think that way?!?

6 days ago I did a usual "apt-get update && apt-get upgrade" which brought up the following output: rock@rock-3a:~$ sudo apt-get update && sudo apt-get upgrade && sudo apt-get -y autoremove && sudo apt-get -y autoclean OK:1 http://deb.debian.org/debian bullseye InRelease OK:2 http://deb.debian.org/debian bullseye-updates InRelease OK:3 http://security.debian.org bullseye-security InRelease OK:5 http://deb.debian.org/debian bullseye-backports InRelease OK:4 https://box64.debian.ryanfortner.dev/debian ./ InRelease OK:6 https://mirror-eu-de1.armbian.airframes.io/apt bullseye InRelease Paketlisten werden gelesen… Fertig Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Paketaktualisierung (Upgrade) wird berechnet… Fertig Die folgenden Pakete werden aktualisiert (Upgrade): armbian-bsp-cli-rock-3a armbian-config armbian-firmware armbian-zsh linux-dtb-edge-rk35xx linux-image-edge-rk35xx linux-libc-dev linux-u-boot-rock-3a-edge tzdata 9 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen noch 68,7 MB von 68,9 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 304 kB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] Holen:1 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 armbian-bsp-cli-rock-3a arm64 22.08.4 [423 kB] Holen:2 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 armbian-config all 22.08.4 [128 kB] Holen:3 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 armbian-firmware all 22.08.4 [9.408 kB] Holen:4 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 armbian-zsh all 22.08.4 [2.302 kB] Holen:5 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 linux-dtb-edge-rk35xx arm64 22.08.4 [450 kB] Holen:6 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 linux-image-edge-rk35xx arm64 22.08.4 [53,7 MB] Holen:7 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 linux-libc-dev arm64 22.08.4 [1.233 kB] Holen:8 https://mirror-eu-de1.armbian.airframes.io/apt bullseye/main arm64 linux-u-boot-rock-3a-edge arm64 22.08.4 [1.033 kB] Es wurden 68,7 MB in 11 s geholt (6.301 kB/s). Preconfiguring packages ... (Lese Datenbank ... 47489 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../0-tzdata_2021a-1+deb11u7_all.deb ... Entpacken von tzdata (2021a-1+deb11u7) über (2021a-1+deb11u6) ... Vorbereitung zum Entpacken von .../1-armbian-bsp-cli-rock-3a_22.08.4_arm64.deb ... Entpacken von armbian-bsp-cli-rock-3a (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../2-armbian-config_22.08.4_all.deb ... Entpacken von armbian-config (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../3-armbian-firmware_22.08.4_all.deb ... Entpacken von armbian-firmware (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../4-armbian-zsh_22.08.4_all.deb ... Entpacken von armbian-zsh (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../5-linux-dtb-edge-rk35xx_22.08.4_arm64.deb ... Entpacken von linux-dtb-edge-rk35xx (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../6-linux-image-edge-rk35xx_22.08.4_arm64.deb ... Entpacken von linux-image-edge-rk35xx (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../7-linux-libc-dev_22.08.4_arm64.deb ... Entpacken von linux-libc-dev:arm64 (22.08.4) über (22.08.2) ... Vorbereitung zum Entpacken von .../8-linux-u-boot-rock-3a-edge_22.08.4_arm64.deb ... Entpacken von linux-u-boot-rock-3a-edge (22.08.4) über (22.08.2) ... linux-libc-dev:arm64 (22.08.4) wird eingerichtet ... linux-dtb-edge-rk35xx (22.08.4) wird eingerichtet ... armbian-zsh (22.08.4) wird eingerichtet ... tzdata (2021a-1+deb11u7) wird eingerichtet ... Current default time zone: 'Europe/Berlin' Local time is now: Sun Oct 16 21:23:09 CEST 2022. Universal Time is now: Sun Oct 16 19:23:09 UTC 2022. Run 'dpkg-reconfigure tzdata' if you wish to change it. armbian-config (22.08.4) wird eingerichtet ... armbian-bsp-cli-rock-3a (22.08.4) wird eingerichtet ... armbian-firmware (22.08.4) wird eingerichtet ... linux-image-edge-rk35xx (22.08.4) wird eingerichtet ... dkms: running auto installation service for kernel 5.19.14-rk35xx:. update-initramfs: Generating /boot/initrd.img-5.19.14-rk35xx update-initramfs: Converting to u-boot format Remove unused generated file: /boot/uInitrd-5.19.10-rk35xx Remove unused generated file: /boot/initrd.img-5.19.10-rk35xx linux-u-boot-rock-3a-edge (22.08.4) wird eingerichtet ... Trigger für initramfs-tools (0.140) werden verarbeitet ... update-initramfs: Generating /boot/initrd.img-5.19.14-rk35xx update-initramfs: Converting to u-boot format Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Del tzdata 2021a-1+deb11u6 [284 kB] rock@rock-3a:~$ After a reboot the USB port bus 007:device 002 on with an Arduino Nano connected rock@rock-3a:~$ lsusb >>> Bus 007 Device 002: ID 2341:0043 Arduino SA Uno R3 (CDC ACM) <<< Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub does not show up anymore as '/dev/ttyACM0' ! Although the device does exist: rock@rock-3a:~$ ll /dev/bus/usb/007/002 0 crw-rw-r-- 1 root root 189, 769 22. Okt 12:40 /dev/bus/usb/007/002 And therefore is no more accessible. Multiple reboots did not resolve the problem. What to do now? I do appreciate any idea 🙂 Thx for helping!