Hi, I am posting this here to notify you about the serious networking performance issue on my Rockpi 4B board. Ever since I installed the Trixie release, the networking on the board has been poor/not working at all. I cannot even run an apt update If I try to connect via SSH, I get: root@rockpi:~# apt update 0% [Connected to github.armbian.com (185.199.110.153)] [Waiting for headers] [Waiting for headers]client_loop: send disconnect: Connection reset >ssh root@192.168.0.200 ssh_dispatch_run_fatal: Connection to 192.168.0.206 port 22: Connection timed out I don't know where to start / what to check here. When I turn on the board, it works barely at starting, very slowly before becoming unresponsive. Technical Details: Board: Rockpi 4B Armbian version: Armbian_community_26.2.0-trunk.44_Rockpi-4b_trixie_current_6.12.60_minimal Boot media: 250GB M.2 PCIE SSD Old Working: Armbian_community_25.2.0-trunk.195_Rockpi-4b_bookworm_current_6.6.66_minimal This issue started only after installing the Trixie images. The bookworm image works butter smooth and flawless. I am sorry if I am cross-posting this, but I couldn't find any known related issue on this board. Thanks in advance!

No clue if it will work. There are hundreds of different TV boxes. It is unlikely anyone here has that exact model So just try. The general rule as the instructions on this site indicate are to try different dtbs until you find one that works the best.

Unfortunately, my knowledge is completely lacking in this. I don't even know how to do it ( If you have some free time, could you please help me create a firmware with a patched U-Boot? I know it's a lot to ask. Forgive me. But I don't know what to do anymore. The manufacturer's Ubuntu 22 is a pain in the ass; I can't even run Docker on it, and so on. I can upload the manufacturer's U-Boot (Ubuntu 22), but if you need anything else, I'll share everything I have without any problems. uboot_22_ubuntu.7z

The connection is correct, the H3 (nano pi neo) output works for external sound i2s, but both the input and output need to be made on a newer board H5 ( Nano{iNeo2 ), the pinout is the same

OK so HW seems OK. And you still use vendor kernel as in 1 of your first messages, that was not clear to me. Maybe as a check, tell what CPU's are in that device? I did not know this '6.1.115' also runs as 32-bit, but the problem then is likely vendor kernel and mainline u-boot; That does not correctly work out of the box on any any of my 64-bit Rockchip devices. So use older U-Boot, what should work I think is the U-Boot from the company Ubuntu22 image and the Armbian vendor kernel+DTB. It means what I indicate, you need to compose your own image by patching some own U-boot in it before flashing or change Armbian build such that u-boot and kernel are a compatible set. So naturally, pick mainline kernel, so edge or current.