• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by Igor

  1. Everything is correct, just script loading is probing one after another since different configuration are possible ... without boot.ini loaded, you can't boot.
  2. Somewhere here: https://github.com/armbian/build/blob/master/lib/configuration.sh https://docs.armbian.com/Process_Contribute/ Also about other bugs yet to be discovered? And who has to do that?
  3. You can try with this tool: https://github.com/zador-blood-stained/fel-mass-storage ... but it was never tested with this hw so its on you to find out. Support terms: https://github.com/armbian/build#support
  4. Everything is fine but your monitor which doesn't show the login prompt. What if you type ENTER few times - can you login ... how? https://docs.armbian.com/User-Guide_Getting-Started/#how-to-login
  5. We are having a slightly different approach. Lima is enabled, but acceleration is disabled where broken - on Bionic for example. On Focal / Bullseye it works, yeah. For headless devices, its blacklisted with a build config: https://github.com/armbian/build/blob/master/config/boards/nanopiair.conf#L6 Tnx for the tip. Cheers!
  6. Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed.
  7. It helps and its already solved. https://docs.armbian.com/Release_Changelog/ https://armbian.atlassian.net/browse/AR-305
  8. AFAIK all possible acceleration for imx6 has been mainlined and they are most likely enabled by default. Old 3.14 and 4.4 kernels were dropped long time ago. You will need to research the topic. Without researching ... I don't know. We never maintained this functionality. We care about basis functionality and if that works and if we have spare time (which never came), we proceed to such fancy and expensive to maintain functions. Armbian provides builds tools which gives you a solid base. General support terms: https://github.com/armbian/build#support
  9. No problem. In context of mvebtu there is not muc, perhaps switching DEV to 5.7.y if not already? More complicated is E-bin upgrade. We stuck at 4.19.y ... https://github.com/armbian/mpads/pull/3 Do we need 3rd party reviewing here, perhaps @martinayotte find some time? Perhaps this needs a bit more clearing / explanation? I am not sure that I understand what options do we have here and why would we need to change this ... ?
  10. Possible / planned ... when we settle up our CI rearrangement ... which is getting extremely complicated and expensive to maintain. If you want better support, you are welcome to add your resources. With trunk we are already at 5.7.y while for pushing updates from a previous build system stable branch we have no maintainer(s), build (probably) fails ... Kernel 5.4.y was first kernel where this hardware become usable to some degree. With 5.6.y some features were fixed, with 5.7.y a bit more ... there are ofc some problems ... one annoying problem which we are sorting out ATM is that board sometimes doesn't come back after reboot. It stays powered off ... This problem was so far only in 5.7.y Philosophy regarding "stability" is slightly different, until software for this particular hw matures. We are not there yet. So it usually doesn't really matter if upstream kernel is LTS or non LTS.
  11. Selinux - also my primary suspect in this case - should in theory be disabled in userspace / on target by default. Perhaps this is not enough or not working properly ...
  12. Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed.
  13. No problem. Well, its always hard to get everyone together ... but at least we have logs. You are welcome to add your ideas here. Regarding TV boxes RFC we only hear out a short update from @TheLinuxBug That part is planned to be discussed in a separate topic - when possible.
  14. Any for that you have to spam forums? Who will clean after you? You are welcome to solve any problem for and with the help of community, but so far I haven't notice anyone asking for this https://forum.armbian.com/forum/38-feature-requests/
  15. Switch to beta (armbian-config -> system -> nightly) - that is going to be next release. There, matched headers must be present.
  16. The one which you are supporting? “Supported” is not a guarantee. https://docs.armbian.com/#what-is-supported Support terms: https://github.com/armbian/build#support Forum ruiles: https://forum.armbian.com/terms "Do not bump topics or create duplicate messages for the purpose of bringing attention to your issue. If bumping an old topic to resume conversation or provide new information, update the beginning post if possible."
  17. AFAIK transmitting is not supported by hardware, first hit in the search engine: https://forum.armbian.com/search/?q=ir transmitting&fromCSE=1
  18. https://linuxconfig.org/bash-printf-syntax-basics-with-examples https://stackoverflow.com/questions/18460123/how-to-add-leading-zeros-for-for-loop-in-shell
  19. If you got some time and will, this might be a good start for contributing to upstream Armbian: https://armbian.atlassian.net/browse/AR-200 https://armbian.atlassian.net/browse/AR-284 https://armbian.atlassian.net/browse/AR-283 Our current involvement in desktop is almost non-existing. We are everywhere but here ...
  20. I assume you have invested some time into this https://forum.armbian.com/search ?
  21. Yes, its upstream problem. The same on x86 workstation. Quick fix: apt install chromium=80.0.3987.162-1~deb10u1 chromium-sandbox=80.0.3987.162-1~deb10u1 chromium-common=80.0.3987.162-1~deb10u1
  22. We added instant translator so people with not perfect English can also participate actively. Just write in your native language and we will see (Google translated) translation. Detail how-to operate will be presented right before. Service is paid which is why it will only be available for meetings. Currently we are in a free testing mode and this meeting should go within, but we actually don't know ... @Werner pawned his credit card @balbes150 русский язык поддерживается
  23. I also don't tend to use / pay much attention to / legacy anymore ... So we add one more IF sentence to check kernel version so that it won't touch modern kernels ... since there, its not needed, right?