Hannes Posted October 22, 2022 Share Posted October 22, 2022 (edited) 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! Edited October 22, 2022 by Hannes removed some lines of irrelevant code output 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted October 23, 2022 Share Posted October 23, 2022 This is how mainline Linux looks like. Features breaks all the time (caused by constant kernel changes / development) and its impossible to track as this is simply too expensive. Linux distributions in majority are not doing any testings of those functions, while our test system is too primitive to detect something like this. A few more hundreds of thousands would be needed to put in, which is, in case you want free service, impossible. If detection would be made, someone needs to invest hours to fix it. Currently waiting things, average resolving rate = 400 days. So you have an idea how little you are investing into maintenance on top and around chaotic mainline Linux experience. 17 hours ago, Hannes said: What to do now? Workaround? Those usually always exists. One of them is going to armbian-config -> system -> other kernels and switch to older kernel, where this function was working. Then freeze kernel (which is anyway good thing for production deployment) and check from time to time if this was fixes. No, nobody will send you email when this will be fixed ... 0 Quote Link to comment Share on other sites More sharing options...
Hannes Posted October 23, 2022 Author Share Posted October 23, 2022 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: Am 22.10.2022 um 15:41 schrieb Hannes: 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 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?!? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.