Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

eselarm

Members
  • Joined

  • Last visited

Everything posted by eselarm

  1. I also do not know this, but what I do for older solar inverters is using my own power measurement modules. The inverters themselves have no I/O for telemetry (can buy as option though), only a simple pixels based display that shows some stats. So it is a matter of (bi-directional) power measurement. I use commercial modules (Sonoff, Shelly) but put Tasmota on those. Tasmota has plenty of options for telemetry I/O, like MQTT, or direct push in to InfluxDB for example. Those ESP based modules are WiFi only, so I had to take some measures w.r.t. WiFi networking/AccesPoints, but still less work than something wired as that also requires full isolation and still will then be destroyed by lightning for example. I assume you don't want to use the SBC for it's 40-pin header (GPIO's, busses), but just just its IP networking, HID (display, etc) and power supply. Or what shall the SBC/Armbian do? Anyway, I am in EU, it is also a matter of connectors and power specifications. So I am only familiar with 230V AC single phase and 400V AC 3-phase. Also the charging is in your car, not in the boxes shown on that ratepick website. Also 'best' might be not best for you but best for Amazon etc and as you (I think) expect, for all those cloud apps and owners trying to benefit from all sorts of stats/data regarding the power flowing from the grid to your car. So they can sell that info to electricity company so then they can raise the price per kWh at night etc. And know when you are at home (or not). So before buying, try to analyze what is actually inside in a more fundamental way. Like that a 'solar invertor' is indeed doing conversion ('invert') from DC to AC, but way more important is the algorithms handling the reality of clouds passing by and simply the complexity of PV cells characteristics.
  2. At least one of the 4 below should show some version: dd if=/dev/mtdblock0 of=/boot/spiflash_0.dump count=32k status=progress strings /boot/spiflash_0.dump | grep "U-Boot SPL 20" dd if=/dev/mmcblk0 of=/boot/bootarea_0.dump count=32k status=progress strings /boot/bootarea_0.dump | grep "U-Boot SPL 20" dd if=/dev/mmcblk1 of=/boot/bootarea_1.dump count=32k status=progress strings /boot/bootarea_1.dump | grep "U-Boot SPL 20" dd if=/dev/mmcblk2 of=/boot/bootarea_2.dump count=32k status=progress strings /boot/bootarea_2.dump | grep "U-Boot SPL 20"
  3. Can you narrow this topic down to the exact SBC, even which HW PCB version of it might be needed. So also then we need exact version of U-Boot and kernel. It is important that others have the option to (easily) reproduce your issues. Maybe you still think it is Armbian, but that makes no sense. The HW matters, so driver and bootloader. A strange/foreign/different U-Boot can make or break, seen that many times, also experienced myself several times. You can dump the first 16MiB or so of the eMMC/SPI-flash/SD-card/UFS into a file parttableuboot.bin and do strings parttableuboot.bin | grep "Armbian", then you will see a version string.
  4. I do not have this OP6plus, but have been looking at some similar Cix CPU based things. This thing can be treated as an x86_64 computer, so roughly 2 decades of issues with getting Linux to run on PC's should apply. Like for example endless issues with NVIDIA drivers/GPUs. 'factory defaults' is difficult to base upon as the version of the (closed-source?) factory firmware is unknown, you need to mention that in theory. But simpler things might be wrong, so it is a matter of enabling more logging, so you and forum users can see what is actually happening. I think it is not dead/frozen, just some issue with graphics subystem, can be setting, is very common problem. I hope you have it networked, so then the lowest effort is to login via ssh with the default root:1234 as soon as possible. I did that for an old 32-bit system where I generated my own image, UEFI and GRUB based. The problem with Armbian GRUB based is that the GRUB timeout for displaying the menu is set to 0, so you see and have no easy way to interrupt boot and ad-hoc edit the boot cmdline by adding loglevel=7 for example. Or have you seen a GRUB menu and just waited the default 5 seconds (the standard Debian that is overruled with 0 by Armbian custom GRUB script generation) ? There plenty of ways to approach, I would edit the rootfs /boot/grub/grub.cfg in another computer, so you are not left in the dark. But I don't know how easy that is for you to do. A serial console/debug cable is the best option traditionally.
  5. What repo are you using then? I see this on mine: ~# apt list -i | grep linux-u-boot-rock-5b linux-u-boot-rock-5b-edge/trixie,now 26.8.3 arm64 [installed] ~# strings /usr/lib/linux-u-boot-edge-rock-5b/u-boot-rockchip-spi.bin | grep "U-Boot SPL 20" U-Boot SPL 2026.01_armbian-2026.01-S127a-Pab8a-Hc429-Vc955-B5da4-R448a (Aug 14 2026 - 13:24:43 +0000)Might be bit out-of-date as I use apt pinning, but: ~# cat /etc/os-release PRETTY_NAME="Armbian 26.11.0 trixie"EDIT: OK I see current is 2017.09 based when I do a test install of that package: Armbian 'uboot-rock-5b-current' for '2017.09-S39cd-P2e20-Hf5b5-V172f-B5da4-R448a': 'postinst' starting.So you can use that, depends on what you want/do with your ROCK5B.
  6. As sort of conclusion, whether wanting grub-efi or not, there is another discovery w.r.t. DS18B20 temperature sensor(s) hooked up to 1-wire. On the Allwinner H3 the default SoC pad/pin is PD14 but that is not wired on the NanoPi-NEO. Via U-Boot scripting, including the fixup.scr and armbianEnv.txt (see boot.cmd how it works) I select PG11. However, extlinux bootmethod that I tend to use besides EFI in KVM, does not support parameter like this. And grub-efi when in KVM needs valid EFI partition which confuses modern U-Boot in a standard configuration. I managed to build a 7.3.3 sunxi kernel+dtbo with that PG11 as default, but it is by hacking the already downloaded sun8i-h3-w1-gpio.dtso file. I made also a patch via kernel-patch first, but I understand now that this patch is against the mainline kernel and not on top of or after the sunxi Armbian overlays for 32-bit. At least it does not work. Maybe I do something wrong w.r.t. Armbian Build, but I think I would need something like 'patch the armbian patch'. Anyway, 1 reason an extra FAT formatted boot partition is used for computers, is that Windows cannot handle Linux filesystems. But I do not use Windows, except a few times per year in a KVM on x86_64 to scan/digitize paper and maybe some unknown old electronics that has no Linux user program. This also means, if kernel crash due to overlay and/or specific HW, extlinux cannot be used to select older kernel ad-hoc. With boot.scr, it would need break autoboot via serial console and then select/load a previous kernel etc via a sequence of u-boot commands, which I once did, but all forgotten now, was in relation to soldered eMMC. For SD-cards, way easier to take out SD-card of-course unless you have glued it which I read once someone did. So I now use this on one of my 24/7 NanoPi-NEO's with just the standard boot.scr+ambianEnv.txt: # gdisk -l /dev/mmcblk0 GPT fdisk (gdisk) version 1.0.10 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/mmcblk0: 62357504 sectors, 29.7 GiB Sector size (logical/physical): 512/512 bytes [...] Partition table holds up to 56 entries Main partition table begins at sector 2 and ends at sector 15 First usable sector is 16, last usable sector is 62357488 Partitions will be aligned on 16-sector boundaries Total free space is 49766385 sectors (23.7 GiB) Number Start (sector) End (sector) Size Code Name 1 532480 13115391 6.0 GiB 8300 Linux filesystem 5 16 8191 4.0 MiB B000 U-Boot boot loader gdisk x l allows sector alignment set to 1 gdisk x s allows resizing partition table I figured out that max 56 partitions is max, so up to sector 16 where the H3/sun8i bootloader starts. The Armbian H3 images rootfs starts at sector 8192. Also nice then to put some protection around that area with a type 0xB000 allocation. This way, it is a bit more convenient to wipe and write u-boot if you hate the dd numbering/arguments. For easy trimming free space (with blkdiscard), I also used to allocate a type 0 partition at the end with high number, but it assumes sub-optimal SD-card internal garbage collection or whatever code is in there. Also good for figuring out if SD-card is counterfeit or so. One normally should not worry about wear-leveling, maybe more about leaving hidden data there. Bigger rootfs is easiest as then fstrim.timer does the job, but old habit of keeping rootfs partition small also plays a role here for me.
  7. The whole issue is that the script /usr/lib/armbian/armbian-led-state-restore.sh writes by itself to the .conf file located in /etc One thing it does is store the state of the LEDs, but storing a state shall not be done in /etc, but in /var, that confused me for months actually as I also did not get the blue blinking of my ROCK3A disabled. The thing is that, if the system does not shutdown the normal way, but for example just by a power-cut, the .conf file is or might be different from the situation when normal reboot. Especially when new/fresh images, that I might configure ran as a container first, it becomes a real mess and frustration, so I masked/disabled the Armbian service and also Armbian repo and made my own simple LED mute .service. After that I saw on another system via: snapper status <snapshot-before>..<snapshot-after> that the .conf file was re-created and I started to understand what happens in the restore script. So what to do? Why should a LED state be restored to something original/boot/kernel state every reboot when the end-user wants it in a state as configured once in /etc ?
  8. The Armbian variant of 2017.09 based for ROCK5B has enough changes/patches such that it runs mainline based Armbian based rockchip64 kernels AFAIK. But never used it on my ROCK5B after many issues with 2017.09 flavors on my ROCK3A, which also was due to PSU (it wants >5V else what should the on-board DC/DC do then). Inside the EDK2 UEFI v1.1 binary there is also the lower level 2027.09 SPL still but the higher level / bigger functionality should be EDK2 based. I don't know exactly how it is all interacting. Maybe a warning is that this UEFI based only is fine if you do not need any special HW (from 40-pin header for example). Also if you use GRUB, there is no support for overlays, so the M.2 E-key slot just stays PCIE2x1 instead of SATA6 when you use the Radxa SATA M.2 E-key breakout adapter, which I do. But luckily that setting is in the EDK2 'BIOS' menu and stored in SPI-flash, so even without loading the devicetree, a rolling release distro generic aarch64 kernel (>= 6.19 works I know) and my 8T SATA HDD is there. I made a sort of automatic change in /etc/grub.d/10_linux so the .dtb was loaded, but then panic days later as my HDD kept ticking like bad sector (so dead I thought) when reboot. Of course it overwrites the devicetree done by EDK2 so default to PCIE2x1 for the multi-PHY in the RK35xx. Also, if boot.scr (or a valid extlinux folder) is found in the first/boot partition, EDK2 UEFI will fall back to that, so make sure to hide/move those. I see I still have this (gdisk -l /dev/nvme0n1) Number Start (sector) End (sector) Size Code Name 1 32768 1081343 512.0 MiB EA00 XBOOTLDR partition 2 1081344 26247167 12.0 GiB 8300 Linux filesystem 3 26247168 38830079 6.0 GiB 8300 Linux filesystem 4 38830080 63995903 12.0 GiB 8300 Linux filesystem 5 63995904 76578815 6.0 GiB 8300 Linux filesystem 6 76578816 391151615 150.0 GiB 8300 Linux filesystem 7 391151616 953188351 268.0 GiB 8E00 Linux LVM 8 953188352 976773119 11.2 GiB 8200 Linux swap This still works with native/plain/original U-Boot and rk35xx vendor based 6.1 kernel, but I think not in an ARM64 computer that has closed-source UEFI (e.g. like an x86 PC) as that needs ESP, so 0xEF00 instead of 0xEA00 But easy to change, same as un-hiding boot.scr etc. I actually think 0x0700 or 0xEF00 or 0xEA00 all should not matter for U-Boot, at least if there is just 1 path/choice. But if multi OS and the option to store bootpath in SPI-flash (run efibootmgr ), you also can have multiple EFI partitions in theory so not sure what the various bootloaders for ROCK5B will do then. But I keep it simple 1 shared EFI/boot partition. Another note is that (I think) Armbian Build on Debian Trixie cannot build (older) U-Boot like 2017.09 based, you need (older) Ubuntu for that. I use my ROCK5B Armbian Trixie for building u-boot and kernels, I have no Docker installed as that changes up my networking beyond my own understanding, so for stuff connected to internet, I removed all potential show-stoppers and complexity (for me).
  9. Download the file from https://github.com/edk2-porting/edk2-rk3588/releases Then: sudo flashcp -v -p --erase-all ./rock-5b_UEFI_Release_v1.1.img /dev/mtd0 Or use armbian-install to write the u-boot binary from the currently installed u-boot package. The EDK2 bootloader is most convenient when you have/use dedicated boot/EFI system partition and GRUB as bootmanager, so just like a x86 PC, also nice setup screen before kernel etc loads. U-Boot need serial console cable to do things before kernel load, it usually does not initialize HDMI fast enough is my experience.
  10. Yes, it is not even Armbian U-boot; ROCK5B is very well supported, any recent mainline based U-Boot will even run a normal Debian Sid kernel (7.3.3+deb14-arm64 currently, I have that running currently, not U-Boot in SPI-flash, but EDK2 EUFIv1.1). But for old BananaPi I used Armbian Build to have 2026.07 with some Btrfs compress fix, so boots/runs 7.3.3-edge-sunxi directly from rootfs all compressed zstd. I do not have eMMC module, only SPI-flash (and SD-card for emergencies maybe). So I am sure I only have 1 bootloader (in SPI-flash). You might have 2, also in eMMC. Make sure you wipe old/double/redundent ones so only '1 captain on the ship'.
  11. I think it is clear now to me how the hardware is, I also took a look at https://www.friendlyelec.com/index.php?route=product/product&product_id=309 (scroll down to the PCB pictures layout and interfaces). Also your b1) and b3) info points help confirming and I see that this is yet another step in complexity (or just more options, it is great hardware) but I can't find where in Armbian config this is handled in a way similar to the script attached in the other topic related to Btrfs for rootfs. In addition I took a peek at the (for me) banned 'AI-bot' account 'Boardcon_yang' and again see rubbish hallucinations. I understand that Boardcon is a real company, but my take is to avoid that company as a plague because simply this is how they deal with individuals/humans then apparently. Also Armbian should do something about it. Same as AI generated videos/pictures that are on social media (I am not, all blocked, I even do not have a big-tech Microsoft github account), it should be marked as such. Else it will be like email spam boxes: block all except the ones clearly human still or just not use Armbian and this forum anymore. So back to the issue: Is a matter of what you want or more difficult, what is wanted/done by Armbian and the people/organizations/companies doing the financial backing. There are (I think) 6 Linux block devices that could contain the bootloader or a part of it (a version of U-Boot in this case): sda sdb sdc sdd SD-card SPI-NOR-flash sdd is new to me and don't know what that shall be used for. It can easily take months or years before it is known in general what is a practical way of working for an individual (so non-profit, users at home for example). For professionals/industry there might be a exchange of info under Non-Disclosure-Agreement, so can be all clear, like Android system builders. Those also need large volume management of systems, at least end-users are certainly not the admins of the things they use. It might be even forbidden by law as is known from telcos (depends on country). The question is what the ROM code in the RK3576 does based on how the M5 HW design is, it is usually some signal level that determines which device is read first or check for a bootloader of some stage. You need documentation then, look in schematics of the board, but then still it might be unclear what steps the ROM does at power-on. If you have used the board with other OS earlier, that one might have written a version of its bootloader to SPI-flash (/dev/mtd0) for example. Compared to other already well-know SoCs/boards like ROCK5B, it is clear that SPI-flash offers the best options like we know from PC's: So you have like a BIOS setup as it can store variables about the OS there. I do that on my ROCK5B as it has SPI-flash only (or SD-card). My NanoPi-R6C has no SPI-flash, just soldered eMMC and with the current U-Boot variants does not offer the variable storage, so I need a sort of own hack/method to switch OS. So for the M5, I would boot with Armbian from SD-card, then wipe all (boot) areas from all devices and use a manual method to flash the Armbian U-Boot to SPI-flash. That is different from what is done in the other topic as there a combination of sda and sdb is used and also is in the UFS install script for the M5. But also SPI install method is there. It is in /usr/lib/u-boot/platform_install.sh The file for SPI is then /usr/lib/linux-u-boot-current-nanopi-m5/u-boot-rockchip-spi.bin and command would be: flashcp -v -p --erase-all /usr/lib/linux-u-boot-current-nanopi-m5/u-boot-rockchip-spi.bin BUT I do not own an M5, so it is just based on what I did last week for my ROCK3A a few times with own build U-Boot (with Armbian build framework) and using also various kernels. Everything related to M5 fails for me as I do this trials in a quick container run. You need to read info and as long as it is unclear to you keep studying and/or wait until the armbian-config tool helps you doing it correctly. You are correct that the script in the other topic is mainly an issue about wanting Btrfs for rootfs. You might not need Btrfs for root now, but having it allows you to manage the installation (so Armbian in this case) and especially the sizes of the block devices/partitions all to be done in the running system. That saves you from quite some boot time issues, as for example you don't need another temporary OS/system to boot with, like it is known as 'Live-CD-ROM' for PC's for example. Also saves money as you can fit a lot more on 1 fast UFS or NVME etc. I use it on all computers, even decade old RaspberryPi1, so can do upgrades etc from my desk or while traveling by train remotely, SD-card just stays inserted and also board is kept powered on via PoE as it is outside in difficult place and might be bad weather.
  12. quick check: # strings /usr/lib/linux-u-boot-vendor-cm3588-nas/u-boot-rockchip.bin | grep "U-Boot SPL 20" U-Boot SPL 2026.07_armbian-2026.07-Sece3-P1c54-H1a10-V102f-B5da4-R448a (Aug 14 2026 - 13:26:47 +0000) which is very recent, not the old 2017.09 we see still quite often for RK3588 based devices, so if also the binary is actually used for booting (so written in SPI-flash or other bootloader device area), then I would say new mainline based kernels should work.
  13. It depends on bootloader and surroundings if it works without action and/or issues. So also DeviceTree and overlays (if you use them). In general, if the CM3588-NAS is considered as a traditional PC, so just 8-core ARM64 CPU and no special Rockchip function block like HW video encoder used/needed, it is no problem to use a latest mainline based 7.x kernel. Even simply vanilla Debian kernel from Debian Sid works fine. I do that for my RK3588 SBC's mostly as for example for Jellyfin I hardly have/watch video's that need HW based video encoding. I use EDK2-UEFI v1.1 as bootloader, then no issue to use 7.x kernels, but a recent U-Boot is also fine if headless (no HDMI at power on). I also use grub-efi, so also same as PC's. Make sure you understand and/or have that in-place, as it allow easy switching the used kernel at power-on, you might need a serial console in order not to be blind for what is happening and able so select adhoc.
  14. UFS is presented as SCSI /dev/sdX kernel names and is not related to SATA (also USB-stick would appear as /dev/sdX name). NVME and SD-card/eMMC both use different names. I see from the script in https://forum.armbian.com/topic/60020-nanopi-m5-2651-ufs-install-btrfs-root-does-not-boot-and-manual-partition-layout-is-not-available that bootfs and rootfs is not special compared to just SD-card, but U-Boot seems different although all covered by the standard Armbian U-Boot install script function. The confusion might be, also for me as I don't own UFS, is the four different sdX devices. I have a similar issue with my NanoPi-R6C where, in the eMMC, there is also 2 extra bootX block devices that can be used for bootloader objects (A and B schemes etc). They are normally not used, but now for UFS maybe, I don't know for real, but from the script one can derive certain things. Also I have not looked into the mentioned 26.8.1 GNOME image w.r.t. the write_uboot_platform_ufs in /usr/lib/u-boot/platform_install.sh, but that is needed if I would own a M5. At the moment, I think more of the 4 sda, sdb, sdc, sdd devices (what is what), kernel might do random order, at least Debian based distros do that, I know openSUSE usually has the device named sda, so the first, for the OS and other HDD's or so in a computer sdb, sdc, sdd, etc. But to have it more predictable, there is: root@rock5b:/dev/disk# l total 0 drwxr-xr-x 9 root root 180 Oct 26 16:23 ./ drwxr-xr-x 20 root root 4.5K Oct 26 18:27 ../ drwxr-xr-x 2 root root 880 Oct 26 18:27 by-diskseq/ drwxr-xr-x 2 root root 2.0K Oct 26 18:27 by-id/ drwxr-xr-x 2 root root 160 Oct 26 18:27 by-label/ drwxr-xr-x 2 root root 240 Oct 26 18:27 by-partlabel/ drwxr-xr-x 2 root root 620 Oct 26 18:27 by-partuuid/ drwxr-xr-x 5 root root 1.2K Oct 26 18:27 by-path/ drwxr-xr-x 2 root root 240 Oct 26 18:27 by-uuid/ Example, yesterday, I had to use a 'by-partuuid' path for iSCSI target in my ROCK5B as the underlying Samsung SSD is virtualized now (so /dev/vda instead of /dev/sda) and the 'by-id' is empty then.
  15. Done this, with the difference no local hacking grub.sh anymore as $ARCH=arm64 (so no failure where topic is about) AND this is with both PR#11072 (already merged) and PR#11084 in effect. The build option BOOTPART_REQUIRED=yes needs removed, so this: ./compile.sh build BOARD=rock-3a RELEASE=trixie BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes NETWORKING_STACK=systemd-networkd FIXED_IMAGE_SIZE=2048 BOOTFS_TYPE=fat ROOTFS_TYPE=btrfs BTRFS_COMPRESSION=zstd COMPRESS_OUTPUTIMAGE=sha EXTRAWIFI=no KERNEL_CONFIGURE=no KERNEL_BTF=no KERNEL_GIT=shallow ENABLE_EXTENSIONS=grub-with-dtb GRUB_FDT_FILE=rockchip/rk3568 -rock-3a.dtb UEFISIZE=100 succesfully generates the desired image. However, without detail knowhow about grub config revert to normal Debian, not a workable solution as terminal I/O is muted and grub menu skipped. As my real rock3a is busy/used (and also there is no (UEFI) bootloader build with the image), I started the image in a KVM I call 'armbian64' just swapping normally used image with this new build. The method is then to hit edit in grub menu and ad-hoc remove the devicetree line as that is for HW rock3a and KVM does not need any, just all virtio. But no grub menu, so same as for real nanopineo revert to standard Debian grub config with a few edits like loglevel=7. Then all fine. Good thing is that also this time, my VM is know by my router, so after with a bit of ssh wiping I could login as root:1234 and immediately fix the grub and serial stuff. I think the idea behind this terrible grub config (for me) is to have the same as U-Boot boot.scr: no debug scrolling, hopefully a logo and no kernel selection. That seems fine if the boards only option is UEFI and no U-Boot or free open source bootloder (e.g. RPI), but people use grub so they can make selections at boot/power-on, not only kernels, but also multiple OSses. Maybe not for tiny 10-year old SBC's, but certainly for high end like RK35xx.
  16. Something happened to the file below while installing and remove packages: root@ekker:/etc# stat armbian-leds.conf File: armbian-leds.conf Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: 0,28 Inode: 42402 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2026-10-23 14:39:59.268000002 +0000 Modify: 2026-10-23 14:39:53.194144084 +0000 Change: 2026-10-23 14:39:53.194144084 +0000 Birth: 2026-10-23 14:02:59.333152304 +0000 root@ekker:/etc# date Fri Oct 23 15:10:41 UTC 2026 So now with empty file of course no leds problem. I will add snapper and change subvols so I can better track what is happening.
  17. I see it is actually a failure for the 7.3.0-rc7-edge-sunxi kernel (with my extra setting CONFIG_EFI=y), just full log from armbian-debug here: https://paste.armbian.com/ucitawavax [ 1.526902] leds-gpio leds: error -EBUSY: Failed to get GPIO '/leds/pwr' [ 1.526958] leds-gpio leds: probe with driver leds-gpio failed with error -16 and already: root@ekker:~# systemctl status armbian-led-state.service * armbian-led-state.service - Armbian leds state Loaded: loaded (/usr/lib/systemd/system/armbian-led-state.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-10-23 14:03:16 UTC; 27min ago Invocation: b071139a57234fb7a65ef3dc88c4534d Process: 376 ExecStart=/usr/lib/armbian/armbian-led-state-restore.sh (code=exited, status=0/SUCCESS) Main PID: 376 (code=exited, status=0/SUCCESS) Mem peak: 1.3M CPU: 485ms Oct 23 14:03:06 ekker systemd[1]: Starting armbian-led-state.service - Armbian leds state... Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:blue:status/trigger could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:blue:status/invert could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:green:pwr/trigger could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:green:pwr/brightness could not be restored Oct 23 14:03:16 ekker systemd[1]: Finished armbian-led-state.service - Armbian leds state. So seems a matter of a new or wrong path for the leds or pins, where the older Debian kernel does is correct, also the leds config file is correct according to my understanding. Long time ago I disabled blue led of my rock-3a, so remenber a bit. Probably I install current sunxi as well (6.18) and see what that does. EDIT: sorry too fast, this won't work as it has no EFI enabled, so needs then booted via boot.scr or extlinux
  18. To my surprise, the board also boots OK with the standard Debian Trixie 6.12.113+deb13-armmp kernel. Noticeable difference is quite a long pause between EFI_GRUB stub messages and kernel starting to spit out messages and that the red LED is constant on and green blinking as sort of activity. I prefer no LEDs on at all during normal operation, but this is a minor issue and likely some Armbian patch for sunxi puts them off. Of course Debian delivers no overlays, so the actual use-case is then 0, as I need analog-codec, SPDIF, 1-wire at leasta and some extra UART as well, all from the header pins, but it is great that it behaves now 'as a small UEFI Debian computer'.
  19. After another power-on, first removing the y2k timestamped ubootenv.var which I thought maybe stores things and not waiting on boot, it turns out the board (still) comes online, just took much longer. It might be due to netplan using some other systemd-networkd config then my own .network files, so as minimal I did: systemctl disable systemd-networkd-wait-online.service that is a bit more relaxing. But still no serial I/O Then I saw my usual edits to /etc/grub: GRUB_CMDLINE_LINUX_DEFAULT="loglevel=7" GRUB_TERMINAL="serial" GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1" where overruled by what is in: /etc/default/grub.d/98-armbian.cfg, especially GRUB_TIMEOUT=0, which makes you cannot select anything and that is reason I saw nothing when EFI compiled kernel. Earlier it just could not load the plain image kernel, so essentially the error menu. So the sledgehammer: mv 98-armbian.cfg 98-armbian.cfg.disabled systemctl set-default multi-user.target # an SBC with no connector at all for a screen/monitor should not default to graphical.target, 'it is defacto headless' Debian's default GRUB_TIMEOUT=5 is just too short in this case due to the error with 'com0' 'serial', I saw just a short flash of the grub menu, so made it 15 Also for GRUB_CMDLINE_LINUX_DEFAULT, 'splash' is not recognised and transferred to userspace. Plymouth I see as a real PITA, certainly purge all when CLI/headless, maybe it is 'plymouth.ignore-serial-consoles' that is the problem. So then update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-7.3.0-rc7-edge-sunxi Found initrd image: /boot/initrd.img-7.3.0-rc7-edge-sunxi Found DTB path: /boot/armbian-dtb-7.3.0-rc7-edge-sunxi Found DTB file, using it: /boot/armbian-dtb-7.3.0-rc7-edge-sunxi Found linux image: /boot/vmlinuz-6.12.113+deb13-armmp Found initrd image: /boot/initrd.img-6.12.113+deb13-armmp Found DTB path: /boot/armbian-dtb-6.12.113+deb13-armmp Found DTB file, using it: /boot/armbian-dtb-6.12.113+deb13-armmp Adding boot menu entry for UEFI Firmware Settings ... done Reboot, then all normal, all U-Boot, grub menu, kernel log, finally login prompt. Armbian-unofficial 26.11.0-trunk Trixie ttyS0 ekker login: root Password: root@ekker:~# cat /etc/update-motd.d/99-blank #!/bin/bash echo "" exit 0 This last thing confused me some months ago w.r.t. ssh login speed testing. After disabled all motd, still a linefeed, was not form ssh config or so, but this file. echo -n "" I would say, but maybe than other issues. The linefeed should be 'pre-' I think, not '-post' w.r.t. all the motd items. As brute force I just removed the whole folder as for almost exclusively unattended login normally, I anyway don't see what is displayed. W.r.t. ttyGS0 v.s. ttyS0, that is still unclear to me, but at least now I can select a kernel, also edit in grub menu to change a few things on command line ad-hoc etc, so much easier to test new kernels/configs (with or without DTB from kernel package).
  20. I did some other test builds, 1 obvious thing is that FIXED_IMAGE_SIZE=2G should be FIXED_IMAGE_SIZE=2048, then image is 2GiB and not about 1.7G or so. Other thing that boot partition was 260 and not 256 is now fixed by https://github.com/armbian/build/pull/11072 Due to that, I looked into grub.sh and after several trial-error and hacking/removing some line locally from grub.sh I got a successful build. But as I already knew actually, a 128-entry GPT overlaps Allwinner H3 8k offset bootloader location. I did convert with gdisk to MBR but then partition error/not-found as grub looks for GPT, probably also a GUID and changing all to old MBR is possible I think, but might even need own grub compile, so no option. What works is to have or to convert the GPT to contain less entries, I set it to 16 (gdisk x or r menu then s). Then after sector 6 free space instead of sector 34. Then some other mutual exclusive issue is that having grub assumes vendor/board UEFI FW like Dragon6 or a PC. Or special EDK2 for RK358.8 ROM-only tiny SBC's nee U-Boot in EFI mode in order to boot an EFI based installation. So I had compiled latest U-Boot (for its Btrfs Zstd compression fix on 32-bit sunxi at least) so just wrote that .bin file at the bootloader offset at 8k Then SD-card started with the 2026.07 U-Boot build, seen via serial console cable and and nice blue kernel menu via screen in konsole on tumbleweed. Then next issue is the the Armbian sunxi 7.3.0.rc7 has no EFI_STUB, so rebuild kernel with that copied that so SD-card. Then it loaded the kernel and activity on the board, also ethernet active, but I did not see the blue grub menu anymore, it just booted the first entry silently after some seconds. No serial output at all, not more that this: Booting: Label: mmc 0 Device path: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,7200000000000000)/SD(0)/SD(0) error: serial port `auto' isn't found. error: terminal `serial' isn't found. error: terminal `serial' isn't found. Booting `Armbian GNU/Linux, with Linux 7.3.0-rc7-edge-sunxi' Loading Linux 7.3.0-rc7-edge-sunxi ... Loading initial ramdisk ... Loading device tree blob... /@/boot/armbian-dtb-7.3.0-rc7-edge-sunxi But as this NanoPi-NEO has HW MAC-address reservation for mu DHCP server, IPv4 was know and I could ssh in as root with 1234. Then normal firstboot sequences so create user/password/localization etc. I think on another boot attempt I also saw 'com1' as serial port, so for sure something wrong there. First reboot did hang, later reboots went fine, is somehow known to me. So it all went remarkably fine, taking into account the many tweaks and hacks. So the build line I used (on ROCK5B running Armbian Trixie with 7.3.0.rc5 rockchip64 kernel ATM): cd /local/s0/armbuild/grubboots/build git pull git fetch origin pull/11072/head:pr-11072 git checkout pr-11072 ./compile.sh build \ BOARD=nanopineo \ RELEASE=trixie \ BRANCH=edge \ BUILD_DESKTOP=no \ BUILD_MINIMAL=yes \ NETWORKING_STACK=systemd-networkd \ FIXED_IMAGE_SIZE=2048 \ BOOTPART_REQUIRED=yes \ BOOTFS_TYPE=fat \ ROOTFS_TYPE=btrfs \ BTRFS_COMPRESSION=zstd \ COMPRESS_OUTPUTIMAGE=sha \ EXTRAWIFI=no \ KERNEL_CONFIGURE=no \ KERNEL_BTF=no \ KERNEL_GIT=shallow \ ENABLE_EXTENSIONS=grub-with-dtb \ GRUB_FDT_FILE=sun8i-h3-nanopi-neo.dtb \ UEFISIZE=100 Unfortunately, after a few extra reboots, networking did not come online, and as the serial console went dead after kernel+initrd+dtb load, I have no clue why, at least no DHCP request visible in router. I have doen update-grub, various changes in console= statement w.r.t. 'serial', but that is current a major showstopper. It is similar frustration as with RPI boards with older BCM SoC only have 2 UARTs and RPL kept swapping because BlueTooth etc so getting mainline to work is endless fiddling with serial parameters (if you try U-Boot or EDK2 on RPI4 for example). I also installed linux-image-armmp, but that did not boot. Not using the kernel package DTB did make LEDs blink differently, but no boot success. So my perception is that Allwinner H3 needs and uses many great Armbian patches in order to be usefull, which means it does not make sense (currently) to have 1 kernel that boots on both real HW and also in a KVM. So same as for RPI0-3 (when Raspbian), when the rootfs is booted in a KVM, select the generic Debian ARMv7 architecture kernel. For that I use apt pinning on Raspbian (as it is not ARMv7) but on Armbian 32-bit armmp can be installed in addition. When on real HW, I use extlinux folder on FAT (or just basic 1 kernel boot.scr), when in KVM with 32-bit EDK2 it sees EFI folder and uses BOOTARM.EFI and grub. This also makes me think that it might be faster to improve scripting around qemu-system-aarch64 using U-Boot native loading instead of EFI-based. I have it for 64-bit, only text-mode/CLI of course. I use Btrfs enabled Armbian qemu-uboot-arm64, it had/has no issues with decompressing Zstd at least. There is no 32-bit variant of that, so I'll have to see how that would work. 64-bit is all no issue AFAIK, the rockchip64 kernels also include virtio drivers same as standard Debian arm64, so runs in KVM/virt-manager without issue, nice same 1 flavor kernel. Maybe I do a similar build for rock-3a, disable SPI-CLK with jumper and then see if SD-card boots (when latest U-boot written to SD-card manually still).
  21. 'Spread around the world' means to me costs of plane tickets and hours lost in travel time etc, so for me it was/is an easy calculation: You can buy a handful of computers/boards for that money and also spend time to think about a dual-setup, e.g. a working link with x86 and devices under test. In the past for just 1000km distance (by car) I just changed ISP's/contracts at the 2 locations such that I got Fritz!Boxes (DSL, Cable modems build in), those have build-in (old fashion) VPN, so I could rather easily create my own OpenVPN and later WireGuard links as well. That was already a few hundred Euros, besides lots a time to figure out IPv6 issues etc. The latency was no real issue, but is just an example how to approach. And really is all DIY, as Linux computers, no support form computer shop what so ever. Nowadays, just at home I use USB serial UART/TTL console/debug cables and maybe a wall plug with some ESP/Tasmota so I can powercycle things. z8350 I have as well, they are low-power, same as RPI4, much better actually as everything with sleep/standby also works and LiPo battery included etc. So one known working computer is 'HID' via the serial cable on header pins 6 8 10 or dedicated extra generic USB-C cable even like for my NanoPi-R6C. So I can watch everything already at power-on, most important is U-Boot/bootloader. For your unknown SBC's the kernel-loading might just takeover buffer sizes w.r.t. on-board ethernet as that is usually initialized before kernel as U-Boot might want to do networkboot. That is just local, might be simple UDP so nothing complex with TCP windowing you will have to deal with at high latency. But is all guessing, you need at least a serial debug cable to start with, else you waste your time also with guessing. Then it is important to consider the HW I/O path what you already figured out already: USB is an extra layer, for sure has extra other/more buffers; you can calculate how big they will be or grow based on latency and speed. And not known by U-Boot, so likely own/new buffer sizes. Same can be the case for PCI-E connected RJ45, as mentioned ROCK5B has its 2.5GbE RTL chip like that, same as my NanoPi-R6C 'LAN' port. I use EDK2 UEFI with netboot disabled as I just have NVME inside, so I guess other buffersizes. Armbian on those high-end but low-power devices uses the same as on x86, I can use Armbian edge rockchip64 kernel or Debian sid generic arm64, makes no real difference, at least not for networking. Even more for userpace, it is both the same Debian Trixie arm64 packages and configs. However, if on-SoC ethernet, various the driver levels are different, and even per SoC. That is where you need to look at I think. Might be very complex and at kernel/uboot development level. Maybe something in DeviceTree, but not likely I think. You might also try 'the OS that came with the SBC', although I guess those are hopelessly outdated, but I guess same problem with high latency IP traffic.
  22. No, maybe others know, I just had a look in Armbian space and I see something I did not know: https://armbian.com/vendors/linkease 1 is RK3568 based which I know from my ROCK3A, other I hadn't noticed before. Maybe use AI based search to get some hints. At least be aware that many ARM computer boards need proprietary drivers/firmware, so for something like an internet router where ISP's themselves consider 10 years operation/maintenance, it is quite a challenge to get that open-source based I think. That is why I focused on virtualization and less integrated HW solution.
  23. Good you provided various links/info, unfortunately, it doesn't look good to me and I recognize several issues from my experience with mt7921u (as USB-stick). I have 2 of them, 1 with a brand name and one without a brand name. Should behave the same, but do not. I tried various setups, but I just can confirm what is on internet for several years already. My goal is coverage, so 5GHz not needed actually, but it is sold as also doing 5GHz, which I got working when client. As Access Point, I only can get 2.4GHz working and then still today now I see issues that I don't understand and thought were fixed with a kernel minor version upgrade, but that is another issue, nothing RF related (I think). So w.r.t. uwe5622, I can not really help you further. I have not looked into specific HW/architecture/design, but make sure you know how specs are marketed. Same as for myself, if you want solid WiFi, make sure you get something with a chipset or from a company that has proven itself for a decade or longer. Or accept that it is like it is and limit your deployment to what works. I personally stay away from something with DKMS, I actually removed the whole dkms from my Armbian installs as it causes too much issues in general throughout the years when using rolling release Linux. But if you already have the HW, maybe try a very latest kernel, build all yourself and hope it is something in the Linux kernel that causes the issue and not something related to unisoc firmware blob. The latter is closed source of course and may have a several updates and well documented what is fixed, or just a one shot and no updates. For my mt7921 for example, the bin/blob file has a name with different increasing timestamps, but contents are the same for years, doesn't matter if Debian or OpenWRT.
  24. I assume then shared kernel. So might be interesting for OP as Proxmox/KVM does not work on Cortex-A9 but containers should (I think, never used container host 32-bit ARM). But I see no option to run OpenWRT (EFI boot) as KVM with Armbian/Debian/Tumbleweed/Ubuntu/RasberryPiOS as host. As indicated, OpenWRT is very small, not only on disk size. I see I have allocated the VM 1 vCPU and 512MiB. Less memory should also work, but not sure how low it can be. It is mostly the GUI that needs RAM I think as the kernel+routing is very small, should be somewhere 50MiB to 100MiB I think. At least if only speeds up to 100Mbps or so and low latency. Also which CPU type (Cortex-A55 or Cortex-A76) is up to libvirtd/QEMU/KVM as this was with mainline based kernel on RK3588, that does not need CPU pinning. For 32-bit guests, I use RPi4 (Cortex-A72) or ROCK3A (only Cortex-A55) as 32-bit does not work at kernel level on Cortex-A76. Related to that, a NanoPi-R76 (RK3576 based) might also be an option for OP as that is bigLITTLE Cortex-A72 + Cortex-A53, still ARMv8.0 but great low-power. An option is then that the whole storage/image of the clearfogpro is put as a KVM on the RK3576, although with different bootloader and kernel (EDK2 and some Debian armhf kernel). Is for people who have some well working 32-bit and fear the transition to 64-bit (so redo whole userspace tuned for many years). Indeed, various possibilities; added to that is that I also have used 4G as DSL was in kilobit speed range and 4G is just IP packets, although I put those on VLANs, so to have smooth transition between DSL 4B fiber (so multi-WAN in fact). I'll will need a test install then to see what it is. I know the GUI's from some managed switches, was difficult to figure out what is meant with what, but after that and having done the same in Opensuse Tumbleweed years ago on RPi4 with 'wickedd' networking and also Ubuntu 'netplan.io', it was a relief to just use 'sudo nmtui' to create a bridge with enslaved VLAN. And that can be done via a serial console cable, so I prefer that as no HDMI monitor+cables needed then, just a laptop, good for panic/trouble situations to keep things as simple as possible IMO. Even Rj45 can be unconnected initially, only power needed. More complex but maybe also interesting is if IOMMU works on the host computer. Is no problem on e.g. N100 boards, but for RK3588, I could not get it to work (yet). Also makes little sense as for example the NanoPi-R6C has only 2 PCI-E devices that could be mapped from host to guest: NVME and 2.5GbE. But NVME is needed for high speed I/O for Armbian Build and VM image storage and I have no 2.5G switches (yet) and also network virtualization works very well if Linux as virtio network driver or a virtual intel 1000e (so then FreeBSD is also no issue).
  25. This it makes little sense, it is just totally different HW and I am quite sure the problem in this topic is related to HW / drivers. I see in you 1 year old armbianmonitorlog: [ 3.039362] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.039448] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 BUT it takes me too long to determine what actual HW SBC this is about, yes Rockchip based, but what brand, series, HW revision, etc, etc. Also what U-Boot, maybe you still have some old illegal one as the first topic line suggests. This is really a no-brainer compared to the topic issue and also depends on which HW/SBC it is. Some need extra udev rules, some might handle it in systemd-networkd. But easy to change yourself, I have done it several times as it fits my preferences better, depending on what computer it is. You need to do that yourself if you plug in extra RJ45 devices for sure. So can you provide: - U-Boot log via serial console UART TTL cable? - an URL to the vendor HW and a version number of your specific HW revision ? What does this mean? And it seems USB2, so half duplex down to the lowest level of the chain. Or not? I can add more confusion, for example why don't you build/compile a latest kernel (7.3 based) yourself and also latest U-Boot (so select edge or bleedingedge branch). I have several of my Armbian Trixie devices with 7.3 or 7.2 rockchip64 or sunxi kernels. Or you run just standard Debian Unstable/Sid kernel version and compare. Maybe there are buffer sizes somewhere that matter, but is up to you to report, only then maybe others can suggest what to do or change.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.