Active threads

The patch brought the idle load average drastically down on the R2S from 2.0 to 0.18. However the temp remains at 57-58 deg C. orangepi@orangepir2s:~$ cat /sys/class/thermal/thermal_zone1/temp 56000 orangepi@orangepir2s:~$ htop orangepi@orangepir2s:~$ cat /sys/class/thermal/thermal_zone1/temp 57000

I think the onboard fan is not being controlled correctly. root@rock5b01:~# dmesg | grep -i fan [ 6.577344] pwm-fan pwm-fan: Looking up fan-supply from device tree [ 6.577352] pwm-fan pwm-fan: Looking up fan-supply property in node /pwm-fan failed [ 6.581563] thermal_sys: Failed to bind 'soc-thermal' with 'pwm-fan': -22 [ 6.581571] thermal_sys: Failed to bind 'soc-thermal' with 'pwm-fan': -22 [ 6.581574] thermal_sys: Failed to bind 'soc-thermal' with 'pwm-fan': -22 [ 6.581577] thermal_sys: Failed to bind 'soc-thermal' with 'pwm-fan': -22 Running: Armbian v25.11.2 for Rock 5B running Armbian Linux 6.1.115-vendor-rk35xx

@210518-nick-a Thanks for the reply. I don’t have enough Linux knowledge, so should I just wait for your new release? My box isn’t an X96Q — it’s a generic no-name one — but after trying many, many images, I found that the version you compiled happens to work perfectly and runs smoothly. So far I haven’t found any issues (the only thing missing is Wi-Fi, but that’s not a problem with your build: SV6256P). Even other images made for X96Q LPDDR3 by different people have all kinds of problems. Another small issue: your current compilation option is fully preemptive scheduling. This option is not suitable for server use. I suggest changing it to voluntary preemption or non-preemptive, thank you. The option of your images: CONFIG_PREEMPT_BUILD=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y # CONFIG_PREEMPT_RT is not set CONFIG_PREEMPT_COUNT=y CONFIG_PREEMPTION=y # CONFIG_PREEMPT_DYNAMIC is not set # CONFIG_SCHED_CORE is not set # CONFIG_SCHED_CLASS_EXT is not set

Hi everyone, I have a Multilaser tablet with the Allwinner A50 chip and I wanted to compile a DTB file for it, so I could boot Armbian, but I haven't found anything on the internet about PIN MAP or anyone who has worked with this chip. Also, it already has an unlocked bootloader. I really wanted to do a project with this tablet, as I'm a student at the Federal Institute and it would be a great project!

What I have already tested: UEFI x86 KDE Neon, Gnome, Ubuntu minimal MusePI Pro Xfce Odroid M1 KDE Neon Orangepi 5

I managed to get some USB-C functionality back by adding a device tree overlay. cat odroid-usbc-fix.dts /dts-v1/; /plugin/; /* 1. Force the USB controller into Host mode */ &{/usb@fc000000} { dr_mode = "host"; status = "okay"; /delete-property/ usb-role-switch; /delete-node/ port; }; /* 2. Target the specific USB3 Type-C regulator by its absolute path */ &{/regulator-5v0-vcc-usb3-typec} { regulator-always-on; regulator-boot-on; status = "okay"; }; /* 3. Target the USB3 Host regulator by its absolute path */ &{/regulator-5v0-vcc-usb3-host} { regulator-always-on; regulator-boot-on; status = "okay"; }; However this disables OTG and devices with strict udev switching timing requirements fail to switch. So my QHY CCD camera is correctly detected as a westbridge device and udev / fxload commences loading the firmware but the power to the device is toggled and the firmware load fails as a result. If I plug the QHY CCD in to the USB-C port via a powered USB-C hub then everything works fine. This works because the HUB is providing constant power. So there appears to be a lot of difference between the Radxa USB-C and Odroid USB-C implementation that will need someone better at kernel stuff than me.

Just a feedback. Device: Orange Pi 5 Plus OS Image: Armbian_26.2.0-trunk.370_Orangepi5-plus_noble_current_6.18.8_gnome_desktop.img.xz media-player: mpv-.37.0-1ubuntu4 Following the gudide on the first page and added "profile=fast" (in order to have smooth 4K/60 playback) in /etc/mpv/mpv.conf. mpv-.37.0-1ubuntu4 playback 8bit 4K/60 h264 and h265 (hevc) video with vpu hardware accceleration. 10bit h265 or any vp9 and av1 video NO vpu hardware acceleration as far as I can tell. 10bit 4k/60 hevc video -- No vpu hw acceleration 4K/60 hevc -- with vpu hw acceleration. Error messages. Full HD av1 -- No vpu hw acceleration Full HD vp9 -- No vpu hw acceleration Edit: Chromium_v144 can play 8bit 4K/60 h264, h265 and av1 videos with vpu hw acceleration. No vpu hw acceleration with vp9 videos. If not mistaken the current kernel-6.18.8-current-rockchip64 or 6.19-rc8-edge-rockchip64 do not support vpu hw acceleration with vp9 codec.

Hello - if someone get this type of TV Box from ebay (10€ ) - and dont have an GoogleAccount or do not want use the ADB way. The switch is located in one corner but not soldered. Use a small cable to put GND from end of arrow where the pointing of arrow in picture - to do the reset - (during restart just hold some seconds and device did start from SD-Card -) This device also features a RX/TX -Console and Jtag Interface - you find it if you take closer look.

Build dropped today with NVME and WiFi support for a5e: https://www.armbian.com/radxa-cubie-a5e/

Hi Andrei, That's perfect, thank you for getting to this so promptly. Kind Regards, Paul

So, a little update from my side for whoever is interested in this (and again, thanks for reading). Been playing with the box 2-3 evenings every week since my last post and still impressed by it (considering what I plan to use it for), yet not there where it should be yet. Bookworm (some various archive images I found online) works fine, and I can install OMV via armbian config, although performance is bad and I’m talking here about applying changes using the UI - like it takes whole minutes, plus some expected issues for the 2.5g interface. Trixie, all good installing, OMV fails from armbian config but works fine via the OMV installation guide from their site, it’s snappy in applying changes, like not instant but just a few seconds. The 2.5g interface is still an issue and while I can get good results on writing to the box after trying various fixes found online (like a 4gb file write is just fine, the interface crashes and I lose connection while copying from it back to my pc). This doesn’t crash the device completely, still works fine on the 1g interface, and accessible, so from my point of view is more of a perf issue than a stability one. Overall, still happy having this box, but man you do spend a lot of time getting things right, an obviously I’m a newbie. Thanks for watching! (Just for clarity, my 1g interface is connected to my 1g router, and the 2.5 one directly to my desktop to a 2.5 usb network card, and this set up was working fine on buster)

Hi all, I was able to make my H96 MAX M9S running on armbian (beta) Linux 6.19.0-rc8-edge-rockchip64. Using: - armbian u-boot, installed by armbian-config - root fs on emmc Working: - both USB ports - HDMI (audio+video) - Ethernet port - Wifi using aic8800 DKMS drivers provided by https://github.com/radxa-pkg/aic8800/releases - Leds Not working: - GPU/NPU - Bluetooth - any HW acceleration - many other things as in attached dmesg Known issues: - no USB port is working in usb3 mode (5000M) - missing hci port for Bluetooth - driver aic8800_btlpm_sdio hast to be loaded manually - other as in attached dmesg Attached you can find: - my working dts for armbian Linux 6.19.0-rc8-edge-rockchip64 - my original dts extracted from the box - dmesg Hope some will be able to help with other things rk3576-evb1-v10-main-h96-v3.dts rk3576-evb1-v10_org.dts dmesg.txt

If anyone is still interested, I have one that I assembled, looked at but never got around to using. No idea what to ask for it but it certainly isn't doing me any good. Have the manual, SATA drive bay adapters for 2.5" drives and the like. Make me an offer and pay shipping from Oregon. Let's talk!

Oh so I stand corrected... I was going from information on the website: I don't see a Linux client, and in other sites: emby was open source but now it's not

Edit the makefile: # keypad support CONFIG += CONFIG_TM16XX_KEYPAD=n #CCFLAGS += -DCONFIG_TM16XX_KEYPAD

Hi there! I got a QNAP TS-228A with RTD1295 and 1GB of memory. I was playing around with the mainline kernel and trying to figure out the correct DTS for this NAS. I managed to boot up my with one working USB from the back, everything looks fine but I feel like the CPU is running with low frequency. The logs clearly shows that the boot is very slow, it takes long minutes for SystemD to start up it's services. The setup is one USB drive with Arch Linux rootfs tarball with custom compiled kernel with options like CONFIG_ARCH_REALTEK or CONFIG_F2FS_FS_ZSTD. Unfortunately Arch's kernel misses this target. Is it worth to spend more time with this device? Were any of us able to setup the Gbit ethernet and SATA interfaces? I can see there are many related repo's with usable dts or drivers. I think most of the driver are available we just need to adjust the device tree according to that. I saw the SMP implementation is also somewhat problematic with the spin table, psci solution. [ 19.016897] VFS: Mounted root (f2fs filesystem) readonly on device 8:2. [ 19.027405] devtmpfs: mounted [ 19.032713] Freeing unused kernel memory: 3264K [ 19.037576] Run /sbin/init as init process [ 19.528716] systemd[1]: System time advanced to built-in epoch: Wed 2026-01-07 19:31:44 UTC [ 80.887403] systemd[1]: systemd 259-2-arch running in system mode (+PAM +AUDIT -SELINUX +APPARMOR -IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +E) [ 80.921626] systemd[1]: Detected architecture arm64. [ 111.625814] systemd[1]: Initializing machine ID from random generator. [ 111.632867] systemd[1]: Installed transient '/etc/machine-id' file. [ 111.641073] systemd[1]: Hostname set to <alarm>. [ 142.877742] systemd[1]: bpf-restrict-fs: BPF LSM hook not enabled in the kernel, BPF LSM not supported. [ 176.038563] systemd[1]: Queued start job for default target Graphical Interface. [ 177.884307] systemd[1]: Created slice Slice /system/dirmngr. [ 209.925527] systemd[1]: Created slice Slice /system/getty. [ 240.645593] systemd[1]: Created slice Slice /system/gpg-agent. [ 271.365518] systemd[1]: Created slice Slice /system/gpg-agent-browser. [ 302.085600] systemd[1]: Created slice Slice /system/gpg-agent-extra. [ 332.805493] systemd[1]: Created slice Slice /system/gpg-agent-ssh. [ 363.525552] systemd[1]: Created slice Slice /system/keyboxd. [ 394.245551] systemd[1]: Created slice Slice /system/modprobe. [ 424.965578] systemd[1]: Created slice Slice /system/serial-getty. [ 455.684357] systemd[1]: Created slice User and Session Slice. [ 486.391860] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 517.111666] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 547.831552] systemd[1]: Arbitrary Executable File Formats File System Automount Point was skipped because of an unmet condition check (ConditionPathExists=/proc/sys/fs/b. [ 547.848314] systemd[1]: Expecting device /dev/ttyS0... [ 578.551439] systemd[1]: Reached target Local Encrypted Volumes. [ 609.271487] systemd[1]: Reached target Image Downloads. [ 639.991487] systemd[1]: Reached target Local Integrity Protected Volumes. [ 670.711612] systemd[1]: Reached target Path Units. [ 701.431485] systemd[1]: Reached target Remote File Systems. [ 732.151447] systemd[1]: Reached target Slice Units. [ 762.871556] systemd[1]: Reached target Swaps. [ 793.591527] systemd[1]: Reached target Local Verity Protected Volumes. [ 824.311963] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 855.041446] systemd[1]: Listening on Query the User Interactively for a Password. [ 885.761590] systemd[1]: Listening on Process Core Dump Socket. [ 916.477769] systemd[1]: Listening on Credential Encryption/Decryption. [ 947.201487] systemd[1]: Listening on Factory Reset Management. [ 977.912008] systemd[1]: Listening on Journal Socket (/dev/log). [ 1008.631975] systemd[1]: Listening on Journal Sockets. [ 1039.361885] systemd[1]: Listening on Console Output Muting Service Socket.

Hi, @Harleyyyu, thanks for the copy of multitool. Sadly it behaves just like before. When turning on with the SD card inserted I only get a red LED. I saw some people saying they had luck booting from LibreELEC, but I get the exact same behavior. I do want to keep a backup of my current OS. Any next steps for debugging it? Maybe it needs a shittier SD Card?

You need to clear the EMMC and flash the bootloader an easy way to do it, just flash the android update image, it will flash the bootloader. if you are making experiments with this board use this bootloader

Hi Armbian community I have a Giada DN74 media player and would like to install Armbian on the box. First I try (through SD card) some community maintained images like the Orange Pi RK3399 or the Firefly RK3399, but none of them worked. Some google search teach me the Rockchip SoCs have fixed boot order (SPI->eMMC->SD card), and this cause my boot issue. Then search again how boot from SD card, the only solution which I find is to erase eMMC, so I erase the eMMC using: "rkdeveloptool ef". Unfortunately the box still not want to boot, so I open the box and try to identify the UART to see what is happening during the boot. I find a 4 pin connector (see images) which I assume this is the UART console, have a label "MCU_D" (Micro Controller Units Debug?) and have 3,3V on first pin and GND on the last pin. I try to use this connector whit some USB-to-UART (PL2303 and FT232RL) with multiple baud rate (115200, 1500000) without output. At this point was able still connect the box through USB and recover Android because MaskRom mode work fine. After some reading on https://opensource.rock-chips.com/wiki_Boot_option I deiced to build u-boot using evb-rk3399_defconfig and flash to the eMMC (which wan was a big mistake). I assume the box is try to boot from eMMC, but stuck there because is only u-boot on the eMMC nothing else. Unfortunately still no UART output (maybe is not UART connector) but also no Maskrom mode. If I understand right jock guide Unbrick Part, the only option to recover the box if I short EMMC CLK pin to GND. So my question is somebody could help me identify the eMMC CLK pin? Some extra info: According the rk3399 hardware design guide, I need to find a 22 ohm resistor near to the CLK pin. The eMMC is a Kingstone EMMC32G-TX29, and the manual write different CLK frequency's, I am don't know what I need to look. I have a Fnirsi dst-210 3in1 (sure not the best), which I could use measurements but I do not know how to set the oscilloscope parameters to find the CLK.

Hi if anyone have interested, this is dtb files and orangepienv file 🙂 allwinner.zip

Hi Gaetano, Maybe the issue is with g_mass_storage rather than OTG USB? "The "dr_mode" property controls whether OTG acts a peripheral or host. By default this is set to OTG mode so you shouldn't need to change anything. In my case I prefer to have OTG set as host for which I have this simple overlay: dts-v1/; /plugin/; /{ compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20"; fragment@0{ target = <&usb_otg>; __overlay__{ dr_mode = "host"; }; }; }; I find it works ok for reading a USB stick. It could be that you have to instead change dr_mode = "peripheral" but seeing as it shows up as a drive this may not be necessary. What kernel version are you currently? Are there any errors that show up in the logs? sudo dmesg | tail -n 20 There is also usb_f_mass_storage however this would need to be manually added as it is not currently included by default within the list of installed modules (Well at least was not on the last build I ran) Best of luck Ryzer

can confirm: I installed the latest image `Armbian_25.11.1_Radxa-dragon-q6a_noble_edge_6.18.0-rc6_minimal.img` and wifi works. After an `apt upgrade` wifi doesnt work anymore... Solution: same as on the Rock 5C @just_facking_about type in `sudo dpkg-reconfigure aic8800-usb-dkms` and reboot the device

I would first check the link, what is on the other side, etc. Also do a flood ping with large enough packages. Or UDP flood, not sure how to do that. Iperf3 might be easier. I have no clue about Radxa OS, never really used it. Maybe also do test boot with mainline based kernel, 6.19 edge I think. And what U-Boot version is used. I use Tianocore EDK2 UEFI v1.1, that might also have effect.

https://github.com/armbian/os/pull/426 Once automation finishes - couple of hours, repo will have a missing package. Workaround: manually install package from https://packages.debian.org/forky/zfs-zed

Headers are present. https://imola.armbian.com/apt/pool/main/l/linux-headers-current-rockchip64/ Upgrade packages to latest and try again.