Meestor_X

Seems there were others with a similar problem. I can't tell if there's a clear solution contained within these threads?

Been using 24.11.1 Bookworm for a while, but yesterday did an apt update && apt upgrade, only to find that the resulting image would no longer boot. No "activity" light at all on the front on reboot. Downloaded 25.5.0 Trixie "just to see", but it doesn't boot either. What happened after 24.11.4? Is there something different I should be doing if I want to run a later version of Armbian?

NB - evtest does not come with Armbian Bookworm. A quick "apt install evtest" and we're away! root@radxa-e20c:~# evtest /dev/input/event0 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 Input device name: "gpio-keys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 185 (KEY_F15) Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value 250 Repeat code 1 (REP_PERIOD) Value 33 Properties: Testing ... (interrupt to exit) Event: time 1739040710.916095, type 1 (EV_KEY), code 185 (KEY_F15), value 1 Event: time 1739040710.916095, -------------- SYN_REPORT ------------ Event: time 1739040711.050330, type 1 (EV_KEY), code 185 (KEY_F15), value 0 Event: time 1739040711.050330, -------------- SYN_REPORT ------------ Do you know where I can find information on how to change settings for this button?

Thank you so much, @Torte! I'll have to bookmark this as my next rabbithole. 🙂

Oh! I thought those commands were needed for your custom dts. What do you know! All I had to do was: echo enp1s0 > device_name echo 1 > rx And it "just works"! Also, this "just works": root@radxa-e20c:/dev/input# cat event0 To see when the user button is pressed. Although, I'm not sure what data is being produced from it! root@radxa-e20c:/dev/input# cat event0 | hexdump -C 00000000 8b 8a a7 67 00 00 00 00 5c 14 0f 00 00 00 00 00 |...g....\.......| 00000010 01 00 b9 00 01 00 00 00 8b 8a a7 67 00 00 00 00 |...........g....| 00000020 5c 14 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 |\...............| 00000030 8c 8a a7 67 00 00 00 00 3e 65 01 00 00 00 00 00 |...g....>e......| 00000040 01 00 b9 00 00 00 00 00 8c 8a a7 67 00 00 00 00 |...........g....| 00000050 3e 65 01 00 00 00 00 00 00 00 00 00 00 00 00 00 |>e..............| I had no idea it was that easy. Is this a Linux thing? Armbian thing? Radxa thing? Where can I read up on this kind of hardware control?

TY for your reply. They definitely can be controlled by echoing values to the `/sys/class/leds/` and even though the "trigger" is set to "netdev" and tx and rx files appear, I'm not seeing any activity on those LEDs with network activity. I can manually make the LEDs blink by doing something like echo heartbeat > /sys/class/leds/lan-led/trigger cat /sys/class/leds/lan-led/trigger will show the available triggers, and a [] around the currently selected one. cat trigger none usb-gadget usb-host rc-feedback bluetooth-power rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock mmc0 timer oneshot disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat backlight gpio cpu cpu0 cpu1 cpu2 cpu3 activity default-on transient flash torch panic [netdev] mmc1 It looks very configurable, just doesn't seem to be "automatically" working to show network activity.

How did you figure this out? I can't really understand anything that's in the dts file or what you've got going in that script... as per the info here: https://github.com/armbian/build/pull/7157 I should be able to get the LEDs working for the ethernet connection on the E20C. Not sure if I need an overlay, or a script like yours or both?

TY, I couldn't figure out where to post as the e20c doesn't have a tag. Did you just add it? NM, I was looking for e20c, didn't realize the tag was Radxa-E20C.

Seems like a great little box, but Radxa doesn't have much info about the hardware side of it. Simple stuff like accessing the LEDs and buttons when running Armbian. Posted on the Radxa website but no replies, so just curious if anyone has dug into it at all?

That tool is great for backing up, but not doing the UUID/boot change I need. I have to see if I can find some documentation on how to copy and change the boot info as staring at the source code of armbian-install (where this is solved) is making my eyes hurt. 😉

I see. The only reason I have to boot from µSD or USB is to update the eMMC, it's not a "regular thing", so if it's slow I don't mind. As I said earlier, with just the eMMC and µSD, it works exactly the way I want, I was simply hoping to add USB to the mix as an alternative to µSD since that would be easier for end users. If it can't work exactly the same as the way it works currently, then there's no point. (i.e. it doesn't matter if the eMMC is unbootable or even unformatted, the µSD will always boot first ATM). If the USB boot relies on the eMMC or µSD then it's not going to be useful in my case. TY for the detailed explanation.

Very cool. I didn't realize it could be that easy. Great (but potentially slow) for making backups. Here's the "tricky parts" that I'm still trying to figure out... - cloning a larger drive that only has part of it used to a smaller drive that has room for the used part. - changing the UUID/boot info so that you can clone a µSD to the eMMC and still have it boot from either one.

TY for your reply. Maybe I missed something, but I don't see anything there regarding setting the boot order or making the device able to "triple-boot".

Still haven't figured this one out, if anyone has a suggestion?

Ty. I picked up a cheap sda1115 ADC which uses I2C. Will i2c on the Rock-S0 need an overlay or is it already enabled by default in armbian. Haven't figured out how to test for that yet. NM - it "just works", I didn't have to change anything or add an overlay! 🙂

find /boot/overlay-user -type f /boot/overlay-user/pwm.dtbo /boot/overlay-user/pwm.dts So, using the included /boot/dtb/rockchip/overlay/ files like rk3308-b@1.3ghz.dtbo, rk3308-s0-ext-antenna.dtbo and rk3308-sdio@10mhz.dtbo and my own overlay in /boot/overlay-user/ named pwm.dtbo The ONLY way it works is this: (important lines in /boot/armbianEnv.txt): overlay_prefix=rk3308 . . . user_overlays=pwm overlays=b@1.3ghz s0-ext-antenna sdio@10mhz

Do you happen to know if the S0 has an ADC input? (Got the overlays working finally)

Very cool! I didn't even know that would be possible to send triggers to GPIOs like that. I'd love to learn more about what's possible with GPIOs. Are these LEDs already on the S0 or they're ones you are connecting to the header?

Here's the fix if anyone hasn't figured it out... sudo chmod +x /etc/update-motd.d/*

motd is no longer showing on boot with my rockpi-s and rock s0. (same cpu) I feel like this started when I updated from 24.8.3 to 24.11.1 Anyone else having this problem? This looks suspect... root@rock-s0:/etc# cat /etc/motd cat: /etc/motd: No such file or directory root@rock-s0:/etc# cat /var/run/motd cat: /var/run/motd: No such file or directory root@rock-s0:/etc# cd /etc/ root@rock-s0:/etc# ls -l motd lrwxrwxrwx 1 root root 13 Nov 24 15:27 motd -> /var/run/motd root@rock-s0:/etc# cd /var/run root@rock-s0:/var/run# ls -l motd ls: cannot access 'motd': No such file or directory

Ok, that doesn't work either! 😉 I understand what you mean, now, @MaxT The added "-" messes everything up. root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 overlays=rk3308-b@1.3ghz rk3308-s0-ext-antenna rk3308-sdio@10mhz user_overlays=pwm usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 294 bytes read in 4 ms (71.3 KiB/s) 14325592 bytes read in 610 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54150 bytes read in 11 ms (4.7 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/-rk3308-b@1.3ghz.dtbo' Failed to load '/boot/dtb/rockchip/overlay/-rk3308-s0-ext-antenna.dtbo' Failed to load '/boot/dtb/rockchip/overlay/-rk3308-sdio@10mhz.dtbo' 538 bytes read in 5 ms (104.5 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000

Looks like the latest armbian-config is better, but it's still not respecting the overlay_prefix. Used armbian-config to add the sdio@10mhz overlay, and it did this to armbianEnv.txt. root@rock-s0:/boot# cat armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 overlays=rk3308-sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Of course, it didn't load the overlay, due to the prefix being added. Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 260 bytes read in 3 ms (84 KiB/s) 14325592 bytes read in 611 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54150 bytes read in 10 ms (5.2 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-rk3308-sdio@10mhz.dtbo' Moving Image from 0x680000 to 0x800000, end=2560000 My suggestion would be to have armbian change the armbianEnv.txt file to not include the overlay_prefix= line by default. Not sure if it serves any useful purpose?

Ok, so one issue is that armbian-config doesn't create the correct line for the overlays. The overlay_prefix is automatically added to the name, and the command is "overlays=", not "ftd_overlays=" root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 user_overlays=pwm overlays=b@1.3ghz s0-ext-antenna sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 295 bytes read in 3 ms (95.7 KiB/s) 14324658 bytes read in 609 ms (22.4 MiB/s) 30097920 bytes read in 1274 ms (22.5 MiB/s) 54895 bytes read in 9 ms (5.8 MiB/s) 459 bytes read in 6 ms (74.2 KiB/s) Applying kernel provided DT overlay rk3308-b@1.3ghz.dtbo 1204 bytes read in 7 ms (168 KiB/s) Applying kernel provided DT overlay rk3308-s0-ext-antenna.dtbo 226 bytes read in 6 ms (36.1 KiB/s) Applying kernel provided DT overlay rk3308-sdio@10mhz.dtbo 538 bytes read in 6 ms (86.9 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14324594 Bytes = 13.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d17d000, end 1df26372 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK Starting kernel ...

Ok, tried some adding some other overlays via armbian-config and I see that they DIDN'T load.. . root@rock-s0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-s0.dtb extraargs=cma=16M rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1 rootfstype=ext4 user_overlays=pwm fdt_overlays=rk3308-bs@1.3ghz rk3308-bs rk3308-s0-ext-antenna rk3308-sdio@10mhz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Found U-Boot script /boot/boot.scr 3633 bytes read in 4 ms (886.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 331 bytes read in 4 ms (80.1 KiB/s) 14324658 bytes read in 610 ms (22.4 MiB/s) 30097920 bytes read in 1275 ms (22.5 MiB/s) 54895 bytes read in 8 ms (6.5 MiB/s) 538 bytes read in 6 ms (86.9 KiB/s) Applying user provided DT overlay pwm.dtbo Moving Image from 0x680000 to 0x800000, end=2560000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14324594 Bytes = 13.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d17d000, end 1df26372 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK

NM, I see that it did load. Applying user provided DT overlay pwm.dtbo It didn't actually enable the PWM, but it does look like it loaded at least! I'll have to try some system ones and see what happens.