Igor
-
Posts
13657 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by 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
-
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
-
@WarHawk_AVG Can you try with self build image?
-
This is usually the only option. Many of those onboard WiFi chips has drivers in a complete sh* state - which is read as "cheap hw with almost no vendor support". Maintaining things as such is a lot more difficult and expensive. We could drive this wireless section better only with a few full time WiFi radio specialists, but project can't afford that. With what Armbian have, it already have a class better support then Kali Linux, which is a dominant name in "hacking" WiFi: This is what author wrote there 😇 and I am happy he noticed this. I am not aware anything is happening in this regard, but its possible, look around ...
-
Video Redesign board support packages CLI & desktop We focused great deal of time to debug and agree how to deal with board support packages. Changes will be added to this merge request XML / JSON generation to support CI XML/JSON development is also progressing nicely. BASH part is done, while there is some work around Python assembly Build framework 1st run configuration Ran out of time for this topic. @Contributor/Maintainer
-
Features complete and stabilisation on mainline kernel is expected within next 12-24 months, some features might never get there. Those images are released for advanced users & testing - not sure if there are many people that can answer this question - sources are available. Support for bleeding edge development is n/a as it expenses are completely out-of-range. If you have time, dig in - its probably the only way.
-
This week meeting topics: 1. Redesign board support packages CLI & desktop 2. XML / JSON generation to support CI 3. Build framework 1st run configuration 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
-
If we would have time / resources we would do this months ago. In case you want to help others: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/
-
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.
-
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. -
[ 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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
This would help identifying the problem.
-
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.
-
This is something I can't answer.
-
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.
-
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.
-
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
-
failed to install OpenVPN Access Server
Igor replied to joula's topic in Software, Applications, Userspace
This way doesn't work? https://pivpn.io/ -
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