Active threads

Hi, is there currently support for NVMe storage in Armbian trunk? I tried to flash the latest build, added nvme ssd storage - but it is not seen in the system. What to check?

@1-igor I followed your guide, I ereased the spi flash. But after rebooting the OPi 5 wont even boot to the previously working ssd m.2. Even no orange pi screen before boot. Is there any fix?

Ok, thanks

For those who are seeking to enable video decode i've been able to get it working with those libs https://www.elektroda.pl/rtvforum/topic4018092.html#20840047 download h618_hwdec.tar.gz and replace the libs and add "extraargs=cma=256M" to your /boot/armbianEnv.txt , mpv works flawlessly with --hwdec=drm --profile=fast, scrcpy is also fast and with minimal cpu usage... i'm also using rolling edge kernel, and latest 25.2 mesa from source libva-v4l2-request-HACK_HEVC.zip

yes, see these two posts: and

Ryzer, you can navigate to the http link http://apt.undo.it:7242 click “pool” and all the other links until you see all the debs for download check you distribution recommended ffmpeg version with “apt list ffmpeg” download the matching deb versions: ffmpeg-x.x.x-v4l2request.deb, lib…x.x.x Sudo apt install ./lib…Deb (one by one) Sudo apt install./ffmpeg….deb sudo apt install mpv (from the original Armbian-configured repository)

Bug reported and fixed. https://bugzilla.kernel.org/show_bug.cgi?id=220261 Hopefully included with rc4

moved to the Pine A64 forum.

Hi, I tried the solution of extracting the idbloader.img from the official OrangePi image and flashing it at the appropriate address, as suggested in one of the previous posts. I tried this with the latest official Armbian Gnome image for OPi 5b. While it did boot, dmesg returned some errors and bluetooth did not work. I didn't inspect if there were more devices affected. The thing is that the boot process consist of several stages as described in the official Rockchip wiki: https://opensource.rock-chips.com/wiki_Boot_option Take a look at the "Boot Flow 2" in the boot flow chart. It involves idbloader.img and u-boot.itb binaries. Both are present in u-boot package inside the official OPi image. When I flashed both, each to the address specified in the wiki linked above, I got everything working. There is, however, an easier way to patch the bootloader. Go to Joshua Riek's Ubuntu Rockchip download page: https://joshua-riek.github.io/ubuntu-rockchip-download/ Download the image for your board and flash it to SD card. After flashing, copy the Armbian image to the same SD card. Don't forget to change the overlay (in the Armbian image) in the /boot/armbianEnv.txt as instructed in the official Armbian OPi5/5B page: https://www.armbian.com/orangepi-5/ Insert the SD card in your OPi5B and boot Ubuntu Rockchip from it. Open the terminal and use the dd command to flash the Armbian image to the emmc as described in the official OPi5B board user manual available at the board manufacturer's website. After that, just run sudo u-boot-install /dev/mmcblkX where you need to replace X with the appropriate number for your emmc (usually mmcblk0). This will install u-boot supplied with the Ubuntu Rockchip to emmc. Notice from the output that the command basically flashes the two binaries mentioned earlier, probably using the dd command. Power off, eject the SD card and try powering on. The board shoud boot Armbian from emmc.

I have been trying to set up labwc as a replacement for openbox (X11) in my project. I can install it very simply by building a minimal image Trixie (Bookworm does not include labwc), then * sudo apt install labwc seatd foot * at the screen with usb keyboard (not from SSH) start: labwc -d -s foot Then I am in labwc, with a terminal emulator on my HDMI screen When I right click on the desktop and choose "Exit", I get a kernel oops: And the labwc process shows "defunct" Has anybody experienced this? Maybe my kernel is too new? I used 6.15.4 (edge). My labwc is 0.8.3 The error in the terminal that started labwc (the HDMI screen) is: ...wlr_drm_lease_v1.c:103] Destroying wlr_drm_lease_device_v1 for /dev/dri/cardiationsodifier LINEAR (0x0000.....) XT_EGL_image_storage_compression GL_EXT_texture_storage_compression GL_MESA_bgra im... Same error message here: https://github.com/labwc/labwc/issues/1424 Source of wlroots, mentioned in the error: https://github.com/swaywm/wlroots/blob/master/types/wlr_drm_lease_v1.c A developer in the labwc group suggest this might be GPU driver related https://github.com/labwc/labwc/discussions/2923 Can someone with an SBC other than H618 try running labwc and exiting? What about xfce in wayland mode... does it crash? Is anyone aware of a H618 or sunxi running wayland successfully?

Hello everyone, I recently bought an used Helios64 NAS without AC Adapter. I found some adapters on AliExpress (for Italian country) but I don't know the PIN disposition (about the polarity, V+ V- etc.) Could someone of you share a photo of the original Kobol Helios64 AC Adapter with the polarity details? Thanks.

Thank you.

Hi there, I'm currently working on installing armbian onto my h96 max tv box (labelled as an rk3318 externally and in software, but the internal board is marked as an rk3328), and like many others here, I am having difficulty getting hdmi to work using the rk3318 build found at https://github.com/armbian/community/releases. I can access and control the box over ssh either over ethernet or wifi once configured, however I definitely need functional hdmi output for the use case of this device. The hdmi output works perfectly fine in both the bootloader, the stock android OS, and the bootable multitool, but once armbian boots, I completely lose hdmi signal on a standard 1080p monitor. My linux experience is intermediate at best (I daily drive Mint and am not very familiar with in-depth hardware configuration like armbian requires), so I am looking for assistance with a few things: I'd like to confirm that I am indeed meant to use the rk3318 build and not the rk3328 one, as while both the device case and the output of cat /proc/cpuinfo claim that this device has an rk3318, the marking on the board states it is an rk3328. I would rather not remove the heatsink to check the chip's markings directly, as I doubt that I have the means to reattach the heatsink once it is removed. If there is another recommended build that has working hdmi for this device or would perform better, please let me know. When/if I am on the right image/build for this device, I unfortunately do not have much knowledge on how hdmi would be enabled/initialised. I have seen others in this thread mentioning doing so, but i cannot find any mention of how this is done. Assuming hdmi is eventually functional, I did have a look through the different options in rk3318-config and armbian-config, but I am unsure how to best use the information printed on the board to select the optimal options in these tools for my system. The wifi did work without needing to select anything special, which is good. I did not test bluetooth or notice the front LED panel working at all, though. Thank you in advance for any help you can provide, and thanks to Jock for porting this neat little distro to this hardware. It's been fun to tinker around with so far. Attached are images of the board and label, and I can provide any other images or output of commands if further information is needed.

@psygnosis Can you run "armbianmonitor -m" (as root) to see what the processor speed and system load is when you are experiencing the high temperature. I found an old distro and loaded it on my test system and the temperature did not change: Welcome to Armbian 22.11.1 Bullseye with Linux 5.15.80-sunxi System load: 10% Up time: 5 min Memory usage: 14% of 491M IP: 192.168.1.69 CPU temp: 49°C Usage of /: 1% of 109G sysadmin@orangepione:~$ sudo armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 16:09:02: 816MHz 0.18 15% 3% 7% 0% 3% 0% 49.9 °C 0/4 16:09:07: 816MHz 0.16 1% 1% 0% 0% 0% 0% 45.6 °C 0/4 16:09:12: 648MHz 0.15 1% 0% 0% 0% 0% 0% 46.0 °C 0/4 16:09:17: 648MHz 0.14 1% 0% 0% 0% 0% 0% 45.6 °C 0/4 16:09:22: 648MHz 0.12 1% 0% 0% 0% 0% 0% 45.6 °C 0/4 16:09:27: 816MHz 0.11 1% 0% 0% 0% 0% 0% 45.8 °C 0/4

Hi @coroner21, Can you share some pics of the Helios4 you have? Thanks, Groetjes,

@ScoreABSM https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_trixie_current_6.12.35.img.xz

Confirming that reversing the USB-C connector fixed the issue for me too. On official firmware it wasn’t needed, but on Armbian 25.8.0-trunk.322 (6.1.115-vendor-rk35xx), the device was only detected as USB 2.0 until I flipped it.

Works with an apt update && upgrade. missing DTB is present, and boots ok. Thank you for the fast fix team.

Thank you for the solution!!! I struggled for days on this.

I finally got around to trying things out again. Here is the armbianmonitor -U (https://pastebin.com/7GUqZ2aP) before upgrading/updating on the 21.05.1 release. Setup a swap and going to try the upgrade now.

Okay partially solved, its the Linux rockchip64 kernel version. On 6.12.32-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. 6.16.0-rc3-edge is not even booting, with BananaPi-M7. @amazingfate Would it be possible to look into this please.

Hi Guillame, unfortuantely there is a file size limit and my SD image breaks the upload limit. If you dm me your email address I can look to send you the image via wetransfer or something similar. Kind regards, Mark

Have the same issue, who has a ideas ?

This past May, we met with the community at the GStreamer Spring Hackfest in Nice, France, and were able to make great strides, including the integration of AI/ML workflows in GStreamer. View the full article

Copying the file over from my rpi zero 2w didn't work. I may try compiling on a different OS on the opi tomorrow to see if that will compile fully.