Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    13897

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor

    Mainline kernel

    Igor replied to Igor's topic in Rockchip

    Those builds are at least daily. We keep last 32 releases as makes little point in keep them all ... I changed link to release download page.
  2. Igor
    We have no partnership with Allwinner nor MangoPi but anyone is welcome to invest into our team. Without, nothing can happen as we are not an investment bank.
  3. Igor
    [ 9.384292] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 9.387030] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2 [ 9.411294] usbcore: registered new interface driver brcmfmac If firmware was up-streamed, then apt install armbian-firmware-full + reboot will do. If not, you will need to find those files and install them on hand.
  4. Igor
    Any from https://www.armbian.com/download that this forum perhaps knows something about? Don't know if this image will fully satisfy you, I don't know if images works, but better than this is unlikely to find anywhere else. All images provided by download can be built from sources and debug on the way.
  5. Igor
    That would be my guess based on experiences. The more people are inexperienced, the more this assesment is underestimated. End users perception on this is bizarre on the other end. They report a problem and come looking for a solution right next day, the day after, ... then they write an email and complain about. This is not personal or directed to you - I don't know you. Its more like a general observation. Bugs are hard to estimate right. Sometimes you find a problem in no time, sometimes you drag it for months sometimes you tune out, forgot about ... You were doing something, other people were doing something ... problem is still here. I am more afraid this was estimated too low as this common research goes on the bill too.
  6. Igor
    Look at forums. Its mainly developers, mainly hard problems. Many topics remain unanswered as there are very little people that are able to understand and answer. I am happy you are offering your help, but estimated several weeks of developers time for few minutes of yours? Try to picture how this sounds from other party perspective. Try to find out how to provide help that would match this. I don't have few weeks, sadly not even a minutes to put into this exchange. Just a tip.
  7. Igor
    I disable them since I got tired of listening how it doesn't work. Yes, images for this hardware are broken, but we can't fix them without significant investment of our most precious resources - time - which is very limited. We have nowhere to take from and we can't hire a person to fix this for you as by providing you this we only generate loss. (i made a link to archived versions now, but don't know what is the status and if upgrade will be survivable) It works enough for running a simple server. Yes. Most of those boards does not have universal way of booting (UEFI). And those who does also need a separate boot loader to be shipped with. Which someone needs to maintain and you need to install it by hand ... which still adds another layer of troubles. Bringing boards to standards is yet another expensive project within this project. Remember that you are not financing this, things go super slow. Sometimes they stop for some time, for a years, forever ... That is automatic so its relatively cheap operation. Images doesn't work because build mechanism for single one is broken. Once one works, all works. One single day of maintaining hardware costs us more then we are asking from you to help us fund new build server. Which will help us saving some time. Which should be in your best interest ... and this is something impossible to communicate.
  8. Igor
    Nothing strange. All software has bugs and I don't fully exclude there is a problem with Armbian, just for this, I would say its probably on their side ... things are complex and is difficult to be sure without a research.
  9. Igor
    This means that OMV, which anyway completely changes OS, somehow breaks networking. OMV was working well for many years, Armbian was even official partner ... As we didn't change anything in this regard, I would assume they changed something so try also to find this answer on their forums.
  10. Igor
    This would help identifying the problem.
  11. Igor
    Video 1. We have cycled issues that are opened and found out there is nothing super critical at this moment https://github.com/armbian/build/issues Most of are minor issues or small to mid feature requests. 2. First run configuration topic was skipped as key people on the topic were not on the meeting 3. We focus great deal of time on idea how to improve interaction with community and how to motivate people that use build system to help arranging documentation. As this is more or less our only option. Another alternative is that someone dedicate his full focus and check all feature. We checked "developers section" of docs and identified sections which can be removed as they are deprecated. The same for build switch. We didn't go into specific switches, but decide to generate section "Deprecated" and moved all features that are not maintained or broken, there. To wait for maintainers. Also we would set a date when feature is going to be removed unless it will be covered by someone.
  12. Igor
    This is something I can't answer.
  13. Igor
    Is 4 years old build we never made and has nothing to do with us. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity This is how you verify if this is genuine Armbian software. If it is not, you are asking for help at wrong location. Images from https://www.armbian.com/olimex-lime-2-emmc/ were tested on HW revision we have in the test lab, but we don't follow possible phy changes on boards. This is in the domain of board vendor.
  14. Igor
    All overlays are present in the image - we are using official Raspberry Pi kernel. Missing is easy handling via a menu like its done for some other boards. Overlay handling is the same as on official Rpi OS (not via armbianEnv.txt). We could not get to the state to standardise Rpi into our scheme.
  15. Igor
    This week meeting topics: 1. Identify critical problems finish caching for other packages 2. Build framework 1st run configuration 3. How to enable documentation updating? 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
  16. Igor
    This way doesn't work? https://pivpn.io/
  17. Igor
    This is how it goes on KVM ... if it helps. wget -q -O - "https://redirect.armbian.com/region/EU/uefi-x86/Jammy_current" | xz -d > image.iso sudo qemu-img convert -f raw -O qcow2 image.iso /var/lib/libvirt/images/image.qcow2 sudo qemu-img resize /var/lib/libvirt/images/image.qcow2 +10G virt-install --name Armbian --memory 2048 --vcpus 4 --disk /var/lib/libvirt/images/image.qcow2,bus=sata --import --os-variant ubuntu22.04 --network bridge=br1 --noautoconsole
  18. Igor
    Try with something that is close to standards, mainline based (older) rockchip / allwinner, x86, Rpi ... when this is confirmed working there, move on
  19. Igor
    Then apologise. People usually wants to change boot logo on commercial deployments. But we don't need that, as we have bugs on the list for several years already.
  20. Igor
    Sadly can't be more precise about that. I have tested upgrades last week, but system is on POC level. @SuperMaximus Since you are using us to help you to make money, this is one way to do the right thing: or by choosing https://forum.armbian.com/subscriptions/. If this is too much., then please do not remove our logo from your product, ok?
  21. Igor
    If you didn't download image from www.debian.org or www.ubuntu.com, then there those OSes does not support this HW. RebornOS is a desktop tweaking on top of one of those "Debian" / "Ubuntu" stock images. Just to straighten things ... and yes, this is common, nothing extraordinary. Armbian maintainers are already totally overloaded, your support is almost not existing, vendor does not support us ... there is little we can do. We don't have endless time or equipment to support random purchases people made. But as our build framework is well maintained, making an image is pretty straightforward. Anyone can do it https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ but maintaining and dealing with problems, that lies in this cheap products, is another story.
  22. Igor
    Reproduced. https://github.com/armbian/build/commit/1a59152009a74ad3312cb7f02ab8e6a8a9a61a3c#diff-8752ea87e0340f217187b70f7b08735d872a14c0467d02a6285222e594db3299R71 https://armbian.atlassian.net/browse/AR-1611
  23. 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?
  24. Igor

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

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept