Dantes

I think you lose the connection because the kernel is loaded. I do not use the friendly elec tools. I just boot from an OpenWRT image. Get a USB-A to USB-C cable Connect USB-A to PC Connect USB-C to DEBUG port Use screen to connect to the NanoPi: (you might need sudo) screen /dev/ttyUSB0 1500000 Get OpenWRT NanoPi-r6c image and write to sdcard Boot from sdcard with maskrom then you can use scp to transfer files and dd to write/erase/backup I think I did something similar here:

This has been a while , so I'm going from memory here: Cryptsetup-initramfs should be installed into the ramdisk (initrd) , thats why it fails. So something goes wrong in step 14. Try execute steps manually (1-16) and check if you have internet in your chroot. It asks for /dev/mapper/rootfs but that device is not there indicates cryptsetup module is not loaded. That's why you did not get the password prompt and thus the disk is still encrypted. ## Something goes wrong here, try executing all the steps manually (1-16). Step by step. ## If the cryptsetup module is not inserted/loaded, you will get that error. #14. chrooted environment cat << EOF > config #!/bin/sh -vx apt update echo 'force-confdef' > /root/.dpkg.cfg apt --yes install cryptsetup-initramfs rm /root/.dpkg.cfg lsinitramfs /boot/initrd.img* | grep 'usr.*cryptsetup' exit EOF chmod +x config chroot . ./config rm config Good luck.

Hiya, Are the mirrors out of sync? or did I break something E: Failed to fetch http://deb.debian.org/debian/dists/bookworm-backports/non-free-firmware/binary-arm64/by-hash/SHA256/bc6dc27f7f88e60504fae9d9271e4dabaaa76b8a3a35ac6ec579e24d01d0ea16 E: Failed to fetch http://fi.mirror.armbian.de/beta/dists/bookworm/main/by-hash/SHA512/31775333c7d89a377fd3d2aac261ef684faeaba308fcf85b3c9ddc7f4f4a61712f5e398bc3b23464fd77d3eabd2b86e92b5dcc8dc2e44a27926f546708418c1a Hash Sum mismatch Hashes of expected file: - Filesize:5041046 [weak] - SHA512:31775333c7d89a377fd3d2aac261ef684faeaba308fcf85b3c9ddc7f4f4a61712f5e398bc3b23464fd77d3eabd2b86e92b5dcc8dc2e44a27926f546708418c1a - SHA256:9338b164942fc9bf1fa6f069d440576bfc2d52d572ca08aa295d2b641e15bc34 - SHA1:e946e275f83429aaacfc505978d8954329f5c842 [weak] - MD5Sum:2470b93cb2c8b144eecb3741d16190e2 [weak] Hashes of received file: - SHA512:95942ee2a9dd6434ee2f1684e69b4f26f27c52522735fb512967c703b5a1088a8f52e71b930973274bacc8083e9228bb3059afbb99ac6fcd428df2c9a1f537bc - SHA256:a53944749f834dc3d01d751c8210741324b9ca9c0bda997e6658750cac61f0cb - SHA1:d5333daa8e6d4186b298a3e79d1a41328da71119 [weak] - MD5Sum:9fa931f4f569d5cbda969b6ac5a51eca [weak] - Filesize:5041046 [weak] Last modification reported: Fri, 11 Oct 2024 03:54:42 +0000 Release file created at: Fri, 11 Oct 2024 03:54:44 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead.

To prevent APT from installing <other-device> kernels that will render an installation useless I did the following: To see which kernel is running: $ uname -r 6.11.2-current-rockchip-rk3588 To see which kernels are installed: $ dpkg --get-selections 'linux-image*' inux-image-current-rockchip-rk3588 install linux-image-edge-rockchip-rk3588 install Its clear to see that I need "rockchip-rk3588" kernels and not the other 1000+ so wonderfully provides. Now that I know which kernel is used and which are not, I will allow and block what I need: $ sudo nano /etc/apt/preferences.d/kernel The first entry allows the installation of any rockchip-rk3588 kernels that my device can use. The second entry blocks the installation of any other kernel. Package: linux-image-*-rockchip-rk3588 Pin: release * Pin-Priority: 1000 Package: linux-image-* Pin: release * Pin-Priority: -1 To check if the policy is recognized run this command: $ apt-cache policy ... linux-image-6.9.7+bpo-rt-arm64 -> 6.9.7-1~bpo12+1 with priority -1 linux-image-6.1.0-11-cloud-arm64 -> 6.1.38-4 with priority -1 > linux-image-edge-rockchip-rk3588 -> 24.11.0-trunk.249 with priority 1000 > linux-image-edge-rockchip-rk3588 -> 24.11.0-trunk.238 with priority 1000 linux-image-6.1.0-11-rt-arm64 -> 6.1.38-4 with priority -1 linux-image-6.1.0-22-rt-arm64 -> 6.1.94-1 with priority -1 linux-image-6.1.0-11-arm64 -> 6.1.38-4 with priority -1 linux-image-6.10.6+bpo-arm64-dbg -> 6.10.6-1~bpo12+1 with priority -1 $ You can clearly see that all kernels are disabled with priority -1 except those for the rockchip-rk3588 To test this simulate the installation: $ sudo apt install --simulate linux-image-6.9.7+bpo-rt-arm64 [sudo] password for test: Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-image-6.9.7+bpo-rt-arm64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: linux-image-6.9.7+bpo-rt-arm64-unsigned E: Package 'linux-image-6.9.7+bpo-rt-arm64' has no installation candidate $ Success

Hiya peoples, Finally figured out what caused my black screen after updating After installing a new kernel (via apt) the '/boot/dtb' symlink is not updated, and fails to boot properly. lrwxrwxrwx 1 root root 31 Oct 7 11:38 dtb -> dtb-6.11.2-edge-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 Image -> vmlinuz-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 uInitrd -> uInitrd-6.11.2-current-rockchip-rk3588 So I wrote a systemd service that: 1. Runs before shutdown/reboot 2. Changes into the /boot directory 3. Reads the version from the dtb symlink 4. Reads the version from the Image symlink 5. Compares the versions 6. And if they do NOT match, creates a new dtb symlink that matches the Image symlink version. [Unit] Description=match dtb symlink with kernel version DefaultDependencies=no Before=shutdown.target [Service] Type=oneshot ExecStart=/bin/sh -c 'set -x;cd /boot;dtb=$(readlink dtb|sed 's,^dtb-,,');vmlinuz=$(readlink Image|sed 's,vmlinuz-,,');[ "$dtb" = "$vmlinuz" ] || ln -sf dtb-$vmlinuz dtb' TimeoutStartSec=0 [Install] WantedBy=shutdown.target To use this: 1. sudo nano /etc/systemd/system/dtb-match-kernel.service and paste in the text above. 2. sudo systemd enable dtb-match-kernel.service You can check the journal if it works with: 3. journalctl -u dtb-match-kernel.service or the /boot directory lrwxrwxrwx 1 root root 31 Oct 7 11:39 dtb -> dtb-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 Image -> vmlinuz-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 uInitrd -> uInitrd-6.11.2-current-rockchip-rk3588 Dantes

Hi, I had some issues regarding WireGuard that are solved now. Since my armbian release already contains wireguard I have no need to install it. However I wanted to prevent any future mistake rendering my installation unbootable. So after some searching and experimenting I did the following: In order to block a package a file must be created in /etc/apt/preferences.d/ , in my case I called it wireguard $ sudo tee /etc/apt/preferences.d/wireguard &>/dev/null <<EOF Package: wireguard Pin: release * Pin-Priority: -1 EOF This is what it looks like now when trying to install the package: $ sudo apt install wireguard Reading package lists... Done Building dependency tree... Done Reading state information... Done Package wireguard is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'wireguard' has no installation candidate Unfortunately this still gave me the option to autoremove wireguard-tools sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: wireguard-tools 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 366 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. So I marked the wireguard-tools package as manual because I still need it: $ sudo apt-mark manual wireguard-tools wireguard-tools set to manually installed. And now it does not bother me with "unneeded" packages warning when using apt : $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Yay!

Hi, I tried to install WireGuard, but it resulted in a non-bootable-system Wasn't WireGuard integrated in the kernel ? How does this apply to Armbian ? Available rk3588 kernels: $ sudo apt search linux-image.*rk3588 Sorting... Done Full Text Search... Done linux-image-current-rockchip-rk3588/bookworm,now 24.11.0-trunk.152 arm64 [installed] Armbian Linux current kernel image 6.10.11-current-rockchip-rk3588 linux-image-edge-rockchip-rk3588/bookworm 24.11.0-trunk.152 arm64 Armbian Linux edge kernel image 6.11.0-edge-rockchip-rk3588 $ Apt tries to install this kernel: $ sudo apt install wireguard wireguard-tools Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-image-6.10.6+bpo-arm64-16k linux-image-arm64-16k Suggested packages: firmware-linux-free linux-doc-6.10 debian-kernel-handbook Recommended packages: apparmor The following NEW packages will be installed: linux-image-6.10.6+bpo-arm64-16k linux-image-arm64-16k wireguard wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 87,9 MB of archives. After this operation, 169 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. $

Reported the bug (and solution) upstream to <pkg-privacy-maintainers@lists.alioth.debian.org>. I wonder how long it will take

Step 6. is incorrect, this must be: $ xzcat armbian.img.xz | sha256sum 05ea4603da3c5f5517f6e3f83b8bc456d31e299ac97f564e77a49487f93e5f1b *- (the checksum from armbian.img.sha is still in its compressed form while the sdcard is obviously written uncompressed)

Running Debian on an x86/64 you can clearly see that "tor" is one of the dependencies for "torsocks" $ uname -a Linux TEST-MACHINE 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux $ sudo apt install torsocks Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: runit-helper tor tor-geoipdb Suggested packages: mixmaster torbrowser-launcher socat apparmor-utils nyx obfs4proxy The following NEW packages will be installed: runit-helper tor tor-geoipdb torsocks 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 3.624 kB of archives. After this operation, 17,6 MB of additional disk space will be used. Do you want to continue? [Y/n] Found the problem, yay! Is this something Armbian fixes, or must this be reported upstream ?

Hi, The package torsocks wasn't working and I could not understand why it was not. Torsocks configuration file: /etc/tor/torsocks.conf (default) specifies port 9050 # Default Tor address and port. By default, Tor will listen on localhost for # any SOCKS connection and relay the traffic on the Tor network. TorAddress 127.0.0.1 TorPort 9050 So port 9050 should be visible with netstat, but it was not: $ netstat -at tcp 0 0 127.0.0.53:domain 0.0.0.0:* LISTEN tcp 0 0 127.0.0.54:domain 0.0.0.0:* LISTEN $ Then I tried to enable tor.service, but got an error: $ systemctl enable tor.service Failed to enable unit: Unit file tor.service does not exist. Maybe the tor package was not installed $ dpkg --get-selections | grep '^tor' torsocks install After installing the tor package: $ apt install tor Netstat should now show the port 9050 to be listening: $ netstat -at tcp 0 0 localhost:9050 0.0.0.0:* LISTEN tcp 0 0 127.0.0.53:domain 0.0.0.0:* LISTEN tcp 0 0 127.0.0.54:domain 0.0.0.0:* LISTEN Why is "tor" listed as a "recommended" package? Should this not be a dependency? $ sudo apt install torsocks Reading package lists... Done Building dependency tree... Done Reading state information... Done Recommended packages: tor The following NEW packages will be installed: torsocks 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 74,7 kB of archives. After this operation, 416 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian bookworm/main arm64 torsocks arm64 2.4.0-1 [74,7 kB] Fetched 74,7 kB in 0s (202 kB/s) Selecting previously unselected package torsocks. (Reading database ... 117684 files and directories currently installed.) Preparing to unpack .../torsocks_2.4.0-1_arm64.deb ... Unpacking torsocks (2.4.0-1) ... Setting up torsocks (2.4.0-1) ... Processing triggers for man-db (2.11.2-2) ... $

I think the problem lies in the command line, which I copied like a complete toddler # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-fd4a703" # uname -a Linux 6.11-rc6 #0 SMP Mon Sep 2 08:09:51 2024 aarch64 GNU/Linux # lspci -vvv 2>&1 |grep -i ASPM LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ + ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- LnkCap: Port #0, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <64us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+ L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-

Can't get hdmi output in Armbian/6.11 yet, so I'll have to wait for that to clear up. However these 3rd party OpenWRT builds (https://github.com/mj22226/openwrt/releases) all show the same thing: OpenWRT Linux 6.1.94 # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-4dc539f" # uname -a Linux 6.1.94 #0 SMP Sun Jun 16 23:31:23 2024 aarch64 GNU/Linux # lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) # lspci -vvvs 01:00|grep -E "L1,ASPM" # OpenWRT Linux 6.4.2 # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-1a94f52" # uname -a Linux 6.4.2 #0 SMP PREEMPT Fri Jul 7 23:03:17 2023 aarch64 GNU/Linux # lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01) # lspci -vvvs 01:00|grep -E "L1,ASPM" # OpenWRT Linux 6.6.48 # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-5a5368e" # uname -a Linux 6.6.48 #0 SMP Fri Aug 30 11:13:30 2024 aarch64 GNU/Linux # lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) # lspci -vvvs 01:00|grep -E "L1,ASPM" # OpenWRT Linux 6.11-rc # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-fe4b9c3" # uname -a Linux 6.11-rc5 #0 SMP Sun Aug 25 07:38:04 2024 aarch64 GNU/Linux # lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) # lspci -vvvs 01:00|grep -E "L1,ASPM" #

That might be because its more of an appliance/router than a desktop. It might be a regression. I'd wait for 6.11 to arrive, Sunday we're at 6.11-rc6, so that would mean another 3 weeks give or take. But I have a couple, so I checked them for you: OpenWRT # grep RELEASE /etc/os-release OPENWRT_RELEASE="OpenWrt SNAPSHOT r0-212b6f9" # uname -a Linux 6.10 #0 SMP Mon Jul 15 13:18:21 2024 aarch64 GNU/Linux # lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) # lspci -vvvs 01:00|grep -E "L1,ASPM" # Armbian $ grep ^PRETTY /etc/os-release PRETTY_NAME="Armbian 24.11.0-trunk.71 bookworm" $ uname -a Linux 6.10.7-current-rockchip-rk3588 #1 SMP PREEMPT Thu Aug 29 15:36:13 UTC 2024 aarch64 GNU/Linux $ lspci 0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) $ lspci -vvvs 01:00|grep -E "L1,ASPM" $ Dantes

Dear Community, This might only be with the NanoPI-r6c images, but the SHASUM contains a temporary path which you don't have an thus fails. Since we cannot change the SHASUM because then the ASC would fail, I have a temporary workaround: sed 's,/.*/,,' armbian.img.sha | sha256sum -c In a script you could either 1. CD into the directory of the image 2. Run the SHASUM there 3. Use $OLDPWD to return or correct the SHASUM inline: sha256sum /path/to/file | sed 's,/.*/,,' > armbian.img.sha Dantes