All Activity

So far I only have working ethernet, which is good enough probably. So, hdmi, wifi, audio, gpu are not working. Is there anything I can do to fix any of these? Install some firmware, edit the dtb or something?

Hello @brunorro, I have uploaded two images to https://privat-in.de/ (navigate to downloads, grab Armbian*.img). Simply post findings here. The "edge" image is rather unstable, e.g. my NVME gives a read-error while working fine with "current", while a Mediatek Wifi card seems to work. Probably no easy task, could be anywhere in the IOMMU - DMA - PCIe triangle. The images are compiled from https://github.com/sven-ola/armbian-build/tree/orangepi-rv2 kernel with defaults plus switched on every Mediatek Wifi driver module. Here's my Todo for ref (+ marks ok): To be merged + Boot from SSD (upper+lower) + SPI NOR flash boot / install + SD/TF speed too slow (15mb/s) - Check SD UHS in uboot speed limit + Brcm SDIO wifi not working - Armbian edge: Brcm SDIO Wifi - Armbian edge: PCIe NVME IOErr + Bluetooth not working - RTL ethernet (2.5gbit R2V board?) - Ky overlay dtbo's missing - Focaltech touch driver from Ky? - Ky MIPI/CSI cam modules - What is that realtime r_uart? - GPU? USB2-OTG? USB3? Sound? Personal wishlist: - Device-mapper / dm_era missing + Mediatek PCIe wifi modules - PCIe adapter: Radeon GPU test Ah, yes. OpenWrt is on the Ky list of supported systems. I have a personal history on that too. While getting rid of systemd may be not that difficult (see Devuan) exchanging libc is another beast probably. LG // Sven-Ola

I have a Magicsee N5 Max X4 TV box (Amlogic S905X4). Has anyone tried this with this model? I tried removing the # S905X4_Generic symbol, but it still gives an error when booting. Could you please help me? Thank you!

On https://www.armbian.com/radxa-rock-5-itx/ there are several things wrong. 1 is a desktop image has stated size of 260.1 MB, that is certainly wrong. Then below there are several filenames Armbian_24.11.1_Rock-5-itx* in a sort of test report list. Note sure if that makes sense, more than 1 year old images. Also 6.1.75 vendor kernel had a few issues for me, although other RK3588 SBC. 1 year old versions of images might rely on older non-KMS HDMI init of a HDMI-monitor (done by older U-Boot), while newer U-Boot fails to init HDMI-monitor and also newer kernel and the current KMS might do things in a different way. I have that for my NanoPi-R6C and a certain older Medion HDMI monitor. Sometimes the KDE login screen just pops-up in 640x480. When login, the normal desktop goes correctly to 1080p60 (fullHD). A soft reboot also keeps it then in 1080p60, but the 2026.x versioned U-Boot does not manage to init the HDMI (maybe on-purpose, I have not looked in build config etc). I have not tried restarting displaymanager via ssh as the 640x480 came eventually, but did it several times in the past (from 2019 till 2024 or so until not using it with HDMI anymore) for 2 RPI4, also different monitor and also with or without a HDMI switch in between. A method is to put a video= statement on the kernel commandline with the desired mode. Earlier via RPi firmware in config.txt. I also looked into journal for the NanoPi-R6C issues of course and various failures w.r.t. HDMI after kernel 6.16.x or so, but all not fatal. So in the end it works and now properly working with kernel 6.18.2 edge kernel (Armbian Trixie KDE6). I went back to other bootloader (EDK2-UEFI v1.1) as that manages to init the HDMI monitor before kernel load and that is what I need, else always other computer needed (serial console) to select a different kernel or kernel config. I have never used video= statement with Armbian (yet), maybe I'll try just to know if and how it could work. So @Bobbox, can you post what image it is (exact filename and sha256sum) ? Even better is also kernel version and U-Boot version (exact UUID build strings), but a better human readable version will also give some hints already. And maybe upload armbianmonitor log, but that is maybe for later.

Hey!! Of course, I will test that one. Let me know (here or in a PM) what can I do for you. I only have a RV2 8GB RAM, but both M.2 slots are filled up (a 256GB nvme on the 2230 and a 512GB on the 2280) so I could test those as well. Everything I can learn will be welcome. Personally I would love to create a musl based, systemd free distro (alpine, void, etc.) for this little thing, but my knowledge is out of that league, I've only got some experience with OpenWRT on old routers Thank you!!

It is not recommended to match ZFS with vendor kernel(s). In general. Use mainline based current / edge kernels. Here v6.18.y we also might not have suitable ZFS yet as the kernel is too fresh. But if not today, it will be avail within days / weeks.

We have hundreds of releases and multiple per version per board hard to tell from this which kernel or which exactly i make a wild guess and the kernel you tried is 6.12.y which isn't good for desktop. try 6.1.115 (with mesa-vpu extension, not sure if there are pre-made ones) or 6.18, 6.19 mainline kernel.

Managed to find how to solve the issue! For anyone with the same board revision (IK316Q-EMCP_V4.1) and LPDDR3 memory who is struggling to boot standard images: I tried multiple generic builds (Ophub, etc.) and DTB edits without success. The solution was using this specific pre-configured image version from the sicXnull repository. The working image is: Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz Download Link: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz It booted immediately. Hope this helps others with this specific hardware.

Hello!! I am looking for help to boot Armbian on a generic TV Box sold as "MXQ Pro 4K 5G". I have tried multiple images (including official and community builds from sicXnull), but I only get a black screen or signal loss immediately after the boot attempt. Device Specifications: Model on case: MXQ Pro 4K 5G Board ID: IK316Q-EMCP_V4.1 SoC: Allwinner H313 (identified as sun50iw9p1 in Android) RAM: 1GB (Single chip configuration) Storage: 8GB eMMC Current Status: I am able to boot into the stock Android. To attempt the Armbian boot, I've tryed the Power up method, the power up pressing the hidden AV switch, using the reboot update command from a terminal emulator within Android. The issue: Upon executing the reboot command, the Android system shuts down, the display signal cuts off (or stays black), and the device never initializes Armbian (no HDMI output, no LEDs blinking differently). What I have tried:

So I tried running Armbian Minimal/IoT version with kernel 6.1 and the fan is operating normally (tested it with the stress command). I didn't realize i was working with two different kernel versions. Sometimes you just need another set of eyes to look at a problem. Thanks for the help, cheers!

desktop: $ uname -a Linux opi5p-cl1 6.1.115-vendor-rk35xx #1 SMP Fri Nov 21 14:02:48 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux minimal/iot: $ uname -a Linux orangepi5-plus 6.12.58-current-rockchip64 #3 SMP PREEMPT Thu Nov 13 20:34:41 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux Good call, I'm going to download the other Minimal/IoT image that uses kernel 6.1 and give it a try. Will let you know what happens.

@JohnU Which kernel version of the desktop installation and which with the minimal?

Hello @brunorro. Yes, sometimes people are hacking badly. I have it working again after restarting with Armbian/Spacemit: u-boot starts, onboard BT and Wifi works, SD card is again reading with 80mb/s, transfer u-boot and SBI to MTD via armbian-install works (MTD boot is required for starting from SSD), both M.2 slots can boot from NVME. Sadly, the Broadcom SDIO wifi driver is a smoking mess. This driver needs heavy porting so its not available with linux-6.18 / edge currently. Are you willing to test anyhow? I can provide a 6.6.99 Trixie image for download if you ACK. There are always things that I may have overlooked such as USB, HDMI. All those little things I have not tested, I' on UART currently. LG // Sven-Ola

Vendor dtb is an Android/vendor kernel dtb. The code that goes into mainline linux is generally vastly different from vendor. So while the vendor dtb can provide some hints as to what is needed in a mainline dtb, it isn't even close to compatible.

Yesterday I was happy to see the new and fresh Armbian release for the Rock 5 ITX after about 1 year from the last update. I also tried the Armbian Imager and the SD creation was very easy and smooth. I selected the recommended release based on Ubuntu 24.04 + Gnome desktop. Unfortunately when the desktop was about to start, everything when black, stucked and zero interface. On the other hand, the OS is alive and I can connect remotely via SSH. Did anyone have the same problem? Possible solution? [EDIT]. sudo systemctl restart gdm and desktop pops up. Restarting the system, black again.

If you don't have X11 or Wayland, try using the linux command "fbi" (frame buffer image). I think I put an example in this trhead or in the Banana Pi ili9341 thread (in this allwinner forum section).

I have several Orange Pi 5 Plus SBCs, and I have found that the fan works correctly if I install the Ubuntu desktop (Noble/XFCE) version of Armbian. But if I install the Minimal/IOT version of Ubuntu (Noble) the fan stays on constantly. I have not had any success trying to build my own orangepi-5-plus-pwmfan.dtbo (overlay), and I also tried copying the /boot/dtb/rockchip/rk3588-orangepi-5-plus.dtb file from the desktop version over top of the minimal version and rebooting, but my orangepi-5-plus would not even boot. it would be really nice if one of the maintainers could take a look at this and see if the minimal version is missing some component. I did see the following error in the journalctl -xe output after booting the minimal version: Jan 12 15:07:56 orangepi5-plus kernel: fan53555-regulator 0-0042: FAN53555 Option[10] Rev[1] Detected! Jan 12 15:07:56 orangepi5-plus kernel: rockchip-thermal fec00000.tsadc: Missing rockchip,grf property Jan 12 15:07:56 orangepi5-plus kernel: fan53555-regulator 0-0043: FAN53555 Option[10] Rev[1] Detected! Thank you, John

Well, chatgpt told me it could generate a modified version of the dtb specifically for my device, provided the vendor dtb and some command outputs (mostly to figure out which chips are used - wifi,ble,hdmi etc). Well it did generate a dts, which I compiled in the linux kernel (pulled from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git). Well, I booted using the generated&compiled dtb, but HDMI is not working, eth is also not working, don't know what else. I also tried meson-gxl-s905l3b-m302a.dtb, which I got from https://github.com/xcray/amlogic-s905l3a-armbian. Eth is working with this dtb (it also probably worked with the p212, but at that time, I didn't have a cable to check). I actually don't know what else to check if working:) Is there a unified check tool for quick testing hardware support? Also, is there anything I can do about the hdmi or wifi? I am ready to write my own dts using the vendor provided one if necessary. HDMI is more of a priority, but I would like to tinker around with this thing just to see how far I can go. I would be very glad if you pointed me in the right direction in order to do this. Or if it's really impossible then fine. I thought provided the vendor.dtb I could get some of the hardware working, if this is not the case, then fine, I'm happy with eth. Anyway, I'll now try to setup ssh, cause it's about time I cleanup the setup and the micropython uart bridge:)

Does anybody know if this will work with Allwinner H618?

Forumtrekker: I am 99% sure that if you see the LCD working OK once, with kungfupancake or any other a txt/bin file, for just console text, it will work for any graphics. There's an issue with plymouth: it modifies the initrd in a way that it loses track of the bin file, and the kernel driver fails to load. See: https://forum.armbian.com/topic/53568-how-to-add-a-specific-single-file-in-the-initrdimg-ideally-automatically-with-update-initramfs/#comment-221767 I am running my SPI at 40MHz fine with 20cm wires. I don't have time to see your DTS file, but are you using the same CS pin as I do? I have noticed there's a default "chip select" pin, which makes everything work better. If you are using panel-mipi-dbi driver, don't use any additional DTS for the LCD, not even additional SPI DTS, and armbianEnv.txt that refer to the LCD. According to the notro wiki, the ili9486 and ili9488 will only work with RGB888 mode (because we use SPI). There's the "format" parameter line just for that, in my DTS. Can you send a good photo of your LCD front and back? My method is for a Red PCB LCD. I don't know the brand, but it is not Waveshare, Creality or any known company. Sorry, saying "Chinese LCD" is like saying "wet water": redundant and not specific. pami: the english in your post is fine, but you can separate ideas and separate processes in paragraphs, to let me focus in one problem at a time Many LCD guides, due to being so old, use the fbcopy driver, or another "classic framebuffer" driver. I could make my ili9341 work with it, but since I learned to use the panel-mipi-dbi I only started using that. It get's you more fluid animations and probably Linux will prefer it in the future. If one dtbo file and a python script makes your LCD work fine, share that script and DTBO (best if you can decompile the DTBO into DTS), in this thread, as attached files. Send more photos of your LCD. AI suggestions will only work if the solution is well documented somewhere in the internet, and the AI has found it. AI will re-word the answer and take credit for it.

Hey, Thank you for working on this one. I have the very same and the sunxi scripts to create the Ubuntu image (tricked into trixie) are horrible. For instance, to create ky image they download all toolchains (ARM and so on) from its site and it's kind of difficult to even change that one. I would love to use upstream u-boot and spacemit 6.19 kernel on this one (already compiled for it) but I'm no expert and the lack of docs and ways to work on this one kills me Thank you!

Has this thread been updated yet, bro? I'm trying out Ubuntu.

Hello community, I am looking for help to boot Armbian on a generic TV Box sold as "MXQ Pro 4K 5G". I have tried multiple images (including official and community builds from sicXnull), but I only get a black screen or signal loss immediately after the boot attempt. Device Specifications: Model on case: MXQ Pro 4K 5G Board ID: IK316Q-EMCP_V4.1 SoC: Allwinner H313 (identified as sun50iw9p1 in Android) RAM: 1GB (Single chip configuration) Storage: 8GB eMMC Current Status: I am able to boot into the stock Android. To attempt the Armbian boot, I am using the reboot update command from a terminal emulator within Android. The issue: Upon executing the reboot command, the Android system shuts down, the display signal cuts off (or stays black), and the device never initializes Armbian (no HDMI output, no LEDs blinking differently). What I have tried: Builds from sicXnull repository (Kernel 6.x). Ophub community builds (H616/H313 variants). I have updated the extlinux.conf / uEnv.txt to point to the sun50i-h313-x96-q-lpddr3.dtb (and others like x96-mate), but the result is always the same failure to initialize. Has anyone successfully booted this specific board revision (IK316Q_V4.1)? Is there a specific bootloader argument or a different DTB required for this MXQ clone? Photos of the board are attached. Thanks!

Unfortunately, I have exactly the same problem.