lpirl

I do run a Neo3 for years 24/7 without problems. Please avoid the rage. Of course, you may have a faulty unit. At the same time, if you want to run a relatively bare board, you should be ready to learn how to do it. This looks like a connection issue before even being able to connect to the board. Can you connect to any network using the USB Ethernet adapter? Your home router, for example? Could you maybe also connect the board to your home router using Ethernet? Are you sure your UART chip supports baud 1500000? CP2102 does not, CH340G and FT232RQ do IIRC (please re-check before buying). Best Lukas

Meanwhile, I got a used device and I'll see how I setup the infrastructure for continuously maintaining the device.

Thanks for all your explanations, @Igor. I think I could have well-anticipated the reasons why the team had to drop support for some boards to save some resources and it makes perfect sense, all good. My question ("If yes, it this on purpose?") has probably been imprecise. I meant to ask "Is it expected that the dtb files of CSC boards are not in the dep package (anymore)?". Since you did not seem surprised, I assume the answer is "yes". Thank you also very much for your offer so send over some hardware. I decline with thanks. However, without the specific board, I cannot plausibly take part in the release process and test upgrades etc. Hence, if someone has a spare Neo3, I am interested. I'll also keep my eyes open if I can buy a used one. If I get one spare Neo3, I'll report back and I'll be happy to be the maintainer for the board (issue, PR, etc. volume for the specific board seems to be quite low) and see how long I can keep up.

That was my intuition too but I could find neither another adequately named file in ``boot/dtb`` nor a commit that changes (the patch file containing) the file name. Could it be that removal of deprecated build targets (9d8a424) causes ``rk3328-nanopi-neo3-rev02.dtb`` not to be included in deb ``linux-dtb-current-rockchip64``? If yes, it this on purpose? If yes, should we maybe introduce ``…-csc`` debs or similar? I actually would not hesitate much to maintain this board. Problem is, I have only one which is in permanent remote use. I'll think about it. Also, I need to understand the test facility. I just built the CSC image for the board and I'd expect it won't boot (same issue as in OP) while the test is green.

Thanks for clarification, I took armbian.com/nanopineo3 for granted despite CSC. BTW, I am also willing to contribute a PR (again ) but it is not yet clear to me what to fix. Happy to receive pointers…

Dear community, dear @Igor (as maintainer of NEO3 CSC), thanks a lot for the NEO3 support. This board ran rock solid for me approx. two years straight – much more stable than my other SBCs running Armbian (due to various reasons, no offense :)). However, the board failed to boot with "ERROR: Did not find a cmdline Flattened Device Tree". It appears that ``rk3328-nanopi-neo3-rev02.dtb`` went missing. This must have happened when upgrading the package ``linux-dtb-current-rockchip64`` from 21.08.2 to 22.02.1. As a workaround, it helps to (download the CSC image for the board again, get the file out of the image,) place the file in ``/boot`` and set ``fdtfile=../rk3328-nanopi-neo3-rev02.dtb`` in ``/boot/armbianEnv.txt`` I think it's a pity that support for this board broke, which works so well with Armbian. Any chance we can get the dtb back into the package? Cheers, Lukas

For those who end up here via search engines: On a NanoPI M4V2 (RK3399) I activated the `tuned` profile "latency-performance" for my use case without the intention to address this issue. Thus, by coincidence, I recognized that the issue apparently disappeared (or got a lot less frequent, at least, since it hasn't appeared in the last 12 hours). I don't have the time/priority to track down which of the settings actually helped but it should be the governor or cstate settings.