Active threads

Hello good people. I honestly had given up on that thing, until last weekend, where I set my mind to finally get it to work. And work, it does! eMMC works, display output works without a trouble, and only today I've seen @eloirotava's comment about the 6051. And I'm calling for help again on that one. I currently am using the kernel 7.0.8-meson64 (the current edge for the tv box) and no matter what i'm doing, there's no way for me to get the correct linux-header files, to compile and install that module. May a kind soul help me? I'll post a full documentation very soon, and will probably push my work to the armbian git, once everything is clean. Thank you very much in advance!

I used Balena for the burning process, do I need another complementary program?

@Suly rtl8703bs works with 8723cs driver, but the proprietary driver has been disabled so far in newer kernels because maintenance was becoming more and more complex. Actually I don't remember if it works with the mainline kernel driver. Probably it works, but I don't know if it is enable in rockchip64 kernel; it is surely enabled in rockchip armhf family.

Howdy. if you have the tf uart adapter thingy, by the time it shows that on screen you are at the u-boot prompt where you can do what you want. e.g. start fastboot. I believe this tablet cannot be bricked because you can always enter FEL mode and use phoenixsuit. It can be maddeningly difficult to phoenixsuit to flash cold tablet but i recall it was like this: press and hold vol+ and power, plug usb cable with phoenixsuite ready to flash. release power button and vol+ few seconds later.

Problem remains the same. i have cloned a new build repos and patch with pr-9626 and rebuild image. console output result remains: U-Boot SPL 2026.01_armbian-2026.01-S127a-Pa547-Hc6a9-V2b7c-Bd0d2-R448a (May 18 2026 - 10:12:32 +0200) DRAM: 1024 MiB Something wrong with the uboot timing of the dram etc.? i can supplied the timing and trimming of the board with the funtional debian bootloader saved to spi. Setting of voltage regulators etc. see attached file. Regards Rolf hardcopy.0

Been doing some RK3588 board porting and kept running into the same category of bug — dtc compiles clean, dtbs_check passes, but the board either panics on suspend or a peripheral silently fails to probe. Stuff like: Peripheral on the EE supply wired to something that only stays alive in the AO domain → suspend-resume panic Copy-pasted a GPIO bank with 32 pins, used pin 35 → kernel panic at driver probe SPI clock request exceeds PLL maximum → silent bus hang Two nodes sharing the same GIC SPI interrupt line None of these are schema violations — they require knowing the actual cross-domain constraints of the SoC, which dtc has no idea about. So I wrote a Python tool that builds an in-memory model of the power tree, clock tree, and pin assignments, then runs constraint rules against it: $ pip install soc-consistency $ socc check board.dts --soc rk3588 error[PD-001] Power domain crossing — i2c@fe2b0000 uses vcc_3v3 (EE domain) but is connected to vcc_1v8 (AO domain). Will panic on suspend. error[GP-003] GPIO index out of bounds — gpio1 pin 35 on a 32-pin bank. warn[CK-003] Clock rate mismatch — spi0 requests 50 MHz from pll_cpll (max 24 MHz). There's also a decompile command that runs dtc on a binary blob and annotates the output with peripheral names from the SoC database — useful when you're staring at a vendor DTB and have no idea which block is at which address: $ socc decompile vendor.dtb --soc rk3588 gpio0@fd8a0000 /* GPIO0 (32-pin, 3.3V) */ { cru@fd7c0000 /* CRU — Clock and Reset Unit */ { RK3588 has the most complete constraint coverage right now. The constraint format is a simple YAML file — happy to accept PRs for other SoCs. GitHub: https://github.com/gahingwoo/SoC-Consistency Docs/rules reference: in the README If you hit false positives on a real BSP DTS, open an issue — BSP files from vendors tend to have a lot of "intentional" violations that I'm still tuning the rules around.

@Nick A TY very much for your reply, I've managed to create my first build but I am a bit confused because it made an IMG with a FAT32 boot partition, is it right or did I miss something?

After many weeks of research, testing and debugging I managed to put together an Unofficial Armbian Linux build for LinknLink iSG Box SE. Version: v26.05 Rolling Kernel: 6.1.115-vendor-rk35xx Flashed and booting from eMMC. All hardware working and tested, including Ethernet, WiFi and Bluetooth. Source, build and flashing instructions here https://github.com/luisdosreis/linknlink-isg-box-se-armbian If anyone is interested I can share a test image ready to be flashed or you can (and should) build it yourselves. I plan to add a Home Assistant flavor to the build system in the future.

Yes, the device is working now. Check the forum manjaro, they put kernel from sunxi and working now.

@jock Is it possible to dump BOOTROM from Linux, or is it hidden/shadowed by ATF ? There is RK3399 dumper code at github, so i am wondering if the same can be done on RK3528.

Note: This is for Odroid m1s, not Odroid m1 - there just isn't a forum for the m1s (yet?) When I tried to start the board with the community image for the Odroid m1s on a SD card, it wouldn't boot. The connected screen (HDMI) would stay black and the blue heartbeat LED would stay on permanently. I tried building and flashing u-boot but that didn't help me. Here's what DID work: (Note: it worked for me. I can't guarantee that this fixes it for everyone, use at your own risk) I mounted the SD card on a Linux desktop and created backups of the boot scripts (just to be safe) sudo cp <mount_path>/armbi_root/boot/boot.cmd <mount_path>/armbi_root/boot/boot.cmd.bak sudo cp <mount_path>/armbi_root/boot/boot.scr <mount_path>/armbi_root/boot/boot.scr.bak Then I set the load address to 0x0c000000 sudo sed -i 's/setenv load_addr "0x9000000"/setenv load_addr "0x0c000000"/' <mount_path>/armbi_root/boot/boot.cmd Then I ran mkimage as follows: sudo /usr/bin/mkimage -C none -A arm -T script -d <mount_path>/armbi_root/boot/boot.cmd <mount_path>/armbi_root/boot/boot.scr This fixed the booting, but just to be sure a future update wouldn't undo it I also wrote it to armbianEnv.txt echo "load_addr=0x0c000000" | sudo tee -a <mount_path>/armbi_root/boot/armbianEnv.txt And that's it! One more thing: I noticed that Ethernet did not work out of the box, so I did this: I attached a UART cable to log into the machine and created the following script, which patches the device tree. You might need to get a little creative if your only access would be through Ethernet, but you I'm sure you can figure something out. (Maybe create the necessary files while the SD card is still mounted on your PC) cat > /usr/local/sbin/patch-gmac-dtb.sh << 'EOF' #!/bin/bash DTB=/boot/dtb/rockchip/rk3566-odroid-m1s.dtb dtc -I dtb -O dts $DTB -o /tmp/m1s.dts 2>/dev/null # Only patch if not already applied if grep -q 'snps,reset-gpio' /tmp/m1s.dts; then echo "GMAC DTB patch already present, skipping" exit 0 fi sed -i '/phy-mode = "rgmii-id";/a \\t\tsnps,reset-gpio = <0x51 0x0f 0x01>;\n\t\tsnps,reset-active-low;\n\t\tsnps,reset-delays-us = <0x00 0x4e20 0x186a0>;' /tmp/m1s.dts sed -i '/reset-assert-us/d; /reset-deassert-us/d; /reset-gpios = <0x51/d' /tmp/m1s.dts dtc -I dts -O dtb /tmp/m1s.dts -o $DTB 2>/dev/null echo "GMAC DTB patch applied" EOF chmod +x /usr/local/sbin/patch-gmac-dtb.sh Execute the script and Ethernet should be working. (Might need a reboot, though). If this works, you should make sure this is applied after every kernel update, because it will get overwritten otherwise: # Run it automatically after kernel/dtb package updates cat > /etc/apt/apt.conf.d/99-patch-gmac-dtb << 'EOF' DPkg::Post-Invoke {"if [ -f /usr/local/sbin/patch-gmac-dtb.sh ]; then /usr/local/sbin/patch-gmac-dtb.sh; fi"}; EOF

Thank you! I ended up getting this working. For one, an update and reboot did get me the 6.18.10 kernel. Then, in the installation scripts for drivers, I just had to specify the package name for the headers explicitly, e.g. replacing: apt-get install linux-headers-$(uname -r) -y with apt-get install linux-headers-current-bcm2711 -y

I am using a Rock 5T 12GB board and have tested multiple Armbian images (24.04, 26.04, and others). Here is my experience so far: Armbian current images Audio does not work at all. When I plug in a 3.5 mm headset, nothing happens — no detection, no sound. Bluetooth works, Wi‑Fi does not. I have to manually compile the Realtek rtw89 wireless driver. After compiling, both Wi‑Fi and Bluetooth work, but still no audio output. Vendor (Radxa) images Audio works perfectly. When I plug in a headset, the system immediately detects it and asks whether it has a microphone. Sound output through the headset works as expected. However, with the vendor image I cannot use Bluetooth and Wi‑Fi at the same time. According to what I found online, the RTL8852BU chip shares internal resources. I must disable Wi‑Fi to use a Bluetooth mouse and keyboard reliably. Connecting a Bluetooth headset causes an immediate disconnect. Feedback from Radxa Radxa confirmed that the Bluetooth/Wi‑Fi coexistence issue is caused by the driver. Summary At the moment, I cannot use either the current Armbian images or the vendor images without running into major problems: Armbian: Wi‑Fi/Bluetooth OK (after manual driver build), but no audio. Vendor image: Audio OK, but Bluetooth and Wi‑Fi cannot work simultaneously. Is this a known issue, and am I the only one experiencing these problems? Thanks a lot for your support and help.

The one from my firmware build.

Solved it by simply removing the upstream folder which had some symlink tomfolery 1. rm -rf /lib/firmware/qcom/sm8550/ayn/ 2. apt update && apt upgrade 3. PROFIT <3

SOLVED by enable on BIOS

Hi everyone, I’m working on an RK3568-based platform (Yocto build, Rockchip BSP) and I’ve reached a blocker regarding OP-TEE / Trusted Application (TA) development. Anyone knows how to get RK3568 + Linux + OP-TEE source/build path Rockchip vendor SDK with RK3568 OP-TEE source a repo showing rk3568 + optee_os + TA dev kit for

@ssdm2nvme Hi, whats up? I tried everything you recommended, including following some other tutorials beforehand, but I still can't get past the TV box's "BIOS" screen. It keeps restarting repeatedly, and I can never actually access the system. Do you have any idea what it could be?

guess it kernel/driver issue The driver does not request the stmmaceth (emac1-25M) clock during probe. Without this clock the MDIO bus does not function on cold boot - PHY ID reads as 0x00000000 and kernel falls back to Generic PHY instead of YT8531. Ethernet does not work until warm reboot.

I've just installed Ubuntu KDE vendor image and now the proper refresh rates are detected. Thank you However, now it seems video players are not working properly. No HW decoding and no audio. It works if I play youtube videos through via Chrome though Strange thing is that after the clean installation, lots of basic KDE packages were missing (dolphin, Konsole, mpv, etc), which I had to install via apt. After that I also performed a apt full-upgrade, but it didnt solve the problem Tried to play h264 and 265 with no success I add some logs, but feel free to request more if they may help

I have a Orange Pi Zero 3 4GB Board. It uses a Micron LPDDR4X RAM and H618 Processor. I have tried a plethora of distros and tried to change Uboot and DTB but unable to make it work. Spent days on Gemini and Claude but no luck. Below is the output from UART debuggger: The Highlight being Unhandled Exception EL3. U-Boot SPL 2025.04-armbian-2025.04-S3482-Pf089-H8869-V3d5b-Bb703-R448a-dirty (May 25 2025 - 14:46:18 +0000) DRAM base address is defined as 0x40000000 DRAM has 16 b/raw, 10 b/col, 4 B/width, 2 #rank and 8 #bank DRAM top address must be less than 0x100000000 DRAM: 4096 MiB Trying to boot from MMC1 Unhandled Exception in EL3. uart_opizero3.txt

I think most important is that people make sure they can fix their own issues if a HW/computer fails. I found high-availability interesting, but for just my house (or even 2 places/countries at the same time) I found it too much to make it all work. The thing I could maybe use is DRDB, however I see v9 is under development since 2011 and it still is not in mainline kernel. Compared to that I have some script to transfer latest differential Btrfs snapshot from 1 computer to the other on-the-fly, I doubt I can really benefit from DRDB, but maybe I set up a test and see what it does. I use only ARM64 for 24/7 servers, so no x86_64 <=> ARM64 incompatibility. So same as for ZFS for example, it is external to Linux distro and my experience is that complicated issues/failures always happen at the wrong moment, e.g. also no internet and/or mains power failure etc. So I try to minimize the amount of 'external' HW/SW modules, certainly if the backing company is commercial and in whatever country far away from where I am. Proxmox is nice, but also 'external'. Same for even Docker, so I have actually no such containers. But it all depends on how much you are involved in various HW and SW. As you can see in my earlier message, I already forgot HA was available as generic aarch64 image, so that says enough. I use several custom (own) HW (like 'changed' solar inverter) and HomeAssistent does not support it, so I actually do not really use it. It is mostly C-code and Node-RED in conjunction with various micro-controllers. A good test is to disconnect internet (power-off fiber-RJ45 box in my case) and/or also do an ad-hoc power cut (no cheating with UPS). And then see if you can get it all running again within a certain time frame (what you think is acceptable, like before temperature in freezer gets > -10 or so).

@humanus You are a very nice guy!

Hi team, I am on the latest vendor release of gnome installed via armbian installer. Kernel is linux-image-6.1.115-*-rk2410. When I look for audio drivers I do not see card 3: rockchiphdmiin [rockchip,hdmiin], device 0: fddf8000.i2s-dummy_codec hdmiin-dc-0 [fddf8000.i2s-dummy_codec hdmiin-dc-0] Subdevices: 1/1 Subdevice #0: subdevice #0 I got the board very recently and the forum is a little mesay about the hdmi rx functionality. It would be a great help if anyone can help me out on this, let me know if i am missing anything.

Hi @Tavares R You should definetly check the "Media framework installer v0.1" by Jock, on this link -> https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/10/#comment-102655 Also, this other link contains a repo to install some patched libs to at least use decoded video -> https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ Hope it helps, but reality check is the rk3229 is just too weak to properly handle a full DE running a modern browser... Something also worth trying is to enable the "cpu-hs" overlay. it will "overclock" the rk3229 from 1200Mhz to 1400Mhz, giving some extra performance, but keep low expectations... PS: Are you brazillian by any means? Tavares is a very common last name in Brazil.