OttawaHacker

I have edge kernel installed and working. I compiled the v4l2 ffmpeg but some of my av1 videos are not working. After some digging I noticed that v4l2-ctl --device=/dev/video4 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture Multiplanar [0]: 'VT12' (Y/UV 4:2:0 (4x4 Linear)) [1]: 'NV12' (Y/UV 4:2:0) Shouldn't this include the 10 bit formats as well? (NV15?) Does anyone know why the 10 bit format is missing in the kernel? Is this specific to the orange pi? I found this GitHub - dongioia/rock5bplus-rkvdec2: Rock 5B+ (RK3588) on mainline Linux 7.1: V4L2 stateless RKVDEC2/Hantro hardware video decode (VP9 / H.264 / HEVC / AV1) up to 4K, plus a guide for stock Chromium 150 with clean in-browser HW decode (VP9 Mali green artifact fixed upstream in the Chromium 150 ANGLE roll). HDMI 2.0 4K@60Hz, on Beryllium OS. · GitHub Going to test their patches, I am unsure if they are related to the issue but they list a 10 bit VP9.

Thank you!! I did a `nand-sata-install` from my working copy and now the images are finally booting up. Wifi is WORKING with mainline kernel 🥳

I never used the UART serial console - is there a guide to set that one up? Also I tried multiple cards - and no difference. Usually any good image would at least make one flash of green light but no luck with any of these (ones published on site and freshly built). Is there a way I can check the u-boot version on my working card?

Only vendor has had the ap6275p driver but it looks like it was integrated to mainline and edge https://github.com/armbian/build/pull/10289 Sadly I cannot get any of the recent images to boot. The board doesn't have single peep of green light with a recent image flashed.

And same with a freshly compiled image with 6.18 btw - it doesn't boot. Going to test with edge kernel...

Got quite excited seen that the wifi driver is finally available and was going to test the browser and graphic acceleration in the current kernel but I flashed 3 times the Desktop image with Gnome/Current 6.18.33 and it did not boot. Is there possibly an issue with u-boot?

I have my kernel locked to 6.1.75 but still after 25.8.2 update, I lost all USB devices on both of my Orange PI 5. Only the USB3 port is working. The only way I've been able to get access to the USB is by switching to the latest `current` kernel... Any clues on what is going on? Firmware or kernel upgrades are not doing anything... where can the issue be???? I tried downgrading to many different versions but beside the current branch, USB is gone. Thanks

I had to use 6.1.75 to get the analog out working. It is the only version where the analog out works - it shows in other versions but there is no playback

/dev/serial is also gone on 25.8.2

yes I can confirm

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

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.

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

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

I sent a PR on the build with a patch - not sure about removing that log entry directly from kernel but on most common armbian builds, this log entry is a pain

With the vendor kernel, my logs are getting flooded with drm error messages Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 this seems an old issue (Kernel messages flooding logs · Issue #86 · Joshua-Riek/ubuntu-rockchip) - it doesn't seem complicated to fix, I am familiar with the build system but I cannot figure out how I can create a patch for the kernel source. Which repo should I patch? Can I just put my patch into build/patch/kernel/rk35xx-vendor-6.1? Thanks

Also just tested ubuntu-rockchip - this one works perfectly (6.1 vendor) and is stable so there must be some patches missing in the armbian-linux repo. I don't mind looking into that but no clue how to test this with armbian-build

So current aka 6.12 is a no-go because armbian/bcmdhd-dkms: Broadcom ap6xxx dkms package doesn't build yet on 6.12 (support for the Orange Pi 5 Max with kernel 6.13-rc1 by shenmintao · Pull Request #7537 · armbian/build) Vendor 6.1 is unstable, after boot, lsmod, modprobe are broken and there are pcie errors. I'm going to assume something is wrong with the dts file. I was hoping to try some hacks there... From what I understand that one is hosted on armbian/linux-kernel but how can I tweak it for the build? I see the dts files in the uboot/legacy but is there any way to customize the dts files without cloning the whole linux kernel repo?

I'm happy to help - but so far the build is unstable and hangs when I request lsmod. The wifi doesn't seem to be enabled out of the box. I checked on the orange pi build and they use the wl module (broadcomm) however I think there are some serious pcie exceptions in the armbian journal that cause the box to blow up. I will probably try ubuntu rockchip version and see if their figured out all the opi max 5 details. If so, I assume this could be a start to bring more board features to armbian?

Oh lol of course 😛 Are there only trunk releases for the opi-max? Was hoping to get a current build instead, anyway, if this doesn't exist, I will build my own image. I got the opi 5 max working by changing the dtb on the 5 plus image - booted fine except I have no wifi.

Was looking at the build repo and noticed there is already support for Orange pi 5 max (add support for orangepi5 max · armbian/build@b38e4b2). Any specific reason there are no "official" community builds, or did I miss it?

That is sad to see,.. were there specific reasons that Joshua did not contribute to Armbian instead? Has the Armbian team had better luck with Rockchip? The issues he mentiosn with SDK sound quite serious.

This is insanely good!!! I have a custom HA setup but was wondering if the armbian HA builds support the official add-ons. I think the official add-ons let you install MQTT, databases and other docker images with a single click.

Hopefully this is not a stupid question but I came across Joshua-Riek/ubuntu-rockchip: Ubuntu for Rockchip RK35XX Devices (github.com) when searching for my video playback issues. Does anyone know how this compares with the current armbian release with vendor kernel? Are all the fixes from that release integrated in armbian or does it go the other way?