Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    14365

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    1. Start with a brand new UEFI image https://www.armbian.com/uefi-x86/ 2. Flash to USB, go to Bios, change to boot from USB 3. Boot, make 1st run config, then optionally erase eMMC flash partitions to force installer to create new ones 4. Run armbian-install, choose install to eMMC, select second partition when asked for where to install (it should only give you option for installing to 2nd as 1st is small FAT EFI partition where you can't install rootfs too) 5. Reboot and it should work. I just tried this on my test device which is very similar to Rockpi X (UP Square)
  2. Igor
    It looks like we are in the middle of this transition. Some packages are in old schema (bsp), some new (kernel, dtb ...) I understand we need to generate upgrade package, but all this needs to be adjusted and well tested. What I propose is to go (temporally) back to the original versioning scheme so we can start producing nightly images and upgrade will just work. If we are o.k. (Richardo is fine with) this is best what can be done in short time, can you help in resolving this?
  3. Igor
    We need to provide this automatically for user.
  4. Igor
    What if revert versioning change to what we have now? And return to this issue later, when we have a system in better stage. We need to make upgrade possible and nothing has been done in this concern. Its not just about upgrading our builds, but also builds people generate for themselves by using a script. They / we can only wait awhile if some critical component is not functioning as expected. (even wrong way)
  5. Igor
    My 2c https://github.com/armbian/build/pull/4904
  6. Igor
    Adjusting versioning is one of next major things before we will start to publish nightly packages again. I don't know if what we have now is correct / as designed. I am aware introducing / switching to NEXT it is painful for regular processes and all developers involved but we are getting many improvements on a long run.
  7. Igor
    I can assure you ZFS from Arbmian repo works perfectly fine. We are using it on two production grade servers. odroidhc4:~:# modinfo zfs filename: /lib/modules/6.0.12-meson64/updates/dkms/zfs.ko.xz version: 2.1.6-0york1~22.04
  8. Igor
    https://us06web.zoom.us/rec/share/-uF9wa9jK1U0CA9KQqIc7hdsRCAEh1QwMQy987GkuvogqVFiur1tGXRrQbO2znsg.g0JXx4SYwDuPZ3zW Open issues: https://armbian.atlassian.net/jira/dashboards/10103
  9. Igor

    Recordings
  10. Igor
    This week meeting topics: 1. Armbian framework after the merge revisiting bugs identify larger chunks of work 2. Changes on "about Armbian" maintainers, developers and support staff are in the database we have POC and scripts for pooling data how / how much to present this data, move tables from documentation 3. 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
  11. Igor
    Try https://archive.armbian.com/
  12. Igor
    This forum is dedicated to Armbian OS which you can get from https://www.armbian.com/download/ and which has nothing to do with Android Orange Pi OS.
  13. Igor
    Because of this switch https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ all CI was put offline and is putting back step by step. Nightly packages are not generating yet, nightly images are. I expect to restore to previous state in about two weeks.
  14. Igor
    This hardware is not supported as far as Armbian goes, upstream can only be worse. If something will break cause of upgrades we will do exactly nothing as we receive no funding for such things. But you can. This is open source, code is available ... Armbian has probably all tweaks that were developed and can only have more RK tweaks then generic kernels provided by Debian or other general purpose distros. What works, works, but it is very difficult to proceed and finance what is missing and keep device stable out of our private savings. Its far out of range Another alternative solution / workaround is picking previous known-to-work-kernel and froze upgrades.
  15. Igor
    Yes, it works for pi3 too. Edit: should work. Those images are not tested.
  16. Igor
    This week meeting topics: 1. Armbian framework after the merge revisiting bugs identify larger chunks of work 2. Moving development related topics to GitHub how to start? 3. Changes on "about Armbian" maintainers, developers and support staff are in the database we have POC and scripts for pooling data how / how much to present this data, move tables from documentation 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
  17. Igor
    - build framework switched today - OK, we are going out with this. Rsync mirror is pushing at average of 1GBbit/s + for a whole day - short video about release was recorded today - release announcement is in the works
  18. Igor
    Try release candidate images (safe to use them in case they work fine) from here: https://stpete-mirror.armbian.com/dl/bananapim5/rc/ and follow instructions from https://www.armbian.com/bananapi-m5/
  19. Igor
    Orangepi-config is fork of armbian-config but they are assembling images with some older version of armbian build script. It was fixed. https://github.com/armbian/config/pull/187 You don't need to do anything else, but to wait for release, planned for end of next week.
  20. Igor
    Change bionic to jammy in /etc/apt/sources.list.d/armbian.list and it should probably be fine.
  21. Igor
    @Contributor/MaintainerTomorrow (Saturday 18th, we will start moving armbian-next into main). @rpardini and me will be around whole (our) day as there is some work and troubles are expected. We need to adjust and test CI and in case someone has no other plans for Saturday, welcome for assistance. Thanks.
  22. Igor
    I think we don't update Bionic repositories anymore ... but plan is to move to common as those packages are identical on different releases.
  23. Igor
    Strange thing that software author was actually testing this on Armbian and now it doesn't work properly. Well, I would suggest pinging author(s). "Flash a MicroSD card with the latest armbian image." https://simpnas.com/docs.php @Tido Long time no see.
  24. Igor
    Please try with armbian-next https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ Current master branch is going towards EOL soon. If we have a bug, it will only be fixed in the new system. Worse case use a workaround - remove it withing build script - remove file patch/kernel/archive/sunxi-6.1/patches.armbian/arm64-dts-sun50i-h6-orangepi.dtsi-Rollback-r_rsb-to-r_i2c.patch
  25. Igor
    Welcome to Armbian community support. This is pretty step step This also means you need to get familiar with some facts first https://docs.armbian.com/User-Guide_FAQ/ If our image is broken, then re-branded image into Dietpi (stealing credits and abusing support is most used way of piracy in free licence software world) images are usually also broken. Small chances, but worth trying. A new release is coming out, but there is little we can do in few days before new release. Even removing this board from the download pages represent some efforts, so others won't waste their time trying broken images. Unless someone steps up, donate his time to fix a problem and asks if there is anything to help out.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept