Jerry Jyrer

Thanks for the pointers. I added them as a local repository and upgraded with the armbian-config. Just for reference, here is what I did sudo vi /etc/apt/sources.list ## add the following line: deb [trusted=yes] file:/<mypath>/armbian/build/output/debs/ ./ cd /<mypath>/armbian/build/output/debs/ sudo bash -c 'dpkg-scanpackages . | gzip > ./Packages.gz' sudo apt update # Switch to the new kernel via armbian-config sudo armbian-config

noob's here. Basically, my goal is to upgrade my system to Linux kernel 6.7 but it's not yet available via armbian-config (edge's at 6.6 at the moment). I went ahead and followed https://docs.armbian.com/Developer-Guide_Building-with-Docker/ ./compile.sh docker-shell root@6bc1d026998c:/armbian# ./compile.sh standard option : no change the kernel config, (my board) nanopim4, edge, jammy, Image with console interface (server), standard image with console interface I got the output below. How do I properly install it without flashing the whole thing -- similar to in the end what I got from armbian-config - System - Other ? My current system: $ uname -a Linux nanopim4 6.1.63-current-rockchip64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux $ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rockchip64 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=014eb55b5 LINUXFAMILY=rockchip64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=csc INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image FORCE_BOOTSCRIPT_UPDATE= VENDOR="Armbian" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com/" VENDORSUPPORT="https://forum.armbian.com" VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=23.11.1 REVISION=23.11.1 BRANCH=current $ ls -R .: debs images logs packages-hashed ./debs: armbian-bsp-cli-nanopim4-edge_24.5.0-trunk_arm64__1-PC3155-V6b08-He03b-Ba537-Rf32b.deb armbian-config_24.5.0-trunk_all__1-SAfb17-B0293-R448a.deb armbian-firmware_24.5.0-trunk_all__1-SA6b6f-B90f5-R448a.deb armbian-plymouth-theme_24.5.0-trunk_all__1-Bfcdb-R448a.deb armbian-zsh_24.5.0-trunk_all__1-SAbfee-Baafd-R448a.deb fake-ubuntu-advantage-tools_24.5.0-trunk_all__1-Bfcde-R448a.deb jammy linux-dtb-edge-rockchip64_24.5.0-trunk_arm64__6.7.6-Sb631-D6b4a-Pd972-C9e08Hfe66-HK01ba-Vc222-B067e-R448a.deb linux-headers-edge-rockchip64_24.5.0-trunk_arm64__6.7.6-Sb631-D6b4a-Pd972-C9e08Hfe66-HK01ba-Vc222-B067e-R448a.deb linux-image-edge-rockchip64_24.5.0-trunk_arm64__6.7.6-Sb631-D6b4a-Pd972-C9e08Hfe66-HK01ba-Vc222-B067e-R448a.deb linux-u-boot-nanopim4-edge_24.5.0-trunk_arm64__2022.04-Se4b6-P9ac8-H8c72-V00d9-B11a8-R448a.deb ./debs/jammy: base-files_24.5.0-trunk-12ubuntu4.6-jammy_arm64__1-jammy-1armbian1-Ba4f9-U12ubuntu4.6-R55fa.deb ./images: ./logs: archive log-docker-shell-2ff7b3cb-0116-4bab-af1f-513f2d12827b.log.ans summary-docker-shell-2ff7b3cb-0116-4bab-af1f-513f2d12827b.md ./logs/archive: log-build-12e521e3-4ee1-4e96-bd23-f7eab8343488.log.ans.zst log-docker-9dabbb7b-14fc-4f43-af22-a35f4d67be8b.log.ans.zst summary-docker-9dabbb7b-14fc-4f43-af22-a35f4d67be8b.md.zst log-build-12e521e3-4ee1-4e96-bd23-f7eab8343488.log.zst log-docker-shell-6c473265-ba31-45ab-83fb-3eafd8b54f89.log.ans.zst summary-docker-shell-6c473265-ba31-45ab-83fb-3eafd8b54f89.md.zst log-build-880a1d96-4ee1-4c1b-9fd5-ab60196a2a91.log.ans.zst summary-build-12e521e3-4ee1-4e96-bd23-f7eab8343488.md.zst log-build-880a1d96-4ee1-4c1b-9fd5-ab60196a2a91.log.zst summary-build-880a1d96-4ee1-4c1b-9fd5-ab60196a2a91.md.zst ./packages-hashed: armbian-bsp-cli-nanopim4-edge_1-PC3155-V6b08-He03b-Ba537-Rf32b_arm64.tar global jammy ./packages-hashed/global: ./packages-hashed/jammy:

FWIW, with my NanopiM4 RK3399 on 6.1.50-current-rockchip6, I have usb drives disconnected when doing file transfer between them. Revert back to 5.15.93-rockchip64, it works fine. > [ +39.294664] xhci-hcd xhci-hcd.3.auto: xHCI host not responding to stop endpoint command > [ +0.013618] xhci-hcd xhci-hcd.3.auto: xHCI host controller not responding, assume dead > [ +0.000049] xhci-hcd xhci-hcd.3.auto: HC died; cleaning up > [ +0.000233] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=35s > [ +0.000011] usb 3-1: USB disconnect, device number 2 > [ +0.000013] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 05 2d 19 ca e0 00 00 01 00 00 00 > [ +0.000011] I/O error, dev sda, sector 22231501536 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 > [ +0.000188] usb 4-1: USB disconnect, device number 2 > [ +0.000014] usb 4-1.1: USB disconnect, device number 3

I've just realized that https://www.armbian.com/download/ only lists Nanopi M4 V2 but not Nanopi M4 (original version). I looked specifically on https://www.armbian.com/nanopi-m4/ it has no recent ones but archives. Just wondered if it's perfectly fine to use image downloaded from https://www.armbian.com/nanopi-m4-v2/ for Nanopi M4 original version. Thanks

It's working for me now. Thanks Igor.

The work around [trusted=yes] no longer works. As Igor said, Bionic one is not signed. If you must, $ sudo apt update -o Acquire::AllowInsecureRepositories=true -o Acquire::AllowDowngradeToInsecureRepositories=true for the time being while it's being solved (hopefully, it is).

here's what I did to get around the issue in the meantime: $ cat /etc/apt/sources.list.d/armbian.list deb [trusted=yes] http://apt.armbian.com bionic main bionic-utils bionic-desktop

Errors shown when doing $ sudo apt update ... Ign:1 https://armbian.tnahosting.net/apt bionic InRelease Get:8 https://armbian.tnahosting.net/apt bionic Release [17.5 kB] Get:9 http://ports.ubuntu.com bionic-updates InRelease [88.7 kB] Ign:10 https://armbian.tnahosting.net/apt bionic Release.gpg .... E: The repository 'http://apt.armbian.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

From armbian-config -> System -> Other, here are the options I'm seeing linux-image-current-rockchip64=21.02. 5.10.21-rockchip64 … linux-image-dev-rockchip64=21.02.2 … 5.10.16-rockchip64 … linux-image-legacy-rk3399=21.05.1 … 4.4.213-rk3399 I don't see an option of rk3399 with 5.x kernel. Do you know which dtb it's for those with 5.x kernel from the Download page: https://www.armbian.com/nanopi-m4/#kernels-archive-all

Yes, that is correct.

I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64 while others uInitrd -> uInitrd-5.10.35-rockchip64 dtb -> dtb-5.10.35-rockchip64 The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard. It works fine afterward but I wondered if there is the right way to fix this issue for good. Thank you,

I'm getting burst "VOP vblank IRQ stuck for 10 ms" error messages in dmesg and wondering what it means and if anything to improve/fix. I'm using Nanopi m4 $ uname -a Linux nanopim4 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux kern :err : [Sat Mar 13 22:20:13 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:09 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:11 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:18 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:21 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms

I didn't know it is available now. I was so excited to try out. As you warned, I did the upgrade and bricked it. I couldn't get it boot up and ended up with restored from my backup back to 4.4 ;-( Anyone success upgrading from 4.4 to 5.1 without reinstalling things? My setup is the boot on SD with root on usb HDD, if that matters.

Right, between the original post and now, I had been switching and trying different Armbian Ubuntu, Debian with Buster, and other variations. None of them worked at the time. I stopped at some point and the workaround was to connect a usb 2.0 hub as a middle man. Recently, I found myself need to do a full local rsync between hard drives again and it works. I'm currently with Armbian 21.02.1 Bionic with Linux 4.4.213-rk3399

Somehow as of today, I tried again and it seems the problem is no longer seen. At least so far, rsync between two hard drives about 30 hrs is working fine. ``` $ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=nanopim4 BOARD_NAME="NanoPi M4" BOARDFAMILY=rk3399 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=b0760915-dirty DISTRIBUTION_CODENAME=bionic DISTRIBUTION_STATUS=supported VERSION=20.11 LINUXFAMILY=rk3399 BRANCH=legacy ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image ```

I ran apt-cache below and it showed that it has only the legacy 4.4.213-rk339. Is it the same for everyone else or somehow I am missing something? $ apt-cache show linux-image*rk3399 | grep -E "Package:|Version:|version:" Package: linux-image-legacy-rk3399 Version: 20.08.8 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.6 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.4 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.3 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.2 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.1 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08 files, version: 4.4.213-rk3399.

Oh let me know if this happens to only for me or in general. If it is the former, I wondered what caused and how to solve it. Thanks

@Werner could you explain a bit more how to switch between legacy and current branch? Thank you

Hi, I'm using NanoPi M4 $ uname -a Linux nanopim4 4.4.213-rk3399 #3 SMP Mon Oct 5 15:53:54 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux and wondering if I can upgrade the linux kernel to 5.8.x without reinstalling other things. I tried armbian-config -> System -> Other All available options are those 4.4.213-rk3399 with different Armbian versions 20.08.x. I'm currently on 20.08.9 Appreciated any step, pointer Thank you

Hi all, I'd just like to share a problem I experienced and what solved after a bit of Googling. Basically, I have Nextcloud installed on my Nanopi M4 (v1) with Armbian: $ uname -a Linux nanopim4 4.4.192-rk3399 When I sync files from my Android phone via local wifi, often the transfers were just failed. Not always but usually, it's when a directory contains lot of large files. After a bit of Googling and came across this: https://unix.stackexchange.com/questions/494290/nanopi-m4-rk3399-apache2-ssl-large-download-hangs/495378#495378 It works. The problem's solved after: ethtool -K eth0 rx off tx off and put the command in /etc/network/if-up.d/ethtool Just wondering if anyone knows the root cause and have better solution than disabling things. Thanks,

Thank you Igor. I finally got it work. Basically, follow your guidance: $vi /lib/systemd/system/ [Unit] Description=Bluetooth nanopi After=bluetooth.target [Service] Type=forking ExecStartPre=/bin/echo 1 > /sys/class/rfkill/rfkill0/state ExecStart=/usr/bin/hciattach /dev/ttyS0 bcm43xx 115200 > /dev/null TimeoutSec=0 RemainAfterExit=yes SysVStartPriority=99 [Install] WantedBy=multi-user.target $ sudo systemctl --no-reload enable nanopi-bluetooth.service $ sudo systemctl start nanopi-bluetooth.service BT is working now. : ) Trying to get my generic gamepad to work is another story : ( But at least, it's connected.

I got the bluetooth working with a fresh install from the download section to a new microSDCard. I have rootfs installed in my external hdd. So, I did similar procedures in what nand-sata-install is doing except formatting the external hdd (rootfs). Basically, - setting the correct UUID and others in /boot/armbianEnv.txt $ mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr - setting the correct UUID and mount locations in /etc/fstab The system boots fine. Other things seem to be working okay. BUT the bluetooth is not working : ( Here is $ sudo armbianmonitor -u http://ix.io/1Qkq Helps are appreciated.

sir, yes sir. : ) I'll definitely try to flash the image from the download section to a new SDCard to just check if BT comes back to work and report here when I get a chance. By the way, do you have any suggestion for me to just update the core parts in my existing system with the image from the download section? I have things setup already and its kind of painful to re-config things from a fresh install.

Thanks Igor. Pretty newbie here. I changed to nightly firmware and upgrade there to $ uname -a Linux nanopim4 5.1.0-rk3399 #5.91.190708 SMP Tue Jul 9 07:58:42 CEST 2019 aarch64 GNU/Linux Things are still not working. Here is $ sudo armbianmonitor -u (it works now :)) http://ix.io/1Qi6 Thanks for your helps.

I think I saw Buster available on the Download page but what I did was simply change /etc/apt/sources.list and apt update & upgrade. Something similar to: https://linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster somehow armbianmonitor -u returned empty string for me. I did something similar here: http://sprunge.us/yK0GdC Thanks for your help.