All Activity

If you are talking about lag with discord webpage, vpu accel won't help because there is no video played in discord. You can check chromium's gpu status at chrome://gpu, see if the gpu driver is working. My ppa only packages chromium for noble, ubuntu 25.04 is not supported. While chromium in my ppa only add patches to let chromium use vpu when playing videos, this should not help improving discord webpage performance.

Hi, Great work thanks! Why no 25.05 for banana pi M4 zero? Perhaps are you waiting for some additional work on missing bluetooth support for rev2? @c0rnelius ? Denis

I'm in a similar situation. But I can't access my board anymore. I cannot put the board in maskrom mode anymore. Still stuck on this one?

@KrzyPac Ur welcome.

I can not get sound out of AnalogCodec LinOutL/R pins either.

Thank you very much c0rnelius. After applying your fix SPDIF works on VONTAR X3 Amlogic S905X3.

Right so 1GB - display framebuffer allocation. Can you confirm HDMI works as it been a while since I built an system image with 6.1 kernel. I dont recall display issues, just problems relating to SPI at the time. Anyway kernel 6.1 is no longer supported, even as a legacy kernel. The earliest kernel you can now build with is 6.6. I am suprised that the mirrror archives I have looked at so far do not feature any 6.6 kernel builds for the Cubieboard. Thats not to say it would be impossible to compile with an older kernel but could prove more trouble than what it is worth. I am interest to see what if encounter any stability issues when booting an edge kernel. Interesting, that is the exact same RAM chips used on the pcDuino2 but the additional text enscribed is different. Just to be safe can you run memtester to see if it picks up an errors. For example: sudo memtester 64MB 2. Even without re-compiling the entire system, what we can do is replace the targeted board dts. This should be doable given you already have a serial link, but you will need to catch uboot early on to hault to boot process to get a uboot prompt. Then running setenv ftdfile sun4i-a10-topwise-a721.dts to see if the onboard display works. *update* - upon checking kernel sources the previously mentioned sun4i-drm patches are no longer necessary as the changes appear to have been included in the latest sub revision of kernel 6.12.30 All the best Ryzer

Actually its the opposite so it must have been something else. Etcher is known to be broken for bigger images (desktops). There is some bug in the .xz decompression method used by Etcher. I am using only USB imager for at least a year and haven't run into any problems. At least not on this level.

moved

yes I can confirm

Is the overlay_prefix line the same in both too?

I will try but I have this line working on exactly the same box with a older build that was upgraded

If you remove the "rk3588-" from each it should work as that is included in the overlay_prefix

Thanks - I'm worried my main issue was with the overlay loading issue I mentioned. I did try 6.15 but prob need to retry with the hack with overlay-user. But man... it is SO incredibly simple to switch the kernels.

@KrzyPac I suspect you just need the DTB correct? Git clone the armbian/build, place the patch in patch/kernel/archive/meson64-6.12/ and build any meson64 board. ./compile.sh KERNEL_GIT=shallow BRANCH=current EXPERT=yes KERNEL_BTF=no kernel BOARD=bananapicm4io The DTS files are one of the first things to be compiled, so once you see them finish, hit CTRL+C to cancel the build and then grab the DTB file from the source dir: cache/sources/linux-kernel-worktree/6.12__meson64__arm64/arch/arm64/boot/dts/amlogic/ That is the easiest way I can think of doing what you want to achieve. Here is an updated PATCH and pr-ecompiled DTB. NOTE: There are different variants of the X96-AIR. I have two. One that uses Qualcomm for wireless and another that is Realtek. Each variant requires a different DTS for it to function properly. This patch is for the Realtek variant. x96-air-gbit-spdif-jack-i2c1-openvfd-jl2xx1-bt-support.patch meson-sm1-x96-air-gbit.dtb

See for more details but without using the overlay-user folder - I was not able to get the pwm to work on a fresh download.

OMG - I can confirm this issue is also happening on orange pi 5 with latest armbian v25.5.1 + Linux 6.1.*-vendor-rk35xx This is my armbianEnv.txt The pwm only loads when I copy it into overlay-user. The really strange thing is that I have two of these boxes and the one that went through upgrades is working just fine but I'm trying a fresh install on another and no way to get the overlay to work except this hack

I have the file .../dts/amlogic/meson-sm1-x96-air-gbit.dts and the patch 004-arch-arm64-dts-amlogic-meson-sm1-ac2xx-tv-boxes.patch. How to patch a dts file and generate a dtb file from it. I am asking for help.

https://paste.armbian.com/cawuyeyice

Selling a fully working Helios64 NAS from Kobol. It has been running continuously since purchase without any issues. Includes 4x Western Digital Red 4TB HDDs (16TB total), all in good health and used only in this setup. All original parts are included: case, power supply, cables, and accessories. Note: the 1GbE Ethernet fix has not been applied. Selling because I recently upgraded to a new NAS. Located in the Netherlands. Pickup possible or shipping within the EU. Contact me for pricing or questions.

Thanks. Etcher worked. Now my device can boot successfully. I will use Etcher instead of USBImager for armbian in future.

6.12.y current is far from being feature-complete and won't get any new ones but bug fixes only. Try 6.1.y vendor or 6.15 edge.

Been trying to enable multiple overlays on kernel 6.12 (orange pi 5) but I am not able to get any pwm device in /sys/class/pwm/ The i2c also seems to be missing. Is going back to 6.1 the safest option? Thanks

Armbian 24.5 works normally, but this issue occurs in versions 24.8, 25.5 and 25.8 [ 0.872698] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 0.872852] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361552] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 2.361723] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361912] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 22.444508] hdmi-audio-codec hdmi-audio-codec.8.auto: Only one simultaneous stream supported! [ 22.444524] hdmi-audio-codec hdmi-audio-codec.8.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 0.871390] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 0.872604] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.360057] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 2.361397] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 2.364674] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 2.510919] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.