Active threads

Hi Installed Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img and one of the USB-3 port, the top one, doesn't work. No reaction when inserting anything, nothing in /var/log/syslog. The same with Armbian_25.11.1_Rock-5c_noble_current_6.12.58_minimal.img The Armbian_25.11.1_Rock-5c_trixie_vendor_6.1.115_minimal.img however is OK. What could be the cause of this problem? Thanks and regards, Chris

Hi I have a Rock5c with a Penta SATA hat and it works OK. It is the only (?) way of having several disk connected to Rock5c. Note, it cannot boot of the disks on the hat. Have two SSDs and mirrored ZFS pool. No problems at all. Setting it up to act as Frigate server. The fifth SATA, in fact e-SATA connector comes very handy to connect a large disc for constant recording. You may also consider Odroid HC4. I think it's the cheapest solution and it's fan is negligible 🙂 Have three of them, acting as mail/backup/HomeAssistant servers. Had in the past some problems with USB but recent kernels are OK. Hope it helps.

With the H618 kernel, the system is very stable but there is no audio output at all. With the H616 kernel, audio works perfectly, but the system starts showing screen distortions, artifacts, and UI crashes. When I said “image became distorted” and “kernel artifacts”, I meant things like the screen going black, color blocks appearing, and the desktop environment crashing. I already tried enabling analog-codec, installing alsa-utils, using alsamixer, and testing with mpg123, but the result didn’t change. I haven’t built my own Armbian image yet, but I’m considering trying an edge kernel with the Armbian build system.

@Learnincurve It is very easy to build only the kernel with the Armbian Build Framework. The result will then appear as output/debs/linux-image*.deb

This is custom hardware world and Armbian is a build framework 1st. It is not Debian vs. Armbian vs. Ubuntu. Debian, Ubuntu and other labels means something in mainstream x86 world while here they mean nothing, they are abused to generate sales. If you go for regular Debian, you will do 1-2-3 steps back and if you are lucky, one step forward - to accidentally load kernel where feature you need, works. If i2c stack wasn't properly ported to mainline kernel or if there is some other trouble that prevents this working in standard world, you can only run firmware that is provided by vendor. This is quite common and there you will have other problems. Problems you have are not simple to resolve or at least not in the "by the way" fashion. In order to help you - there are two ways and both are difficult - you are lucky and meet a person on this forum that knows rare technical specifics for this particular board from head or you meet someone that will invest few days to get down to this level ... People who are maintaining this place, don't have time to breathe and some are old too. It is impossible to focus into every problem that shows up as there is no capacity. And bugs are being re-introducted all the time. By everyone. In that case you would need to go for Intel mini PC. Custom hardware needs hard push sometimes to get something in order. I can assure you that Armbian works perfectly on Intel PC I use it for my desktop. Many of boards we present here would be paperweight long time ago.

ping @amazingfate and @prahal

maybe @schmiedelm has an idea?

@xiaobao80I did manage to get 3.5mm working with the help of ChatGPT. The box is using HT5010. ChatGPT told me to disable the es8388 nodes, but it still works with them enabled. My sai@2a61000 looks like this: My ht5010-sound node looks like this: I got bluetooth working with a hack from the Radxa forums here (creating a shell script and adding it to the root's crontab): I tried to send audio from a TV to the rk3576 box - it did work, but the latency is too much for me. The brown box has beefier cooling than the purple one. I haven't recompiled, used my "stable" image from before to fix the 3.5mm issue, might need to recompile to try the GPU driver. Tried the rkr7.1 dts, but couldn't get it to work (might need additional time to look at it); armbian / linux-rockchip is still at rkr5.1.

I got the display to work! I left out a phandle = <0x01> line in my ili9486@0 section, adding it made it work. DTS was fine otherwise. It's a little glitchy and laggy so I need to tinker with it more, but I see plymouth displaying properly! I can't seem to get into tty or XFCE, but I believe I'm not running wayland and it sounds like thats a requirement for tinydrm? I'll figure it out, but the hard part is over. Once I get everything polished I'll write a summary of my steps so its easy for others to follow. Working DTS for the red ili9488 display using tinydrm driver: Edit: Removing XFCE & plymouth seems to break things, display is pure white again. It also rearranges /sys/class/drm to be card1-SPI-1 instead of card0-SPI-1. Adding this line to /boot/armbianEnv.txt results in the blue and black stripes again, instead of a white screen, but prevents the screen from working with plymouth or XFCE. extras="fbcon=map:0" Reinstalling plymouth and XFCE reverts this white screen and shows boot messages again but no tty console, only if there is no fbcon line at all. Installing just plymouth and not XFCE shows boot messages only if fbcon=map:1 is set, note the 1 instead of 0. Still no tty. The last boot message is and the one after (which I see on serial console) is this, so maybe plymouth finishes writing boot messages to display and the system just never accesses it again? Maybe I need xorg to access /dev/dri/card0 instead of /dev/fb0, since it is not a fbtft device but a DRM one? [ OK ] Finished plymout… Write Out Runtime Data.

There are none. https://docs.armbian.com/User-Guide_Networking/#networking

moved

I know of a way to install a specific kernel version: sudo apt install linux-image-edge-sunxi64=25.5.1 --> installs linux 6.14.8 But how do you install specifically linux 6.15.4? Also, have you checked if the newest linux version requires a dtbo to be activated in armbian-config? If you still can: compare the output of lsmod under 6.15.4 and under 6.16.8

Orima, Ubuntu 22.04 is recommended, but I have no problem installing armbian build in Linux Mint 22.0. I think Debian Trixie in your laptop is too new to have the right requirements and versions for armbian build. You can build Debian Trixie for your orange pi, with no problems. Don't try to fill all the parameters in a single command line. Just download the armbian zip, "git clone" it in a new directory. Then run "./compile.sh". You will be presented with all the text user interfaces to make your board selections, linux and debian versions, etc.

Anyone knows how enable usb 3.0 with Radxa cubie a5e? I found cubie-a5e-enable-usb3.dts from radxa's git but could apply it. Currently I am running 26.2.0-trunk.22.

I'm not sure vulkan is the best solution, RK3588, as most ARM SoCs has a dedicated video engine, vulkan is mainly needed on hardware without dedicated engine, using graphic card to decode, as it's often the case in x86_64 worlld. You can then including it's decoding in vulkan if you want. Don't know wich version of kernel/mesa/video decoder you use. The best, is to remove all dedicated package, and use system one, today, everything work fine with standard linux kernel, as armbian one, standard video tools, rockchip specific libs/video tools was used with rockchip made tools, until everything was mainlined. I don' use VLC, that needs specific libs, but mpv, or several other video players (including firefox one), and everything plays fine.

I dont know how to do that, sorry!

Thanks Robertoj All the documentation for the board is here https://github.com/zharijs/zmxxxp-re But the LCD is not an himax-hx8394. The screen is a "MTF0397SWI-06" using the chip OTM8019A. It just that I am starting from this driver to port the sunxi driver: sl698ph_720p. I will now look at your links.

Tried this with a Ubuntu PC today, and have the same result. lsblk shows one partition.

I followed your tutorial, and it works! I did it with a server image instead. But I was not able to make Wifi work. Did you manage to connect to the Wifi?

Thanks! This fixed the issue!

Furthermore, today I built an Ubuntu desktop PC, and flashed a build onto an SD Card. The resultant installation has only ONE partition. No Windows involvement whatsoever Same with a USB flash drive (to eliminate the SD card adapter). So where do we go from here?

Thank you! I've been unable to give this a crack over the last couple of days, but I'm hoping to try this weekend. I'll post back here with how I go

FWIW, on my rk3588 devices the NPUs are working with recent mainline releases: [ 5.967316] [drm] Initialized rocket 0.0.0 for rknn on minor 0 [ 5.975499] rocket fdab0000.npu: Rockchip NPU core 0 version: 1179210309 [ 5.978652] rocket fdac0000.npu: Rockchip NPU core 1 version: 1179210309 [ 5.985602] rocket fdad0000.npu: Rockchip NPU core 2 version: 1179210309 This script runs the Mesa example with the latest available working versions: And with this script, the Mesa example runs, with a small adjustment, also with the TFLite successor LiteRT: A MediaPipe sample can also be set up easily: But unfortunately, the MediaPipe framework does not support the extended delegate functionality of LiteRT (TFLite). And therefore no NPU support. classification-3.11-tflite.logclassification-3.13-litert.logobject_detection-3.12-litert.log

you may actually want to extract the dtb file on the android side of the tvbox you have just to get the OS to get recognize that chipset (but may not work due to missing driver).The odds for this kind of tv box to have a working wifi chipset is a lottery, most likely you better off not waste that effort and just buy a USB WiFi dongle instead, at least it works far better than a SDIO based wifi chipset like that.

I'll try. So far, just booting the board did not work. I suppose it does need mainline uboot. Need to figure out this fdt stuff somehow too...