Igor

tl;dr; It a business support / donation deal between Armbian and SBC maker. We have some budget, we aim on at least positive zero, and we have some people behind those boards. This doesn't mean we will be able to resolve all problems and in real-time as budget is still too small and resources remain limited. Support is better https://docs.armbian.com/User-Guide_Board-Support-Rules/ then on boards without.

The software used by the Orange Pi "team" is, to a very large extent (estimates go as high as 99.9%), based on the work of developers from the Armbian project (and beyond). Their contribution mainly includes adding basic support for new boards, but unfortunately, without further maintenance or long-term support – which practically means that the entire burden of maintenance and support falls on the community. It should be noted that systems such as Orange OS Ubuntu and Debian on ARM architecture are the result of years of work by more than 500 people gathered around the Armbian project. Orange Pi only makes minor adjustments. In the past ten years, we have not seen a single contribution from any member of the Orange Pi team to the development of these key components. Absolutely nothing, while they keep signing under our work (even changed to some degree) ... on top of stealing software support. Which they don't provide in any way. The work of the Orange Pi team (which appears to be just one individual), on top of some old Armbian, can be tracked here: https://github.com/orangepi-xunlong/orangepi-build/commits/next (they removed other board configs)

IIRC this was never integrated but was supported via community initiative:

I assume you have a GitHub account (if not, make it)? Click "Subscribe" on that issue and you will get a notification when its closed down. 4 hours later, still not fixed. No, there is no cheap and quick solution to patch this problem. I would like to see that too.

Aha, its probably this: https://github.com/armbian/build/issues/8052 Working on it.

build with SHARE_LOG=yes SHOW_DEBUG=yes and provide full log. This tells noting.

This is everyone's problem. Buy boards that are supported and maintained. We have not received any support from Orange Pi, contrary, their business model is very damaging to us and donations only pays coffee and beer. We do not maintain or officially support hardware you have, and AFAIK it is not maintained by anyone else - but if it is, it will get to Armbian too. However, given the similarities across these boards and the nature of open source, it’s difficult to prevent Orangepi and their customers (you) from abusing open source development. This is everyone's problem. Stop buying hardware that we don't and won't support as making a pressure to open source developers is worse thing you can do. Hardware dealer abuse is already big enough. Just a polite reminder that you are not a customer, so adjust your over-expectations.

As predicted. Vendor kernel - I am working on establishing better cooperation with Rockchip. Without that, its difficult to "fix everything" in that kernel.

Thank you for reporting this problem and Welcome to forums! Looks-like issues with HDMI driver / edid readout, perhaps forcing resolution might be a workaround? But how-to, you need to look into the kernel code. Also make sure to try daily builds from time to time to see if things are fixed. https://docs.armbian.com/User-Guide_Armbian-Config/System/#switch-system-to-rolling-packages-repository I hope the general difference between vendor and mainline derived kernel (and u-boot) is understandable? https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Depends on your technical understanding - look into the code, compile kernel with additional debug, understand how it works ... I am not familiar with HDMI subsystem, so you need to hope from attention from someone that is. Or just dig into the code and share findings. Telling that it fails / errors out, is just a very first step from a possible long journey. This is community support, we all have this problem. Helping others is helping yourself. You are welcome to help the project anywhere you can. That helps too. The amount of issues in open source code (not Armbian problem per se) that are waiting to be fixed is already enormous and we fight this without your help and without help from company that should be around actively (Rockchip). Whenever I spoke to them, they brag how good they are and how many engineers they have and how well their products are ... while I know state of their products better then themselves. Functional regressions you experienced are totally normal, expected and will happen in the future. No matter how much time goes into the code, Linux is maintained and developed by many people, overall complexity is quite extreme. This problem is not yours, but from everyone. So it is approach for solving it.

Try modern kernel, 6.12.y

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.