Active threads

New version (v24.11) with even more targets has been released. Home assistant takes few minutes and might require reboot at first install or there will be some errors related to privileges. This gets away after waiting few minutes and reboot. Testing was done on Odroid M1. Latest: https://github.com/armbian/distribution/releases/tag/24.11.1 Previous: https://github.com/armbian/distribution/releases/tag/24.8.4

I'd like to try Joshua Riek's image, but not sure how. @Hqnicolas, your link in previous post is 404 now. I tried to boot kernel linux-image-vendor-rk35xx with rk3566-h96-tvbox.dtb but got instant kernel panic.

We are cleaning those builds as they have very little value. But you were lucky: https://github.com/armbian/community/releases/tag/24.11.0-trunk.351

OK, as soon as my new 2 32GB cards arrive, I will check that. Or even manually install.

@DantesWhen I still had the original 2017 U-boot on the eMMC (from the OpenWRT that came pre-installed), inserting an SD-card with some recent Armbian image booted always from the SD-card. So in serial/debug console I had full control of the eMMC (and also an NVME in the M.2 slot). So that is also how I recently wrote a new/latest 2024 U-boot from the current-branch Armbian to the eMMC with dd. But that 2024 U-boot is more flexible and I needed quite some time to and figure out what was what (after stop autoboot prompt): 1 - SD-card with a known good simple basic Armbian Bookworm 2 - eMMC where the custom kernel did not work 3 - NVME with an EFI boot partition with grub.efi and some variant of openSUSE and some Debian flavor After reading U-boot command docs like 'bootflow', I somehow booted from NMVE. Fine but I want also operation with no NVME in the M.2 slot inserted. So eMMC and SD-card can be selected in U-boot but was a bit guessing as I had to rely on some addresses, so 3rd try or so I started the good simple basic Armbian Bookworm from SD-card and from there I could put a working kernel Image/uInitrd/DTB on the eMMC again. But what will happen if the somehow the U-boot on eMMC is corrupt? That has not happened, but when it would, will it then always somehow re-init and try SD-card? That is my point, that is why I thought I should also get to know USB loading, like I know from Android smartphones with fastboot tool. But you state: "Boot from sdcard with maskrom", that I had not thought of. Does that skip eMMC always? And scp? You mean the ethernet port(s) is/are up and running then? Or something over serial cable downloading what is known from simple old processor boards?

OK, You suggest FTDI, will buy one. Now trying to "apt upgrade" on 28.8.1 with 6.1.75(43) kernel. Will describe what I did and results in other (mPCIe OrangePi5) thread.

This is not a viable option.

Hello Everyone, Unfortunately my helios64 is not glowing any power LED. As soon as I connect the power supply it only shows a blinking orange LED light, that is basically for the battery status. My power supply is perfectly fine and even I have tried using with the ATX power supply same result. Does anyone face this issue and please help me to get my board working again. Thanks!

- Using the panthor driver might help, the 6.1.75 kernel with the panthor overlay enabled. - If Xorg is the trouble maker, try wayland with Sunshine server and moonlight-qt as client. - Disable hw acceleration in de xorg config file, although here it never crashed for months

I have this issue with the Le Potato from time to time. I use a service and script to run `ethtool -r eth0`.

Take a look at universal projects that are made far better, and are universal by design. https://forum.armbian.com/forum/40-reviews-tutorials-hardware-hacks/ (pinned topics)

They are not needed. We use flash media friendly and more advanced ZSWAP solution by default. https://www.google.com/search?q=zswap If you don't want to have this, you can of course disable this feature in /etc/defaults/ (will be soon added to armbian-config) and add swap file. But that is not recommended.

Hello everyone I wanted to build Armbian on the AIO-3588Q board. But I did not see that there was a configuration of this board. There was a configuration of the ITX-3588j board and other manufacturers on the same rk3588 platform and tried to build Armbian. In the assembled images in GPT format, only rootfs was stored (it combines rootfs and kernel (boot.img) according to the rockchip documentation). After I built it, I installed it in the rootds partition, it was installed without any errors. But the system does not start. You turn on the power, the fan starts spinning very fast, spins for 5 seconds, the lower LED lights up, and then the fan stops, the light goes out, a second passes and the fan starts spinning again. I tried to get logs through the debug port, nothing was output except Chinese characters mixed with question marks (binary data) I tried to create a custom board profile for building Armbian, but I constantly got errors during the build. Dragged all dts and makefile from source firefly. Also could not understand what is needed to modify uboot so that uboot can run from gpt kernel located in rootfs. Please tell me how to: 1) Get logs from uboot and connect to its command line? 2) How can I build Armbian for AIO-3588Q together with Uboot? Or build Uboot separately, but what is needed for correct parsing of GPT from rootfs? Maybe someone had experience of building for this board

Thank you for your feedback, I think you are right in that my problem related to an issue with 24.8.4. I could not boot from NVME when I used kernel 6.1.75 with 24.8.4 (ie the version of images published here https://www.armbian.com/radxa-rock-5c/) I built a new image using 6.1.75 and 24.11.0 (subsequently upgraded to 24.11.1), this now boots fine from the NVME drive.

I have the same issue when I connect my OrangePi Zero 3 to University WiFi [ 173.980677] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection XMUNET+ failed status code:1! [ 249.201042] sprdwl:sprdwl_fc_add_share_credit, 533, mode:1 closed, index:0, share it But it is stable when I connect to home WiFi. When I run `iwconfig` it shows that the wlan0 may switch between 2.4GHz and 5GHz from time to time. So I force it to use 2.4G by adding `band: 2.4GHz` to `netplan` configuration. And it seems to work pretty well.

@Vito Dgb I'm sorry but I returned that TV box to the seller for free because it was counterfeit. You could put the Multitool for TV boxes with RK322x Soc that you find in this forum on a USB drive. if the multitool boots you have confirmation that it is a sox 322x I recommend an old kernel to start with, like 5. Good luck

and firefox 😁

Im using armbian server edition. Im trying to setup my box to route internet from end0 (192.168.1.6) to internet on usb0 (dhcp). Im running dns & dhcp via docker adguard - but assume thats not working for now because once the nftable rules are applied I cannot access their web interfaces. But for now ping with ip is okay. With my current setup I can ping the internet from the 'router' via the interface usb0. But I cannot ping from the interface end0. ping 8.8.8.8 -I usb0 <- works ping 8.8.8.8 -I end0 <- Destination Host Unreachable Do I need to setup any static routes? Or should nftables handle all the routing? Ive tried several guides with various nftable rules, but none of them work: https://peppe8o.com/raspberry-pi-portable-hotspot-with-android-usb-tethering/ https://oxcrag.net/projects/linux-router-part-1-routing-nat-and-nftables/ https://wiki.nftables.org/wiki-nftables/index.php/Simple_ruleset_for_a_home_router my network config: usb0: [Match] Name=usb0 [Network] DHCP=yes end0: [Match] Name=end0 [Network] Address=192.168.1.6/24 my nftables: table inet filter { chain input { type filter hook input priority filter; policy accept; } chain forward { type filter hook forward priority filter; policy accept; iif "end0" oif "usb0" accept iif "usb0" oif "end0" accept } chain output { type filter hook output priority filter; policy accept; } } table ip nat { chain prerouting { type nat hook prerouting priority filter; policy accept; } chain postrouting { type nat hook postrouting priority srcnat; policy accept; oif "usb0" masquerade } } my routes: default via 192.168.102.208 dev usb0 default via 192.168.102.208 dev usb0 proto dhcp src 192.168.102.114 metric 1024 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown <- docker? 172.18.0.0/16 dev br-cc00a7d88795 proto kernel scope link src 172.18.0.1 <- docker? 192.168.1.0/24 dev end0 proto kernel scope link src 192.168.1.6 192.168.102.0/24 dev usb0 proto kernel scope link src 192.168.102.114 metric 1024 192.168.102.208 dev usb0 proto dhcp scope link src 192.168.102.114 metric 1024

@ deelan thanks a lot for the hint with the specific Kingston industrial card! Before that i tried 6 different micro sd cards without success in fixing the reboot issue. (Sandisk Ultra, Extreme, Extreme Pro from different years/specs and Samsung Pro/Evo cards). Bought exactly the same kingston industrial with 16gb and now reboots perfectly fine. Edit: I use the Odroid HC4.

Running Debian bullseye? This is EOL. Edit: Aha, yes, that's it. https://unix.stackexchange.com/questions/669004/zst-compression-not-supported-by-apt-dpkg

Yes, we should probably add REPLACE: neofetch to the control file. Well, there are several reasons for this: - we are patching neofetch on our own to add Armbian branding. As Neofetch is not maintained anymore, we can't add Armbian normal / official ways by opening a PR at their GH - we would like to switch to fastfetch but this has to be resolved first https://armbian.atlassian.net/browse/AR-2336 (we have extreme lack of hands since ever as we focus into kernel space hard problems, so there is no way to proceed on this) - during the switch to new generation of armbian-config there are many things to tackle and this (known problem) simply live somewhere in backlog This is how this transition is made and we could probably remove this double packaging to make it easier. We already pack it at Armbian config repo https://github.com/armbian/configng https://github.com/armbian/build/blob/main/lib/functions/compilation/packages/armbian-config-deb.sh

perhaps https://github.com/ThomasKaiser/Knowledge/blob/master/articles/Quick_Preview_of_ROCK_5_ITX.md#sata-power-ports may help

i got it working by renaming the files with smaller numbers. /etc/systemd/network/10-internet-usb.link /etc/systemd/network/10-internet-usb.network

This has been a while , so I'm going from memory here: Cryptsetup-initramfs should be installed into the ramdisk (initrd) , thats why it fails. So something goes wrong in step 14. Try execute steps manually (1-16) and check if you have internet in your chroot. It asks for /dev/mapper/rootfs but that device is not there indicates cryptsetup module is not loaded. That's why you did not get the password prompt and thus the disk is still encrypted. ## Something goes wrong here, try executing all the steps manually (1-16). Step by step. ## If the cryptsetup module is not inserted/loaded, you will get that error. #14. chrooted environment cat << EOF > config #!/bin/sh -vx apt update echo 'force-confdef' > /root/.dpkg.cfg apt --yes install cryptsetup-initramfs rm /root/.dpkg.cfg lsinitramfs /boot/initrd.img* | grep 'usr.*cryptsetup' exit EOF chmod +x config chroot . ./config rm config Good luck.

I've just tried Armbian_24.11.1_Rock-5c_bookworm_edge_6.11.7_minimal.img wlan works. No ZFS, however. Building zfs-dkms fails, from /var/lib/dkms/zfs/2.2.5/build/make.log: 93 | #error "Unsupported kernel" According to https://github.com/openzfs/zfs/releases: zfs-2.2.5 is compatible with 4.18 - 6.9 kernels zfs-2.2.6 is compatible with 4.18 - 6.10 kernels zfs-2.3.0 would be compatible with Linux kernels 4.18 - 6.11 Armbian_24.8.4_Rock-5c_bookworm_vendor_6.1.75_minimal.img - ZFS OK, wlan after 'apt upgrade' not anymore. But $ /sudo dkms install aic8800-usb/3.0+git20240327.3561b08f-2 does the trick. ------- Sign command: /lib/modules/6.1.75-vendor-rk35xx/build/scripts/sign-file Binary /lib/modules/6.1.75-vendor-rk35xx/build/scripts/sign-file not found, modules won't be signed Creating symlink /var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/source -> /usr/src/aic8800-usb-3.0+git20240327.3561b08f-2 Building module: Cleaning build area...(bad exit status: 2) make -j8 KERNELRELEASE=6.1.75-vendor-rk35xx -C /lib/modules/6.1.75-vendor-rk35xx/build M=/var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/build/USB/driver_fw/drivers/aic8800 && make -C /lib/modules/6.1.75-vendor-rk35xx/build M=/var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/build/USB/driver_fw/drivers/aic_btusb....... .... depmod... -------- root@rock-5c:~# iw phy0 info Wiphy phy0 wiphy index: 0 max # scan SSIDs: 3 max scan IEs length: 200 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) .... Regards, Chris