Igor

Yes.

Its not uncommon and is highly possible that network drivers were not ported to modern u-boot. Or they are just not enabled? We switched to the modern u-boot about a year ago and lack of this functionality does not bother us.

https://docs.armbian.com/#what-is-armbian Armbian is closer to Embedded Linux then Debian / Ubuntu. From embedded Linux perspective, "Debian" or "Ubuntu", upper levels, user space, different versions of standard libraries and application, is irrelevant. Something that has absolutely no relationship with problems most people face. Like to issue you have. General Linux Experience, like you probably already figured out, doesn't help to fix the problem. There are a few of reasons why this instability happens and all require investigation, usually into boot loader ("bios") or related kernel functions. It can hang because of not well tuned power management, badly written network driver, hw quality ... diagnostic can take an hour, but can stretch to weeks. If you have experiences and know where to look. I would start with an easy solutions, which doesn't take much time. 1/2 hour to build, then testing.

This problem was mitigated this way https://github.com/armbian/build/commit/4a689f8b89bca4ecc60a5c24cd8f9beee73bbec9 but perhaps its not enough?

https://docs.armbian.com/User-Guide_FAQ/ Yes they are. They are actively stealing what we develop. They even come to this forum with their users asking us to support their clients. Its sick how other distributions operate.

Changes in kernel 5.19.2 -> are responsible to adjust the code yet again I tried, but I find myself running in the circles ... Anyone more familiar with this driver? @arclight @piknew @Skupsy @Icenowy We are still attached to @karabekfork https://github.com/armbian/build/blob/master/lib/compilation-prepare.sh#L418-L424 but this https://github.com/dbeinder/xradio/commits/karabek_rebase looks like most recent.

Can you perhaps elaborate in detail what have you tried so far? And supplying all the logs. If feature works on hardware and with their legacy kernel, this doesn't mean it works elsewhere right away. We ditched old and security highly problematic legacy code long time ago. But the price is that not all functions work yet. Here its not mentioned https://linux-meson.com/mainlining.html# and I don't recall if we have this working or not.

This is a bit outdated, but might help https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-freeze-your-filesystem-outdated

Which image exactly? Link.

If you have a battery and its getting faulty, perhaps this or the bug within was the trigger? https://github.com/armbian/build/pull/3084

Kernel is what defines interaction with the hardware. Which kernel is there. "ubuntu" plays zero role. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Contact ASUS. This is their duty and expense to cover. Or yours. Our build system will save you few weeks so welcome to make a donation. It is very expensive to keep it maintained. https://docs.armbian.com/Developer-Guide_Build-Preparation/ When you are done, by you or by people you will be hiring to solve this problem for you, share a patch with others. Armbian does not need this to function. You do.

Here you can find build system: https://github.com/armbian/build and here are instructions how to use it: https://docs.armbian.com/Developer-Guide_Build-Preparation/

This is Ubuntu problem, but the solution is probably sudo apt install ca-certificates Also check if your clock / date is correct.

Working here ... re-director is currently under some re-work. Could be related. Its should be a temporal problem.

I was also looking into usbip as I want to implement it to be able to attach devices under test to USB server containing a bunch of wireless cards. This seems covered well. Under this? https://github.com/armbian/build/tree/master/packages/extras-buildpkgs

This (except lines 107 and 108) https://github.com/armbian/scripts/blob/master/.github/workflows/maintain-runners.yml#L104-L109

I didn't fix this for you, but for all of us. I know it works, as it was tested. If you really do, you can equalise your dept in a few years by getting lowest possible https://forum.armbian.com/subscriptions/ or by doing something project needs to help you https://forum.armbian.com/staffapplications/ Both options are in your best interest. This is the problem and solution. https://armbian.atlassian.net/browse/AR-1285 Here you can start learning https://docs.armbian.com/Process_Contribute/

I have upgraded our runners this way: https://github.com/armbian/scripts/blob/master/.github/workflows/maintain-runners.yml#L94-L123

You don't need to install anything. This is a script I use on a very similar device: #!/bin/bash task(){ gp=$1 [[ ! -d /sys/class/gpio/gpio${gp} ]] && echo ${gp} > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio${gp}/direction echo "0" > /sys/class/gpio/gpio${gp}/value sleep 10 echo "1" > /sys/class/gpio/gpio${gp}/value } task "$1" doing this. More info: https://www.google.com/search?q=sunxi+gpio

@going Is there a simple way to package all those tools within a kernel compilation: https://armbian.atlassian.net/browse/AR-1283

Since you are new around, perhaps tell us who you are and what you do https://forum.armbian.com/forum/10-off-topic/ Welcome! Also make sure you read documentation: https://docs.armbian.com/User-Guide_FAQ/ Bug reporting requirements: https://www.armbian.com/bugs/ Workaround for this problem cost me around 2h https://armbian.atlassian.net/browse/AR-1282 Each commit has to be reviewed. Please spent some time to figure out how to do that: https://docs.armbian.com/Development-Code_Review_Procedures_and_Guidelines/ as this is a very first step from here. Then things has to be compiled and once released, then you will be able to update and have this fixed on your device. You can ofc skip all this and do it on your own https://docs.armbian.com/Developer-Guide_Build-Preparation/ Proper fixing of code that is not maintained by Armbian https://github.com/aircrack-ng/rtl8812au/issues/987 would cost us week, perhaps more. Which we don't have so this "quick" solution should do. Welcome to Armbian 22.05.3 Jammy with Linux 5.19.0-odroidxu4 System load: 1% Up time: 6 min Memory usage: 5% of 1.95G IP: XXXXXX CPU temp: 47°C Usage of /: 5% of 29G [ 13 security updates available, 29 updates total: apt upgrade ] Last check: 2022-08-13 13:52 Last login: Sat Aug 13 13:49:49 CEST 2022 on ttySAC2 odroidxu4:~:# iwconfig lo no wireless extensions. wlx40a5eff39254 IEEE 802.11bgn ESSID:"XXXXXX" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX Bit Rate:150 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-****-****-****-**** Security mode:open Power Management:off Link Quality=61/100 Signal level=40/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I am sorry, but this is something that has to be consulted with an legal expert. We never had such case. We have no option but to wait for a legal adviser with a appropriate licence / background that will donate their time and research the case. Anyway nobody, except administrators, have access to sensitive data. Answering random topic in community forums is probably not following instructions -> "contacting administrator"? What about: https://forum.armbian.com/contact/ (for next time and others that might hit into this topic) Software breaks all the time. I don't see a reason why you should be deleting "technical support" account as you will probably soon need to ask another question. People that fooled you they support a board don't have a clue about real problems and we don't provide support for their clients. This is the truth and they are aware of it, just don't care or respect open source software agreements. The conflict originates from that. Initially theirs. They should not drag you into this in first place ... Switching to Armbian is a 1st step of showing minimum respect, second one is to become a community member and 3rd to understand what we do, what are our limits, what is our price to we are paying so you don't need to. Who you are, what you do, do you like our work? Do you drink beer with strangers? I don't.

Because software support is difficult, complex and expensive I am glad you noticed the critical difference and get it sorted out. What if what we as users of free software got is already beyond reasonable? https://docs.armbian.com/User-Guide_FAQ/#why-is-armbian-constantly-asking-for-money-free-software-should-be-free