All Activity

SOLD

I found the error, don't do it again.

Probably never will until roll-over to next LTS version. We don't have people to maintain this.

You can switch to an edge kernel using armbian-config. You can install the stable edge or switch to the rolling releases and install the rolling edge. Stable edge is at 6.16.4 and should work just fine.

Even with the new version,I am still running into the same error dmesg.multitool.log

HDMI audio support was introduced in kernel version 6.15-rc1, but has yet to be backported to the Long-Term Support version. The absent audio functionality is currently the only notable issue affecting the overall user desktop experience.

I also purchased this MXQ Pro 4K 5G TV box but I'm not sure if it's rk3128 or rk322x, how do I know for sure? the host name print rk322x but cpuinfo print rk3128: rk322x_box:/ # getprop ro.hardware ro.hardware.chipname rk30board rk322x_box:/ # cat /proc/cpuinfo Processor : ARMv7 Processor rev 5 (v7l) processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Rockchip RK3128 Revision : 0000 Serial : b57642ed91a64924

Recommendation: Switch to the edge kernel (eMMC drive access + better performance + more complete kernel features) I just tried out that Armbian Noble image with the vendor kernel. I noticed the eMMC drive didn't show up. Also the user interface seemed a bit sluggish. I normally use the edge kernel, it's far more complete than the vender kernel. I tried that here, and the eMMC drive appeared, and also the user interface become much smoother. You can use armbian-config to switch to the latest edge kernel (6.16.4).

Additional Tip: The sync command: Btw - an additional tip, whenever you're copying files or images, it's a good idea to finish it off with the sync command. When using cp or dd, the prompt returns when the CPU portion of the copying is done, but that doesn't necessarily mean that the final data buffer has finished transferring its data to the drive or device. The sync command holds and only returns the prompt once the buffer has finished copying to the drive or device. Note that if you're copying a batch of files, the sync command will return only when the current file has finished, not necessarily the entire batch.

"if you have ever booted a different distribution then your box will be incompatible with the Armbian build" are you serious? No matter after all this linux on arm shit problems i had last week, i really must say that a windows 10 + kodi.exe on a thin client is really the best in quality (dxva) and stability. And it only eats 1-2w more power than this u1 thingie. So, i just keep my moonlight on windows and put tvheadend together with the wintv solohd into a vmware player. bye bye.

Great!! I'm glad you got it working!

SteeMan - OK - so as a total non-developer, I will steer clear of 'mainline kernels (at least until I can learn some more😀 TallMan - I only wish everyone online was as helpful as you have been. I actually got the thing to work using your instructions, which is a first for me using online 'help'. I no longer have a useless brick. I have a red/blue flashing LED, a working desktop, and (now) a need to learn something about Armbian - this being my first sight of it. Some of it looks familiar from Mint due to the Debian heritage I also want to learn how to make the OPi boot from either the EMMC or the SDD, as I understand this is much faster - although it works, booting from the SD card clearly doesn't do justice to the OPi hardware (and life is too short😀. Thanks to all who responded - you all helped. Keith

You should also be updating your /etc/apt/sources.list.d/armbian.list as well (otherwise you will be mixing bookworm armbian packages with trixie debian packages)

First off, why do you want to? As the name 'edge' should imply, edge kernels are development kernels that are for testing purposes and may or may not work, and may break at any time. 'current' 6.12 in your case are LTS kernels that should be stable and more suited for non-development/testing use cases. If you do want edge kernels then you can use armbian-config to switch.

Lack of feature implementation, not a bug. 6.1 is the vendor supplied kernel where most things will work, but the vendor doesn't provide support. 6.12 is linux mainline kernel, where much functionality may be missing (as the vendor doesn't work to get their features into mainline linux, but relies on others (volunteer opensource developers) to do their work for them).

Per the install instructions on this site, if you have ever booted a different distribution then your box will be incompatible with the Armbian build. Although it is generally using coreelec builds that will do this. I don't know about the libreelec builds. Also you need to provide a lot more information about what you are doing. There are a number of steps in installing armbian on a TV box and you haven't specified any of the steps you performed. Finally debugging boot issues often requires that you find the debug serial console connection on the board and hook up a usb uart reader to get at the boot messages.

I recently updated from bookworm to trixie, here's how i did it: commands: sudo apt update sudo apt upgrade -y sudo cp -p /etc/apt/sources.list /etc/apt/sources.list.bak sudo sed -i 's,bookworm,trixie,g' /etc/apt/sources.list sudo cp -p /etc/apt/sources.list.d/armbian.list /etc/apt/sources.list.d/armbian.list.bak sudo sed -i 's,bookworm,trixie,g' /etc/apt/sources.list.d/armbian.list sudo apt dist-upgrade /etc/apt/sources.list : deb http://deb.debian.org/debian trixie main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian trixie main contrib non-free non-free-firmware deb http://deb.debian.org/debian trixie-updates main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian trixie-updates main contrib non-free non-free-firmware deb http://deb.debian.org/debian trixie-backports main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian trixie-backports main contrib non-free non-free-firmware deb http://security.debian.org/ trixie-security main contrib non-free non-free-firmware # deb-src http://security.debian.org/ trixie-security main contrib non-free non-free-firmware /etc/apt/sources.list.d/armbian.list: deb [signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com trixie main trixie-utils trixie-desktop

How do install armbian in my TX98 TV BOX Processor:Allwinner H313 I bought it on tiktok shop

My setup is still running, yay! I even updated to Trixie and all worked out fine. But I'm stuck on edge kernel 6.12.x, I saw that rolling had 6.16.x. So how do I install/convert to the rolling 6.16.x edge kernel ?

Thanks again for the inputs - I'm slowly working through the instructions, and hopefully learning. TallMan is right - I meant 1 TB, not 1 GB - (it was tiring day!) I'm not really bothered at this stage with which OS Image I use - My original intention was to get the thing going, then eventually try each available OS until I found something I could live with. Normally I use Linux Mint on my desktop computer (user - not nerd!), so this was why Ubuntu came to the top of the pile for testing because of the common Debian background, but not necessarily as the 'finished' job. I more or less did as suggested above (using the Orange Ubuntu 'Official' download. As noted, I seem to have had a dead SD card, and did not have the error reported after validation after I got a new card - but the odd thing now is that although the old 'faulty' SD card at least produced a 'splash' screen, the new card does nothing - the OPi just does a good imitation of a warm brick. I did the SHA check, and the Etcher validation was OK, so presumably the burnt image was OK (?). I'll work through Tall Mans instructions, and see what happens, and report back - thanks for the detailed description - its more useful than many people realise to someone who doesn't do this sort of thing every day. Just out of curiosity - is the 'no-video output' of Armbian 6.12 a bug (as I suspect) or deliberate - and if so why? Thanks again for the help. Keith

To maintain changes between different kernel versions, you can use overlays. I did this by following some dts changes from @ebin-dev. Add this line user_overlays=rockchip-rk3399-op1-opp rockchip-rk3399-l2-cache to /boot/armbianEnv.txt Copy the dtbo files to /boot/overlay-user (mkdir -p /boot/overlay-user if the folder does not exist). rockchip-rk3399-l2-cache.dtborockchip-rk3399-op1-opp.dtborockchip-rk3399-op1-opp.dtsrockchip-rk3399-l2-cache.dts

@ebin-dev not sure with your cpufreq settings as it should be 40000 otherwise the regulator cannot ramp-up the voltage so quickly. regulator@40 { compatible = "silergy,syr827"; reg = <0x40>; fcs,suspend-voltage-selector = <0x01>; pinctrl-names = "default"; pinctrl-0 = <0x83>; regulator-name = "vdd_cpu_b"; regulator-min-microvolt = <0xadf34>; regulator-max-microvolt = <0x16e360>; regulator-ramp-delay = <0x9c40>; regulator-always-on; regulator-boot-on; vin-supply = <0x82>; phandle = <0x0e>; regulator-state-mem { regulator-off-in-suspend; }; }; I have been using Helios64 for few years without any issues (four years ago, when I detected instability, I disabled the a72 cluster and continue only with updates, without any problems). Now that I have upgraded my network to 10 Gbits, I am experiencing problems with the 2.5 Gbits network card, which I did not use previously (link https://forum.armbian.com/topic/43858-helios-64-network-issues-with-armbian-2453-on-kernel-6639-frequent-disconnects/#findComment-225220 ). My theory is that the instability also affects USB 3.0 and RTL8156, causing crashes and triggering the watchdog. I also tried connecting an active switch to type C with an external RTL8156BG, and the watchdog was also triggered (some transmission errors, not many, but some). So I can confirm that with the a72 cluster and the 2.5 Gbit network card disabled, you have an extremely stable NAS (now with kernel 6.12.44). Does anyone have a damaged or non-functioning helios64 motherboard they can send?

Hello, i tried "Armbian_community_25.11.0-trunk.208_Aml-s9xx-box_plucky_edge_6.16.7_xfce_desktop.img" booting from a usb stick. First it looked, that it loads (the minix logo disappeared for some 100ms) which indicates that it loads, but then at the end the internal android booted. For comparison "LibreELEC-AMLGX.aarch64-13.0-nightly-20250926-2f25ce3-box.img.gz" booted fine, even from the sdcard slot. My final goal is, to run "tvheadend" as server with a "Hauppauge WinTV-soloHD" Usb STick and "Moonlight" client for "sunshine" on a 1280x1024@60hz nec display. Can anybody pls tell me what i must download? Thx.

@JaydenWithaWhy I rebuilt and uploaded again a new copy of the multittol. Please download and try again, I tested successfully on a tvbox of mine and worked fine.

Hello, and thank you for the suggestions. Just to clarify, I am not using an ILI9341 or ST7789 display. My display is a ST7735S (1.8", 128x160), a generic model purchased from AliExpress. The main issue is that while this setup worked perfectly on older Armbian kernels, it's no longer working with the current Kernel 6.12.x. It seems like the necessary module might have been removed or changed in the newer versions. I am not using a desktop environment; my goal is to use the display directly from the console/framebuffer (no X11). I’ve made some progress, but now I’m stuck. Here’s what I'm observing: The system does create a framebuffer device at /dev/fb0. When I use a tool like fbi to show an image, it runs without any errors. If I try to dump the framebuffer device (e.g., cat /dev/fb0), it outputs data, which suggests something is being written to the buffer. The problem is on the physical display itself: the screen's backlight turns on, but it remains completely blank (white). No image is ever displayed. I'm unfortunately not sure how to proceed from here. It feels like the display is being initialized enough to turn on the backlight, but the actual image data isn't being displayed correctly. I suspect the driver is not sending the right commands. Does anyone have an idea what I could try next? Thank you!