Active threads

@Werner I imagine there are plenty of people here who could help solve similar problems. In theory, I could provide a pair of an old RPI (master) and a 4A (slave), with the slave serial connected to the master and power controlled via the GPIO, and they are also on the same VLAN. However, if something goes wrong it needs control to the slave's SD card, all I've found is an SD card extender, and it needs something like an emulator that connects to the master via the same USB/SPI.

First: https://forum.armbian.com/terms Second: Provide full logs

Hey tparys! Thank you very much for your reply and apologies for my delay getting back to you. I haven't had much time to play with this board, but lately I've managed to do some very good progress. Basically I've got Armbian 20 Bullseye working with kernel 6.19. that was a victory! Versions that work/don't: [WORKS] Armbian_20.07_Arm-32_bullseye_current_5.7.7_desktop.img (From a MiQi board) [NOPE] Armbian_25.11.1_Tinkerboard_bookworm_current_6.12.58-homeassistant.img [NOPE] Armbian_25.11.1_Tinkerboard_noble_current_6.12.58_minimal.img [NOPE] Armbian_25.11.1_Tinkerboard_trixie_current_6.12.58_minimal.img [NOPE] Armbian_26.2.0-trunk.370_Tinkerboard_noble_current_6.18.8_xfce_desktop.img [NOPE] Armbian_26.2.1_Tinkerboard_trixie_current_6.18.8_minimal.img Armbians 25 up, some times hangs at Starting Kernel, and majority of the times stops at Loading Ramdisk, all of them tested with most of the DTBs provided The android that runs on the other working board has a kernel with version 4.4 Havent test that because I believe it stops earlier than that I have extracted the DTB from the working Android and got a frankenstein EVB DTS working with some of the features. So far I've got working: *4Cores *2GB Ram *Wifi (using rtw8723d_fw.bin ) *Status LED What doesn't work for sure: -Ethernet -FE2.1 USB Hub 2.0 Untested: ? LVDS 1/2 Panel ? EDP 1/2 Panel ? Speaker ? MIC ? SIM Card Module (Attached to the FE2.1 Hub, so defo not working) And maybe some other peripherals that I was not able to test. I'm still to make the FE2.1 USB Hub work as the 4 only USB physical ports are not working. Also ETH has an issue on stmmac that returns the reset value. and this was merged recently to the kernel. (I'm trying to build v6.19 from source with my patch, but thats being painful too ) Here is my stmmac patch: diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c index 01ede5148163..9f0ee9ea96fa --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c @@ -3208,8 +3208,7 @@ static int stmmac_init_dma_engine(struct stmmac_priv *priv) ret = stmmac_reset(priv); if (ret) { - netdev_err(priv->dev, "Failed to reset the dma\n"); - return ret; + netdev_warn(priv->dev, "Failed to reset the dma, device will work with reduced throughput\n"); } I have also attached my current DTS built on top of the EVB version based on the Android with logs from both. Once again, thank you very much for your help! Best Regards, Mauricio. Armbian 20 Bullseye booting log.txt Android Boot Full log.txt android_check.dts rk3288-evb-rk808-armbian-fixed36.dts

Finally managed to restore the box to stock official Android firmware, everything works as expected. I also tested a firmware for the H96 Max M1, with this one the WiFi is not working, they seem to use a different wifi chip. Any recommendations on where to start with flashing Armbian on this device?

OMV 8+ doesn't support 32bit architectures anymore (including Helios4). https://forum.openmediavault.org/index.php?thread/58798-helios4-omv-8/ Given it seems to be stuck on kernel 6.6, it does feel like it's on life support unfortunately.

which of course fails as nmtui it will not accept the dot separators in an ipv4 address needed to be entered in an ipv4 only situation. I'll repeat as I have said quite a few times already, that I, in weston wv, am at least 100 miles from ANY ipv6 enabled net access. There surely are some ipv6 in pittsburg pa., 150 miles north, maybe in Charleston, 100 miles south. I have battled this using armbian-config and in using that microscopecly tiny moving radiation symbol at the top right of the xfce4 screen. If that is a defense to prevent ipv4 addresses where ipv6 is expected, change the box color so we know it can be skipped in real estate not yet blessed with ipv6 addresses. We are NOT mind readers any more than you are, but this particular group off us is about a 3/4 million in the whole state where flat ground to build a house on is measured in the gallons of diesel fuel to make it flat enough to build on. Fix nmtui so its actually usable and do a respin. while at it, fix whatever prevents our mounting it to edit such stuff before 1st boot. That restriction is a huge pain in the ass too. fdisk tells us its dos partition for sdc with an ext4 sdc1, but when we attempt to mount it, the ext4 cannot be found. That restriction is also present in the 25-5 release. Yet it boots & almost runs. next try?

just go threre: https://forum.friendlyelec.com/viewtopic.php?f=93&t=4691

Built image with such flags: Etched img to sdcard and SBC has no response on power up. U-boot log: OS boots normally if I use ext4, but would like to stick to f2fs. Btrfs or f2fs used to work if I used 7 months old armbian-build git checkpoint but not any more. Anyone else had similar problems?

The initrd might be missing needed drivers for you to continue getting console output. Kind of a pain to troubleshoot that. The kernel I linked above is configured so that it should actually boot with no initramfs at all (though that isn't recommended). It obviously can't hurt to try a different PSU if you have one. The device also will do PoE (on the WAN port I believe) which is a nice little feature so you could try that too. The device tree I use comes directly from the linux tree. It is built into U-Boot and then U-Boot provides it to the kernel via standard location as specified in UEFI. It is entirely possible that older kernels might be unhappy with a newer device tree but you really shouldn't be having any issues with 6.18 and newer but they do need to be configured to load the device tree from UEFI. I think that kernel config option is CONFIG_OF.

No; an Intel (virtual machine) image does not run natively on ARM (OPi5+). You need an ARM (virtual machine) image, but those are not available (at least not click-to-download). If you look in raw downlaod folders and/or github, maybe there are nowadays. Or ask on the forum there. You need a general Aarch64 UEFI HAOS image, qcow2 or raw/flat/img format and that will be able to run at full speed on a hypervisor. Not sure about VirtualBox, but for sure the Linux built-in QEMU/libvirtd/KVM. Main user-inteface program is installed via sudo apt install virt-manager.

Armbian image placed on internal soldered eMMC 64GB - only one issue now aic8800 not supported yet by kernel 7.0-rc6 so no wifi 😕 No PCI as no PCI slots... Experimental image based on Kwiboo repo dispo here.

This week’s Armbian development saw significant enhancements across hardware support and system functionality. The Arduino UNO Q was officially added, along with new firmware and flash binaries for the QRB2210 and QCM2290 variants. HDMI CEC support was introduced for Rockchip RK3588/RK3576 SoCs, while panel compatibility expanded with updates for Raspberry Pi and Hardkernel ODROID-Vu8S. Key kernel improvements included a bump to version 7.0-rc6 and rewritten patches for Rockchip64-6.18. The release also featured workflow hardening, exclusion of unsupported boards, and fixes for USB-C OTG mode on Odroid-M2. These updates collectively strengthen Armbian’s platform stability and broaden its device coverage. ChangesAdd Arduino UNO Q. by @igorpecovnik in armbian/armbian.github.io#268Add firmware for Arduino UNO Q (QRB2210/QCM2290). by @SuperKali in armbian/firmware#123Add HDMI CEC support to Rockchip RK3588/RK3576 SoCs. by @chaitan3 in armbian/build#9622Agatti: add flash binaries for Arduino UNO Q (QRB2210). by @SuperKali in armbian/qcombin#1Arduino logo. by @igorpecovnik in armbian/armbian.github.io#269ch13726a: Added missing MIPI_DSI_MODE_VIDEO. by @kay-lambdadelta in armbian/build#9621config: rockchip64: build Motorcomm YT6801 drivers built-in for OOB Ethernet. by @c127dev in armbian/build#9625drm: add support for rpi panel v2. by @ackPeng in armbian/linux-rockchip#465Exclude end-of-support boards from armbian-images.json. by @igorpecovnik in armbian/armbian.github.io#271Harden data-update-partners workflow. by @igorpecovnik in armbian/armbian.github.io#270mainline: bump edge to 7.0-rc6. by @EvilOlaf in armbian/build#9618Odroid-M2: Add support for Hardkernel ODROID-Vu8S panel. by @mlegenovic in armbian/build#9627Odroid-M2: Fix USB-C port in OTG mode. by @mlegenovic in armbian/build#9633Remove radxa-dragon-q6a from targets-release-nightly blacklist. by @igorpecovnik in armbian/armbian.github.io#267rockchip-vendor: CONFIG_BT_HCIBTUSB=m. by @vidplace7 in armbian/build#9628rockchip64-6.18: rewrite kernel patches against 6.18.21. by @EvilOlaf in armbian/build#9629SpacemiT: Disable k1-usb: add disconnect function support. by @pyavitz in armbian/build#9620View the full article

Thanks for the info to try other options 🙂 Thanks for the tip, I'll try other options 🙂 It worked for: odroid-c4 ... basically, the settings are the same as for the OrangePI3LTS, I'm talking about connecting cables to a 40x2 / 20x2 LCD. The diagram for the BananapiM2pro is as follows: My Winstar 40x2 OLED LCD compatible with drivers: hd44780 / driver: WS0010 is detected in the system as: 3f .................................. sudo i2cdetect -y 0 [sudo] kris: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 3f 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- .................................. You can also enter the appropriate values yourself in the file: sudo nano /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=meson fdtfile=amlogic/meson-sm1-bananapi-m2-pro.dtb rootdev=UUID=a4fb8074-c453-45da-ab31-4d61dca46cfa rootfstype=ext4 overlays=sm1-odroid-c4-i2c0 sm1-odroid-c4-i2c1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u regards

@tparys Thanks for your precious advices I merged them in one dts. This suppress the dummy rtc0 rplace it by the real ds3231 rtc , and as it's rtc0 linux uses it at boot with out any service or script. the dts : /dts-v1/; /plugin/; / { compatible = "amlogic,meson-sm1"; fragment@0 { target-path = "/soc/bus@ffd00000/i2c@1d000"; __overlay__ { status = "okay"; clock-frequency = <100000>; pinctrl-names = "default"; pinctrl-0 = <&i2c2_pins>; #address-cells = <1>; #size-cells = <0>; rtc@68 { compatible = "maxim,ds3231"; reg = <0x68>; }; }; }; fragment@1 { target-path = "/soc/bus@ff600000/bus@34400/pinctrl@40"; __overlay__ { i2c2_pins: i2c2_pins { mux { groups = "i2c2_sda_x", "i2c2_sck_x"; function = "i2c2"; bias-disable; drive-strength-microamp = <3000>; }; }; }; }; fragment@2 { target-path = "/soc/bus@ff800000/rtc@a8"; __overlay__ { status = "disabled"; }; }; }; then I set up a basic service to keep ds3231 up to date either by internal system clock or NTP if chrony synchronize with internet extract of syslog : 2026-04-06T10:19:22.245210+02:00 bananapim5 systemd[1]: Started sync-rtc.timer - Run RTC sync every 6 hour. 2026-04-06T10:19:22.248077+02:00 bananapim5 kernel: rtc-ds1307 0-0068: SET TIME! 2026-04-06T10:19:22.248112+02:00 bananapim5 kernel: rtc-ds1307 0-0068: registered as rtc0 2026-04-06T10:19:22.248120+02:00 bananapim5 kernel: rtc-ds1307 0-0068: setting system clock to 2026-04-06T08:19:16 UTC (1775463556) 2026-04-06T10:24:18.665668+02:00 bananapim5 systemd[1]: Starting sync-rtc.service - Synchronize RTC0 avec l'horloge systeme si NTP actif... 2026-04-06T10:24:18.743806+02:00 bananapim5 sync-rtc: NTP actif : mise à jour RTC0 depuis l'heure système 2026-04-06T10:24:18.751001+02:00 bananapim5 sync-rtc: Mise à jour RTC0 depuis l'heure système NTP actif/inactif 2026-04-06T10:24:19.005750+02:00 bananapim5 systemd[1]: sync-rtc.service: Deactivated successfully. 2026-04-06T10:24:19.006443+02:00 bananapim5 systemd[1]: Finished sync-rtc.service - Synchronize RTC0 avec l'horloge systeme si NTP actif. root@bananapim5:/home/gerard# service : root@bananapim5:/home/gerard# cat /etc/systemd/system/sync-rtc.service [Unit] Description=Synchronize RTC0 avec l'horloge systeme si NTP actif After=chronyd.service [Service] Type=oneshot ExecStart=/usr/rtc/sync-rtc.sh root@bananapim5:/home/gerard# cat /etc/systemd/system/sync-rtc.timer [Unit] Description=Run RTC sync every 6 hour [Timer] OnBootSec=5min OnUnitActiveSec=6h Unit=sync-rtc.service Persistent=true [Install] WantedBy=timers.target root@bananapim5:/home/gerard# cat /usr/rtc/sync-rtc.sh #!/bin/bash # sync-rtc.sh # Synchronisation RTC <-> système avec logging # Vérifie si Chrony a des sources NTP actives NTP_OK=$(chronyc tracking | grep 'Reference ID' | grep -v '0.0.0.0') if [ -n "$NTP_OK" ]; then # Chrony OK, mettre RTC à jour depuis l’heure système logger -t sync-rtc "NTP actif : mise à jour RTC0 depuis l'heure système" else # NTP indisponible logger -t sync-rtc "NTP inactif" fi logger -t sync-rtc "Mise à jour RTC0 depuis l'heure système NTP actif/inactif" hwclock -w -f /dev/rtc0 root@bananapim5:/home/gerard# thanks again

@rsbuffalo's Feb 18th post worked a treat for me on my Dragon Q6a (Armbian 26.2.1 trixie, xfce 4.20). Thanks so much for sharing your solution.

@HenricoLegal can you find the wifi chip on your board?

Holy Shit this is great! Finally can get use out of this doorstopper if you continue. Imagine getting MeshCore or Meshtastic installed.

@Nick A Thank you, can you publish a server image for the Radxa A7Z with kernel 6.18?

If an pre-made image is not there, just DIY. https://docs.armbian.com/Developer-Guide_Build-Preparation/

Tried building a trixie image with this tee and still locks at the same spot

ok. I have 5 cubieboard 1. Not possible memory card for every one.

Great! I will start to tinker around with armbian.

My PBP died, so I can no longer test it myself. You can start by testing the PPSSPP aarch64 AppImage. https://github.com/hrydgard/ppsspp/releases A couple of years ago I had performance issues with the PPSSPP Flatpak on my Phytium D2000, so I built it on Ubuntu 22.04. I'm not sure if I followed the instructions for Qt, or for Linux. So you need to install the prerequisites and I guess it doesn't hurt to install the additional packages mentioned for Ubuntu. https://github.com/hrydgard/ppsspp/wiki/build-instructions#building-with-cmake-other-platforms-eg-linux

moved to tvboxes

Hi @BOFFBOY, have you managed to make it work? Having similar issue : tried with two different orange pi 5 , two different nvme SSDs, three different Power supplies up to 5V/5A and three armbian kernels: 5.10 | 6.1 and 6.18