All Activity

Ok, create a new dts /boot/overlay-user/bt_enable_full.dts /dts-v1/; /plugin/; &pio { bt_en_pin: bt_en_pin { pins = "PH1"; function = "gpio_out"; bias-pull-up; output-high; }; bt_wake_pin: bt_wake_pin { pins = "PH0"; function = "gpio_in"; bias-pull-up; }; }; &{/soc} { wcn_bt: wcn_bt@0 { compatible = "wcn,bt"; status = "okay"; enable-gpios = <&pio 7 1 GPIO_ACTIVE_HIGH>; // PH1 = GPIO225 wake-gpios = <&pio 7 0 GPIO_ACTIVE_HIGH>; // PH0 = GPIO224 (if connected) }; }; And compile it: sudo armbian-add-overlay /boot/overlay-user/bt_enable_full.dts Then enable it in /boot/armbianEnv.txt user_overlays=bt_enable_full See if there's an improvement on boot.

Here is the login prompt that failed: And about my SD Card, it is just a class 10 SanDisk Ultra card but does not say A1 anywhere. So next I tried the pre-built image for Cubieboard and it booted too! This is more stable than before, but as soon as I try to do downloads or file operations, I start seeing similar page state or mmc errors. I think this might be related to RAM frequencies as you mentioned. Is there a way I can change DRAM clock on a system after it boots? Adding to that, is there a way I can enable the display on this after it boots, or install drivers using an overlay? That would be great to test things out. I am trying to build again but it keeps failing at the same stage as last time, even after pulling the latest version. I think I should try either docker or a VM to build this, because it does not seem to be working on WSL. Thanks, Shivam

Thanks for your reply. You're right — the image I initially used came from the debmfc GitHub fork. I understand now that it's not officially supported by Armbian. I now tried the image from Armbian itself: Armbian 25.8.0-trunk.90 Bookworm Gnome However, I wanted to follow up on the CPU identification part, as you mentioned uncertainty about the S905M. I’ve opened up the stick and inspected the hardware. The SoC is clearly labeled as: Amlogic S905M Quad-Core Additionally: RAM: 2x Samsung K4B4G1646B (total 8GB DDR3) Storage: no internal NAND/eMMC, boots entirely from MicroSD Original SD card runs EmuELEC out-of-the-box I’ve attached pictures of the board below (top and bottom views), including close-ups of the SoC and RAM chips and screenshots of the partitions of the normal EMUELEC Emulator. I also tested your suggestion about verifying the CPU. It is definitely not an S905L or S905X2. This unit appears to be an Amlogic S905M I now tried the image from Armbian itself: Armbian 25.8.0-trunk.90 Bookworm Gnome and it still does not give any display output. I opened up the Game Stick and on the CPU iteself it says "@mlogic S905M

That was successful. Unfortunately, the fail rate not too much better than as I added new service: one boot was good, one was bad. Here is a log of the fail boot. bt_boot_fail_after_new_devicetree.txt

A little typo in the commands: patch -b sun50i-h6-orangepi-3-lts.dtso opi3lts-dtb.patch Should be: patch -b sun50i-h6-orangepi-3-lts.dts opi3lts-dtb.patch it should be .dts and not .dtso, its'n not an overlay. Sorry if that confused anyone.

Ok, replace the contents of the dts file with this: /dts-v1/; /plugin/; / { fragment@0 { target = <&pio>; __overlay__ { bt_enable_pin: bt_enable_pin { pins = "PH1"; function = "gpio_out"; bias-pull-up; output-high; }; }; }; }; And try again the steps

sudo armbian-add-overlay /boot/overlay-user/bt_enable_ph1.dts Compiling the overlay Error: /boot/overlay-user/bt_enable_ph1.dts:22.30-31 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay Unfortunately, I didn't understand what the error is.

Can you help me install a unlocked version of android.

Ok, if you want we can try one more thing. According to AI, the correct way to always enable the bluetooth is to do it via a custom overlay, which is not done. First, remove the bt-gpio.service, it does not help: sudo sytemctl disable bt-gpio.service sudo rm /etc/systemd/system/bt-gpio.service sudo systemctl daemon-reload Then, create the custom overlay file /boot/overlay-user/bt_enable_ph1.dts with the following content: /dts-v1/; /plugin/; &pio { bt_en_pin: bt_en_pin { pins = "PH1"; function = "gpio_out"; bias-pull-up; output-high; }; }; &uart0 { pinctrl-names = "default"; pinctrl-0 = <&uart0_pins>; status = "okay"; }; &wcn_bt { compatible = "wcn,bt"; uart = <&uart0>; enable-gpios = <&pio 7 1 GPIO_ACTIVE_HIGH>; // PH1 = GPIO 225 status = "okay"; }; Then we can try to compile and install it: sudo armbian-add-overlay /boot/overlay-user/bt_enable_ph1.dts Then activate it in /boot/armbianEnv.txt, add the following line: user_overlays=bt_enable_ph1 If all works well try to reboot and see what happens.

Unable to reproduce. Probably date and time is out of sync. Edit: aha, this is / was the problem: https://github.com/armbian/build/commit/aa5526a9189097b87ada0784cff61bda85e46609 Which means next week community build will have this auto-fixed.

Surprisingly the fresh installation gives so much trouble for typical first command like apt-get update. I suppose something is missing in this download. It's first time the command apt-get update did not work out of the box.

_ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.8 rolling for Orange Pi Zero2 running Armbian Linux 6.12.30-current-sunxi64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 1 package available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.51 (WAN) 103.112.33.59 Performance: Load: 38% Up time: 4 min Memory usage: 14% of 971M CPU temp: 49°C Usage of /: 17% of 7.2G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@orangepizero2:~# sudo apt-get update Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB] Hit:2 http://deb.debian.org/debian bookworm InRelease Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:4 http://deb.debian.org/debian bookworm-backports InRelease [59.4 kB] Get:5 https://github.armbian.com/configng stable InRelease [3,992 B] Get:7 http://security.debian.org bookworm-security/main arm64 Packages [262 kB] Get:6 https://netcup-03.armbian.com/beta bookworm InRelease [53.3 kB] Get:8 http://deb.debian.org/debian bookworm-backports/main arm64 Packages.diff/Index [63.3 kB] Err:5 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 Get:9 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2025-06-12-0204.25-F-2025-06-01-1404.04.pdiff [10.4 kB] Get:9 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2025-06-12-0204.25-F-2025-06-01-1404.04.pdiff [10.4 kB] Get:10 https://netcup-03.armbian.com/beta bookworm/bookworm-desktop all Packages [2,110 B] Get:11 https://netcup-03.armbian.com/beta bookworm/main all Packages [1,590 B] Get:12 https://netcup-03.armbian.com/beta bookworm/bookworm-utils all Packages [3,873 B] Get:13 https://netcup-03.armbian.com/beta bookworm/bookworm-utils arm64 Packages [29.8 kB] Get:14 https://netcup-03.armbian.com/beta bookworm/bookworm-desktop arm64 Packages [3,256 B] Get:15 https://netcup-03.armbian.com/beta bookworm/main arm64 Packages [261 kB] Fetched 857 kB in 5s (172 kB/s) Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://github.armbian.com/configng stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 W: Some index files failed to download. They have been ignored, or old ones used instead. sudo gpg --keyserver keyserver.ubuntu.com --recv-keys 93D6889F9F0E78D5ro2:~# sudo gpg --keyserver keyserver.ubuntu.com --recv-keys 93D6889F9F0E78D5 gpg: directory '/root/.gnupg' created gpg: keybox '/root/.gnupg/pubring.kbx' created gpg: key 93D6889F9F0E78D5: 1 duplicate signature removed gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 93D6889F9F0E78D5: public key "Igor Pecovnik <igor@armbian.com>" imported gpg: Total number processed: 1 gpg: imported: 1 sudo gpg --export 93D6889F9F0E78D5 | sudo tee /etc/apt/trusted.gpg.d/armbian-configngapt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 https://github.armbian.com/configng stable InRelease [3,992 B] Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Err:2 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 Hit:5 http://security.debian.org bookworm-security InRelease Hit:6 https://netcup-03.armbian.com/beta bookworm InRelease Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://github.armbian.com/configng stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 W: Some index files failed to download. They have been ignored, or old ones used instead. root@orangepizero2:~#

The base device tree for the Renegade (roc-rk3328-cc) already includes a PWM2 device but armbian does not include the .dtbo to enable it. Thus, it is also unavailable through armbian-config. The Libre builds of Debian support it, but not armbian. I have copied the overlay from the Libre build of Debian for Renegade and it applies correctly on after I manually add it to the overlay directory: /boot/dtb-6.12.32-current-rockchip64/rockchip/overlay/rockchip-rk3328-pwm2.dtbo Note that as of today armbian-config is having a general issue with loading overlays via armbianEnv.txt. This can be bypassed by avoiding using armbian-config for overlays and editing armbianEnv.txt directly and adding the overlay name to the overlays= line minus the "rockchip-" prefix. FWIW - here's the overlay source: =========================== /dts-v1/; / { compatible = "libretech,roc-rk3328-cc\0rockchip,rk3328"; fragment@0 { target = <0xffffffff>; __overlay__ { status = "okay"; }; }; __fixups__ { pwm2 = "/fragment@0:target:0"; }; };

That's completely understandable. Given how long the A10 and A20 have been around, I wouldn't expect recent kernels to be thoroughly tested on them. Even from my perspective HDMI is more of a nice-to-have rather than a priority. I realize I might be an exception in this, but I prefer trying to fix issues myself rather than relying on someone else to do it. The only real barrier is my own lack of knowledge. That said, I believe I’ve firmly gotten to grips with device trees now. I acknowledge that I still have some way to go before I can confidently dig into driver development myself. I really appreciate the effort from you and others in making the build system so easy to use. Thanks to that, I’m able to apply my own fixes where needed with relatively minimal technical knowledge of the intricacies of Linux. I actually noticed the change today while browsing kernel.org. Exactly what I had in mind.

Further, I can't find any reference to an Amlogic S905M cpu. (https://en.wikipedia.org/wiki/Amlogic) In a google search, I see reports of some people saying the actual cpu is an S905L while others report having an S905X2. You might want to open up the stick to see what the actual CPU is.

That is not an Armbian build, but a third party fork of Armbian. These forums are for Armbian. You need to direct your question to the provider of the software you are testing, as we can't answer questions for third party software.

That github page tells you that the in-kernel driver is better than morrownr's driver. Have you tried that first? Search for rtw88 in the /lib/modules folder Try rebuilding armbian, find rtw88 or 8812au in the linux configuration menu and activate them.

Hello, I'm trying to get Armbian (Ubuntu 24.10 XFCE Desktop) running on a retro game stick device with the following specs: CPU: Amlogic S905M RAM: 8 GB Samsung (2x K4B4G1646B) Storage: Samsung 128 GB MicroSD (new, flashed via balenaEtcher) Ports: 1x USB-A, 1x MicroSD slot, 1x MicroUSB power (possibly supports OTG), 1x HDMI male output Original firmware: EmuELEC (working fine from factory SD card) What I tried: Flashed Armbian Ubuntu 24.10 (from debmfc GitHub) to the SD card Tried box=s905_generic in the config file Replaced dtb.img with several DTBs, including: meson-gxbb-p200.dtb meson-gxbb-p201.dtb meson-gxbb-xtmqbox.dtb Performed toothpick method to boot from SD card Green LED turns on, but: No HDMI output CPU stays cold, no signs of booting USB devices receive no power No blinking, no UART logs (I don’t have serial access yet) It feels like the CPU doesn’t even begin to initialize Linux – maybe it doesn't load the u-boot from the SD at all? Any idea what else I can try? Is there a minimal verified Armbian image known to boot on S905M-based TV sticks? Do I need to trigger multiboot somehow? Could this be a special bootloader variant? Could I use the original EmuELEC SD and inject Armbian files into it? Any help or known working image would be greatly appreciated. Thanks in advance!

Me too. I was not paying attention to this due to dealing with many non technical things in past few months and as already mentioned, those upgrades are not being tested on older boards. We simply don't have enough resources, test automation is limited - HDMI is not tested in any case. There is more or less just one main person doing general maintenance on Allwinner with occasional help of random people. 6.14 is already EOL and we just switched to 6.15 (EDGE branch), but we will probably stay on stable CURRENT branch with 6.12.y for awhile as its fairly stabilized in general across several platforms. IMO it is best to backport this patch for 6.12.y or fix whatever breaks this.

@Igor I can only guess that something has changed within the drm framework somewhere between kernel 6.6 and 6.12. After a bit of digging I did find the patch mentioned in my previous post, which I can confirm does restore HDMI functionality albiet with what appear to be minor errors. Taken from Pcduino3: ryan@pcduino3:~$ sudo dmesg | grep drm [sudo] password for ryan: [ 1.000426] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc0caec14) [ 1.000666] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc0caec14) [ 1.001260] sun4i-drm display-engine: bound 1e60000.display-backend (ops 0xc0cae380) [ 1.001797] sun4i-drm display-engine: bound 1e40000.display-backend (ops 0xc0cae380) [ 1.002745] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 1.002787] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0cac870) [ 1.003623] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 1.003671] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0cac870) [ 1.005703] sun4i-drm display-engine: bound 1c16000.hdmi (ops 0xc0caf610) [ 1.007882] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.068719] sun4i-drm display-engine: [drm] *ERROR* Unsupported infoframe type: 131 [ 1.068755] sun4i-drm display-engine: [drm] *ERROR* Unsupported infoframe type: 129 [ 1.126922] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device [ 4.022304] [drm] Initialized simpledrm 1.0.0 for 7e000000.framebuffer on minor 1 [ 4.150136] simple-framebuffer 7e000000.framebuffer: [drm] fb1: simpledrmdrmfb frame buffer device [ 4.537321] [drm] Initialized lima 1.1.0 for 1c40000.gpu on minor 2 [ 8.416996] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 8.783119] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 8.785117] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. kernel 6.14 already has the changes adopted so does not need to be patched. I appreciate that boards like the pcduino2 are over a decade old now and not likely to achive the same attention as something like the orange pi zero.

Did you make any progress with this? Also looking to build something with I2S.

I have noticed regression on A20, probably also on A10 few weeks ago ... but so far we haven't been able to do anything - almost no active developer have those boards. ... and Welcome!

From https://github.com/morrownr/8821au-20210708

Welcome! This question is a bit off topic here as general Armbian updates are not part of HA extension. As this is community supported hardware, stable BSP upgrades - where OS version is stored - might not be generated, while kernel and everything else is getting upgrades. tl;dr; Don't worry about this. For board related topics proceed here https://forum.armbian.com/forum/173-allwinner-sunxi/

Hey if it’s still available I will pay the shipments