MattWestB

@mkultra Looks like the command package is not installer as standard in ubuntu: # route Command 'route' not found, but can be installed with: apt install net-tools But install net-tools it shall working OK (I hope)

Thanks @jock and the LED cofig was from memory and form the very old install and it was running on the default one. Something is crashing the kernel then loading modules but i shall looking if its being OK then not loading the new drive. And in the e log: [Tue Oct 8 20:04:53 2024] tm16xx_led_set+0x60/0x6c [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_probe+0x390/0x6e0 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_i2c_probe+0x5c/0x80 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_init+0x5c/0x1000 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx 4-0024: Display initialized successfully So its loaded OK. But cant testing it by instruction then the display-utils is not installed and i cant finding how to do that. The service call is also not working (/sbin/display-service dont exist) but writing to sys-class is working OK. cat /sys/class/leds/display/digits 4 3 2 1 cat /sys/class/leds/display/segments 0 1 2 3 4 5 6 echo "boot" > /sys/class/leds/display/value Is showing "BOOT". Do you have some other ways testing the e display and setting up service call ? Thanks for great work done and continuing doing it well !!! Edit: Was looking in the Makefile and was doing the "install: module module-install service-install" part manually and now its working !!! I think we need one package for installing it in the system for normal users and adding boot and WiFi / Eth indicator from OS.

I have 2 H69Max branded boxes with 4G RAM and 64G eMMC. PCB is only labeled RK3318_V1.4 with fd6551 LED-driver chip. Using LED conf 7 and working great WiFi and BT AP6330 looks working OK but using Eth for network access. Only USB is worse then other RK3X boxes if using little bandwidth on them. I have one backup of original Android but its very large and must look if i can extracting the original DTS files from it.

base-files looks being fixed for ARM32 devices now after updating with apt-get: _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.8.4 for rk322x-box running Armbian Linux 6.6.47-current-rockchip Packages: Ubuntu stable (noble)

Looks like the kernel problems have being fixed and working as expected updating jammy stable: /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.8.3 for RK3318 Box running Armbian Linux 6.6.47-current-rockchip64 Packages: Ubuntu stable (jammy) Support: DIY (community maintained) IP addresses: (LAN) 192.168.2.X (WAN) X.X.X.X Also possible updating to Noble after getting all updates installed with command do-release-upgrade but is little work getting the external apt-sources working after being done (hint: /etc/apt/sources.list.d/ ).

Ubuntu noble base-files broken after Armbian 24.5.1. Upgrading Ubuntu Jammy to Noble is working OK is little trixy. Current base-file is not in noble (last is 24.5.1). So is losing rk322X-config and all Arbian futures. Its depends on armbian-bsp-cli-rk322x-box-current and armbian-bsp-cli-rk322x-box that have 24.5.1 so can forcing downgrading and get the base-files installed but in on obliterate version. Both is having the current version of 24.8.3 but cant being used then base-files not exiting in this version. Command used for debug and installing working file set for getting armbian working after ubuntu update: apt install base-files=24.5.5-13ubuntu10-noble apt list -a base-files Listing... Done base-files/noble,now 24.5.5-13ubuntu10-noble armhf [installed] base-files/noble 24.5.1-13ubuntu10-noble armhf base-files/noble 24.2.1-13ubuntu7-noble armhf base-files/noble-updates 13ubuntu10.1 armhf base-files/noble 13ubuntu10 armhf apt install armbian-bsp-cli-rk322x-box=24.5.1 apt list -a armbian-bsp-cli-rk322x-box Listing... Done armbian-bsp-cli-rk322x-box/noble 24.8.3 armhf [upgradable from: 24.5.1] armbian-bsp-cli-rk322x-box/noble 24.8.2 armhf armbian-bsp-cli-rk322x-box/noble,now 24.5.1 armhf [installed,upgradable to: 24.8.3] armbian-bsp-cli-rk322x-box/noble 24.2.5 armhf armbian-bsp-cli-rk322x-box/noble 24.2.1 armhf apt install armbian-bsp-cli-rk322x-box-current=24.5.1 apt list -a armbian-bsp-cli-rk322x-box-current Listing... Done armbian-bsp-cli-rk322x-box-current/noble 24.8.3 armhf [upgradable from: 24.5.1] armbian-bsp-cli-rk322x-box-current/noble 24.8.2 armhf armbian-bsp-cli-rk322x-box-current/noble,now 24.5.1 armhf [installed,upgradable to: 24.8.3] armbian-bsp-cli-rk322x-box-current/noble 24.2.5 armhf armbian-bsp-cli-rk322x-box-current/noble 24.2.1 armhf Then getting one little more happy RK322X box: _ _________ ____ _ _ __| | _|___ /___ \|___ \__ __ | |__ _____ __ | '__| |/ / |_ \ __) | __) \ \/ /____| '_ \ / _ \ \/ / | | | < ___) / __/ / __/ > <_____| |_) | (_) > < |_| |_|\_\____/_____|_____/_/\_\ |_.__/ \___/_/\_\ Welcome to Armbian 24.5.1 Noble with Linux 6.6.47-current-rockchip And apt-get is saying: The following packages have been kept back: armbian-bsp-cli-rk322x-box armbian-bsp-cli-rk322x-box-current Then base-files is broken. Pleas triggering one new build of base-files for our RK322X boxes so we can getting then updated to newer version of armbian without installing the OS new. Thanks in advance. Edit: Wast testing the daily build with current build state but after doing update with apt the installed base-files and its dependencies is flagged as local and is not working OK but is possible installing the same version as for the normal current ubuntu Noble and its working on one old code base = working but not expected of the edge build that shall being at the last code base /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v24.8.3 for rk322x-box running Armbian Linux 6.6.47-current-rockchip Packages: Ubuntu stable (noble) Support: DIY (community maintained) = base-files is the nightly build and the 2 dependency files is the old one but its possible downgrading the base-files but then cant going back to the nightly ones.

= three month not working stable if not jumping to nightly. Way not manually triggering one rebuild with latest commits for stable / current kernel of the RK33X8 so users can have working boxes without large problems ? I knowing CSC but having one OK working stable / current is also important for this devices and edge / best is not the way for most users. By the way the armbian-config scrip was working great getting old kernel back after getting changeroot mapping all OK.

Unfreez i getting the kernel 6.6.39-current-rockchip64 (the bad one). Updating i getting the kernel 6.6.47-current-rockchip64 (not tested then it look being one bad one). Installing edge i getting kernel 6.10.6-edge-rockchip64 that booting but have not testing it for real if its working OK.

Great thanks @mrdotdotdot it was fixed in some minutes !! Was already having Armbian 24.5.1 Jammy with Linux 6.1.63-current-rockchip64 (last found current image) on USB-stick so it was only booting and mounting and configuring and shutting down and connecting the Thread RCP and HA is working well !! And as you was writing dont forgetting freeze the kernel update or must redoing all more times.

@mrdotdotdot or some one else have one good instruction how booting external media and chroot and fixing the kernel package installed ?

By the way i agree with @Netraam31 with the install is using edge and its no download of current install so for new users is one no go then the edge kernel is being broken if not having one one year old current image that is working OK.

Welcome to Armbian 24.5.1 Jammy with Linux 6.6.32-current-rockchip64 After package upgrade: Kernel update it braking booting then cant finding root file system and landing in Ubuntu Busybux. Only one of 3 RG3318 ungraded the other ones shall waiting. The package is 6-linux-image-current-rockchip64_24.5.3_arm64.deb with kernel 6.6.39-current-rockchip64 (current NOT Edge !!). So recommending frees kernel updates so staying on 6.6.32 or you is getting no working system.

From first post: Prebuilt images: Archived images - built by Armbian servers and GPG-signed: https://imola.armbian.com/dl/rk3318-box/archive/ Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Stables provided by me (unsigned): https://users.armbian.com/jock/rk3318/ but the Archive with current images for RK3318 is down (many types is missing on the homepage) but the RK3228 is there but its not helping for my RK3318 boxes. Do some have one mirror of the latest current / stable builds that can being shred ?

Looks like the CE (China Export NOT the EU CE) have "re branding" one RK to some HUW chop that was likely in one phone copy running one RK chip and (or more likely tablet).

@svdmk Thanks for sharing the knollage !! Did you also finding the console comport on the PCB ?

Can you making one hi rec photo of both sides of the PCB its likely have pads for MASKROM but you can using the pads for MMC / NAND but need looking for the pining of then for getting the right one. Also if being in MASKROM it shall booting DC-card with bootloader on it. Then having (updated not factory Android) bootloader on the EMMC it shall also booting USB-flach sticks without problem.

@audio kees Use disk manager in windows system for erasing all partitions on the SD-cad and it shall being OK. But burning one new images its making more partitions agen.

Was just running apt-get update and rebooting and its getting updated kernel: _ _________ ____ _ _ __| | _|___ /___ \|___ \__ __ | |__ _____ __ | '__| |/ / |_ \ __) | __) \ \/ /____| '_ \ / _ \ \/ / | | | < ___) / __/ / __/ > <_____| |_) | (_) > < |_| |_|\_\____/_____|_____/_/\_\ |_.__/ \___/_/\_\ Welcome to Armbian 23.11.1 Jammy with Linux 6.1.63-current-rk322x And i have one Ubuntu CLI on the HDMI monitor and the LED have being fixed so not the fix is online !!! Great thanks for great work done !!!!

Looks like only minimal is being build for Ubuntu but the loggfile is shoeing the standard shall have being done 2. From the "Armbian_23.8.99_Rk322x-box_jammy_current_6.1.62.img.txt" file: "Armbian_23.8.99_Rk322x-box_jammy_current_6.1.62.img.xz" but the file is missing.

If i have understanding it right if erasing the eMMC and installing the loader in it the its possible jump stating eternal media also USB as secondary uboot is on the media. Then the system is using the first boot bin from the eMMC and the uboot from the media. Your try is working OK until the trust OS is starting and its getting some problems (legacy kernel need one old type and current need one newer one for working OK). I think fabiobassa is the one that having more deep knowledge of this functions but its very deep in the RK boot code.

@Aapo Tahkola My experience of USB on RK boxes is that its working good some time but if getting problem is needed being repowered for detecting new and disconnected device and normally its one time bomb before getting problems with USB both 2 and 3 then its using the same hardware implementation.

@remlei very true 1/8G can running but best mounting one SD-card for docker data so all HA containers is being out of the eMMC then its being full then HA is installed and booting up for the first time also USB is tricky and need repower for getting disconnected device being reconiced after some time but they is working pretty good for no production systems.

For the journalctl problem reinstalling the package restart the system and reinstall HA as is written in the HA hint and its working. The large problem is if having less RAM its braking the zram logging but its one other story. For install download one older HA installer and its working without local mode.

Your board is not having the current limiting resistors for the comport they is not populated on the picture. Put some soldering led instead of the resistor or if you is having some around 100 Ohm in the right place and it shall working well.

ARM devices is not using boot manager then they is not having one PC-BIOS they using U-boot and booting the installed system and nothing else.