Actually spoke to soon, seeing this issue on the 6.18 kernel but happens randomly, its a known upstream issue that has been fixed in 7.1, but you guys should back port this fix here: Upstream fixed this exact Radxa/RTL8852BE problem by retrying the eFuse operation five times. The fix is https://chatgpt.com/g/g-p-69619e56d4d48191866d830f3ebddfc0/c/6a5ee909-da2c-83ea-981e-de8591585c8c, with the Wi‑Fi/BT contention confirmed by the Realtek maintainer in the patch discussion https://patchew.org/linux/20260301042422.195491-1-christianshewitt%40gmail.com/?utm_source=chatgpt.com. The fix: Is absent from 6.18.28 kernel. Is still absent from vanilla 6.18.39. First shipped upstream in Linux 7.1. A matching ROCK 5B+ Armbian trace shows the PCIe device and firmware loading successfully, followed by the eFuse failure and error -16. Matching Armbian report.

i got the same problem my ethernet is gone. how does one downgrade i cant figurer it out at all

More likely: friendlyelec is maintaining a separate patch (source code additions to the official ffmpeg), that allows it to do it. The code should be available in the friendlyelec github, to be shared with the public. "No v4l2request"... that means that they implemented another protocol and/or another kernel module to work with the video decoder.

Thank you for your reply. My H96 Max M9 is running Android 14 with the original stock firmware. I have not installed Armbian or any Linux-based operating system. Therefore, I don't think I can run sudo armbianmonitor -u on the TV box. Is there an equivalent way to collect and share the Android system logs, for example using ADB and adb logcat or dmesg? The problem appears when Android's system file picker/Storage Access Framework is used by applications such as PPSSPP and Dolphin Emulator.

6.18.10 or 6.18.35? Gnome build? I look for kernels in armbianconfig... Ernst