All Activity

@jock Than you for the hints. If I measure on all (except GND) UART Pin 3.3V is not indicate that all resistor in place? Regarding the rk3399 schematic design, there should be some 100 ohm resistors there. To be honest for me was also very difficult to find the MaskRom pins, search something what is not there is a bit challenging. I measure all black SMD item (far as I know they are resistors), but non of them 100 ohm. (The board other side I do not see any missing resistor) Could you please advise me what I need to look? There is 3 point where possible to solder resistor, how to identify which one I need?

You would just burn your downloaded image file to any USB storage, just like you would to an SD card (i.e. plug the USB storage into another device and burn the image to the storage)

I've setup an Armbian build environment that was able to build a Rock-S0, trixie, minimal image. Using the patch for the Rock-S0 also rk3308b based, as a basis, I would like to create a sv06-Ace patch using the rk-kernel.dts that I managed to pull from the OEM SV06 Ace firmware. If I get a working Armbian image for the SV06, Mainline klipper should be doable. Can someone point me to the documentation on howto do this. rk-kernel.dts

Thank you. I have managed to successfully boot Armbian from SD card. Android is preserved. Now I am trying to install (move) Armbian (the "/root" partition) to an external USB drive. I run "armbian-config", then I pick "System" --> "Storage", but no "Install" (Copy the running Armbian system to another device) option is listied (according to the documentation here). I get only the following items: Download a fresh, official Armbian OS image and write it to a device Enable read only filesystem Enable Network filesystem (NFS) support etc... I have tried also in Terminal: "armbian-config --cmd STO001" but I get an error. In the instructions for TV boxes here it says: "running the shell script in the /root directory: install-aml.sh" But it refers to installing (moving) Armbian to the internal eMMC, if I am not mistaken. Is it possible to install it either to an external USB HDD or internal SATA HDD?

@BigDi I was able flash the Image Armbian_26.2.1_Nanopim4v2_trixie_current_6.18.8_minimal.img.xz to the emmc and start Armbian on the device. Interesting that Wifi (Realtek RTL8821CU) is work well but Ethernet not.

With a lot of trial and error I figured out the issue but not the cause. This seems to only effect HEVC (x265) videos when drm is successfully enabled with MPV from this repository. If I try a different player, they play fine but no hardware acceleration. If I encode the videos to x264 they play but hardware acceleration fails with the following error [ffmpeg/video] h264: v4l2_request_probe_video_device: set controls failed. Invalid argument (22) The issue is the width of the video. Outside of certain ranges it will display a black video (audio works). It doesn't seem to matter what the height is set to. Eg) 704x480, 704x960 image is displayed. 706x480, 706x960 black screen The ranges go for 14 pixels and each range is separated by 50 pixels. eg) widths in the range of 690 to 704 display an image. Widths between 706 and 752 display a black screen. 754 to 768 display an image. It's a strange one.... Here is a list of ranges that work. Any widths outside of these ranges produces a black screen. It only goes up to 1984 but I'm sure the same rules would apply above this value.

PREEMPT_RT is fully merged in mainline Linux as of 2024 (https://en.wikipedia.org/wiki/PREEMPT_RT).

Here is the updated image with Wifi and EMMC boot https://github.com/sicXnull/armbian-build/releases/download/mxqpro/Armbian-unofficial_26.02.0-trunk_Mxqpro-h313_trixie_current_6.12.74_cinnamon_desktop.img.xz

I just tried booting this LibreELEC test build on my nanopi R6S and to my amazement everything worked great in that build/kernel/bootloader. This means it is technically possible and the ingredients are out there, to bad it isn't on Armbian yet...

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.5.3 30~40fps@720p (low settings, texture high) box64 environment variables: RESIDENT EVIL 6

I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.

Dear @Werner , Thank you very much for your quick reply, and sorry for the delay on my end (I started a new job last week). If this board is not yet compatible with Armbian, then why this article ? EDIT: FriendlyElec's Wiki seems to imply that the board is compatible with Armbian's M6 / T6 and R6 images... https://wiki.friendlyelec.com/wiki/index.php/NanoPC-T6_Plus#Install_OS Best regards, Samuel

Thanks for your insights @eselarm. I was led to believe that the bootloader could not have any impact on this - guess AI is wrong again 😅 Anyhow I am running EDK2-UEFI v1.1 so might try one of the later artifacts

Please read the FAQ and installation instructions linked on the download page. https://www.armbian.com/amlogic-s9xx-tv-box/

thank you for your reply! I reverted to the stock ubuntu for opi5 for now. I will have a new device in my hands in the next days, I will then try this

hi @spaceship we 'need to start working on it', what that means is that if you search around sufficiently, it is likely u-boot (the bootloader) and linux already supported A733. the task is 'system integration' to build that into Armbian. But as with all things, it means work, to spend hours / days figuring out how to do that and to do so and send a pull request for Armbian to include it. The challenges in life is such that most of us (including me) has very little fragmented time / energy to work on it. Perhaps that if more users 'request' it and support Armbian by way of donations, maybe they'd try to put it together and complete this work. The initial integration is one thing, the trouble is that linux keeps moving and linux 7.0 is about to drop. Hence, say you take what is there now integrate it, and no sooner 7.0 is out, you need to keep maintaining it. Hence, for a more sustainable setup, perhaps is for the community to fund Armbian to do so with donations, and efforts from the side. it is good for the community to support this effort both finanically and efforts from the side, this is to ensure that there is no "influence from a controlling (3rd) party" (possibly including a govt) i.e. no conflict of interest, e.g. to try to embed exploits in it for the govt's or 3rd party purpose, as in that the project is truly open source and inspected to prevent such exploits. but for what is worth, what it takes is a 'project' to get from here to integration e.g. in an 'edge' 7.0 kernel. --- off-topic but related, the security situation affecting commonly used commodity devices sold globally is *bad* https://www.kaspersky.com/about/press-releases/kaspersky-discovers-keenadu-a-multifaceted-android-malware-that-can-come-preinstalled-on-new-devices https://securelist.com/keenadu-android-backdoor/118913/ https://www.tomsguide.com/computing/malware-adware/dangerous-new-keenadu-malware-found-pre-installed-on-cheap-android-phones-and-tablets-how-to-stay-safe https://www.forbes.com/sites/daveywinder/2026/02/17/android-backdoor-pre-installed-on-devices---thousands-already-infected/

Hello NickA, fire-hound from discord here ... You do a tremendous service for us all, keep it up buddy! I loaded your recent build from here: https://github.com/NickAlilovic/build/releases and can confirm it works on my A7A. It correctly detected my Pimorony NVME Base lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 8M 0 disk mmcblk0 179:0 0 29.2G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot └─mmcblk0p2 179:2 0 28.6G 0 part /var/lib/containers/storage/overlay /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part /srv/dev-disk-by-uuid-b28b2f5c-ee2e-4ded-959e-22bc63051b1d and: screenfetch _,met$$$$$gg. root@radxa-cubie-a7a ,g$$$$$$$$$$$$$$$P. OS: Debian 13 trixie ,g$$P"" """Y$$.". Kernel: aarch64 Linux 6.6.98-vendor-sun60iw2 ,$$P' `$$$. Uptime: 11h 14m ',$$P ,ggs. `$$b: Packages: 661 `d$$' ,$P"' . $$$ Shell: bash 5.2.37 $$P d$' , $$P Disk: 4.9G / 271G (2%) $$: $$. - ,d$$' CPU: ARM Cortex-A55 Cortex-A76 @ 8x 1.794GHz $$\; Y$b._ _,d$P' RAM: 534MiB / 7928MiB Y$$. `.`"Y$$$$P"' `$$b "-.__ `Y$$ `Y$$. `$$b. `Y$$b. `"Y$b._ `"""" So far so good The issues: 1. The typical Armbian image has a module in the armbian-config and radxa's rsetup where one can set up the two leds conveiently to other than full on and heartbeat for the green and blue gpio leds respectively. I find it to be a nuisance to dig for that manually 2. The Ovralys module in armbian-config is returning an error - when entering DTO001 module (Device Tree Overlays) saying: Invalid overlay_prefix that might require deeper digging into the issue i guess? What works: Open Media Vault registers the NVME nicely as additional storage. I suspect booting off that NVME would work for an updated SPI bootloader i could test that if you want me to? If you need any other info or output I stand at Your disposal 😁

You should also consider the bootloader (type and version), in principle you do not need the dtb- package as the dtb files are also in the kernel package (enough when doing own extlinux). U-Boot philosophy is to provide just enough so that the kernel/initrd/DTB can load and started. Audio is not part of that I think. LE certainly used other bootloader and as you already showed has more non-upstreamed patches. See my experience:

@ag123 what does that mean exactly? I can't stand custom GNU/Linux builds from Orange Pi's company. I have a OPi Zero 3 and few OPi zero 2w, they're awesome with armbian, no issues at all. But now using the OPi Zero 3 as an hostap, i'm noticing that the throughput regarding network io seems to be a bottleneck, i was looking for something cheap and came accross this OPi 4 Pro. Thank you for doing this research.

Hello, I would like to use Armbian on control hub too but without disassembling it. I tried latest renegade image and usb and internet were not working. What is exactly everything I need to change in the image to make the usb at least work? I tried enabling the rk3318-box-led-conf3 in some file I forgot but it did not work, maybe else more needed or I did it wrong. I would be very grateful if you could write what I need to change! I do not want to disassemble since it's legality in FTC rules is ambigous for me.

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!