All Activity

Thank you. I also can confirm this issue on Armbian 25.5.1 Bookworm, and that the suggest workaround works. For those interested, here is a more detailed explanation of what @Lars Christian Nygård said. Create a backup of original DTB. sudo cp /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts-orig.dts Decompile the DTB for the Orange Pi 3 LTS. sudo dtc -I dtb -O dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Modify the decompiled DTS file according with your favorite editor, e.g. nano or vim. sudo nano /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts Navigate to the "spi@5011000" section and modify it. Set "status" to "okay" and add the "spidev@0" section. spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x06 0x53 0x06 0x51>; clock-names = "ahb\0mod"; dmas = <0x2e 0x17 0x2e 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x31 0x32>; resets = <0x06 0x20>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x78>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; Save and compile the modified DTS file. sudo dtc -I dts -O dtb /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Remove any previously configured overlay for SPI using "armbian-config" or editing the "/boot/armbianEnv.txt" file directly. No further modifications are needed to load our new recompiled DTB, since we directly modified the base DTB. Reboot when done.

ls: unable to get access to '/boot/dtb/overlays': No such file or directory. Despite this, I attached full tree of "boot" directory. boot_dir_content.txt

Difficult to see like this, better list the overlay directory: ls /boot/dtb/overlays

I don't see such interfaces. Could you point me if one of these are suitable?

sudo armbian-config Are you able to see the below overlays ? If yes, activate them. System → Hardware/Kernel → Activate UART0, UART1, BT overlays

Sure. armbianEnv.txt

Can you post your /boot/armbianEnv.txt ?

Just plugged a M.2 M key to E key adapter with an Intel AX200 iwlwifi (installed the firmware) booted up and Wifi 6 is going without using a USB port. My project is one step closer!!! Just have to get that last USB-C port working.

Description fix build error with new compiler update uboot to v2024.04 ras314: fix sd-card regulator error How Has This Been Tested? [x] Build and Boot CLI/Gnome image on mba8mp [x] Build and Boot CLI/Gnome image on mba8mp-ras314 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

user@orangepizero2w:~$ systemctl status bt-gpio.service × bt-gpio.service - Enable GPIO for Bluetooth chip Loaded: loaded (/etc/systemd/system/bt-gpio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2025-06-10 23:18:23 +03; 11h ago Process: 489 ExecStart=/bin/sh -c echo 225 > /sys/class/gpio/export || true; echo out > /sys/class/gpio/gpio225/direction; echo 1 > /sys/class/gpio/gpio225/value (code=exited, status=2) Main PID: 489 (code=exited, status=2) CPU: 5ms jun 10 23:18:23 orangepizero2w systemd[1]: Starting bt-gpio.service - Enable GPIO for Bluetooth chip... jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: echo: echo: I/O error jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/direction: Directory nonexistent jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/value: Directory nonexistent jun 10 23:18:23 orangepizero2w systemd[1]: bt-gpio.service: Main process exited, code=exited, status=2/INVALIDARGUMENT jun 10 23:18:23 orangepizero2w systemd[1]: bt-gpio.service: Failed with result 'exit-code'. jun 10 23:18:23 orangepizero2w systemd[1]: Failed to start bt-gpio.service - Enable GPIO for Bluetooth chip. Also I attached boot log which is connected to that "systemctl status bt-gpio.service" command. bt_fail_boot_log_3.txt When the board was boot correctly (BT is working fine) the output looks the same: user@orangepizero2w:~$ systemctl status bt-gpio.service × bt-gpio.service - Enable GPIO for Bluetooth chip Loaded: loaded (/etc/systemd/system/bt-gpio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-06-11 11:04:21 +03; 1min 30s ago Process: 492 ExecStart=/bin/sh -c echo 225 > /sys/class/gpio/export || true; echo out > /sys/class/gpio/gpio225/direction; echo 1 > /sys/class/gpio/gpio225/value (code=exited, status=2) Main PID: 492 (code=exited, status=2) CPU: 5ms jun 11 11:04:21 orangepizero2w systemd[1]: Starting bt-gpio.service - Enable GPIO for Bluetooth chip... jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: echo: echo: I/O error jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/direction: Directory nonexistent jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/value: Directory nonexistent jun 11 11:04:21 orangepizero2w systemd[1]: bt-gpio.service: Main process exited, code=exited, status=2/INVALIDARGUMENT jun 11 11:04:21 orangepizero2w systemd[1]: bt-gpio.service: Failed with result 'exit-code'. jun 11 11:04:21 orangepizero2w systemd[1]: Failed to start bt-gpio.service - Enable GPIO for Bluetooth chip.

Sounds good, thank you Werner! If anyone wants to share their favorite boards then please go ahead too 🙂

No

tl;dr: Yes Status of CSC boards is unknown to the Armbian team. They probably work but could also be broken. Standard and above are tested to some extend.

That is worrying, I wonder if there could potentially be issues with the RAM, which could either be faulty or clocked higher than a level it is stable at. Reffering back to the fex you provide earlier it suggest a dram value of 384, so you may have to the def_config file to include the line CONFIG_DRAM_CLK=384. Is the card just class 10 rated or is it an A1 SD card? https://docs.armbian.com/User-Guide_Getting-Started/ Strange it should auto login on first boot. What it should be request is to set a new root password then confirming that password. Could you please provide a screen shot of the login screen you are greeted with. Alternatively it may be possible to set the root password external to get around this issue. Please see: https://docs.armbian.com/User-Guide_Autoconfig/ Strange never encoutered that before, have you tried pulling the latest version of armbian build to see if it fixes it? Unfortunately I have not had a lot of luck in trying to get WSL2 to work so I have stuck with virtual box. Worth a shot with the pre-built images, but I dont believe the Cubieboard is in a much better state. best of luck Ryzer

Description Fix the peripheral aliases to ensure consistent allocation when enabled, so that kernel assignment matches the numbering convention of the SOC. This targets the Allwinner A10 and A20 and ensures, that for example if enabling UART2 exposes it correctly in userspace as ttyS2 rather than dynamically assigning it to the first avaliable ttySx slot. Secondly spidev overlays creates an instance of spidevX.Y based on the bus specified with armbianEnv.txt however it does not correctly configure the corresponding pins into spi mode. To resolve this the individual spi bus overlays have been include in the makefile. The desired bus must be enabled alongside spidev or seperately if using another spi device driver in order to be functional. I have also corrected the A10 spi overlays where they incorrectly target the A20. How Has This Been Tested? Built and tested on Pcduino 2 running 6.12.23-current-sunxi Built and tested on Pcduino 3 running 6.14.5-edge sunxi Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings View the full article

5B+ on vendor (6.1.115) has all I/O related stuff fixed (since 6.1.84) as far as my testing (the one reported in the https://www.armbian.com/rock-5b-plus/ description). Looking into the broken gnome image though and will update here!

Yes, that is the main idea, but sometimes things slipped trough. Images were tested (we aim to have two people on one platinum target to be able to provide better service, but perfection is still not possible), but here we ran into weird problem that CI compilation silently broke on u-boot recompilation, while local build works. We have a problem with build framework / compiler internals, unrelated to this specific hardware and problem only manifest on some u-boot variants. Right now, I don't have a clear picture, but we are working on it. This was introduced while moving framework to Noble, which is mandatory for some targets and there are some Python libraries troubles ... which are sometimes used for u-boot / ATF compile. Its a mess. Software maintenance within such extreme complexity is job that is never done. Generally speaking.

Are platinum supported boards not tested on actual hardware before posting images? FYI we are on of radxas big partners that paid for the platinum membership so there is better support for this board, not sure if all the USB/wifi related driver issues were fixed?

hi , can i use these image to boot armbian to my s805X Amlogic soc.

Yeah, it was reported at GH too: https://github.com/armbian/build/issues/8227 Probably related: https://github.com/armbian/build/issues/8269 No solution yet.

Hi, If you are having trouble sourcing a proper serial dongle, you could also try to set (or cap) the serial console's baudrate yourself in armbianEnv.txt. Use/replace the following: console=comfort extraargs=console=ttyS2,115200 earlyprintk=ttyS2,115200 This should prevent your bootscript from setting the kernel's serial baudrate to 1M5 and at least give you some kernel logging during booting. Not sure if the login prompt will follow the same baudrate, as `getty` (or one of it's variants) might use different default settings. Groetjes,

I see this bug increasingly, and now even a lot of kernel panic and shutdowns, but I was able to get the login screen two or three more times. At the login I faced the same error: using root and 1234 I was told 'login incorrect'. I tried to check whether this is an SD card related issue, and I used h2testw to test my Class 10 SD card, and got no errors there. Then I tried to recompile armbian but repeatedly got this error: https://paste.armbian.eu/daxamubowe So I am unable to build now, but the next thing I am going to try is the Cubieboard pre-built image and see what happens. Thanks, Shivam

the manufacturer hates us, that's it There is no method, they are all hobbyist experiments

@maka into this file: https://github.com/hqnicolas/ubuntu-rockchip-joshua/blob/main/config/suites/noble.sh it makes refference to the kernel repo: https://github.com/hqnicolas/linux-rockchip that contains the dts file: https://github.com/hqnicolas/linux-rockchip/blob/arm64--dts--rockchip--add-rk3566-h96max-v56/arch/arm64/boot/dts/rockchip/rk3566-h96max-v56.dts That have the USB setup: &usb2phy0 { status = "okay"; }; &usb2phy1 { status = "disabled"; }; &usb_host0_ehci { status = "disabled"; }; &usb_host0_ohci { status = "disabled"; }; &usb_host1_ehci { status = "disabled"; }; &usb_host1_ohci { status = "disabled"; }; &usbdrd_dwc3 { dr_mode = "host"; extcon = <&usb2phy0>; status = "okay"; }; &usbdrd30 { status = "okay"; }; &usbhost_dwc3 { status = "okay"; }; &usbhost30 { status = "okay"; }; &pinctrl { usb { vcc5v0_otg_en: vcc5v0-otg-en { rockchip,pins = <0 RK_PA5 RK_FUNC_GPIO &pcfg_pull_none>; }; }; There Are 3 Branches:

Just a brief update to say that I've gotten overwhelmed with other things in my life. I still primarily suspect something is up with the connection to the serial console and that I should experiment there, as @Igor suggested. In three weeks time, I will have several days at my server's location with plenty of time to devote to this. I will try to get my hands on a machine with a USB-A port running something other than macOS.