All Activity

BTF is hungry for memory, yes. KERNEL_BTF=n and it needs less. On 16Gb+ machine you should be fine. If not memory is eaten away by something else.

I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video I've set it to use mpv but it seems the emby package has it's own version of mpv and ffmpeg baked in as the versions reported in the mpv.log are different and it fails to use drm, it seems the following errors are the problem. [ 0.028][v][libmpv_render/drmprime] drmprime hwdec requires at least one dmabuf interop backend. [ 0.028][v][libmpv_render] Loading failed. [ 1.422][v][ffmpeg] Unable to open any dma_heap device [ 1.422][e][ffmpeg/video] hevc: Failed to set destination format: S265 1920x1080 [ 1.422][e][ffmpeg/video] hevc: Failed setup for format drm_prime: hwaccel initialisation returned error. When I launch the same file directly in mpv, it plays fine and doesn't have the errors above. The system has mpv version 0.35.1 but emby reports using 0.38.0-dirty. Same with ffmpeg and all the associated lib files, they are all higher versions and I can't find duplicates in the system so I believe they are packaged as part of the emby app so I really doubt it's something I will be able to fix unfortunately. Tried Kodi and that's missing all the acceleration settings. Jellyfin client doesn't work with an emby server anymore. Just to attempt to keep this on topic, I don't suppose there is anything I can config with the image that might resolve the dma_heap errors? edit: I figured out a solution, emby lets you configure an external player. I just set that to /usr/bin/mpv and it works.

Issue booting Multitool on RK322x Box (Kingston eMCP) - Red IR Light Only Hi everyone, First of all, thank you for this incredible project. Bringing new life to these generic boxes is vital work. I am struggling to boot the Multitool on an "RPC Plus" TV Box. Here are my hardware specs and the steps I’ve taken so far: Hardware Specs: SoC: Rockchip RK3229. Storage/RAM: 8GB Kingston eMCP (Chip ID: O8EMCP08-ELSCV100). SD Card: 16GB Lexar microSD (Class 10). Board LEDs: POWER, NET, and IR. Since the official download links for the Multitool are currently down (I get a 404 error idk why), I had to compile it myself on a Debian machine using the https://github.com/paolosabatino/armbian-build?tab=readme-ov-file repo and the ./create_image.sh rk322x script. I flashed the 500MB image to a 16GB Lexar card using BalenaEtcher and placed the Armbian minimal forky (6.18.7) image inside the /images folder (file name Armbian_community_26.2.0-trunk.357_Rk322x-box_forky_current_6.18.7_minimal.img.xz). The problem is that the box just won't boot from the SD card. When I hold the reset button and plug the power, the only thing I get is a static red light on the IR LED—no HDMI signal, no activity on the Power or Net LEDs, nothing. Android still boots fine if I pull the card out, so the hardware is okay, but it seems the boot process is hanging. I've tried both the reset and update buttons with different timings but no luck so far. I’m attaching pictures of the board and the chip. Any help to get this thing past the red light would be great. I'm putting the pictures of the board here in case it helps. Thanks! IMG_6826.HEIC IMG_6827.HEIC

You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv.

Hi if anyone have interested, this is dtb files and orangepienv file 🙂 allwinner.zip

I found the problem: [ 2299.766819] Out of memory: Killed process 43216 (pahole) total-vm:8235296kB, anon-rss:4667816kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:12912kB oom_score_adj:0

@maxsub: Out-of-RAM may be possible if it simply spits out "killed". My machine has 32 Gb RAM and 16 Gb swap, does not encountered the OOM-killer lately. Until now, but exhausting RAM is probably kernel-dev-hobby 😗

pahole is current. The build fails inside the docker-shell when manually invoked as well. Looks like the BTF invocation is getting killed (maybe needs more RAM)? 🐳|🔨] BTF .tmp_vmlinux1.btf.o [🐳|🔨] Killed root@c408bbb4ccde:/armbian# apt show pahole Package: pahole Version: 1.25-0ubuntu3 Priority: optional Section: universe/utils Source: dwarves Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Thomas Girard <thomas.g.girard@free.fr> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 2012 kB Depends: libbpf1 (>= 1:1.0.0), libc6 (>= 2.38), libdw1t64 (>= 0.157), libelf1t64 (>= 0.142), zlib1g (>= 1:1.1.4) Breaks: dwarves (<< 1.22) Replaces: dwarves (<< 1.22) Homepage: https://git.kernel.org/pub/scm/devel/pahole/pahole.git Download-Size: 275 kB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports noble/universe arm64 Packages Description: set of advanced DWARF utilities

Hi Gaetano, Maybe the issue is with g_mass_storage rather than OTG USB? "The "dr_mode" property controls whether OTG acts a peripheral or host. By default this is set to OTG mode so you shouldn't need to change anything. In my case I prefer to have OTG set as host for which I have this simple overlay: dts-v1/; /plugin/; /{ compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20"; fragment@0{ target = <&usb_otg>; __overlay__{ dr_mode = "host"; }; }; }; I find it works ok for reading a USB stick. It could be that you have to instead change dr_mode = "peripheral" but seeing as it shows up as a drive this may not be necessary. What kernel version are you currently? Are there any errors that show up in the logs? sudo dmesg | tail -n 20 There is also usb_f_mass_storage however this would need to be manually added as it is not currently included by default within the list of installed modules (Well at least was not on the last build I ran) Best of luck Ryzer

Next idea: run ./compile.sh kernel-config and switch off DEBUG_INFO_BTF. But this should not happen. Also (probably) this BTF stuff now pops up here and there anyhow...

The try ./compile.sh docker-shell to start the Armbian compile environment. In the VM, check the pahole package version. If it's missing, you probably need to re-create by removing all from docker images|grep armbian which should be re-created on the next round. <whisper><small><hidden>And if nothing helps, docker system prune --force --all?</hidden></small></whisper> HTH // Sven-Ola

@sven-ola I have docker. The build BRANCH=current works but BRANCH=edge errors in the BTF section.

Hello @maxsub Compiling without Docker? You probably need apt-get install pahole, since ./compile.sh docker-shell shows: From the relevant kernel Kconfig: HTH // Sven-Ola

@sven-ola I did try the BRANCH=edge build and got an ELF error: 🐳|🔨] libbpf: failed to find '.BTF' ELF section in vmlinux.unstripped [🐳|🔨] FAILED: load BTF from vmlinux.unstripped: No data available [🐳|🔨] make[2]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 255 [🐳|🔨] make[2]: *** Deleting file 'vmlinux.unstripped' [🐳|🔨] make[1]: *** [/armbian/cache/sources/linux-kernel-worktree/6.18__spacemit__riscv64/Makefile:1242: vmlinux] Error 2 [🐳|🔨] make: *** [Makefile:248: __sub-make] Error 2

Hello @maxsub! Thank you for testing this. Especially on the R2S, since I do not have this device at hand. I am in the final spurt to get this merged into Armbian, but there are one or two rabbits to be hunted down (aka coding quirks). You compiled BRANCH=current and kernel=6.6.99. Can you repeat and recompile with BRANCH=edge, which is the same u-boot but should give you kernel 6.18.7? LG // Sven-Ola

can confirm: I installed the latest image `Armbian_25.11.1_Radxa-dragon-q6a_noble_edge_6.18.0-rc6_minimal.img` and wifi works. After an `apt upgrade` wifi doesnt work anymore... Solution: same as on the Rock 5C @just_facking_about type in `sudo dpkg-reconfigure aic8800-usb-dkms` and reboot the device

It's this image from @Nick A github. Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img I had to copy over a few firmware files to get wifi/bluetooth working but otherwise it's unchanged.

Hey Paul! Thanks for flagging this, going to look at it today and send a patch, the name probably got changed in the TI tree relatively recently so hadn't caught it yet. Best, Andrei

This is fantastic work! Thank you so much. I was able to build from source. Tested it on RV2 and R2S and both work great. Your changes are patched on to the 6.6.99 kernel as far as I can tell. Are these going to be merged upstream and make their way into 6.17? Thanks again for your amazing work.

Thank you for the comment Jock Yes, I know that Trixie's mpv made some changes that made it incompatible with your ffmpeg+v4lrequest package. I tried to compile mpv, and I wasn't sure of how to do it. I asked for help in the mpv github, and someone told me to wait for ffmpeg to merge this function. https://github.com/mpv-player/mpv/pull/14690#issuecomment-3369553163 Recently, I got more suggestions to build ffmpeg for Trixie https://github.com/mpv-player/mpv/pull/14690#issuecomment-3828170966 Boringname... can you specify which Debian version, Linux kernel and graphical desktop (kde, xfce, gnome, plasma, labwc, sway)?

I would first check the link, what is on the other side, etc. Also do a flood ping with large enough packages. Or UDP flood, not sure how to do that. Iperf3 might be easier. I have no clue about Radxa OS, never really used it. Maybe also do test boot with mainline based kernel, 6.19 edge I think. And what U-Boot version is used. I use Tianocore EDK2 UEFI v1.1, that might also have effect.

Hi, i think the rpm setting-step's of the onboard fan is to low. - how can this be adjusted? SBC: Rock5b

...or maybe an r8169 driver problem under heavy load dmesg -w | grep -i r8169 [ 5.072779] r8169 0004:41:00.0: enabling device (0000 -> 0003) [ 5.115535] r8169 0004:41:00.0 eth0: RTL8125B, 00:e0:4c:03:00:fc, XID 641, IRQ 166 [ 5.115550] r8169 0004:41:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [ 6.328634] RTL8226B_RTL8221B 2.5Gbps PHY r8169-4-4100:00: attached PHY driver (mii_bus:phy_addr=r8169-4-4100:00, irq=MAC) [ 6.518776] r8169 0004:41:00.0 eth0: Link is Down [ 9.721015] r8169 0004:41:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off [ 9717.405068] r8169 0004:41:00.0 eth0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5227 ms [ 9717.405345] r8169 0004:41:00.0 eth0: ASPM disabled on Tx timeout [ 9717.418437] r8169 0004:41:00.0 eth0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 9941.759110] r8169 0004:41:00.0 eth0: Link is Down [ 9945.329364] r8169 0004:41:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off I have a frigate container running on this sbc. A second Rock 5b (same os version) with 10 docker images but very low traffic run smoth on the same switch with 2.5Gbps. Could someone check which driver Radxa OS uses?

Hello everyone, I'm still having trouble flashing the h96 max m9 to armbian os, I still haven't succeeded in using the maskrom, but the uart connection has worked, is it possible to flash only the uart connection? Please help me with the steps for flashing the H96 M9.

already in the first dmesg part I see: [54475.779558] r8169 0004:41:00.0 eth0: Link is Down [54479.115749] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [54479.115748] r8169 0004:41:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off [55390.928391] br-ce724241dce3: port 1(veth1664549) entered disabled state [55390.928949] veth6932af4: renamed from eth0 [55391.020157] br-ce724241dce3: port 1(veth1664549) entered disabled state [55391.021811] device veth1664549 left promiscuous mode [55391.021831] br-ce724241dce3: port 1(veth1664549) entered disabled state [55391.493933] br-ce724241dce3: port 1(veth1a65439) entered blocking state [55391.493954] br-ce724241dce3: port 1(veth1a65439) entered disabled state [55391.494085] device veth1a65439 entered promiscuous mode [55391.500502] br-ce724241dce3: port 1(veth1a65439) entered blocking state [55391.500519] br-ce724241dce3: port 1(veth1a65439) entered forwarding state [55391.539757] eth0: renamed from vethb9b9ca0 [55391.561925] IPv6: ADDRCONF(NETDEV_CHANGE): veth1a65439: link becomes ready Which means to me that you use containers/docker or so and something on that networking level goes wrong. I think it had nothing specifically to do with Armbian nor ROCK5B. You should figure out what is running on your computer and what is done to networking in general. I do not use containers like seems to be done here, so cannot really help here. I have no clue about your networking setup and plans. I use various bridges and VLANs on my ROCK5B (Armbian Trixie), but all strict manually done by myself, only own files in /etc/NetworkManager/system-connections/