All Activity

Hello, I have a MXQ Pro 5G 4K TV Box with Allwinner H616 and the motherboard IK316-EMCP_V4.1. I am looking for a server (CLI only) version of the Armbian image for this device. The previously shared Google Drive links in this topic are no longer working. Could someone please provide a new download link (Google Drive, MEGA, etc.) for the latest server image compatible with my device? If there are any specific instructions for booting or the correct DTB file, please let me know. Thank you very much! Best regards, Luska1331 BTW: I generated this message with the help of Copilot because I don't speak English very well.

Difficult to say how to fix without further logs. What I am looking into and what it could possibly be related to is the simpledrm module loading alongside sun4i-drm. I wonder if you remove simpledrm then does the cursor become less erratic? Without diverging to far off topic, I suspect this related to sun4i-gpadc and how the temperature sensor is polled is carried out. The 6.12 Hdmi patches are a backport of the changes found in 6.15.

Ok, maybe @jock has some suggestions to this issue.

@Werner - When the Armbian Official Nobel upgrades it has the same issue.

I modified the armbianEnv.txt file : verbosity=1 extraargs=coherent_pool=2M bootlogo=false overlay_prefix=rk322x fdtfile=rk322x-box.dtb rootdev=UUID=87d2bf72-4b91-4d33-8f77-284fa91fc3a7 rootfstype=ext4 extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 drm.debug=0x4 overlays= usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u This is apparently preventing the tv box from booting, I lost access. I will have to flash it again with the multitool to get back in, and this will have to wait on monday, since I was remoting into it at the office. Thanks for your help!

Can you check if you can pass drm.debug=0x4 to the kernel command line and see if you get more info ? If yes, paste here the boot log.

Thanks for the hint Sirmalinton. Today, I could solve the problem. Here is a short summary that might be of use for people running into similar issues. Running lspci -k shows the "Non-Volatile memory controller" but it does not show the line "Kernel driver in use: nvme". Hence, I ran echo nvme > /sys/bus/pci/devices/0002\:01\:00.0/driver_override echo 0002:01:00.0 > /sys/bus/pci/drivers_probe where 0002:01:00.0 is from the output of lspci -k. That worked and made the disk appear as files /dev/nvme0*. To have a solution that works after reboot, I created a udev rule /etc/udev/rules.d/99-nvme-override.rules with the content: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x144d", ATTR{device}=="0xa80d", ATTR{driver_override}="nvme" The vendor and device IDs are from lspci -nn. To trigger the probe, I created a systemd service /etc/systemd/system/nvme-rebind.service with the content: [Unit] Description=Rebind NVME controller to driver after override After=udev.service [Service] Type=oneshot ExecStart=/bin/sh -c "echo 0002:01:00.0 > /sys/bus/pci/drivers_probe" [Install] WantedBy=multi-user.target The service can be enabled via systemctl enable nvme-rebind.service. Maybe one reason it does not work in the first place is because /lib/systemd/system/nvmefc-boot-connections.service is not started. The reason is that the condition ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery is not met. Another reason, I can imagine is that the vendor/device ID combination is not registered to the nvme driver in the current kernel. As I mentioned before, it did work out of the box when I installed Armbian at first.

Well, since this same edid file I use on the Libre Renegade board works perfectly fine with this same monitor, I think the file is ok. This link you provide is the one I followed, I tried most of the things in there, as well as a bunch of stuff I found from other users. Again, since this works on U-Boot, this points at something defective on Armbian and how the edid communication happens. This Armbian kernel that came with the armbian image I downloaded it from the armbian github as a part of the image I use on my device. I did not build it. I would think it was the Armbian team, correct?

More like a kernel issue than Armbian. The Armbian supplied edid bin file probably does not match your monitor's. Take a look here on how to get the actual edid and force it: https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID

Yes, The 1920x1080.bin file comes with Armbian. I use the multitool to flash https://github.com/armbian/community/releases/download/25.8.0-trunk.309/Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img.xz , this is the latesst build. On a Libre Renegade board I have (rk3328 CPU instead of rk3228 for this TV box), I have the same issue where it reverts to 1024x768, and adding the line extraargs=drm.edid_firmware=edid/1920x1080.bin to armbianEnv.txt fixes the issue, with the Armbian provided 1920x1080.bin file. To me, since it works fine under U-Boot, this hints at an Armbian bug.

@Igor thank you for fixing overlay-prefix problem in current armbin-config now on OZPI V1 and V3 overlays in armbianEnv.txt are without prefix

Do you actually have this edid file : edid/1920x1080.bin ? How did you generate it?

Use `vendor` kernel and enable hdmirx overlay.

Another good thing : previously, the A20 CPU load never goes below 1 due to something wrong in the kernel. It's now corrected. I can confirm also it is corrected : I upgraded my ArchARM BananaPI and the HDMI is back as well.

Hello all! I have a radxa rock 5b (8GB, not the plus version) and am running armbian (bookworm) on it. The kernel version (uname -r) reports as 6.12.32-current-rockchip64. By and large almost everything seems to be working - video playback in VLC is fine, 3d acceleration is working (I get around 58-60fps in the game 'torcs' as an example). The only thing I can't seem to get working (and can't find much about it) is the hdmi input. I see some five devices listed in dev (from /dev/video0 to /dev/video4) although none of these seem to relate to the hdmi input. Does the hdmi input work on the 5b under armbian at all? thanks ljones

Most Armbian systems use a file located at /boot/armbianEnv.txt. You can add kernel parameters using the extraargs line.

thread about video in case anyone is looking for it and a recent 'success story'

I juste installed it, and it's pretty working 🥰 # wget https://armbian.lv.auroradev.org/beta/pool/main/l/linux-6.12.35/linux-image-current-sunxi_25.8.0-trunk.346_armhf__6.12.35-S783c-Dbdda-Pf7b7-C34a1Hf8af-HK01ba-V014b-Ba566-R448a.deb # apt install ./linux-image-current-sunxi_25.8.0-trunk.346_armhf__6.12.35-S783c-Dbdda-Pf7b7-C34a1Hf8af-HK01ba-V014b-Ba566-R448a.deb My dashboard is back ! Trying to update my arch with the latest kernel ... ps: in addition, if someone knows how to disable cursor blinking on this HDMI, it would be fine (I already disabled getty on it, but the cursor remain).

Can someone tell me if Linux 6.14.8 or 6.15.4 supports this hardware acceleration? I can play 1080p H264, but with 100% CPU, with 6.14.8... and I get "unsuppoerted hwdec: drm" everytime I start mpv

It is now half a year later, this SD-card was put back into the RPi4 and no issues there. The RPi4 has been upgraded from Bookworm to Trixie in-place (just latest pre-release) so gets quite some writes. It still has Bookworm Btrfs snapshot as well, total of about 9GB excluding 2GB swap partition and 512MB bootFAT. Avarage Btrfs scrub speed 41MB/s. The ROCK3A has no SD-card inserted anymore, running fine, except that in the last 40 days I see: root@rock3a:~# uname -a Linux rock3a 6.1.115-vendor-rk35xx #1 SMP Fri May 30 01:18:17 UTC 2025 aarch64 GNU/Linux root@rock3a:~# dmesg | grep "page allocation failure:" [ 527.016616] dmcrypt_write/2: page allocation failure: order:0, mode:0x800(GFP_NOWAIT), nodemask=(null),cpuset=/,mems_allowed=0 [2879228.441453] dec0:0:hevc_rkm: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0 [2879523.127829] dec0:0:hevc_rkm: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0 [3029341.482298] kworker/0:1: page allocation failure: order:0, mode:0x800(GFP_NOWAIT), nodemask=(null),cpuset=/,mems_allowed=0 The middle 2 is clear what source is, the others I do not know. I think I will first upgrade userspace to Trixie. I currently have no clue what the details w.r.t. page faults mean, so have to see and figure out what issue could be or maybe mitigate somehow.

Does this happen with Bookworm or Noble? Plucky userspace is unsupported.

Yes it is dead, that is why my comments between brackets. Start with http://beta.armbian.com then click with your mouse per sub object. Or wait until it is out of beta phase or modify your sources.list.d

Currently using Armbian as a PiHole DNS server, it seems that after a few days the server just shuts itself down (Armbian 25.5.1 Noble 6.12). Not sure if it is a hardware related issue, I'll do some more tests and revert back to 25.2.2 Bookworm for now and see if the issue is replicated. Please note that my primary Armbian PiHole DNS does not encounter the same issue, though the version of it is Noble v25.2.3 / 6.12.30.

@JuanEsf Yep, here it is a080ed7128c898bec1cad6ec68c57bae159169d2fa06fb18008100ad63e4445c

You are right, this is a strange DTS issue. U-Boot is working, but the kernel can't initialize the SD card, which is why it drops to the initramfs shell. Unfortunately, I can't reproduce this specific error myself, but I agree with your analysis. I suspect this is the same reason why newer U-Boot versions initially failed to boot for me. I will start working on fixing the DTS next week. Thanks for finding this bug!