Jump to content

Igor

Administrators
  • Posts

    14420
  • Joined

  • Last visited

Everything posted by Igor

  1. They will provide you new drivers only if you will pay them to do that for you. End users, including this project, can do nothing about - we have negative budget and can only do best-effort work to keep those drivers at least operational with recent kernels: https://github.com/armbian/build/tree/main/patch/misc while bulk of the patches goes directly to the Git of specific driver. What you are hoping exceeds ability of amateur maintainers, those few people that are actually looking into the code and fix bugs that are made by kernel API changes. HW vendor is usually long gone from there - their development capacity is also limited and they are focused into current products. FYI
  2. A10 / A20 hdmi support was reported as broken and bug was recorded https://armbian.atlassian.net/browse/AR-2674 some time ago.
  3. Here some troubles are expected ... Can you try manual steps to install docker by follow: https://github.com/armbian/configng/blob/main/tools/modules/software/module_docker.sh#L26-L56 installing packages, adding to group, adding docker bridge. This might reveal more. BTW. My F3 died - waiting for replacement.
  4. Actually its the opposite so it must have been something else. Etcher is known to be broken for bigger images (desktops). There is some bug in the .xz decompression method used by Etcher. I am using only USB imager for at least a year and haven't run into any problems. At least not on this level.
  5. Images were tested. Do you perhaps use Etcher for flashing? And try minimal image. That might even work with Etcher.
  6. Just FYI why images are delayed. GitHub, which we rely our build infrastructure on, is having many troubles and builds does not start due to out of (their) resources (probably). 30 out 30 tries, I am getting Error: Error 504: We couldn't respond to your request in time. Sorry about that. Please try resubmitting your request and contact us if the problem persists. Perhaps this is a limitation of free tier, dunno.
  7. You can try on actual machine by editing device tree file. (/boot/dtb/rockchip/name.dtb probably rock5b something) https://chatgpt.com/share/684bbac2-2728-8005-bb50-a2751316ac2b If similar changes work - you need to reboot to apply changes - then report here.
  8. Those builds are made by automation, once per week if nothing else goes wrong.
  9. Perhaps same bits are missing in 5b device tree? https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.12/rk3588-1020-Add-HDMI-and-VOP2-to-Rock-5A.patch If you get it working, make a patch and push it here: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.12
  10. Unable to reproduce. Probably date and time is out of sync. Edit: aha, this is / was the problem: https://github.com/armbian/build/commit/aa5526a9189097b87ada0784cff61bda85e46609 Which means next week community build will have this auto-fixed.
  11. Me too. I was not paying attention to this due to dealing with many non technical things in past few months and as already mentioned, those upgrades are not being tested on older boards. We simply don't have enough resources, test automation is limited - HDMI is not tested in any case. There is more or less just one main person doing general maintenance on Allwinner with occasional help of random people. 6.14 is already EOL and we just switched to 6.15 (EDGE branch), but we will probably stay on stable CURRENT branch with 6.12.y for awhile as its fairly stabilized in general across several platforms. IMO it is best to backport this patch for 6.12.y or fix whatever breaks this.
  12. I have noticed regression on A20, probably also on A10 few weeks ago ... but so far we haven't been able to do anything - almost no active developer have those boards. ... and Welcome!
  13. Welcome! This question is a bit off topic here as general Armbian updates are not part of HA extension. As this is community supported hardware, stable BSP upgrades - where OS version is stored - might not be generated, while kernel and everything else is getting upgrades. tl;dr; Don't worry about this. For board related topics proceed here https://forum.armbian.com/forum/173-allwinner-sunxi/
  14. Yes, that is the main idea, but sometimes things slipped trough. Images were tested (we aim to have two people on one platinum target to be able to provide better service, but perfection is still not possible), but here we ran into weird problem that CI compilation silently broke on u-boot recompilation, while local build works. We have a problem with build framework / compiler internals, unrelated to this specific hardware and problem only manifest on some u-boot variants. Right now, I don't have a clear picture, but we are working on it. This was introduced while moving framework to Noble, which is mandatory for some targets and there are some Python libraries troubles ... which are sometimes used for u-boot / ATF compile. Its a mess. Software maintenance within such extreme complexity is job that is never done. Generally speaking.
  15. Yeah, it was reported at GH too: https://github.com/armbian/build/issues/8227 Probably related: https://github.com/armbian/build/issues/8269 No solution yet.
  16. 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.
  17. 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
  18. Welcome to submit PR here: https://github.com/armbian/build/tree/main/config/kernel Best to all those configs:
  19. I think this is handled with overlay "audio" "analogue" or something similar. https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-overlays
  20. 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.
  21. 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.
  22. 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.
  23. 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 ...
  24. 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.
  25. 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.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines