-
Posts
21 -
Joined
-
Last visited
-
Cannot install linux-image-current-rockchip64
Kalli Lowman replied to Kalli Lowman's topic in Rockchip
Hello lanefu, its http://ix.io/2rQq sorry i forgot about that. -
Hello, (i opened a new thread because the other one had another topic...) At the moment im stuck in updating my linux image... When i run apt-get install linux-image-current-rockchip64 Then i get: The following packages will be upgraded: linux-image-current-rockchip64 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 38.2 MB of archives. After this operation, 97.2 MB of additional disk space will be used. Get:1 https://apt.armbian.com buster/main arm64 linux-image-current-rockchip64 arm64 20.05.7 [38.2 MB] Fetched 38.2 MB in 3s (14.4 MB/s) (Reading database ... 128592 files and directories currently installed.) Preparing to unpack .../linux-image-current-rockchip64_20.05.7_arm64.deb ... Unpacking linux-image-current-rockchip64 (20.05.7) over (20.02.11) ... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3F Creating new extlinux.conf... cp: cannot stat '/usr/lib/linux-image-5.4.49-rockchip64': No such file or directory run-parts: /etc/kernel/postrm.d/zz-update-extlinux exited with return code 1 dpkg: warning: old linux-image-current-rockchip64 package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3F Creating new extlinux.conf... cp: cannot stat '/usr/lib/linux-image-5.4.49-rockchip64': No such file or directory run-parts: /etc/kernel/postrm.d/zz-update-extlinux exited with return code 1 dpkg: error processing archive /var/cache/apt/archives/linux-image-current-rockchip64_20.05.7_arm64.deb (--unpack): new linux-image-current-rockchip64 package post-removal script subprocess returned error exit status 1 Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3F Creating new extlinux.conf... Installing new extlinux.conf... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3F Creating new extlinux.conf... Installing new extlinux.conf... Errors were encountered while processing: /var/cache/apt/archives/linux-image-current-rockchip64_20.05.7_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Does someone have a solution for this? I can also do a full reinstall as i have an image of my eMMC but this might be more work
-
Okay... i got the next problem incoming... (i think when i reboot its bricked again...) I cannot install linux-image-current-rockchip64... It says CP cannot find /usr/lib/linux-image-5.4.49-rockchip64... i dont know why root@rockpi:~# apt-get install linux-image-current-rockchip64 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-image-current-rockchip64 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/38.2 MB of archives. After this operation, 97.2 MB of additional disk space will be used. (Reading database ... 128592 files and directories currently installed.) Preparing to unpack .../linux-image-current-rockchip64_20.05.7_arm64.deb ... Unpacking linux-image-current-rockchip64 (20.05.7) over (20.02.11) ... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE Creating new extlinux.conf... cp: cannot stat '/usr/lib/linux-image-5.4.49-rockchip64': No such file or directory run-parts: /etc/kernel/postrm.d/zz-update-extlinux exited with return code 1 dpkg: warning: old linux-image-current-rockchip64 package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE Creating new extlinux.conf... cp: cannot stat '/usr/lib/linux-image-5.4.49-rockchip64': No such file or directory run-parts: /etc/kernel/postrm.d/zz-update-extlinux exited with return code 1 dpkg: error processing archive /var/cache/apt/archives/linux-image-current-rockchip64_20.05.7_arm64.deb (--unpack): new linux-image-current-rockchip64 package post-removal script subprocess returned error exit status 1 Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE Creating new extlinux.conf... Installing new extlinux.conf... Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE Creating new extlinux.conf... Installing new extlinux.conf... Errors were encountered while processing: /var/cache/apt/archives/linux-image-current-rockchip64_20.05.7_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
-
I got it all working, i manually downloaded the deb files for the firmware and kernel image and re-ran apt-get again and all worked... after restart i was booting up the newest kernel and all is working. Thanks so much for your help
-
I see that he got some problems with the modules: after i did apt-get update and upgrade he installed the 5.4.3.2-rockchip64 but inside is only a build folder... in the old folder there are much more folders (5.4.28) root@rockpi:/lib/modules/5.4.32-rockchip64# ls build root@rockpi:/lib/modules/5.4.32-rockchip64# cd .. root@rockpi:/lib/modules# cd 5.4.28-rockchip64/ root@rockpi:/lib/modules/5.4.28-rockchip64# ls kernel modules.alias.bin modules.builtin.bin modules.dep modules.devname modules.softdep modules.symbols.bin modules.alias modules.builtin modules.builtin.modinfo modules.dep.bin modules.order modules.symbols root@rockpi:/lib/modules/5.4.28-rockchip64# root@rockpi:/var/log/apt# apt-get install linux-image-current-rockchip64 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Die folgenden NEUEN Pakete werden installiert: linux-image-current-rockchip64 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 22,1 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 95,4 MB Plattenplatz zusätzlich benutzt. Holen:1 https://apt.armbian.com buster/main arm64 linux-image-current-rockchip64 arm64 20.02.11 [22,1 MB] Es wurden 22,1 MB in 4 s geholt (6.307 kB/s). Vormals nicht ausgewähltes Paket linux-image-current-rockchip64 wird gewählt. (Lese Datenbank ... 127748 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../linux-image-current-rockchip64_20.02.11_arm64.deb ... Entpacken von linux-image-current-rockchip64 (20.02.11) ... linux-image-current-rockchip64 (20.02.11) wird eingerichtet ... update-initramfs: Generating /boot/initrd.img-5.4.32-rockchip64 update-initramfs: Converting to u-boot format Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE Creating new extlinux.conf... cp: der Aufruf von stat für '/usr/lib/linux-image-5.4.32-rockchip64' ist nicht möglich: Datei oder Verzeichnis nicht gefunden run-parts: /etc/kernel/postinst.d/zz-update-extlinux exited with return code 1 dpkg: Fehler beim Bearbeiten des Paketes linux-image-current-rockchip64 (--configure): »installiertes linux-image-current-rockchip64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: linux-image-current-rockchip64 E: Sub-process /usr/bin/dpkg returned an error code (1)
-
I think its not the kernel, i think its my manually copied things because before it was mmcblk1 with the same kernel and linux version. Is there a "safe" way to rename this? Or can i just ignore this and continue working
-
What i found out when i wanted to create another image of my emmc: dd status=progress bs=512 if=/dev/mmcblk1 | pigz --fast > /home/kalli/eMMC_backup.img.gz - it was mmcblk1 all the time is that device name changed from mmcblk1 to mmcblk2, can you explain my why? Maybe this is also causing those weird problems.
-
This is the content of boot -> seems as if some files are missing :O total 96 4 -rw------- 1 root root 151 Apr 28 15:28 armbianEnv.txt 0 -rw-r--r-- 1 root root 0 Jun 24 2019 armbianEnv.txt.out 4 -rw-r--r-- 1 root root 195 Apr 17 18:46 armbianEnv.txt.save 4 -rw-r--r-- 1 root root 229 Apr 18 16:26 armbianEnv.txt.save.1 4 -rw------- 1 root root 1536 Mar 28 13:26 armbian_first_run.txt.template 40 -rw------- 1 root root 38518 Mar 28 13:26 boot.bmp 4 -rw-r--r-- 1 root root 2877 Jun 6 2019 boot.cmd 8 -rw------- 1 root root 4882 Mar 28 13:26 boot-desktop.png 4 -rw------- 1 root root 2940 Mar 28 13:32 boot.scr 0 lrwxrwxrwx 1 root root 21 Apr 29 12:23 dtb -> dtb-5.4.32-rockchip64 4 drwxr-xr-x 3 root root 4096 Mar 28 13:24 dtb-5.4.28-rockchip64 4 drwxr-xr-x 3 root root 4096 Apr 29 12:21 dtb-5.4.32-rockchip64 4 drwxr-xr-x 2 root root 4096 Apr 28 15:26 dtbs 4 drwxr-xr-x 2 root root 4096 Apr 29 12:23 extlinux 4 -rwxr-xr-x 1 root root 1807 Oct 21 2019 hw_intfc.conf 0 lrwxrwxrwx 1 root root 25 Apr 29 16:23 Image -> vmlinuz-5.4.28-rockchip64 4 drwxr-xr-x 2 root root 4096 Apr 18 13:42 overlays 0 lrwxrwxrwx 1 root root 25 Apr 29 16:24 uInitrd -> uInitrd-5.4.28-rockchip64 It only changed DTB to point to 5.4.32 and added a new folder "dtb-5.4.32-rockchip64"
-
I tried updating board firmware and kernel via armbian-config and i got the same result (now i know how to fix it) but why does that happen? This is what the debug console shows after i choose restart in armbian-config after Firmware Upgrade Hn0 serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Radxa ROCK Pi 4 `Nnp mode 5242c300. normal boot Ldt: @`h0: ethernet@fe300000 itany key to stop autoboot: 0 CA`d did not respond to voltage select! mmc_init: -95, time 10 bf@pch to partitions #0, OK mmc0(part 0) is current device Bc`lning mmc 0:1... otl` /boot/extlinux/extlinux.conf aprieving file: /boot/extlinux/extlinux.conf "&bytes read in 81 ms (0 Bytes/s) belect kernel Enter choice: BHT FAILED: continuing... NpnD U-Boot script /boot/boot.scr 0$ bytes read in 102 ms (27.3 KiB/s) ## Executing script at 00500000 @OO` script loaded from mmc 0 01 bytes read in 81 ms (1000 Bytes/s) "File not found /boot/uInitrd ** Dile not found /boot/Image ** &0724 bytes read in 330 ms (214.8 KiB/s) $98 bytes read in 210 ms (11.7 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 @d Linux ARM64 Image magic! SCRIPT FAILED: continuing...
-
OMG its working... after i changed the DTB symlink it works!!! I think copying the files from the image to /lib/modules did the trick... I never did this before until you wrote me to do so and i think this solved the problem! It booted up and all is working again.. i might now try to update the kernel again
-
I have replaced the symlink now Its not pointing to the right folder lrwxrwxrwx 1 root root 22 Apr 29 18:05 dtb -> dtb-5.4.28-rockchip64/ lrwxrwxrwx 1 root root 22 Apr 29 18:05 dtb -> dtb-5.4.28-rockchip64/ This is the content of armbianEnv.txt verbosity=1 overlay_prefix=rockchip rootdev=UUID=3c50a1d1-71a5-4a0f-9899-099b17a1050b rootfstype=ext4
-
Hello, this is the content of the emmc (after i already copied the files from the image downloaded and extracted: total 39020 drwxr-xr-x 6 root root 4096 Apr 29 17:45 . drwxr-xr-x 24 root root 4096 Apr 29 16:01 .. -rw------- 1 root root 102 Apr 29 17:45 armbianEnv.txt -rw-r--r-- 1 root root 0 Jun 24 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 195 Apr 17 18:46 armbianEnv.txt.save -rw-r--r-- 1 root root 229 Apr 18 16:26 armbianEnv.txt.save.1 -rw------- 1 root root 1536 Mar 28 13:26 armbian_first_run.txt.template -rw------- 1 root root 38518 Mar 28 13:26 boot.bmp -rw-r--r-- 1 root root 2877 Jun 6 2019 boot.cmd -rw------- 1 root root 4882 Mar 28 13:26 boot-desktop.png -rw------- 1 root root 2940 Mar 28 13:32 boot.scr -rw------- 1 root root 189434 Mar 28 12:07 config-5.4.28-rockchip64 lrwxrwxrwx 1 root root 22 Apr 29 16:23 dtb -> dtb-5.4.32-rockchip64/ drwxr-xr-x 3 root root 4096 Mar 28 13:24 dtb-5.4.28-rockchip64 drwxr-xr-x 3 root root 4096 Apr 28 15:27 dtb-5.4.32-rockchip64 drwxr-xr-x 2 root root 4096 Apr 28 15:26 dtbs -rwxr-xr-x 1 root root 1807 Oct 21 2019 hw_intfc.conf lrwxrwxrwx 1 root root 25 Apr 29 16:23 Image -> vmlinuz-5.4.28-rockchip64 -rw------- 1 root root 7286379 Mar 28 13:33 initrd.img-5.4.28-rockchip64 -rw-r--r-- 1 root root 0 Apr 18 13:29 .next drwxr-xr-x 2 root root 4096 Apr 18 13:42 overlays -rw------- 1 root root 4294688 Mar 28 12:07 System.map-5.4.28-rockchip64 lrwxrwxrwx 1 root root 25 Apr 29 16:24 uInitrd -> uInitrd-5.4.28-rockchip64 -rw------- 1 root root 7286443 Mar 28 13:33 uInitrd-5.4.28-rockchip64 -rw------- 1 root root 20787712 Mar 28 12:07 vmlinuz-5.4.28-rockchip64
-
Hello, yes im using a rock pi 4b with emmc. I used my emmc usb adapter to access the filesystem from another linux system. As you mentioned above i have taken a look into /lib/modules and i saw 5.4.28-rockchip64 -> So i downloaded Armbian_20.02.7_Rockpi-4b_buster_current_5.4.28.7z unpacked it and mounted the img so that i can access the files. -> Then i copied the files from the image (lib/modules* and /boot) to my emmc card. I also checked that the rootdev uuid in armbianENV.txt is the right one. If you need further information please specify, then i can put more information into this thread. Im thankful that you take your time to help me. -> what happened before When i remember right... i changed from 20.02.11 to 20.02.8 (thats what i can see in apt cache) i downloaded "linux-image-current-rockchip64_20.02.11_arm64.deb" yesterday . And then i ran the firmware upgrade via armbian-config and then i powered the device off... maybe too early when it wasnt finished at all.
-
Okay nothing happens even the debug console does not put out any more after "starting kernel".
-
I will give it a try and leave it alone for 30 minutes. What i see is that after 1-2 minutes the red heartbet led is starting to flash twice every second.