All Activity

Thank you @KhanhDTP. I think I have a pretty good handle on how (and your post on that thread was in particular very helpful, thank you). It looks like a lot of people here are desktop optimized. My plan is headless, so expectation is 25.11.1 / 6.1 and libMali route but with RKNN (XFCE only for occasional desktop, Gnome is too hungry, XFCE + X11 + software rendering is fine on rare occasions I'd need it). I think the question I was trying to ask is more along the lines of understanding what to expect for the default, and if it made sense to enable one of the drivers by default, but I'm realizing there are proprietary dependencies and enough obscure use cases that this gets more challenging. Thanks to everyone for all of the thoughts, hard to imagine navigating all of this without your contributions.

Noble image didn't boot on Orange pi 4A

I have a unit that I am unable to boot from SD card as it has no such physical device. Using a terminal emulator in Android I can see partitions being loaded, and have managed to get several "partitions" (mmcblk01p01 to p20) copied off to a flash drive. These turn out to be data files, so I can't load/modify them on a VM. I had hoped to find the boot.scr/boot.cmd file and modify it to force it to mount from USB in the first instance. The unit has 2 USB ports. There is a push switch that I had to unglue. It runs Android when pushed in, and I get a black screen when it is in the OUT position, so I'm assuming that the OUT position puts the unit into USB burning mode, or whatever. I have ordered UART header pins and adapter so will be able to do more research once those are in place. From your analysis above, can you recommend a way of forcing a boot from USB using the UART serial interface (I don't see a recover-from-usb U-Boot command)? I have an armbian s905x image all ready to go. Ideal situation would be that I get the Armbian running from USB then flash the eMMC. Any help gratefully received, Best, John

I did a new build this time removind BTRfs from kernel but I still get stucked on ... Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems I dont see how can I remove that FS since I never use it in my TV Box?

Armbian provides vanilla Debian (or Ubuntu) Cinnamon. In general, touch to the user-space part is minimal, so you are running plain Debian Cinnamon desktop, more or less. And as packages comes from there, bugs follow. Armbian team don't have resources for dealing with desktop. Minor problems only. And as it was already mentioned Exactly. I saw this (recently introduced) problem but since I have absolutely no idea where to look, I removed Cinnamon images from upcoming release. We don't touch Cinnamon nor other desktops beyond installing wallpaper. Probably tasksel installed variant will likely be broken too.

Yes. It is only enabled / working with 6.1 and desktop (Gnome) builds. For mainline based, perhaps 6.18.y ...

@gpupoor You want to set up GPU Acceleration, right? Have you read this post yet?

I've successfully booted Armbian from USB following the tutorial above, and I've managed to write Armbian from the USB drive to the eMMC. Now I want to create an Armbian firmware that can be directly flashed to the H96 M9/S eMMC using RKDevTool.exe, but I'm not very smart - even simple things take me a very long time to figure out. If any of you have this, please share it. If I manage to figure it out, I'll also share my findings.

"no". but don't trust anybody, that was the point. you don't know me. moreover, you probably already have on your stock firmware, like a lot of chinese android tvbox

afaik wayland is not supported in this version of xfce. You have to use Gnome or KDE.

What do you expect from single lane M.2 PCIe2.0?

I have nothing to complain about. glmark2-wayland-odroid-m2.log vkmark-wayland-odroid-m2.log

In case everyone else is interested: the easiest way I found to get a running system with the latest kernel is Start with an image based upon the vendor 6.1 kernel (I used "Armbian_25.8.2_Orangepi5_noble_vendor_6.1.115_minimal.img.xz") Once it's running, launch "armbian-config" Choose "System", then the entry to install a different kernel Now you can select the latest kernel, in my case "6.18-RC5" Just for the records, I was interested in trying the latest kernel because, with the vendor-provided 6.1 kernel, my NVMe drive was limited to 400 MB/s ("downgraded link speed"). Unfortunately, the same applies to the latest 6.18-RC5: probably a DTS issue, but I don't know how to fix it, so be it. Best, Fernando

Hello, I just flashed the latest minimal img from the github releases (Armbian_community_26.2.0-trunk.7_Rock-3c_trixie_current_6.12.58_minimal.img.xz) but I see no output on hdmi and it gets stuck at login, nothing I type works.

Digging deeper @Igor... I tried 25.11.1 Noble Gnome Vendor 6.1.115 from today, and am also seeing Mali-G610. However it's [disabled for xfce](https://github.com/armbian/build/blob/d2e208ace18b8003f926057ddfc038f8cce0bce0/extensions/mesa-vpu.sh#L19). I'm also reading some conflicting info so guessing there have been other conversations I'm not aware of. I started another post to try and better understand expectations.

I understand that panthor is not supported for wayland but in that case I would expect libmali to fill in... but I ended up with lvmpipe. The overlay along with another recent post led me to believe that panthor was the expected default and libmali was an artifact, but I'm now questioning that after finding a thread identifying use cases where libmali can be preferred and a comment suggesting panthor wouldn't be available until 6.13. As a result, I am now questioning if there is a reason that software acceleration is the default and the user is expected to determine which path they want to go? I know support for the hardware has been slow going so I understand that it's not well supported yet, but hoping to get a better handle on expectations. Is there an expected default for a Rockchip RK3588 SoC with the Mali‑G610 GPU? Does it vary between 6.1/6.12 and the desktop/server builds?

I never said it was a Debian issue (you failed to mention which userspace you were running in your original post, btw). The issue is with whereever you got your authelia package from (which you also failed to mention). You also failed to mention what error exactly you are running into. But yes, you are right, Debian will and can do nothing about it. Basically the same is true for Armbian, the symlink is there for a reason and there to stay. You are in the wrong place to get this fixed.

The first post reads "your mileage may vary" and "the latest kernel will work best" Start by recompiling armbian for your Rockchip SBC, with the edge kernel option, then follow the ffmpeg install instructions If it doesn't work, try the older Ubuntu, and both Debian options

If you already checked "dmesg|grep panel-mipi" and "dmesg|grep spi", check this: * share which LCD you are using. Half of those LCDs are waveshare clones, which need a different driver. My DTS works in the RED LCDs. * Look at the uboot messages in the serial port output. Does it confirm it is finding your dtbo and using it? * verify that panel-mipi-dbi.ko exists in the modules folder. I know it is not preselected by default within the linux configuration menu * Search the word "pinctrl" in this thread https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204741 To confirm that the kernel driver is using the gpio and spi pins * send link of the rock3c DTS you are referencing, to see an example of how GPIOs are configured * correct the gpio pin map you shared. Instead of tx/rx, use MOSI, MISO. Highlight and label clearly the CS0, CS1, RESET, DC, IRQ * explain how those gpio numbers gpioX,XX transform into the DTS gpioX XX 1/0 If you at least get noise in the LCD, you are 50% done (and maybe you will get lucky in the last 50%)

Just answer it... Will i have malware if i installed it on my tv box H96 max RK3528 4gb ram 64gb rom

I did it, so, you say that edge Ubuntu 24.04 have all required drivers for VPU ? that was my question

In this case it is not a Debian issue but one of Armbian. Debian has no /var/log.hdd directory, hence /var/log/journal is a directory not a symlink. ==> no issues with installing authelia in Debian. For armbian additional handling is required to handle this issue. I doubt Debian will do anything about it.

Your best bet is to compile your own image. It's super easy: "git clone https://github.com/armbian/build.git;cd build;./compile.sh" https://docs.armbian.com/Developer-Guide_Building-with-Docker/ https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://www.youtube.com/watch?v=kQcEFsXEJEE

I tell you to read the first post of the thread.

you clearly didn't get the point