CSC Armbian for RK3318/RK3328 TV box boards

[MattWestB]

Have don apt-get update and grade.

Armbian-config disabling firmware update = freeze kernel.

apt-mark showhold
linux-dtb-current-rockchip64
linux-image-current-rockchip64

dpkg -i  on dtb and image.

sync and reboot and the  box rebooting OK with old kernel (3 times) !!

 

CLI printout from kernel install:

root@RK3318-Box-Orange:~# dpkg -i linux-image-edge-rockchip64_25.11.0-trunk_arm64__6.16.0-S038d-D0b5d-Pa674-Cb487H3d80-HK01ba-Vc222-Bd200-R448a.deb
(Reading database ... 74668 files and directories currently installed.)
Preparing to unpack linux-image-edge-rockchip64_25.11.0-trunk_arm64__6.16.0-S038d-D0b5d-Pa674-Cb487H3d80-HK01ba-Vc222-Bd200-R448a.deb ...
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'prerm' starting.
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'prerm' finishing.
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'preinst' starting.
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'preinst' finishing.
Unpacking linux-image-edge-rockchip64 (25.11.0-trunk) over (25.11.0-trunk) ...
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postrm' starting.
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postrm' finishing.
Setting up linux-image-edge-rockchip64 (25.11.0-trunk) ...
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postinst' starting.
 * dkms: autoinstall for kernel 6.16.0-edge-rockchip64 was skipped since the kernel headers for this kernel do not seem to be installed
update-initramfs: Generating /boot/initrd.img-6.16.0-edge-rockchip64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.16.0-edge-rockchip64
Image Name:   uInitrd
Created:      Thu Aug 14 15:40:18 2025
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    25341844 Bytes = 24747.89 KiB = 24.17 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.16.0-edge-rockchip64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.16.0-edge-rockchip64'
update-initramfs: Armbian: done.
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.16.0-edge-rockchip64'
Armbian: Debian compat: linux-update-symlinks install 6.16.0-edge-rockchip64 boot/vmlinuz-6.16.0-edge-rockchip64
Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postinst' finishing.
root@RK3318-Box-Orange:~# sync
root@RK3318-Box-Orange:~# reboot

Is i doing something wrong then it was i remember how to do offline kernel up and down grade ??

Have double checking its the right USB-SSD and not  the SD-Card for all try.

 

fdisk -l

Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SSD PLUS 480GB

 

df -h

/dev/sda1       436G   19G  414G   5% /

 

List of /boot/

root@RK3318-Box-Orange:~# ls -la /boot/
total 186536
drwxr-xr-x  4 root root     4096 Aug 14 15:40 .
drwxr-xr-x 23 root root     4096 Aug  1 16:59 ..
-rw-r--r--  1 1004 1004      365 Aug 14 15:40 armbianEnv.txt
-rw-r--r--  1 root root     1536 Nov 30  2023 armbian_first_run.txt.template
-rw-r--r--  1 root root    38518 Nov 30  2023 boot.bmp
-rw-r--r--  1 1004 1004     3180 Nov 30  2023 boot.cmd
-rw-rw-r--  1 root root     3252 Nov 30  2023 boot.scr
-rw-r--r--  1 root root   258998 Jul 14 17:06 config-6.12.38-current-rockchip64
-rw-r--r--  1 root root   263963 Aug 13 17:16 config-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       26 Aug 14 15:38 dtb -> dtb-6.16.0-edge-rockchip64
drwxr-xr-x  3 root root     4096 Jul 16 14:39 dtb-6.12.38-current-rockchip64
drwxr-xr-x  3 root root     4096 Aug 14 15:38 dtb-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       30 Aug 14 15:40 Image -> vmlinuz-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       33 Aug 14 15:20 initrd.img -> initrd.img-6.16.0-edge-rockchip64
-rw-r--r--  1 root root 25352236 Jul 16 14:44 initrd.img-6.12.38-current-rockchip64
-rw-r--r--  1 root root 25341844 Aug 14 15:40 initrd.img-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       37 Jul 16 14:40 initrd.img.old -> initrd.img-6.12.38-current-rockchip64
-rw-r--r--  1 root root        0 Aug 14 15:40 .next
-rw-r--r--  1 root root  5618205 Jul 14 17:06 System.map-6.12.38-current-rockchip64
-rw-r--r--  1 root root  5756639 Aug 13 17:16 System.map-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       30 Aug 14 15:40 uInitrd -> uInitrd-6.16.0-edge-rockchip64
-rw-r--r--  1 root root 25352300 Jul 16 14:44 uInitrd-6.12.38-current-rockchip64
-rw-r--r--  1 root root 25341908 Aug 14 15:40 uInitrd-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       30 Aug 14 15:20 vmlinuz -> vmlinuz-6.16.0-edge-rockchip64
-rw-r--r--  1 root root 38277632 Jul 14 17:06 vmlinuz-6.12.38-current-rockchip64
-rw-r--r--  1 root root 39352832 Aug 13 17:16 vmlinuz-6.16.0-edge-rockchip64
lrwxrwxrwx  1 root root       34 Jul 16 14:40 vmlinuz.old -> vmlinuz-6.12.38-current-rockchip64

 

First line in dmesg -T:

[Thu Aug 14 15:33:40 2025] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[Thu Aug 14 15:33:40 2025] Linux version 6.12.38-current-rockchip64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #1 SMP PREEMPT Mon Jul 14 14:02:59 UTC 2025

 

The install is noble:

 

   /_\  _ _ _ __ | |__(_)__ _ _ _
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|

 v25.5.1 for RK3318 Box running Armbian Linux 6.12.38-current-rockchip64

 Packages:     Ubuntu stable (noble)
 Support:      DIY (community maintained)

 

Any creative / constructive thinking ??

Edited August 14 by MattWestB

[jock]

@MattWestB According to /boot, your box should boot 6.16. I don't know though if you have other eMMC/sd/USB devices which may interfere 

[MattWestB]

I  was thinking the same.

Must soldering the TTY cosolle so can getting the Uboot messages.

The eMMC is the flash dead and have one Armbian on the SD-Card for jump starting the USB-SSD but the device used is only the USB-SDD i the demesg and it shall writing other devices if not booting one the USB-SSD and its the right one then HA is current and on the SD-Card is not updated.

 

Shall i rewriting the bootloader on the USB-SSD but it shall being updated for some mouths ago ?

[Thiên Thư Lục]

@jock @MattWestB thank you for you help! Sorry for the late reply.

Im did update the dtb files jock said, and usb 3.0 work better now, but not as stable as 100%. Sometimes it still hang on reboot unless i disconnect the device on usb 3.0 port and re-insert power for complete reboot and booting, and sometimes it boot without recognise the device on usb 3.0 port. And sometimes the WiFi drop connection and reconnect repeatedly many times without dmesg errors, and need manual reboot. So maybe im just unlucky getting the bad batch of H96 Max.

 

Due to the needed of stability, especially with the usb port, i switching to Dell Wyse 3040 for now. It's was fun playing with armbian and rockchip. Thank you for your contribution @jock 🥰

[MattWestB]

The deep rabbit hole of (DAS) UBOOT !!

This is not for you if you is running on:

Internal eMMC with factory Android boot loader.

eMMC with updated boot loader but no other boot media.

eMMC with updated boot loader and second boot loader and system on SC-Card and no other boot media (Jump booting eMMC > SD-Card).

eMMC erased / not working and loading boot loader and system and boot loader from SD-Card and no other boot media,

 

But if you is running on:

eMMC with updated boot loader and jump booting to SD-Card with boot loader and booting from there other media.

eMMC erased / not working and loading boot loader (and perhaps system) from SD-Card and jump booting other media.

 

Then jump booting on one SD-Card the UBOOT is loading the init system with first stage of the kernel from the SD-Card.

If have one compatible second stage boot on the SD-Card and UBOOT is loading it it shall being OK.

But as all armbian media have the the same "rootdev=UUID=c6b30a59-8162-46cb-b449-e9615c4a9889" or lable in the armbianEnv.txt on the uboots boot partition its "roll the dice" witch partition the kernel is using then its have loading. If using the SD-Card and its current with the uboot kernel all is OK. But around 50% is using one of the USB media and if its boot partition is not in sync with the kernel its being very strange.

 

If having one SD-Card with latest noble with updated system and kernel 6.16X and putting in one USB-SSD with one old  Jammy and uboot on the SD-Card is booting it is the first kernel loading first stage from the SD-Card (sd /boot) and then mapping the system with /boot from the USB-SSD. The result is very interesting then the old Jammy is coming up with 6.16X kernel but cant loading modules that it need after the first stage  of booting then the /boot/ is the Jemmy with original system and modules that  the 6.16X kernel cant using (but its BOOTING !!!).

 

For booting the system in the right  way its possible caging the "rootdev=" UUID or lable in the armbianEnv.txt on the SD-Cards /boot.

Its working but you is missing the auto select of boot media = if labling the USB-SSD "SSD" and putting in the lable "SSD" it cant boot the system on the SD-Card or other USB devices (and i think its still getting  mixing files from the SD-Card and SSD).

Also formatting the XF4 partition on the SD-Card (not touching the partition table) its booting all USB media OK then uboot is using the system and boot form the USB media and only mini loader from the SD-Card.

Or if having the same system type / version it shall working updating both the system to the same level and have the same hard and software configured on the SD-Card and the USB system media.

 

Normal symptoms is problem with network manager starting all services, Docker service not starting and other services can having problems. Also if installed kernel and the real booted one is not the same its not good then its being miss match of many files its depends on.

 

I have using the erase and sync method and its looks working OK but the sync is more work but can have more systems working OK as backup if somthing is going wrong.

 

As long our UBOOT cant select / and /boot partitions like in X86 systems wi must living with that but if knowing how its working we can living better with it.

 

PS: some version of armbian-config can force witch media to boot from but i have not testing it and its not in the latest version also i have not testing eMMC with updated boot loader and jump booting then the box i testing it on have failed eMMC so only SD-Card boot = no risk for bricking  the system hard and must force mask-rom.

 

So now running  Noble with 6.16.1-edge-rockchip64 kernel !!!