Igor

Use it. In case you want this function in a quality OS with mainline kernel ... here you can see some overview how the process of mainlining looks like: https://elinux.org/images/d/dc/Petazzoni-soc-mainlining-lessons-learned.pdf Mainlining is expensive and long process of porting board support from a static development kernel to the mainstream. Not all boards get there and very rare with all functions. A bit more concrete information - for Allwiner devices, what works, what not: https://linux-sunxi.org/Linux_mainlining_effort ... while bugs in the implementation are not there.

Support terms https://github.com/armbian/build#support I gave you hints how to start, but free solving problems is not on the menu. You are welcome to open a bug, but you have no influence on resolving speed. Also, in the documentation, there is a clear notice that feature is experimental:

I understand that, users don't. We should communicate this with as little words possible, with a banner or bold text. "Support is on a best effort level" "Never seek personal attention for end user support" ... on the long run, things will be changed.

OK, like - support for TV boxes is very limited ... - expect no expert support in this area - community support only What suits best?

Until we don't have a better strategy https://armbian.atlassian.net/browse/AR-230 I would propose to simply move related posts to TV boxes forum. At this stage, it would be good to assign / find moderator to help @balbes150 moving posts to correct place. I have no better idea ATM.

Nice catch. I forget that with USB-C not sufficient powering problem didn't go away completely. Moving the topic to the "SD card and PSU issues" sub forum, where it belongs. I am sure this limit is helping in saving precious resources. Ratio between people that seek support and people that provide (100% on their expense) is equally severe. Actually much more severe. Get a subscription and limit is gone at once. People around Armbian adds around 30-50 h every day on top of general community contribution to make this possible.

Use latest kernel and provide logs with armbianmonitor -u

Yes, that's my IIRC too ... https://github.com/armbian/build/blob/master/patch/kernel/sunxi-legacy/ths-29-add-correct-h5-thermal-zone.patch

Test report: https://dl.armbian.com/_test-reports/2020-05-20_17.14.00.html - apt update + upgrade - iperf lan & wifi - iozone and reboot Spotted problems: https://armbian.atlassian.net/browse/AR-244 https://armbian.atlassian.net/browse/AR-275 Devices that didn't survive this: Opi Lite 6 tasks to go: https://armbian.atlassian.net/projects/AR/versions/10002/tab/release-report-in-progress https://armbian.atlassian.net/projects/AR/versions/10002/tab/release-report-todo

Thanks. I will check that when possible. Can such symptom also be related to wrong regulator settings?

Menu handling works just fine in (properly configured - usually by default) serial console. Sort that problem first. But also you can connect to wifi with one line. Mind checking network manager manual.

Time is sync by default just by using a different app as @xwiggen pointed out.

I login via mUSB or serial console and connect via Network manager. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-connect-to-wireless When board reboots it reconnects to my wireless network automatically.

Damage control is alright, its working, but board is getting powered off which is not exactly a desired way of normal operations. I am aware of the problem, but we are looking for a best solution. A possible workaround would be to add: CPUMAX=1080000 to all smaller board configs, that might be affected by this problem https://github.com/armbian/build/blob/master/config/boards/

I have OPi Zero Plus 2 H3 and H5 devices in the test rig (3,4) https://dl.armbian.com/_test-reports/2020-05-19_20.25.35.html and so far they never failed to connect to the wireless network without any changes to the network stack. Network manager, WPA2 network, ... From Armbian point of view, there is nothing wrong but I can understand your frustration. Check your router and always go the way we recommend. Not every how-to from the internet will always work ...

It can take months before patches finds the way into the kernel, so you are welcome to add it here: https://github.com/armbian/build/tree/master/patch/kernel/sunxi-current https://github.com/armbian/build/tree/master/patch/kernel/sunxi-legacy https://github.com/armbian/build/tree/master/patch/kernel/sunxi-dev

How do you mean by default? That you will build the image with limited CPU speed to 1Ghz?

https://docs.armbian.com/Process_Contribute/ https://github.com/armbian/documentation/blob/master/docs/User-Guide_Getting-Started.md also this https://armbian.atlassian.net/browse/AR-213 needs to be integrated Thank you for your help.

Today's stress testings: https://dl.armbian.com/_test-reports/2020-05-19_20.25.35.html Victims - boards that didn't survive: "Orange Pi Lite" "Orange Pi Lite 2" "Rock 64" "NanoPi Neo" "Pine H64" "NanoPC T3+" "Orange Pi+ 2E" Investigation follows ...

No. Just keep this conversation under the general forum terms - don't bump topics.

... as we are drowning in the flow of (mainly unrelated to our work) questions that are coming up every day. Welcome to the battleground If you would asked before whether is it worth fighting it, I would save you a week ... I have that kind of experiences which I am glad to share with you. This know-how is manifested in our labels: "WIP", "COMMUNITY SUPPORT", "SUPPORT", "EOS". For your own good, you don't want to ignore them, but do ignore sales messages, "review" sites, users hype fueled by impressions and marketing, ... Use supported hardware. Even that is not a guarantee, but it's a much more solid ground. A place where one person (with 20-30 years of general computer / Linux experience) can do something useful. In this case, its useless since lower level support is fragile, immature and unstable. If you want all this to work, you have to fix many things - if you have seniority in this field and you will need to find some friends. Alone is always hard. You have to lead and be a developer. On our forum you can find useful clues which will save you time ... Perhaps they are useless for your battle, but it might save somebody else's week.

Start there and debug. IMHO this is your by the far shortest way of getting where you want. Other options will require much more efforts. This is Armbian support forum ... which has best support for the hardware you tend to use.

This is a great opportunity to learn about and to learn about hot to contribute.

By downloading free software you didn't get free premium support or any rights to complain about. This is best effort support forum: https://github.com/armbian/build#support Ask, if no answer, research more -> if you need a solution, pay for help / DIY. Technical questions can't be solved without focusing into it. For that someone needs to be up to date and have to find time to pick up "clients" problem. There are about 1000x more people that seek help, then give. Have you used search before to help making this ratio more pleasant for those who give help? There are many similar ideas on this forum. I am sure you could get some clues if not a solution. Since we don't (pay for) support this hardware, there is a great chance nobody is listening ... sorry. You should be aware of that. Rather support software development which is the only way you will get some rights to complain - cheap hardware without is a paperweight. Currently you - users - are not covering download costs, which means demanding help - 100% on our expense - is at least rude if nothing worse. Demanding free 1000 USD valued help is ... no words for that. Doing something for the project or community first, then asking for help .... can perhaps change things.

Rough estimate of "05" is May 2020. It can also be delayed into June for various of reasons. This is our private cash / time we are burning for. https://github.com/armbian/documentation/blob/master/docs/Process_Release-Model.md We are staying close to the plan. If you add your resources, things can go smoother, with less delay, better next time.