Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    13961

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    You can certainly change all this on your side, but if you want to help us providing nicer desktop, you are more then welcome. Most of the people around Armbian is dealing with low level problems and we never get to the problem of desktop or icons that are used there. Actually, we haven't change how desktop looks in years ... If tweaking is in question, welcome, complete design renewal? I am on conservative side regarding this as my first app is terminal, second chat then browser. @monkaBlyat also promised some help in making desktop looking better. Teaming up?
  2. Igor

  3. Igor
    Video Summary: 1. Changes on "about Armbian" An email will sent out to all people mentioned on new "about armbian" to confirm their presence as is, chose anonymization (forum nick instead of "first name l."ast name) 2. Armbian versioning and repository management - we are temporally going back to original versioning (as known from master branch) as its one step to far - repository management was already tested with previously mentioned revert. It is already done, but need cleaning and making PRs - we will drop DTB package and move dtb blobs to the /boot/ Short term to do: - matrix to generate JSON for images and packages generation - add warnings and exists on deprecated functions such as KERNEL_CONFIGURE=yes which is causing users many problems - prepare more design related documents and instructions for developers to join in easier 3. Build framework 1st run configuration We ran out of time, next week. @Contributor/Maintainer
  4. Igor
    Nothing unexpected. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Porting this feature to mainline? Download SDK, look into the source code, check documentation, ...
  5. Igor
    This week meeting topics: 1. 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 2. Armbian versioning and repository management 3. Build framework 1st run configuration 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
  6. Igor
    I also use it with Jammy / Gnome, image with preinstalled desktop, and it works. tells nothing. Logs or at least telling a lot more then "i am using Armbian". Besides different HW properties that could cause troubles, there are different package releases and different DEs.
  7. Igor
    IIRC serial on imx6 kernel broke down year(s) ago and it seems it stayed that way. When that happened? No idea. Just saying this is possibility.
  8. Igor
    I had a discussion with Oleg about packaging. He got rid of DT package long time ago, while we kept it for "don't touch it if its not broken" reasons. Since we already break everything apart and we need to adjust versioning, repository might also need to be changed ... should we get rid of the DT package and place DT blobs to the same /boot/ location as in DT package (as done in media kernel)
  9. Igor
    Armbian doesn't have problems. We didn't design this wireless chip and we didn't write drivers. We already tried to make the best out of this, we already lost months while you didn't even noticed. Try one of those. Or just switch to kernel 6.1.y where this driver anyway doesn't work (yet).
  10. Igor

    Mainline kernel

    Igor replied to Igor's topic in Rockchip

    With working PCI https://github.com/armbian/os/releases (look for Rock5 "midstream")
  11. Igor
    It has been silent for a year Anyone has thoughts or tried to merge Asahi Linux into Armbian? Apple mini could serve as a nice small Armbian build machine or just general purpose workstation. Well, compilation runs on MacOS, but running native Armbian Linux would be a lot cooler. The task of bringing Asahi family into Armbian https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ probably should not be very difficult anymore https://github.com/AsahiLinux/docs ? Anyone with a strong enough wish & ability?
  12. Igor
    You need to provide more information: - which image (link) - which hardware revision (perhaps a photo) - where booting ends - is this the only SD card you have ...
  13. Igor
    https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one This is clear, right? Armbian is using mainline kernel, where not all features are developed or worked the same. GPIO's https://www.acmesystems.it/gpiod UART is where it is. If its enabled by default and usually is, then is on the same UART as legacy kernel. Just in some cases its not (for no apparent reason).
  14. Igor
    What was the install procedure? Strange. Perhaps there was something wrong with burning to USB? Use some other USB key? Usually its something stupid
  15. Igor
    I have tried yesterday https://github.com/armbian/build/issues/4892#issuecomment-1460176070 and last image + update, everything is fine. At least for me.
  16. 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)
  17. 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?
  18. Igor
    We need to provide this automatically for user.
  19. 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)
  20. Igor
    My 2c https://github.com/armbian/build/pull/4904
  21. 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.
  22. 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
  23. Igor
    https://us06web.zoom.us/rec/share/-uF9wa9jK1U0CA9KQqIc7hdsRCAEh1QwMQy987GkuvogqVFiur1tGXRrQbO2znsg.g0JXx4SYwDuPZ3zW Open issues: https://armbian.atlassian.net/jira/dashboards/10103
  24. Igor

    Recordings
  25. 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept