Active threads

I made some patches so that the unified driver / TIM-VX for the NPU works on the A7Z. I am also building a MLIR pipeline that emit TIM-VX code, so hopefully we can get more flexibility running ML models on the SBC soon. https://github.com/MaverickLong/Radxa-A733-NPU-Unified-Driver-Support-Package

@curse well yes i started this port because shift did a static analysis of the firmware with ai. but well its not usable (mostly) and there are obviously differences between the 2 projectors. i would somehow call it hacky, its nowhere near to be stable but for now its acceptable. i dont know if i will ever be able to complete it.

Hi everyone! I tried installing hardware decoding from this link - https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ , but it didn't work for me. My board version is 5.1. Has anyone been able to fix this?

I tried to enable the I2S / PCM5102 service with AI, but unfortunately, despite numerous attempts, I couldn't. But anyone can use a USB audio card. Maybe someone else will figure out how to enable it 🙂 Best regards

Board image

yes, i've studied the schematic well to see if that gave any clues and I have learned that it ties into the Power Management Unit. It remains that the button doesn't work on mainline kernels but does on the vendor kernel. There must be some init step or configuration that's missing.

https://docs.armbian.com/User-Guide_Armbian-Config/System/#desktop Should be straighforward to enable desktop on top of CLI.

Looks like the current-rockchip64 kernel that one receives with apt on PINE64 rockpro64 is 3.18.10 (6.18.10-current-rockchip64), vulnerable to copy-fail. This seems weird because if you go to https://armbian.com/boards/rockpro64 that page says that the "current" kernel for these systems is 6.18.26 and that is what you get when you download the image file. Is there an issue with updating the apt repos?

Things are still very sad with Ethernet. Is this could be related to some low-level timings in device configuration?

First of all, thanks for your reply. Even though you said there are no "vendor-lockin" i felt like so that's why i created a post on this forum as this issue came only after armbian os flash. As i said, after flashing armbian os, i was not able to use MASK button to bypass emmc boot and about a dozen of different os other than armbian failed to boot from SD card. Then i experimented on different methods including the PC connectivity but changing bootloader or os image didn't work as the mask communication is getting lost during flash command run. I deleted boot files from armbian boot partition to check if that fall back to SD card, but there was no luck. However armbian SD card boot still worked. So i confirmed that it is the change in bootloader that armbian made. Then i re installed armbian os inside emmc and used dd command to write the original bootloader images which is taken from the nanopi r6s official eflasher download link. It worked! Now i am able to install other os than armbian. Kindly fix this issue and acknowledge the same, otherwise people like me will think twice before testing latest armbian os next time. Best regards

Ah, this board has n out of tree dt as well which most likely overwrites the patch. Try adjusting this file: ~/build/patch/kernel/archive/rockchip64-6.18/dt/rk3576-nanopi-r76s.dts

I'll give it a go when ready for download 🙂 ljones

I am trying to get the ARM performance assessment setup working (I'm trying to get Mali profiling for OpenCL code) on the Rock 5B+, and I've hit a blocker. The main component to this is some kernel configuration (CONFIG_ARM_SPE_PMU) and a loadable module. Oddly, those work fine in a custom kernel build. What I am hitting appears to be some missing interrupt setup that renders all those components inert. (It has to be a custom build to get CONFIG_ARM_SPE_PMU set. The issue is that even with the kernel configured and the module loaded, the SPE component remains inactive. ARM has its own system report tool which analyzes a setup, and that tool is reporting an issue: And indeed, nothing seems to show in cat /proc/interrupts. The man page for the module suggests this is the issue: It says: KPTI is definitely disabled and the SPE PMU loads (it's in lsmod) but it still doesn’t show in /sys/bus/event_source/devices/. Nothing relevant seemed to show in dmesg either. Frankly, I have no idea where to look for the SPE interrupt, or how to set it up. If anybody has any pointers or suggestions, I'd be extremely grateful.

The TV box is equipped with an AP 6330 WiFi module. The Ethernet RTL module is 8911F.

In case someone finds this useful, I found a way to change the display mode from NTSC (default) to PAL NTSC to PAL: xrandr --output Composite-1 --set "TV mode" PAL xrandr --output Composite-1 --mode 720x576i PAL to NTSC: xrandr --output Composite-1 --set "TV mode" NTSC xrandr --output Composite-1 --mode 720x480i I thought I would have to recompile the whole kernel because the patch isn't working properly but these two commands did the trick. I don't know how to make this permanent but it works in the terminal.

@Ducdanh Nguyen Your board is using a HiSilicon Hi3798MV310. I have no experience with this SoC. The kernel sources for this SoC are too old. You are better off finding another cheap box to run Armbian.

@KV1 I've fixed the build issue above: https://github.com/MarvellEmbeddedProcessors/A3700-utils-marvell/pull/36. I don't think anyone at Marvell pays attention to this old repo anymore so I don't expect it will actually be merged.

Yes it looks like but with reboot on Ornage Pi zero back. After fixing the problem with kernel 6.12.xx https://github.com/armbian/build/issues/8197 now when we use kernel like 6.18.24 we can not reboot OZPI v1. When we run 'reboot' it is rather to power off so it looks like it is a problem with Crust https://github.com/armbian/build/pull/8503 it wille nice to fix this problem with reboot in kernel 6.18.x like was fixed in 6.12.x I know that the Orange Pi Zero platform is on community support, but maybe there will be a volunteer who will fix this problem. but extraargs=reboot=watchdog help solve problem

Thank you for your kind words. For RK3229, I thought it's supported by mainline kernel and you can easily install using method provided by Jock?

We have information on which mirrors are good and which bad. We just don't display it. Good are passed to the redirector.

anyone try on jellyfin? docker jellyfin especially?

@Сан Дич Хуу, good day! How was the process of replacing the kernel and DTB? Is the device working now?

Ok, thanks for such a fast reaction...will have to buy the module, thanks:-)...until it arrives, i will boot from sd, and have system on nvme - found that option under Install on another device in armbian-config. Regards Jan

Did you ever get this working?

I have running v26.2.1 for Odroid HC4 running Armbian Linux 6.18.10-current-meson64