Active threads

It happened a few days ago that I rebuilt my complete firmware package to try something with another device. An HC4 firmware binary also automatically falls out in this process. If you like, you can put it on a microSD card (dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/${entire-device-to-be-used}), place the prepared microSD card in your HC4 and start it with the boot button pressed. Check whether it meets your expectations, and if all tests are successful, you can transfer it to the SPI flash.

Board: Orangepione Testing results for the three available images. Should there be more images available? Armbian_26.5.1_Orangepione_resolute_current_6.18.33_minimal.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot Connect via ssh iperf3 after installing iperf3 gpio after installing gpiod HDMI video HDMI audio after installing mpg123 Used usb keyboard/mouse to test HDMI. Note that resolute now uses gpiod for gpio instead of sys. Gpiod had to be installed whereas trixie minimal comes with gpiod installed. Armbian_2Armbian_26.5.1_Orangepione_trixie_current_6.18.33_minimal.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot Connect via ssh iperf3 after installing iperf3 gpio HDMI video HDMI audio after installing mpg123 Used usb keyboard/mouse to test HDMI. Armbian_26.5.1_Orangepione_resolute_current_6.18.33_xfce_desktop.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot On HDMI connecter screen with usb keyboard/mouse Using terminal emulatori tested perf3 and gpio HDMI audio with vlc media player. Not working: Ran chromium to get to Armbian download page but took over a minute for each page to load and then the system crashed. With only 512MB RAM this system is under powered for general purpose desktop use. ubuntu_resolute_minimal.txt debian_trixie_minimal.txt ubuntu_resolute_xfce.txt

The longer answer is that for standard releases, updates only occur with each release cycle (i.e. every three months in Feb, May, Aug, and Nov each year. So you will get new kernel release on that schedule. Armbian also has rolling release repositories and these put out new versions on a frequent basis. And you should be able to switch between stable releases and rolling release apt repositories using armbian-config. Note that rolling releases don't get any testing (other than automated builds) and therefore may not be suitable for many users needs. But those are your two options.

You can send your DTB, that has wi-fi?

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I recognize this is an old thread - but there are no newer ones open and I figure having one thread instead of many is best. I'm trying to do the same thing as you OP, getting a raspberry pi DSI display working on a rockpi 4b+. I tried to adapt Radxa's DTS in a similar way you did from Armbian's Base DTS, and seeing what definitions changed and I came up with this non working DTS: Which gives the following DMESG error, very similar to yours: `[ 21.477004] rpi-ts-dsi ff960000.dsi.0: failed to attach dsi to host: -517 [ 21.477086] mipi-dsi ff960000.dsi.0: deferred probe pending: (reason unknown)` You'll note various differences between our DTS, like panel_in instead of panel_in_dsi, and mipi_dsi instead of mipi_dsi1. I based these off looking at the base DTS in Armbian kernel 6.18.32, but also on this project I found recently that brings support for 7 and 10 inch Osoyoo brand of DSI panels to the RockPi 4b+. I think that's really promising and will help with bringing DTS support to the raspberry pi panel (and others that are compatible). I recommend you look into it. I will continue iterating and update this thread with results if any. I don't think OP was pinning the problem on Armbian. OP was asking how to configure a custom DTS to work with the hardware they have. This is the community support forum, which is the correct place for this kind of discussion.

You could flash armbian to an SDcard, then set Jumper P10 to force UBoot to skip booting from EMMC and pick the sdcard instead. From there you can directly mount the internal storage and chroot into it to run armbian-config and enable the overlay.

https://libre.computer/products/roc-rk3399-pc/ Can the computer run entirely on free software which is software you can use, share, modify and redistribute? The question includes firmware, microcode, etc, any piece of software that is running on the computer. If some devices on the computer requires non free software in order to work then what devices are they? And will the computer still work if you choose to not install the pieces of non free software in question? Thank you.

For those who want to compile from source: a) locate file ~ /armbian-build-mxpro/patch/kernel/archive/sunxi-6.12/series.conf b) delete the following lines before issuing ./compile.sh: spi-rockchip-Fix-runtime-PM-and-other-issues and spi-fixes c) save the file and proceed to compilation (./compile.sh) Note: if you want to upgrade the Armbian firmware be aware that: linux-dtb-current-sunxi64/trixie 26.5.1 arm64 [upgradable from: 26.02.0-trunk] linux-image-current-sunxi64/trixie 26.5.1 arm64 [upgradable from: 26.02.0-trunk] will render the ethernet interface inoperable. You can prevent this by issuing sudo apt-mark hold armbian-firmware before sudo apt upgrade -y

Is it possible to change the boot order? For my use case, I would like the boot priority to be: eMMC, NVMe, and microSD card. Can this be configured?

I've created a guide here how to run a Home Assistant OS suprisingly it run mostly natively. Didn't do anything except replacing the DTB. Also right away flashed it into a emmc. On my board emmc is from Samsung and has a read speed on 180Mb/s...

Known issue on multiple older 64 bit Allwinner socs Try these: https://fi.mirror.armbian.de/incoming/igorpecovnik/pine64/archive/

I'd like to run the mainline kernel https://github.com/nickfox-taterli/avaota-a1-mainline-linux The board used to have a page and downloads here: https://armbian.com/boards/avaota-a1 but it's gone. Has support for this board been dropped?

@Sancho this is amazing! If you have the test image ready I will be really glad to test it out. I have more than 1 iSG Box SE so I can test it on multiple devices.

Ask AI to fix problems at repo level: https://github.com/armbian/supervised-installer so we can all benefit. I don't have capacity to maintain this alone.

Proprietary DDR and maskrom images from Rockchip Bare metall should provide DDR init replacement code, the only missing part in u-boot.

I assume you are talking about local connection here, not from the internet, so it's ngiinx webserver you are talking about, not nginx-reverse-proxy? Can you at least ping the ip of the server? Syncing apps might not connect over http or https (or rather, they probably don't), which your browser does. Are you sure letsencrypt works properly and it's not just your browsers refusing to connect over https due to missing/miss-configured ssl certificates? Does forcing http connection at least give you some response? As for using wget to test: "wget --spider <url>" should get you some info. It should look something like this for correct setup using https: (enter url without http or https, I have redacted url and ip for obvious privacy reasons) $ wget --spider <your_url_here> Prepended http:// to '<redacted>' URL transformed to HTTPS due to an HSTS policy Spider mode enabled. Check if remote file exists. --2026-05-23 14:48:27-- https://<redacted> Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt' Resolving <redacted> (<redacted>)... xxx.xxx.xxx.xxx Connecting to <redacted> (<redacted>)|xxx.xxx.xxx.xxx|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 0 Remote file exists and could contain further links, but recursion is disabled -- not retrieving. But as eselarm said above, we need way more information to be able to help.

also check this for kernel 7.0 https://github.com/Mr-DS-ML-85/rtl8188fu/tree/main

Wifi chip?

I have modified the wifi driver for linux kernel 7.0 and backwards compatible https://github.com/Mr-DS-ML-85/rtl8188fu

I bought this board because it has 2 lanes. So I changed the number of lanes in the dtb from 1 to 2. I need confirmation of an expert but my quick speed test with 2 lanes looks promising : gt@yy3568:~$ sudo hdparm -tT --direct /dev/nvme0n1p1 /dev/nvme0n1p1: Timing O_DIRECT cached reads: 1062 MB in 2.00 seconds = 530.34 MB/sec Timing O_DIRECT disk reads: 928 MB in 3.00 seconds = 308.97 MB/sec gt@yy3568:~$ sudo dmesg | grep lane [ 4.183004] phy phy-fe8c0000.phy.6: lane number 0, val 1 [ 4.183679] phy phy-fe8c0000.phy.6: lane number 1, val 2 pcie@fe280000 { compatible = "rockchip,rk3568-pcie"; #address-cells = <0x03>; #size-cells = <0x02>; bus-range = <0x20 0x2f>; clocks = <0x0f 0x8f 0x0f 0x90 0x0f 0x91 0x0f 0x92 0x0f 0x93>; clock-names = "aclk_mst\0aclk_slv\0aclk_dbi\0pclk\0aux"; device_type = "pci"; interrupts = <0x00 0xa5 0x04 0x00 0xa4 0x04 0x00 0xa3 0x04 0x00 0xa2 0x04 0x00 0xa1 0x04>; interrupt-names = "sys\0pmc\0msg\0legacy\0err"; #interrupt-cells = <0x01>; interrupt-map-mask = <0x00 0x00 0x00 0x07>; interrupt-map = <0x00 0x00 0x00 0x01 0xcb 0x00 0x00 0x00 0x00 0x02 0xcb 0x01 0x00 0x00 0x00 0x03 0xcb 0x02 0x00 0x00 0x00 0x04 0xcb 0x03>; linux,pci-domain = <0x02>; num-ib-windows = <0x06>; num-ob-windows = <0x02>; max-link-speed = <0x03>; msi-map = <0x2000 0x66 0x2000 0x1000>; num-lanes = <0x02>; phys = <0xca>; phy-names = "pcie-phy"; power-domains = <0x11 0x0f>; reg = <0x03 0xc0800000 0x00 0x400000 0x00 0xfe280000 0x00 0x10000 0x00 0xf0000000 0x00 0x100000>; ranges = <0x1000000 0x00 0xf0100000 0x00 0xf0100000 0x00 0x100000 0x2000000 0x00 0xf0200000 0x00 0xf0200000 0x00 0x1e00000 0x3000000 0x03 0x80000000 0x03 0x80000000 0x00 0x40000000>; reg-names = "dbi\0apb\0config"; resets = <0x0f 0xc1>; reset-names = "pipe"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0xcc>; reset-gpios = <0x58 0x1e 0x00>; vpcie3v3-supply = <0xcd>; phandle = <0x271>; legacy-interrupt-controller { interrupt-controller; #address-cells = <0x00>; #interrupt-cells = <0x01>; interrupt-parent = <0x01>; interrupts = <0x00 0xa2 0x01>; phandle = <0xcb>; }; };

You'd better upgrade the kernel to 6.18 and keep Debian Bookworm, because Trixie has an mpv version which is not exactly friendly with hardware video decoding because some things are in the middle of a transition

OK, it looks like the BSP PCIe driver might have some issues related to power management. I’m not entirely sure of the root cause yet, but when I connected an NVMe drive, it got extremely hot and failed to initialize properly. The NVMe dmesg output suggested adding the following kernel parameters: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off This resolved the NVMe issues on my side. I’ll try to dig deeper into the root cause, but @humanus please give it a try as well.

Thank you @greg396 for this sum-up on how to upgrade to 6.12 Since last months, have you experience any issue with this version ? I'm on 6.6.8 based on kernel 23.08.0. Stable so far...

Hi @OverNautt! Sorry not replying in time. Great that you found a solution to your issue and provided feedback!