Igor

Administrators
  • Content Count

    9083
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by Igor

  1. It goes the other way around. Check which hardware is supported well and you buy that one. x86 platform is not supported. You have plenty of support for that elsewhere.
  2. That is expected/known. Download latest image and use that (old versions are not supported) unless you know exactly what you are doing. Which kernel / u-boot goes where ...
  3. Yes, it looks like somebody played with timings or we miss some patch adjusting this ... since we are changing release model, master will only be build ready, other things will be more fragile https://github.com/armbian/documentation/blob/master/docs/Process_Release-Model.md (WIP) users should stick to released branches. They should not have this problem since u-boot is old there ...
  4. config files https://github.com/armbian/build/tree/master/config/kernel https://docs.armbian.com/Process_Contribute/
  5. This is quite odd since low level features on all variants are the same. Perhaps there is a bug in systemd which would be (possible but) strange. To verify this theory you will need to make an image and force recreating of rootfs. I assume it hang the way you described in previous posts?
  6. Nobody is working on since Armbian does not have any crew/budget for such troubles. I have put it to the Jira to take a look once I am back to tho office ... if it will not be solved by someone else in the mean time. Currently 20.000 km away.
  7. What if you build bionic image on your own ? Is that making troubles too?
  8. Acknowledged https://armbian.atlassian.net/browse/AR-89 but don't have access to hardware until next week. It worked fine before this (big) change.
  9. ... which is a part of the README https://github.com/brektrou/rtl8821CU#arm-architecture-tweak-for-this-driver-this-solves-compilation-problem-of-this-driver Does it work now?
  10. I think no. Nobody is specifically take care over model B I only test on model A. No idea. Yes, until someone sent a PR with changes. https://github.com/armbian/build/blob/master/config/targets.conf#L521-L525
  11. Most of important ones are supported out of the box with best driver found, recommended ones you can find on download pages. If you get exotics, you will have to dance. With Armbian SDK, this is easy. Officially supported: https://www.armbian.com/download/?device_support=Supported All: https://www.armbian.com/download In general: https://docs.armbian.com/#what-is-armbian
  12. Good to know you made a progress on this - I tried to get some progress on this several months ago without much of a success ... then I have to adjust my estimation. Build system is ready for this.
  13. Well, that's actually an u-boot environment file which is/can be stored on a file system ... and used if one choose to use it (change some uboot varible following by saveenv from uboot cmd prompt). This is a case only on Allwinner boards, on others this is done differently.
  14. Generic images that would be covered with a same kernel? Not yet, but you can join some platforms today. Generally speaking - too many problems and IMO perhaps a year or more to have good coverage under one. Actually two binaries - one 32 and one 64bit. For the booting part - not possible on boards that have nothing on board (SPI/eMMC) to solve 1st stage booting. That is very hw specifics. But again, some boards are similar enough and can share this.
  15. 3rd party hardware was never supported because this is simply not possible to provide. It's your problem.
  16. Waveshare corporation does not support Armbian and vice versa. DT support for those display does not exists. Somebody has to make overlays. Then it becomes simple.
  17. Hmm, I don't know how their support is organised and if it exists at all. But usually author driver/maintainer/their GitHub is IMO the best source.
  18. When you plan to modify sources you build with CREATE_PATCHES="yes" and output patch is getting updated on each recompilation. Once you are happy with a resoults you move it from output to userpatches, patches, sent upstream ... Welcome to sent a pull request with removing the patch from the patch set. Thank you! Armbian builds script was initially designed as a script to compile boot loader, kernel and Debian user space. Everything else was added later to the existing process. Yes, its not perfect, but your suggesting and improvements can make it better. We wouldn't get this far without.
  19. Have you asked Noralf if he has some clues?
  20. Do and choose legacy for 4.19.y or current for 5.3.y. In both cases you will find matched headers.
  21. ... I also didn't get any sound when I did testings but it was a quick test without any research so I can't conclude nothing out of that. If people report its not working, then its not working and if sound is working in Librelec means that it can be fixed without extensive work. But its still work and since development is amateur ... its done when its done. One is for sure - only HDMI sound can be brought up, while there are no drivers for analogue.
  22. Don't open new topics and read the topic which yours was merged to. You will find all answers here.
  23. Debian is a community backed OS. If nobody beside Armbian is providing Debian (Armbian is Debian or Ubuntu for your hardware), that's it. Documentation for open source community backed project are made by random people in their free time. If its not good, you can correct that and make a better one. I am afraid there is no other way. And yes, there is far from simple to have the same experience as on your Intel based desktop.