Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    13937

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one In some cases (Rock 5, Bananapi 5, ...) we are providing images with pretty well working but outdated kernel which is responsible for interacting with hardware. Difference between legacy and modern mainline is extreme. 1) devices that are plugged to the board were never officially supported. Porting drivers to the mainline for all Linux community (by a few people) is done in best effort manner. 2) it always works this way https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-nvme-usb unless it doesn't / its broken. If its broken it can be broken for all boards. SPI boot method is not always working / supported. My 2c
  2. Igor
    "Ubuntu" does not define interacting with the hardware, kernel does. As we don't use proprietary kernel from Hardkernel, this is done different, possibly its undeveloped feature. What you need to do is edit device tree and enable this UART (this is standard procedure on all boards). If overlays were made, then this is a lot easier: armbian-config -> hardware -> enable / disable, save, reboot.
  3. Igor
    Daily ATM and if it performs well, it stays that way.
  4. Igor
    It's know that is broken, it was fixed but since we are in the middle of big changes, we have deconstructed updating mechanism which is slowly going to be back in function. Try to use self build or daily auto build image and this problem is probably gone.
  5. Igor
    https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
  6. Igor
    Video 1. Progress of CI support - build matrix almost work. It could be integrated into production code, but we will do another week of polishing. - we have added on-demand cloud runners action to add additional 128 build runners when needed 2. Security concerns We talked about potential issues and how to improve that. A dedicated person, a CSO volunteer for Armbian project is most welcomed. There are issues in general and GitHub CI specifics, so understanding of those process is needed to understand or learn. @Contributor/Maintainer
  7. Igor
    Unknown. Plus I managed to fry the board. It was sent to repair, got repaired, it is coming back ... but sadly anyway don't have time to do anything. When they boots, images would be at the download pages with at least WIP / community support status. This might be helpful. https://github.com/Kwiboo/arm-trusted-firmware
  8. Igor
    Thanks to @Efe Çetin Lets keep it in WIP section for awhile until we don't do more testings. I found out armbian-install doesn't work well so this needs to be fixes, perhaps something else ...
  9. Igor
    Download: https://www.armbian.com/nanopi-r6s/ (unofficial WIP support)
  10. Igor
    Those are images versions IMAGE_VERSION= ... Probably is just adding confusion while otherwise it should not play a role if I understand this correctly.
  11. Igor
    This week meeting topics: 1. Progress of CI support 2. Security in GitHub actions 3. 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
  12. Igor
    Video 1. Progress of CI support https://github.com/armbian/os Changes: - release numbering changed from 23.05 -> 23.5 - we have two separate version configs. One for nightly, one for stable, so its easy to generate a new release. Full or partial - for a single board only. It automatically increment patch number when doing that. - all images are rebuild every run / night on 8 build clusters. - splitting testing related tasks from armbian/os to armbian/ci is planned for future - all currently enabled 3rd party packages are syncing also to stable repository. All those scripts needs to be feed with JSON which is still around a week or two before integration. We checked the progress. 2. Mechanism for rebuilding packages from sources We concluded its better to switch to some existing solution. As this is still a low priority and not needed for upcoming release, main development won't be touching with it within next two months. @Contributor/Maintainer
  13. Igor

    Probably OBS is best maintained, but overkill and complicated ?. Mini builds sounds nice but never seen it ... What we need is: patch, recompile and host several packages per distribution. Starting with things like https://packages.ubuntu.com/jammy/base-files Repository management we have, so if this system throws out a deb we only make a translation to our schema ...
  14. Igor
    You mean this? https://www.google.com/search?q=debian+auto+login+cli
  15. Igor
    Strange that Ubuntu package is broken ... but we have a nice mechanism to workaround such issues. Synchronising applications with Armbian repositories: https://github.com/armbian/os/pull/34 Once this gets merged it will automatically sync libcec from Debian to (our) Ubuntu Jammy repository and manual hacking won't be needed anymore. This covers Ubuntu Jammy, for Lunar (if needed) a similar new config file has to be created.
  16. Igor

    Can't say it was abandoned. Just its not used much and mechanism was not transferred to Armbian NEXT due to that fact that it was not mandatory and as it represent additional work. Those paths needs to be discussed: - moving to armbian next - keeping as a standalone functionality - something else
  17. Igor
    We added Rpi4b late so its possible there are no Focal images. But it should be possible to build one: https://github.com/armbian/build ./compile.sh SHARE_LOG=yes EXPERT="yes"
  18. Igor
    This was adopted 8-9 years ago and was perfectioned since then. No need to worry about this. Perhaps this is the reason why read-only variants were not requested that much. Also SD card quality improved within years alongside with emergin eMMC / SSD as primary media also in this segment.
  19. Igor
    Possible. I ran a rebuilt for this board, but as I am out of office, those were not tested on hardware https://imola.armbian.com/dl/odroidxu4/archive/
  20. Igor
    In cheap & plug and play range, this is the only option I am aware of. Last time I played with it, it was working on Ubuntu (IIRC Jammy) out of the box, while on Debian it didn't want to start. I didn't proceed in debugging.
  21. Igor
    By default not really But you can try into this direction https://spin.atomicobject.com/2015/03/10/protecting-ubuntu-root-filesystem/ (try to find more recent guide, perhaps even on this forum).
  22. Igor
    Normally I would already push this to the repository but in present state (due to upgrade to Armbian next and destruction of CI & repository management) this represent lots of hacking. Its one of those ... should I temporally fix old code to produce artefacts, fix repo management ... or invest time / wait that new system is up. According to yesterday's meeting, we are around 10-14 days from generating all artefacts properly. Good point is that repository management is more or less back as it was before. In case I manage to find time and rebuild BSP artefacts manually, they this can be done few days earlier ... but I have many other things
  23. Igor

    Video
  24. Igor
    This week meeting topics: 1. Progress of CI support 2. Mechanism for rebuilding packages from sources 3. Misc 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
  25. Igor
    This week meeting topics: 1. XML / JSON generation to support CI 2. Compilation of legacy configurations (Opi Zero2 legacy does not build) 3. Re-organise forums - Maintained / Unmaintained hardware 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept