Active threads

But if that were the case, simply leaving it powered off for a while and then turning it back on should fix it, but it doesn't. As I mentioned, I have to re-flash them from scratch with Android before I can reinstall Armbian. Additionally, the boards are completely exposed (out of the casing), with a heatsink on the SoC and proper ventilation. The power supply shouldn't be the issue either, as it is also fully ventilated.

posting output of : armbianmonitor -u Helps with support.

While doing various tests, also other bootloader than EDK2-UEFI v1.1 that I had in eMMC, I discovered that with 2026.01-rc2_armbian-2026.01-rc2-S365a-Pa203-He3cc-V062a-Bbf55-R448a kernel 6.18.0-rc7-edge-rockchip64 did not find/enable audio via HDMI. I moved the computer to other room where I rely on the speakers in the monitor, else I would not have discovered it as I also use networked pulseaudio. What works is 2025.01-armbian-2025.01-S6d41-Pdb4b-H2194-V062a-Bb703-R448a, so sort of last-known-good, got that via: sudo apt install linux-u-boot-nanopi-r6c-current=25.8.1 and wrote the binary with dd to eMMC Another issue is that the monitor does get out of sleep too late, so the loglevel=7 effect can only be seen on extra serial console, whereas with the UEFI bootloader, the HDMI gets always initalized properly, so before kernel is loaded. Note that this is with booting via grub. So with EDK2-UEFI v1.1 bootloader, I get a normal Debian graphical kernel selection menu, like on x86-64. With Opensuse Tumbleweed it is slightly different, as that also automatically duplicates on serial console (if 't' is pressed , from 'text'). So this is actually quite ideal. The only disadvantage is that it does not want to store boot entries (but works on ROCK5B in SPI-flash). I probably need an own build on SD-card first to see how 2026.01 (or later) can do the same as EDK2-UEFI v1.1 more or less. I should note that with EDK2-UEFI v1.1 bootloader, I do not load the DTB that comes with the kernel version. I used the setting 'vendor' or 'mainline' in the UEFI settings, that gets stored well actually. Now with the 25.8.1 U-Boot, I manually added a devitree loader line in grub.cfg, but that will be overwritten, so need to see what makes sense.

@Nick Aforgot to add, it has allwinner h313, also how do you backup or dump stock? I need it so I will be able to return if something won't work. Also thanks for help.

From https://github.com/armbian/build/pull/5056#issuecomment-1529793978

I fixed my i2c gpio ldo regulator issue by disabling the axp_gpio in the device tree. &axp_gpio { status = "disabled"; }; The separate driver must have been rewriting the registers configured by the regulators driver. Now back to the LCD

display-service -c [INFO] all digits and leds on /usr/sbin/display-service: 116: cannot create /sys/class/leds/display/message: Permission denied == could it be the the tm16xx module does not create "message", I have seen (Hqnicolas) succes, but guess the "message" got created compiling tm16xx and(!) patching with https://lwn.net/Articles/1027664/ . did not solve this (got errors). Maybe related to kernel version? : 6.12.58-current-rockchip64.

First thing backup all the configs with another linux computer. Then you can try to chroot the sd card on the other linux computer and run passwd as root.

Still working through things, but FYI I was able to get 6.18 going on Ubuntu with some small effort. GPU needs work but still beats CPU, NPU looks great.

You’re more than welcome to clone my repository and fix the frame buffer console. All the sources are there except u-boot.

Got it connected now to a simple 13.8V PSU and it’s working a treat, just working my way around Linux and Runners but all good ! Thank you for the help @eselarm!

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v1.5.5 >=60fps@720p Super Robot Wars V

@laibsch, the answer to your question is in my last post. All those bad/"half-broken" adapters don't have problems with sequential writing/reading. And if you consider helpful pointing me to some obscure GUI writing tools as helpful, sorry, it's was not. I trust "dd" more then any of them. Very helpful was, however, @eselarm's post and I expressed my gratitude for it. To be honest, I don't really understand the intention of your last post. Could be my English is not good enough... Anyway, if my tone was was too harsh, I apologize for it.

Does this still work with current armbian version? I am using v25.11.2 for Orange Pi Zero3 running Armbian Linux 6.12.58-current-sunxi64 and I can't even get the display to turn on. Now I'll admit I am a complete noob when it comes to linux so I am most likely doing something wrong. I know am doing something that's way over my head but I enjoy researching and learning things but it's hard to find things on the subject. I am using the DTS from this comment: - copied it into ~ili9341 then did: - cd ili9341 armbian-add-overlay ili9341-spi1-opiz3.dts I rebooted and notice the screen didn't come on, so I did: dmesg and then following message came up: sun6i-spi 5011000.spi: cannot register SPI host It's a cheap ili9341 tft from aliexpress, it says it's using ST7789V for display drivers, is that maybe why it isn't working? driver ili9341.ko does show up in /lib/modules/6.12.58-current-sunxi64/kernel/drivers/gpu/drm/tiny any help would be appreciated.

Thank you, @Mangix. We bumped u-boot to v2025.10 for Helios, so I would assume those commits are already incorporated, aren't they? I have only looked at commit dates, not actual code.

@robertoj OK. I managed to build Armbian, selecting mipi-panel-dbi support and booting to 16-bit. After setting it up and running the dts you provided, my screen still doesn't work. I'm probably doing something wrong, because although the screen glows white, it still shows barely noticeable backlight flickering. I also tried to do it according to Pancake's instructions, but I also didn't have any success. This log with Pancake's cat log.txt [ 1.623324] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.173154] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.242555] sdiohal:sdiohal_parse_dt adma_tx:1, adma_rx:1, pwrseq:0, irq type:data, gpio_num:0, blksize:840 [ 7.591150] systemd[1]: Starting systemd-backlight@backlight:backlight_gpio.service - Load/Save Screen Backlight Brightness of backlight:backlight_gpio... [ 7.652908] systemd[1]: Finished systemd-backlight@backlight:backlight_gpio.service - Load/Save Screen Backlight Brightness of backlight:backlight_gpio. user@orangepizero3:~$ hostnamectl Static hostname: orangepizero3 Icon name: computer Machine ID: a5f7b63422b54dc5a365def0a7294555 Boot ID: 4445f89ef8cb4b999e3fa684f292ca2a Operating System: Armbian-unofficial 26.02.0-trunk bookworm Kernel: Linux 6.16.8-edge-sunxi64 Architecture: arm64 And this log with DTS from you cat log.txt [ 1.623908] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.172898] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.242212] sdiohal:sdiohal_parse_dt adma_tx:1, adma_rx:1, pwrseq:0, irq type:data, gpio_num:0, blksize:840 But I'm very happy that I managed to build my first Linux, albeit in such a simple way. My pinout Displ OpiZ3 Vcc - out 3.3v Gnd - gnd Cs - ph9 Reset - pc14 Dc/rc - pc7 Sdi(mosi) - ph7 Sck - ph4 Led - 5v Sdo(miso) - ph8

Hi, I’ve installed Armbian to my Vero4k+ and all works fine except wired ethernet, the thing is it kind of works, but when I use different dtb files: meson-gxl-s905d-vero4k-plus.dtb wifi works, bluetooth works eth doesn’t, eth0 interface is UP but can’t get IP or set one, meson-gxl-s905d-p230.dtb wifi works, bluetooth doesn’t, eth generally works but when testing with iperf3 in server mode it’s great cca 930mbps 0 errors, but in client mode it depends of OS (ubuntu or debian) and kernel (5 or 6) used from 1-350mbps but with looooot of errors (cca. 67000 for 10 sec test) and if I limit link speed to 100mbps it doesn’t change much, also lot of errors, if I boot it to osmc it works fine (920mbps symetrical, also some errors on client side but fine). Is there anything I can do to troubleshoot - fix this? Thank you

Did a fresh install of community Armbian desktop this time, running current 6.12.60 from here. It seems there is no need to compile from scratch if you are using the panel-mipi driver from kungfupanda, I copied my DTS, panel-mipi.bin, etc. from my edge custom compiled installation to the community one and it worked fine after repeating the initramfs process, but I still get a stuck display after a bit, this time on the Armbian loading screen. SSH and Serial console work fine, its just the system stops knowing how to use the display after the initial boot sequence is done, and the kernel hands off the display to X11 / Wayland? This is consistent with how I believe tinydrm works, which is storing the image in memory and displaying new ones from memory if given (which in this case, none are given after a certain stage in the boot process and this hand off to the window manager never happens.) Need to figure out how to tell the system to keep using the drm display. I already tried putting /dev/dri/card0 instead of /dev/fb0 in 99-fbdev.conf, and I've been trying the following extraarg in /boot/armbianEnv.txt to try and get it to work. Screen still pauses halfway through boot messages / loading screen. extraargs=video=SPI-1:480x320@30

go armbian-config - Wait warning message "The current OS (bookworm) is not a officially supported distro!" - Kernel - KER001 Use alternative kernels - Would you like to continue? <Yes> - Show only mainstream kernels on the list? <No> And there the list: then choose "linux-image-edge-sunxi64=25.8.1 v6.15.4 " mainstream kernels: linux-image-current-sunxi64/bookworm 25.8.2 arm64 Armbian Linux current kernel image 6.12.47-current-sunxi64 linux-image-edge-sunxi64/now 26.02.0-trunk arm64 [installed,local] Armbian Linux edge kernel image 6.16.8-edge-sunxi64 linux-image-legacy-sunxi64/bookworm 25.8.2 arm64 Armbian Linux legacy kernel image 6.6.75-legacy-sunxi64 6.16.8: 6.15.4: In the working kernel 6.15.4, the following audio-related modules are loaded: snd_soc_sunxi_machine, snd_soc_sunxi_ahub, snd_soc_sunxi_ahub_dam In the broken kernel 6.16.8, these three modules are completely missing. Only the generic snd_soc_hdmi_codec is present, but it doesn't seem to bind to the hardware correctly without the sunxi-specific modules. I don't know how, but there the list in 6.16.8: tried to activate all dtbs in armbian-config - DTO001 - Manage device tree overlays noghing happend

I don't even think this has anything to do with Armbian / Debian / Ubuntu. It's simply someone mucking around too much for their own good and frankly being arrogant about it. Until I see the problem reproduced in a stock setup this is simply PEBKAC as far as I can tell. I mean, for anyone actually willing to read, it's right there: Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. systemd is essentially a monolith, you don't really get to pick and choose for all intends and practical purposes. The choice @Quantum needs to make is whether he wants to have something that works or whether he prefers to be high-and-mighty and run around being condescending to those whose work he uses without paying a dime all the while making outlandish claims. This is a non-issue.

Hi Installed Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img and one of the USB-3 port, the top one, doesn't work. No reaction when inserting something, nothing in /var/log/syslog. The same with Armbian_25.11.1_Rock-5c_noble_current_6.12.58_minimal.img The Armbian_25.11.1_Rock-5c_trixie_vendor_6.1.115_minimal.img however is OK. What could be the cause of this problem? Thanks and regards, Chris

Hi I have a Rock5c with a Penta SATA hat and it works OK. It is the only (?) way of having several disk connected to Rock5c. Note, it cannot boot of the disks on the hat. Have two SSDs and mirrored ZFS pool. No problems at all. Setting it up to act as Frigate server. The fifth SATA, in fact e-SATA connector comes very handy to connect a large disc for constant recording. You may also consider Odroid HC4. I think it's the cheapest solution and it's fan is negligible 🙂 Have three of them, acting as mail/backup/HomeAssistant servers. Had in the past some problems with USB but recent kernels are OK. Hope it helps.

With the H618 kernel, the system is very stable but there is no audio output at all. With the H616 kernel, audio works perfectly, but the system starts showing screen distortions, artifacts, and UI crashes. When I said “image became distorted” and “kernel artifacts”, I meant things like the screen going black, color blocks appearing, and the desktop environment crashing. I already tried enabling analog-codec, installing alsa-utils, using alsamixer, and testing with mpg123, but the result didn’t change. I haven’t built my own Armbian image yet, but I’m considering trying an edge kernel with the Armbian build system.

@Learnincurve It is very easy to build only the kernel with the Armbian Build Framework. The result will then appear as output/debs/linux-image*.deb

ping @amazingfate and @prahal