All Activity

You can try the following: After writing to nvme and spi do NOT reboot but mount the nvme drive to a random directory and check in /boot/armbianEnv.txt if the UUID matches the one from the nvme. If not, correct it (check blkid).

Neither of these is good advice. dd does not verify written data and balena etcher has known issues, hence it is not recommended either. Either use Armbian Imager (https://docs.armbian.com/User-Guide_Getting-Started/) or USBimager (https://gitlab.com/bztsrc/usbimager). Both are known to work.

I don't like my chances of any resolution to this problem but here goes. I'll start off by saying thanks for providing this repository, I recently went on holidays and was able to use my little magcubic box to watch content off my nas remotely. It was mostly great. One issue I have come across is most of my SD content (ripped from DVD) just displays a black screen. I encode it to 10 bit x265 the same as I do for blurays. Blurays at 1080p play fine, the DVD rips at 480p and 576p just display a black screen, audio works. When comparing them with MediaInfo the only real difference (aside from resolution) is the color primaries, transfer characteristics and matrix coefficient tags. Blurays are bt.709 and the DVD rips are bt.601. Also NTSC vs PAL for the blurays. I've also come across some files that I believe I downloaded at some point that are DVD resolutions, 10 bit x265 PAL that play ok. In MediaInfo these files are missing the all the tags mentioned above. I don't know how this is possible... To troubleshoot I've tried converting a non working file to 25 FPS (PAL) and setting the elements above to bt.709 but no dice. I've run mpv from the terminal in verbose mode and tried to compare a working file to non working file and nothing is really standing out. I think ffmpeg is just serving up black frames with v4l2 in certain circumstances, maybe when the color primaries are bt.601. I'm not overly confident the method I used above to set the bt.709 values would actually work. I installed mplayer and this plays the files ok but doesn't have hardware acceleration. This is why I think the issue is ffmpeg and v4l2. Probably not relevant but 2160p content plays (bt.2020). It really struggles with it but it displays an image. Any ideas would be great. At this stage I'm probably going to take a 10 second clip of a non working file and just run it through bunch of different encode settings until I get something that displays and work backwards from there.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-4-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-4/wine-proton-10.0-4-amd64-wow64.tar.xz) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.4.1 30~40fps@720p (low settings) box64 environment variables: DRAGON BALL XENOVERSE

i took a look through your repo and used 2025.01 plus the patches in your u-boot-h616 directory and booting from EMMC works now. Thanks for the nudge!

Hello everybody. I'm new to this and I would like to install Linux on my BTV X p212 TV box. I saw that there are several versions of systems but I couldn't find them for this specific one and I would like to know if you can help me? Please. Ps: I searched here on the forum, google but I couldn't find it.

Good news: this is merged in Armbian main now, many thanks to @c0rnelius and @Igor for reviewing this. So no more need to grab my fork, just clone Armbian/build:main. I was able to build and quick-test orangepirv2/edge-kernel and this looks fine including Wifi. There are of course unsolved quirks currently. With edge-kernel, Wayland does not work, we need to use Xorg. And with the current bcmdhd Wifi driver, AP mode is not possible. This is caused by outdated file in armbian-firmware for bcmdhd and may be the same on OrangePi5. There is a mechanism to load a different fw_bcm43456c5_ag.bin (the one downloadable from github/xunlong seems to work). LG // Sven-Ola

is there a guide for booting opi5 from nvme that works with Armbian 26.2.1 -noble or trixie? The standard way via armbian-install seems broken

I just tried LibreELEC 13 testing builds as they are also running kernel 6.18. Audio seems to work there and I can hear all channels or speakers. I guess LibreELEC includes HDMI audio support patches for RK3588/S and NanoPi R6S that Armbian hasn’t incorporated yet ? The ALSA rockchip-i2s-tdm driver needs to support more than 8 TDM slots or support the HDMI multi-TDM mapping for 5.1 / 7.1. LibreELEC patches

As it turned out, Orange Pi does not support Power Delivery Negotiations and requires a "dumb" power supply providing 5V 4A. My power supply delivered 2A and then went into protection mode; the board itself had nothing to do with it

Make sure you have ili9486.ko in your ko module folder: modinfo ili9486 Can you use the DTS that I published in: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446 But change the "compatible" line with waveshare,rpi-lcd-35 , Delete the stuff under the "compatible" line, until the "}vsync-len = <0>;", and replace it with what you had in your DTS. Change these lines, if they are different: spi-max-frequency = <24000000>; rotate = <270>; bgr; fps = <30>; buswidth = <8>; regwidth = <16>; Reference: https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/piscreen-overlay.dts

then this topic is not applicable

Orange pi 5. In the m.2 slot there is an nvme drive actually.

What hardware do you have? What exactly is in the M.2 slot?

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-4-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-4/wine-proton-10.0-4-amd64-wow64.tar.xz) + DXVK-stripped v1.6.1 >=60fps@1080p (medium/high settings) box64 environment variables: Hollow Knight

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + ge-proton10-29 (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton10-29) (GE-proton is more likely to be segment fault-proof than other wine-proton versions) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.4.1 ~40fps@720p (medium settings, no AA) box64 environment variables: Fallout New Vegas

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + ge-proton10-29 (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton10-29) (GE-proton is more likely to be segment fault-proof than other wine-proton versions) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.4.1 40~60fps@720p (medium settings, no AA) box64 environment variables: Fallout 3

Is this guide still relevant? Armbian-config has a completely different menu now

You are not using Armbian. Ophub is a fork of Armbian. They do not contribute to Armbian development nor do they participate in these forums. You need to go to ophub to ask this question, as no one here can help you.

What is in armbianEnv.txt then? Anyway you need to load and edit it such that you make sure loglevel=7 Then there will be more text after Starting kernel ... You also seem to have a power and/or reliability problem w.r.t. cables as characters are missing in your debug log text.

High chance this uses some proprietary hardware for 3.5mm audio jack. It has been like that for decades and you probably need to find some firmware blob somewhere maybe. I have also a similar situation, most part s of the computer work fine with Debian Trixie etc, but it took ages to get sound working and still buggy, endless beep or crash occasionally. If you are lucky is it maybe only a mute setting or so, use aumix etc to look what is going on. Not something Armbian specific I guess, but up to you to figure out. Then also mention various versions, what BIOS/UEFI version the computer is loaded with, what Armbian kernel and also specific image release (if it is an unmodified image writer based installation).

I recently got this tv box emulator thing but i now emulate games on my laptop for convineince. I decide to download armbian on the tv box so that i can set up pi-hole for network wide ad blocking. Ive tried multiple times but i cant see to get it working. Cpu: Amologic S905L Ram:2 gig DDr3 ive been downloading this version https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_jammy_arm64_server_2026.02/Armbian_26.02.0_amlogic_s905l_jammy_6.1.161_server_2026.02.02.img.gz been using this dtb meson-gxl-s905x-p212.dtb been using this u bootfile named: u-boot-s905x-s912 To reboot the system there is no button in the AV port and the box refuses to download any apk or app for terminal emulator, Developer tools are not available,threfore i prefer to do it through the update method. the file structure Ive been following these instructions from gemini https://gemini.google.com/share/1e335432197f https://gemini.google.com/share/0a6ce8a19d0c Please ask me if you need more info I also asked in reddit btw

Hi, is it still working now?

moved

@sicxnull This might be the patch that fixed it. It's in mainline u-boot now. I would use a newer u-boot. https://lists.denx.de/pipermail/u-boot/2025-March/582900.html