Jump to content

Igor

Administrators
  • Posts

    13937
  • Joined

  • Last visited

Everything posted by Igor

  1. This weeks meeting topics: Merging of next generation build framework Primary goal is to understand benefits it is bringing as we all will need to sacrifice some time in order to review it, then merge and fix remaining bug. Despite our current system produces images, we have many bugs and dirty workarounds that this upgrade is addressing. The future of rockchip64 family Main goal is to make it maintainable again. GitHub development and review process Main goal is to motivate people to take more responsibility for reviewing and merging. Define clear rules. Goal of the 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 Conclusions: Everyone interested should watch a recording (~1h) and place a comment below. Comments will be discussed here or at next meeting. Before we can do anything in real regarding merging NEXT, we need to clean patches but also address several things, starting with those: Making a tool / module for patch generation (@rpardini) Preparing guidelines for review and contribution (@giddy) Move repo management from the build system (@igor) How can anyone help? Cleaning the patches! 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. armbian-next_-_meeting_21.dec.2022.pdf
  2. Nobody will read your observation, so why would that be important? Hire a developer and explain him troubles you have. Then send a patch to Armbian or upstream. Good luck!
  3. I know this very well, but I also know that bug resolving can easily take 1000 x more. Lets trade. Your week for my 5 minutes. Do you feel insulted?
  4. Igor

    Video Playback

    No.
  5. Solution is to set to previous boot loader in a board config, similar to those.
  6. Igor

    Video Playback

    We don't have enough of people to tweak desktops well and I am by no mean an expert in this area. I am more interested into low level. KDE is maintained by nobody / vanilla install ... I am trying to address XFCE, Gnome, Cinnamon, while for more (in fact already this is out of possible) ... https://docs.armbian.com/Process_Contribute/ I am just playing with Rock 5 at this very moment, running Gnome (Jammy), kernel 5.10.y ... Chromium under Wayland is accelerated, under X, not. Not sure if we want to enable Wayland by default as its not very stable. Arch / Manjaro don't care about stability at all.
  7. Igor

    Video Playback

    If you want acceleration within Chromium, you need to switch to Wayland. It doesn't work under X.
  8. That should not happen. What apt-mark showhold tells after installing OMV. It should list that kernel and dtb package are set to hold back from updates. Another workaround is to comment out repository /etc/apt/sources.list.d/armbian.list
  9. Igor

    Video Playback

    Don't have Rock 3A, but 3D acceleration is present in all Armbian desktop builds OOB since years. Video acceleration within browsers? That is something else and doesn't work in Linux. Any. Their ARM section development is more or less porting from Armbian and build what comes to upstream.
  10. https://www.armbian.com/lepotato/ Gnome Jammy desktop comes with Wayland support -> logout / login with wayland.
  11. Recent boot loader has some issues. Our test device is running SD card, where problems weren't detected. Try to build an image with changes similar to those. By using previous boot loader ... ... adding this: BOOTBRANCH_BOARD="tag:v2022.04" BOOTPATCHDIR="u-boot-rockchip64-v2022.04" to board config file following by full recompilation.
  12. This is not related. But it seems you don't understand. There is a group that is doing something and you are from the group that is consuming that work and pressing on the first group. There is no joint effort whatsoever. This is an illusion.
  13. This forum exists for this. Here on graph below https://armbian.atlassian.net/jira/dashboards/10103 you can see how long it takes before tickets are closed when developers are sponsoring you at close to 100% and not the other way around. Biggest challenge and personal time loss is organising and coordinating activities (what you are expecting can easily be a full time job for several people) so we are rather relying on automated testings. Its significantly cheaper, more reliable and can be executed at any moment. We know for most of the issues, but since day has only 24 and not 2400 hours, this is best what can be done. What you would do? Project needs more help in other non technical tasks.
  14. It seems that support for SPI got lost when upgrading kernel. Nothing unusual for software where maintaining is sponsored by its developers in their free time. Workaround (thank you) - previous 5.10.y kernel images from archive works well ... use it and don't upgrade (apt-mark hold linux-image* and linux-dtb*)
  15. Worth trying older armbian-firmware package. Perhaps changes in https://github.com/armbian/firmware break it ?
  16. SD / eMMC card compatibility. Possible workaround = power cycle several times. I found the same problem on Bananapi M5 and it seems this https://github.com/armbian/build/pull/4523 and https://github.com/armbian/build/pull/4524/files helps. If you can, try this. I'll double check when possible.
  17. Now this is odd. I just built current and edge images from sources in no time. Hmm. Try with Docker as a last resort. Can you provide debug/output/compilation.log
  18. You need to adjust sources that will be compatible with kernel 6.0.y If you know what needs to be done, then it looks like this: https://github.com/aircrack-ng/rtl8812au/pull/1008/files some of ours https://github.com/armbian/build/tree/master/patch/misc Can be few hours of work ...
  19. Igor

    booting device

    This is my test M1 which runs perfectly fine. With kernel 6.1.y it will be declared supported / stable. Boots from SD card, root on NVME. This is currently the only way as we don't want to use dirty proprietary boot solutions provided by Hardkernel. Support for SPI boot / NVME root is under development, mainline ATF is floating around , but integration and testing is a lot of work ... we receive no funding so things doesn't really move fast. I can't tell when this will be done and integrated. Probably mid next year.
  20. This should do: https://armbian.atlassian.net/browse/AR-1412
  21. We have been applying many fixes for this ... is this happening with latest image? Or this is some old build with upgrades? Always provide this.
  22. As this is not supported target anymore, you need to build from sources. Build from pre-build packages might not work, from sources works:
  23. Which desktop environment?
  24. Aha, ok, we merge this then. Remaining ones for H616 some other day ...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines