Igor

Updated test (including some onboard wireless chips):

Can you provide more detailed info - last images were not tested as there were very little changes from previous one (check lastest from archive https://imola.armbian.com/archive/inovato-quadra/archive/)... Which images did you try and can you try daily images that are at the bottom of the page: https://www.armbian.com/inovato-quadra/ Also we are just about to merge big changes on Allwinner, so stay tuned. https://github.com/armbian/build/pull/8004

Enabling remaining with https://github.com/armbian/build/pull/8051

Should be fixed in Armbian repo for some time now: https://github.com/armbian/os/pull/299/files But for kernel 6.14.y this wont be enough anyway. https://github.com/openzfs/zfs/releases/tag/zfs-2.2.7 "Linux: compatible with 4.18 - 6.12 kernels"

Most likely P2P wireless, not necessarily functional. This is automatically present by a (wireless) kernel driver. Use the device that works and ignore the other. If bogus device gets to your nerves, dig into the code, find a way how to disable it and sent a patch.

First you need read FAQ as you might be missing some important facts https://forum.armbian.com/forum/189-faq/ https://apt.armbian.com (APT packages) In reality you need TV box vendor adjusted kernel source. Which is impossible to find as its often not even released. You need to find (extract from official FW) hardware settings ("device tree") for your model or not everything will work. Nobody can help you from developers perspective. You can only hack this on your own or with help of other end users. (Armbian) developers are mainly avoiding this endless pile of junk hardware. Absolutely no warranty that any of this will work, just chances of success are > 0% (your initial approach).

This is just 2-3x more expensive for time then just doing it However, I can give you few tips: - AFAIK driver currently present is not very stable. Our tests (on kernel 6.12.y are failing): - driver provided by Hardkernel is better but might need adjustements for recent kernel (perhaps 1h of work) - general information on USB drivers, perhaps a solution via DKMS https://github.com/morrownr/USB-WiFi?tab=readme-ov-file

Mainline kernels or kernels from Ubuntu / Debian won't work on most of those devices. For several reasons. And if they will work by some luck, they will have less functions enabled / operational. Probably here you are looking for a vendor provided kernel 6.1.y, which we provide for some flagship devices. You can try to install "vendor" kernel from repository (with matched dtb), but you need help from higher power or some work, where you will most likely need to do it alone - our team is not touching this hw with this kernel and we don't have resources to deal with this, to get it working. It requires time nobody have - you need to find people that share this wish / problem and try to do something. And this is where this forum might help. & moving to TV boxes. This part I don't know.

We were not united at which driver to include and eventually nothing was made as kernel deprecation kicked in. This kernel is not used anymore, we have 6.12.y where same procedure has to be made once again. Since this is a public project and anyone can contribute to fixing it for everyone, I’m already pushing the limits of what’s possible.

It is. I have workaround it, but updating process needs some improvements. Once mirrors get in sync, it should be operational.

Without maintaining, those boards (upgrades) simply stop working. This is one of the ways how it manifests. Features starts to break apart and we have to spent insane amount of time trying to keep this herd operational. Every board has its own caveats. And here we also have OS release upgrade - deprecated OS. There are enough of troubles without that. Start with a new image and see if it works. Upgrade from Bullseye to Bookworm is problematic and I advise you to not deal with that if you are not experienced.

What is wrong with Armbian in production? Where you anyway have to work with kernel / firmware under your control. We have several cases. But yeah, hardware support wise, one needs to be careful what to choose. Here OS is irrelevant anyway. You are welcome (to join). If you go that route, remember that it is usually a lonely one and sharing here gives some companionship. Forum can provide some tech but mainly moral support, share some tips and ideas, but expect that nobody have much time to do the homework instead of you - answering "why this doesn't work", "how to fix this and that feature", ... Most of those questions require research - some are already answered but not integrated, so forum search is probably best 1st step. AI is also getting better every day and can help in some cases ... If you convert some popular unsupported board into supported (within Armbian), we can help more. Working with them made us bigger financial loss and worse software support. Most of what they provide SW wise is what they get from Allwinner (SDK) + board level adjustment or they steal (our framework) or push their buyers to milk open source projects. We suffered biggest loss and some had to close their projects down to this negative impact. They also re-brand-port our work into "Orangepi OS Debian / Ubuntu" and "Orangepi Arch OS" with help of Manjaro, which is yet another dirty FOSS player. They also produce fake Kali, fake Armbian and other fake images by themselves. To make sales and leverage support costs to others, mainly to us. We will keep supporting some old boards for end users, but we won't be touching any new HW from them. Association between brands and articles from years ago exists and still makes us damages. They will keep sucking from Armbian without contributing a single cent. They are directly stealing from our work and this is their business model and there is little we can do about except informing you. They always could make a donation, like everyone else, but they never found that button. tl;dr; Fake.

Yes, you need to install matching kernel and headers, otherwise it won't work. Remove CURRENT kernels by hand, install LEGACY and then proceed with headers installation. This will work.

This is custom hardware world, not general purpose Linux. There are 15 x Bananapi https://www.armbian.com/download/?tx_maker=sinovoip and every device has its own firmware. There are similarities, sure, which help, but if one boots and works fine, perhaps others won't. We keep images for those too, as some still might work. Trunk = development branch, changes daily. There was never ever support for that. This is for developers and experienced users, which are able to fix the problems as such. And even when "standard support" is declared, when whole SW stack is stabilized to some degree, it means "high level of software maturity" and you are welcome to share your frustration with everyone. Nobody can provide warranty on software support where users contribute less then 0.5% of costs for making it usable. In general. For specific - you need to share all data and logs, and then maybe someone will have a clue on what is happening here.

Moved to Allwinner section as this is not an user space problem. Percentage of breakage on not supported and (also not supported) trunk / untested / nightly build is very high. What you experience, under those circumstances, it is normal and expected.

Is a raw material from which we are developing / keeping support. It takes thousands of hours annually on top of that - for Allwinner hw to keep in a good shape. Use Armbian kernel and tell your customer to make a donation and your job is done - unless you are here to improve Allwinner support withing Armbian, Armbian itself? If you need Arch - it is probably easier to implement Arch to the build framework (not sure if it makes sense), then what you are aiming at. We are generating a loss by keeping those cheap boards usable - and we expect from you to at least not make the loss bigger - asking questions for 3rd party benefits is a path to this direction. Allwinner, Orangepi, ... are already making us enough of damages by doing nothing else but selling their cheap stuff - and not supporting any of our work. Similar to your customer, just at significantly bigger scale. Perhaps this is one of the reasons why things are as they are?

Probably. This can be solved by adding an overlay, so user can enable this at will, manually or via armbian-config. armbian-config lives in its own repository. Always make sure your packages are up2date / latest. Or at least armbian-config.

https://netcup-03.armbian.com/apt/pool/main/l/linux-headers-legacy-bcm2711/ Try with: sudo apt install linux-headers-legacy-bcm2711

Until only you, me and those few people that will read this thread knows about this .... doesn't make any sense. Our current download logic and UX is very bad at this state, almost as bad as Debian It is very difficult to know that such image exists, what are their advantages (this part I have some draft and will be sent to the docs eventually), then telling them that they can choose between .xz .qcow2 .xz.qcow2 ... while ISO (what people understand) is nowhere to be found. Enabling a feature at build framework. This is trivial and I think it's even supported with a switch already "KEEP_UNCOMPRESSED_IMAGE" or similar, but its not supported at CDN. When compressed qcow2 was replaced with uncompressed, redirection followed as it doesn't carry file extensions https://dl.armbian.com/uefi-arm64/Noble_cloud_minimal-qcow2 which means we don't have support for .xz at this moment. Changing this? Chain of command and execution is slow, I can't deal with everything, and people are busy. I still wait that https://dl.armbian.com/uefi-arm64/Noble_cloud_minimal-hyperv.zip (HyperV Azure) started to work. As you can see, compressed is even bigger then qcow2 image and apparently it has to be zip (don't know that yet). Once re-director is extended, now hard coded values goes out of the code, so its small refactoring - easier job for the future. When re-director is fixed, we need to adjust (already messy) web page. Which is now half broken, those cloud images are mixed with minimal / IOT. You don't know until you click on the link. That cloud kernel supports features required to run Docker. Something like this: curl https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh | bash Already have some draft ready, but wanted to do more tests before. On some clouds.

Understand. But I also just prove you that it works on Armbian perfectly. Problem is with this TV box device. (probably / hopefully "just" wrong DT settings) The reason that it works on Alex / random OS is randomness, pure luck and just to understand why, someone needs to sponsor (!) days to weeks of his time. Armbian provides you build framework, we maintain and supports this community and many of those device, but there are simply too many of them. Those are resources that will help, we can provide hints and tips, but fixing this "small problem" is up to the one that sold you this device (never) and general Linux community, not necessarily Armbian community, and certainly not Armbian OS maintainers. Once you fix this problem, someone needs to keep those features working on firmware upgrade ... so you have some idea on the scale of operation.

Yes. Cloud providers, those that accept direct qcow2 images loading, expect uncompressed variant. It is handy if you can just pass URL or upload image without any additional handling. This should address the problem. https://github.com/armbian/build/pull/8046

Copy / paste / automation ... but joke on a side, robots & AI tools are helpful in the process, but saying thanks to them probably not make much sense.

This is a report from our automated testing. This device works well with generic kernel withing VM. Lets say a proof that a driver itself is O.K. Ah, I see, you don't see results:

If you boot with this plugged in? AR9271 is one of the most stable things on USB, but USB hardware / sw stack on weird tv boxes can vary. We are also having it in the auto performance testing case: https://github.com/armbian/armbian.github.io/actions/runs/14167367586

Thank you for letting us know! Hardware troubles of this board are unrelated to HA deployment. If you install this to not supported device, its on you to deal with HW level bugs. You can try engaging here https://forum.armbian.com/forum/173-allwinner-sunxi/ or contact the one that sold you this device. tl;dr; I suggest you to run it from a quality SD card. I also do.