All Activity

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/

If there is anyone still running an older version of the kernel and the USB-C is working it would be helpful if I can get a copy of your rk3588s-odroid-m2.dtb.

Hi rock5b user 🙂 My sbc hangs after 8-14 hours on the network. no ping from inside or outside works # ip link - show eth0 up after the commands ip link set eth0 down ip link set eth0 up - the network worgs again, https://paste.armbian.com/tiqabekoje - any hints for this issue?

I initially tried the instructions in the original post and it didn't work for me. On an allwinner h618 box with a mali-G31. I then spent pretty much all day today trying to find a fix. I came across a post on here stating the version of mpv that works with v4l2 needs to be compiled with the same package versions as ffmpeg or something along those lines. When I first tried the instructions I already had mpv installed and I remember it stating that it didn't update it. So for a hail mary I ran apt remove ffmpeg and apt remove mpv. Then I ran the instructions again and noticed first one didn't actually run successfully which could have been why they didn't work this morning.... When I copy pasted into the terminal it left the $ signs in there and caused errors. So I manually typed it out and got everything to run successfully. Now everything works. mpv is buttery smooth. Previously mpv stated drm was unsupported now it says "using hardware decoding (drm)". I had checked ffmpeg and it did list v4l2 as supported so maybe that didn't need to be reinstalled. Anyway, if it hasn't worked for you maybe try uninstalling ffmpeg and mpv and running the commands again.

And now I've hit a road block. I can't get video acceleration to work. VLC just displays a blank screen no matter what output I select and MPV playback is very stuttered. I wanted this box to act as an Emby client, got it all configured to load emby via the ir remote and got all the functionality working but when I play a video it's so choppy it's basically unwatchable. 576p is almost bearable, 1080p is not. I've spent all day on it and got nowhere. I've followed the instruction in this post but it made no difference - Repository for v4l2request hardware video decoding (rockchip, allwinner) edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same.

Installed to the EMMC with armbian-install and no issues it all. Took about 10 minutes and now boots from the EMMC with no SD card inserted. I think I paid $35AU for this thing and it came with the remote, a bluetooth keyboard, HDMI cable and power supply. Absolute bargain when you compare it to the current price of Rasperry PI's especially when it comes with it's own case and internal storage. Thanks to everyone who contributed to getting these images out there, it's fantastic. I've also got the IR remote working. I followed rafman's post but this didn't fully work for me. It allowed the remote to work and I could see it was working with ir-keytable -t but the desktop and any open apps wouldn't respond to it. The solution was to copy the toml file to /etc/rc_keymaps/magcubic.toml then edit /etc/rc_maps.cfg and add the following to the bottom of the file * rc-empty <whatever_name>.toml * rc-empty magcubic.toml Adding the line to the rc.local file was not required. I've attached a picture of the remote and the toml file I created. I didn't map the buttons in the top right section as this remote has a learning function and you're supposed to learn the codes from your TV remote. But here are the codes my remote was using for these buttons by default. Power 0x1f1 Set 0x1f2 TVIN 0x1f3 VOL- 0x1f4 VOL+ 0x1f5 Edit: If you are going to use on media player apps you will probably want to edit the toml file and change "KEY_OK" to "KEY_SPACE". OK doesn't let you select things with the OK button but SPACE does. magcubic.toml