Igor

We do have 3A https://fi.mirror.armbian.de/incoming/igorpecovnik/rock-3a/archive/ (need report if this latest build works) and build config for 3C but not 3B. Does it make sense to make for 3C too or 3A can cover them all. I don't have any of those, so I can't check.

He probably meant upstream driver version v5.7.9_35795.20191128 https://github.com/jwrdegoede/rtl8189ES_linux/blob/rtl8189fs/include/rtw_version.h and by looking into Makefile it feels as we are in 2010

Welcome to submit PR here: https://github.com/armbian/build/tree/main/config/kernel Best to all those configs:

I think this is handled with overlay "audio" "analogue" or something similar. https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-overlays

No and we can't get new one as it doesn't exists. Common practice is that vendor drops driver sources to the wild and never look back. All costs of maintenance are on few people in and around this community and similar (volunteer based) projects that deals with Linux wireless. This chip is probably only used by few (Orangepi) single board computers and perhaps some Android tablets, TV boxes. Which are not in our focus anyway. There is some community efforts to bring such drivers to mainline code, but I doubt this chip will ever find a way there - and this doesn't mean that it will work better. Check here https://github.com/torvalds/linux/tree/master/drivers/net/wireless/realtek if there is any sign of it.

This method will keep working for years and I will try to fix problems as long as they won't take too much time. Most of Armbian images doesn't have boot partition as it is not needed. Most of boards does not support boot from flash drive, but from SD card. I have absolutely no clue. There is a whole section of Armbian community forums that are dealing with the complexity of booting weird TV box hardware. I suggest you to start here: https://forum.armbian.com/forum/189-faq/ It is enough that board uses different memory modules and device won't give any sign of life. When you manage to boot Armbian Bookworm with help from TV box section, use armbian-config.

Well, for Home Assistant, Armbian / Debian Bookworm image is required. That we usually provide for all variants, supported and not supported. Since this hardware is not actively maintained, we don't know if there are any hardware level issues related to this board. Here you are on your own, hope for / wish you luck. Usually things works ... Next step is this: https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#home-assistant It will provide the same result as image with pre-loaded Home Assistant.

Welcome to Armbian forums. Most of general questions are answered in: https://docs.armbian.com/ https://docs.armbian.com/User-Guide_Board-Support-Rules/ Remove those you will get answers there ...

I would suggest you to download clean Debian minimal image and proceed this way: https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#home-assistant EVCC can be installed this way - official Docker container: https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#evcc How to deal with EVCC from HA, no idea. This is application level knowledge and I am just an average user of HA. I assume addon will want to connect to the service which runs on some IP address and some port. IMO this part is similar as official HAOS image. Current application images are not yet rebuild with latest stable base, so until then its better going clean Debain + armbian-config way.

I see. This package is done bad in first place. No wonder they decide to simply drop everything ... Most of people anyway use embedded HAOS. Then we should not adding updated packages to the repository anymore.

Thank you for reporting. If current images have troubles, you can try to use previous ones. There is a link on the download pages or you can find them this way. https://forum.armbian.com/topic/52406-helios-64-fails-to-boot-since-upgrading-to-bookworm/#comment-219614 Which works best for your case, you will need to find on your own. We don't store this information / forum search might help. Similar goes with 3rd party images - most are Armbian based and none is in perfect state, things break apart all the time. By providing logs (if possible) someone might give you hints to workaround the problem, without hardly. As I understand from your report - image boots, but USB port doesn't work to enter password? And also network is down, so you can't login remote. I haven't tested HC4 on last builds, but C4 works just fine. In any case, fixing the problem can take some time - Hardkernel never supported our work, so we don't have active maintainer at stand by. It depends on volunteers that read this forum. When they notice and found time to look into this.

What do you mean by that? Images that are currently available are still from 25.2 ... new will be created soon. But you can anyway update them standard way: apt update + apt upgrade.

Also try to fix serial console, using different cable, different terminal application, ... doing this blindly ain't best practice.

We keep (most of) old images here: https://fi.mirror.armbian.de/archive/ https://fi.mirror.armbian.de/oldarchive/

This is what AI tells: Role of BL30 The BL30 component serves as the firmware for the Amlogic Secure Co-Processor (SCP). Its primary responsibilities include managing system-level operations such as Dynamic Voltage and Frequency Scaling (DVFS) and handling suspend/resume functionalities. These tasks are crucial for optimizing power consumption and ensuring efficient thermal management within the system. lists.denx.de In addition to BL30, there is a closely related component called BL301. BL301 acts as a board-specific firmware "plug-in" that provides customized parameters for DVFS and suspend/resume operations, tailored to the specific hardware configuration of the board. lists.denx.de Integration into the Boot Process The typical boot sequence in Amlogic devices follows this order: BL2 → BL30 → BL31 → BL33. Each stage is responsible for initializing specific aspects of the system, with BL30 focusing on power management and system control tasks. If any stage fails, the boot process may attempt to fall back to an alternative boot medium, although this behavior can vary depending on the specific SoC and its configuration. 7Ji’s Blog+1lists.denx.de+1 Understanding the role of BL30 is essential for developers and system integrators working with Amlogic platforms, especially when customizing firmware or troubleshooting boot-related issues. All Amlogic SoCs boards needs this. AFAIK here we don't have open source alternative. Only from the owner of this file after you sign certain papers https://www.amlogic.com/#Company/Contact/index.html This is complex operation and possible where / when there is a big enough interest and when more people join in this common interest and are willing to sacrifice months of their precious private time. https://github.com/crust-firmware/crust Here is an example of similar feature for some other SoC (allwinner). It works, but it's also not feature complete and probably never will. Many of those SoCs are already commercially obsolete, similar for the one you are asking.

Its 64bit, but support quality (tl;dr;) of Allwinner is behind Rockchip.

And I have ruled out that this is Armbian OS problem.

30-40% of GH runners we use are on arm64 platform. Compilation work in all combinations. Yes. This was lying around. Allwinner should work the same, but *edge kernels are experimental, adjust expectations. You have all tools you need, but nobody will be debugging some old experimental kernel just for you. Hint: when you generate image from sources, enable kernel headers install (i think parameter is INSTALL_HEADER=yes), so you have the one that are matching your kernel. In repository, they are probably different / not compatible. I checked if it works for latest stable (the only target that is worth spending time) kernel on supported hardware (that was around my desk). Unsupported hardware running unsupported kernel - it is expected that things will be failing.

This 100% works - we are even running daily automated tests on Bookworm, Jammy and Noble. https://github.com/armbian/os/actions/runs/15362508470/job/43232345405 Manual test on Rockchip64 (Bananapi M7) with 6.12.28-current, latest kernel from daily repository. System: https://paste.armbian.com/tiwisuhugi Here is build log:

Welcome to the club Perhaps you rather help us maintaining and fixing what is possible, so I would guide you away from things that are complete waste of time. Such as this. DKMS works on Armbian, but if this (shit) driver works, that is another question. In some cases it takes years before driver become usable ... while performance still sucks. https://docs.armbian.com/WifiPerformance/#xradio-xr819 AFAIK, there are no reliable driver for aic8800. Sorry for bringing bad news ...

Beta repository. - should be on servers where we push on directly and this error can't occur (unless something broke down) - is the same quality as other Linux distributions (there is no other distro that would maintain those custom devices) - currently assembly is broken as some patches are failing and thus (beta) repo is not getting any updates until its fixed https://github.com/armbian/os/actions/runs/15337468717/job/43160986093

Automation, not guys And they it can't be quicker then others elsewhere. Armbian adds a value on top of this. We have our EDGE kernels attached to latest mainline with additional stuff from Collabora and additional stuff from our own work. They are released daily in beta channels, which here doesn't have any fancy name (rawhide). https://github.com/armbian/build/blob/main/config/sources/families/include/rockchip64_common.inc#L36 https://github.com/armbian/build/blob/main/config/sources/mainline-kernel.conf.sh#L7-L14

I moved them to production already as I got another report they are working - so they are the same, but also community build images are mixed with those links ... this needs to be fixed eventually. Thank you for comprehensive testings. Here is image for 2w if anyone have it laying around: https://fi.mirror.armbian.de/incoming/igorpecovnik/orangepizero2w/archive/

Also need someone to test this: https://fi.mirror.armbian.de/incoming/igorpecovnik/orangepizero3/archive/

Yes. And we will keep fork maintained as long as possible. https://community.home-assistant.io/t/feedback-requested-deprecating-core-supervised-i386-armhf-armv7/880968/313