Igor

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.