Active threads

Hey Paul - Once this gets merged it's going to be fixed, thanks for the report! https://github.com/armbian/build/pull/9349/ Best, Andrei

I think I've completed all tasks. Thus the OpiRV2 PR now waits for a team member to press the [merge] button probably. @maxsub I compiled 6.6.99 kernel on my board with 2Gb RAM once. Needed 3 hours and a decent swap file. HTH // Sven-Ola

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?

There's no armbian community image available to this device, don't flash images from other users, you will need to build your images, for tv-box it's all at your own risk, build your armbian image by applying this custom files use this DTS

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

It's this image from @Nick A github. Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img I had to copy over a few firmware files to get wifi/bluetooth working but otherwise it's unchanged.

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.

Hi, i think the rpm setting-step's of the onboard fan is to low. - how can this be adjusted? SBC: Rock5b

If there is anyone still running an older version of the kernel and the USB-C is working it would be helpful if I can get a copy of your rk3588s-odroid-m2.dtb.

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.

etcher did decompess before flash to the SD card

Hi @Anto, Igor has built that version if you look in his post above: https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15377&key=f234d69d5a19f0081fdad46abb21cc36

Version 3 Has been released! Complete UI Overhaul The entire user interface has been rebuilt from the ground up using Qt QML, delivering a modern automotive HMI experience optimized for touchscreen displays. New Home Screen - Large centered clock with configurable 12-hour/24-hour format - Gradient background (#00021A → #001D3F) - Swipe navigation to media player - Clean, minimal design with Readex Pro typography New Bottom Navigation Dock - 5-button dock: Home | Music | Android Auto | Volume | Settings - Always visible for quick access (except when running AA) - Icon-based navigation with visual feedback New Music Player - Album art display with track metadata - Playback controls (Previous, Play/Pause, Next) - Integrated with system media Redesigned Settings - Modern two-column layout with left sidebar navigation - 8 categories: General, Video, Audio, Input, Bluetooth, WiFi, System, About - Toggle switches, sliders, and radio buttons - Real-time system info (CPU temp, memory, frequency) - Live date/time display in header New Features - 12/24-Hour Time Toggle: Switch between time formats in Settings → General - Readex Pro Font: Variable weight font for consistent automotive typography - Modernized UI: The Original Crankshaft-NG was just not suitable for car use so i had to refresh it Technical Changes - Qt Widgets → QML Migration — Complete rewrite of UI layer - UIBackend Bridge — New C++ backend class exposing 50+ properties to QML - EGLFS Optimized — Designed for direct framebuffer rendering - No Animations — Instant transitions for 1GB RAM constraint - Centralized Theming — Theme.qml singleton for consistent styling Removed - GPIO settings (not applicable to TV Boxes) - DAC settings (using ALSA directly) - RTC settings (no CMOS battery, NTP only) - TSL2561 light sensor support (Pi-specific) - Camera module settings (Pi-specific) Bug Fixes - Fixed Cursor issue by utilizing Cursor plane (41, z-pos 2) - Fixed std::mutex missing include in RtAudioOutput - Fixed ColorOverlay import for Qt GraphicalEffects - Fixed time display showing 24hr with AM/PM suffix - Fixed buffer overflow warning in FFmpegDrmVideoOutput - Fixed QCursor conversion error in autoapp.cpp Known Issues: - Music player metadata not populated (requires media service integration, will be done in the next patch) - Volume popup not implemented (this require modifying the asound.conf before implementing) Issues? Open a ticket in https://github.com/Harleythetech/openauto-rk3229-armbian/issues Download https://github.com/Harleythetech/openauto-rk3229-armbian/releases/tag/oark322x-V3.0.0-alpha

Some context: https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working The hardest part and expensive for time is keeping functions working while kernel changes, goes up. Image you are referring too is probably a demo image with some ancient kernel that will never be changed. This is usual way to sell hardware. It is made to work, but you will stay at this very old SW stack without any real option to change or fix anything. All functions on 300+ boards, which on top of extreme diversity, have also different revisions, quality issue ... is already not possible to keep up by entire open source community. Armbian is small part focused into SBCs and we do what we can. Work we are doing is never complete, we (nobody) can't solve bugs and especially not near to (expected) real-time. We (or community open source in total) can address a problem within weeks or months fastest as resources are tiny compared to problems that are constantly found in open source code that somebody else made. We have no option to expand the team / project as users don't care about well being of SW developers. We can only try to keep SW stack operational on a best effort principle. Once this job becomes too expensive (<1% of costs share is on users side), we have to step back and declare support as "community". We will continue to build and ship images as they might still work for some use cases and as downstream projects will provide those Armbian images anyway.

A month ago when doing test boots and power measurements, see I discovered that when using the RPL 27W 'Pi5' PSU, the NanoPi-R6C with the indicated bootloader(s) and kernel(s) sticks to 5V. But when using a 45W USB-C PD PSU from a HP laptop or 60W USB-C PD PSU white-label, switch is made I saw on a USB-C PD power measurement device that was also in the chain. More detailed USB-C PD protocol analysis seems to be needed in order to figure out what happens. One could guess 3A is requested at highest possible voltage as with the 45W PSU, I saw 15V. 9V or 12V would also be OK, but the PD handler cannot be 100% sure I think, depends also what is inserted in USB type-A ports on device etc.

does emmc working yet?

armbianmonitor - u result: https://paste.armbian.com/nocetohemu Best regards Rolf