All Activity

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using https://www.armbian.com/orange-pi-zero-3/

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using it seemed to be similar for orangepi zero 2 https://www.armbian.com/orange-pi-zero-2/

Hi I have upgraded an existing x86 Armbian system with kernel 6.6.63 and zfs 2.3.2 to the suggested kernel 6.12.32-current-x86, but I cannot get the zfs kernel module loaded after the latest updates to Armbian 25.5.1 noble. I also tried on other kernels, only the old 6.6.63 seems to work. Normally when you select a different kernel in the armbian-config menu, it should automatically compile the zfs modules if it is activated. It just skips it. But you can of course compile it with the provided DKMS system: the build just finishes fine, without any error, also the install, but when you try to load the module: it responds with: dmesg: I have zfs 2.3.2 on kernel 6.12.32-current-bcm2711 running just fine on a Raspberry Pi 4, so I tested what would happen if I just build a small kernel driver module: root@armbian:/usr/src/dummydriver# cat dummydriver.c root@armbian:/usr/src/dummydriver# cat Makefile So when I run this on the Raspberry Pi 4, I can load the module and unload But when I run this on the x86 machine I get the same error: root@armbian:/usr/src/dummydriver# modinfo dummydriver.ko root@armbian:/usr/src/dummydriver# gcc --version I also tried gcc 11.4.0 Here is my armbianmonitor -u: https://paste.armbian.com/orepumazam Any help welcome! Philippe

i answered in your thread.

https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/ user wdr_s had success with that same lcd. Try it with linux 6.1 (check the success case) If you have a file named orangeEnv.txt... you arent using armbian yet! Make sure to use armbian-add-overlay In the ili9341 or ili9488 there's someone trying with orange pi zero 2w, which is very close to zero 3

About wrong color i think the driver cause it. Driver for render image in this kernel sunxi is ili9486drmtft. I get right color in raspberry pi 4 but raspberry pi 4 use fb_ili9486. On this orangepi zero 2 w, i try 3 different OS but still get same wrong color after adding dts for ili9486 1. Orangepi OS Kernel 6.1 2. Armbian OS Kernel 6.1 3. Debian Bookworm 12 Kernel 6.1 All using ili9486drmtft and get wrong color I also try to change bgr value in dts, but it only create change in .../spi@1.0.../bgr not the color on screen I try to get source code https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9 to change the bgr field in driver, but i can't insmod the module i build. It say invalid symbol I see someone comment that after kenel 5.4 in repo sunxi remove fbtft_device, so we can't add the fb_ili9486 . The Offical OS supported by Orangepi has Kernel 5.4 Debian, i use it, but after add overlays and reboot, it seem wrong setup, ethernet not working, and i don't know why.

Hello @robertoj I think i have the same problem with @RimYT above about wrong color with ili9486, i'm using screen MPI3501 which is clone screen of waveshare tft35 I apply the same device tree and guide in https://github.com/dev-null2019/orangepizero2w35tft. The screen work but i wrong color, it seem revered Red. —> blue Green —> red Blue. —> green I also write detail in here I know my problem not totally related to your topic, but can you suggest me what i should to check more

So yes, HDMI does work on the archived image. Interestingly, USB does not work. I tried to connect a keyboard and a mouse but that did not work. So, on the HDMI terminal I successfully reach the login screen but can't go past that. But through ssh/serial I can work on the system. I tried memtester and it does show some issues with the memory, but overall, this archived image has worked without issues. I was able to use octoprint_deploy to install Octoprint, but again since USB does not work couldn't connect the printer itself. To replace the dts file easily I need input devices to work, I will try and see if I can do that over serial. And the next thing to try is to compile using an edge kernel and report back. Thanks, Shivam

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