Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    14420

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    Meetings to support development of: https://github.com/armbian/configng @sgjava @D-mo @joekhoobyar @Ameer Dawood @esanya @TRS-80 @TheLinuxBug and anyone interested in some bash coding!
  2. Igor
    Because nobody volunteered to try, check for possible regressions and submit changes? From project perspective, if @Heisathdon't have much time and interest, there is nothing we can do as project is way way too small to follow endless users & HW needs. We don't have a backup.
  3. Igor
    To change display resolution, add below to the /boot/armbianEnv.txt: extraargs=video=HDMI-A-1:1920x1080M@60
  4. Igor
    Kernel is defining hardware features. Which kernel are you using in "Ubuntu"?
  5. Igor
    We will continue to provide kernel updates for imx6 (Cubox-i and Udoo) and other 32bit devices, just quality assurance won't be applied anymore. For matured support, as in this case, this is usually not a problem. Migration is possible, but not on OS (different arhitecture & different boot process) but application level - copy data and configuration for nginx, then copy data and config for samba/nfs ...
  6. Igor
    Some problems has been solved, but not all. Switch to nightly beta repository that is tied to development and see if it helps. Otherwise we invested our private time to research paths that might get us to the solution or at least to the better state, but we also face problems our "customers" don't want to hear about: - we don't have resources for integration or help on integrating this. Voolonteers are scarse and overloaded. We are already over the limits, - with donations https://liberapay.com/armbian hiring help is not possible. Who wants to work for free, already works, others can't afford, - we are also under constant attack by swindlers which waits we solve this so they can take credits or sell it to someone. Remember that its a big difference helping you or helping someone that is making profits out of our generocity. What would you do?
  7. Igor
    1. Checking the progress of Armbian-next Video: https://us06web.zoom.us/rec/share/ly7gbgZBTY1M4eiumUk6Gp357Jl0RV0h7usdUEGN5WcNKXNIwsOoNHbtoLbBeEje.KCku4wdAigfEI7pB Armbian Next Jira: https://armbian.atlassian.net/browse/AR-1451 @Contributor/Maintainer
  8. Igor
    until
    This week meeting topics: 1. Checking the progress of Armbian-next define upgrade path 2. Moving development related topics to GitHub ideas for moving comm 3. Questions around upcoming release Different starting hour!!! General goal of weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
  9. Igor
    https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/
  10. Igor
    Just additional measure to divide kernel and user land packages update. If you want to update kernel packages go to armbian-config -> system -> unfreeze (freeze back after) ... do update & upgrade.
  11. Igor
    We are trying to put together an automated test system for various (WiFi) USB devices. Hardware is in place, but software part is in early design phase:
  12. Igor
    Oh, you want to take care of this?
  13. Igor
    Thank you! BTW. We are just about to switch to a completely reworked version of it: https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ This should also help dealing with RT patches. If we had someone around to deal with RT patch discrepancy, we could also generate RT kernels.
  14. Igor

    until

    yes. Just like in forums.
  15. Igor

    until

    @Contributor/Maintainer FYI By looking into Google search statistics I found out that armbian-config documentation is most clicked with around 3000 hits per month (numbers are for 1/2023): https://docs.armbian.com/User-Guide_Armbian-Config/ https://docs.armbian.com/User-Guide_Getting-Started/ following with 600-700 by those https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://docs.armbian.com/User-Guide_Allwinner_overlays/ 300 https://docs.armbian.com/Release_Changelog/ Not having right mindset to explain this , but those are numbers.
  16. Igor
    I am sure there will be! We even played with idea to present armbian-next build framework, but I guess next year or at another conference. I'll have to skip it this year. Somehow too busy.
  17. Igor
    1. Checking the progress of Armbian-next Video: https://us06web.zoom.us/rec/share/vq04OFykxpw7nGp8wJxKME7w8uNf1kMrwHRLldQLTCLJCT-zsZY8KP76aCknhBfN.JyvzRmfR9qulexM2 Slides: https://github.com/rpardini/armbian-build/blob/extensions/README.armbian-next.slides.md#update-feb-1st-armbian-next---general-changes Armbian Next Jira: https://armbian.atlassian.net/browse/AR-1451 2. Moving development related topics to GitHub Summed here: https://armbian.atlassian.net/browse/AR-1529 3. Questions around upcoming release Today is the code freeze. Actions: notify maintainers and prepare them to be ready on testings in two weeks from now notify developers: their code gets into release log only if exists in Jira. Minimum requirement is Jira issue or Jira story with Name, short description and field "Fix versions" set to 23.02 that code freeze is a milestone when we change our focus into code stabilisation and fixing bugs. It is not expected to drop existing work in progress at once but gradually close it. in the code freeze period, there is additional restriction on code merge: pull requests approval from 1 person to 2 persons @Contributor/Maintainer
  18. Igor
    We have DTS, I even tested it few days ago, but don't have the energy nor time to open PR ...
  19. Igor
    Kernel headers on this particular kernel are not in good shape as kernel is not in good shape RK3588 is using changed Linux kernel fork used by Rockchip to bring the hardware up - focus is their hardware functions only. More or less only they maintain it without general purpose fixes. Many standard functions are broken or unmaintained. Volunteers and people at board vendors can only try to fix most critical things to make hardware usable ... until this is not working decently (1Y+), there will be many strange problems to find. Both is good I guess, but can't say how vendor takes care on PR. With Armbian - if its clear what it is about, tested, came from trustful author, ... its merged pretty fast https://github.com/armbian/build/pulls
  20. Igor

    until

    😆 OMG. I saw it now Fixed, thanks.
  21. Igor
    Not familiar with. You mean you have tried, but it didn't work? So far, booting from USB key always worked, but am not familiar much how Ventoy is combining distributions. If it doesn't work, we must be missing some small details in this UEFI structure or Ventoy is too rigid. I have recently found a bug which could affect UEFI booting, but this is related to the install part. https://github.com/armbian/build/pull/4758/files
  22. Igor
    That is a great resource regarding wireless modules. This is not that easy as drivers build into the kernel can still have such problems. In fact, those drivers are build into, just by Armbian. TBH i didn't look closely enough to see which drivers are actually in use. It is also possible to have different drivers for the same device and then you block one or another. Where is "at the end" ? I am exploring Unix / Linux systems and hardware for 30 years. And the more you know, the more you are aware how little that is. There are many things that can go wrong. Stay open minded.
  23. Igor
    until
    Meetings to support development of: https://github.com/armbian/configng @sgjava @D-mo @joekhoobyar @Ameer Dawood @esanya and anyone interested in some bash coding! Lets move things further! Once we got it moving, it will get a lot easier.
  24. Igor
    Raising issues is reserved for project contributors that are planning to work on issues. End users can't raise issues to maintainers. They spot a problem on forum and open a task. Or not. This is amateur development. We use ticketing system to tell you what we did https://docs.armbian.com/Release_Changelog/ in hope that someone will notice our efforts. To clarify few things: stable images are generated every three months. Stabilisation is extremely expensive and nobody else is providing that service. Little above 0% is compensated by "you" and cold 0% by HW vendor. It seems everyone is happy if images are just built and provided for download. To satisfy this need, we are generating rolling releases, every week all boards, supported or not supported, gets their images with latest code. This costs us perhaps few hundred per month, while providing stable images costs 1000 x more as includes manual and automated testing, fixing problems, testing, fixing, writing documentation, coordination ... For most interesting and WIP devices, we also provide images per code change. This system is maintained by team private resources and with help of unselfish community actors, partners.
  25. Igor
    This is not a very long term solution as this kernel is (more) security hazardous, contain bad code and is only maintained by Hardkernel. We want to get rid of it as soon as possible. In fact we already did - we don't promote it anymore, but one can still build an image with. Fixing WiFi (your initial problem) is super super tiny compared to all problems that comes with legacy kernel and will never be fixed vs. modern kernel. Its always a trade.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept