Igor
-
Posts
13937 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Igor
-
PMU on Orangepi 3LTS is Allwinner AXP805, so perhaps checking those pages: https://linux-sunxi.org/H6 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/mfd/axp20x.c?h=v6.1.11 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/allwinner/axp803.dtsi?h=v6.1.11 and board DT, patches & modifications from: https://github.com/armbian/build/tree/master/patch/kernel/archive/sunxi-6.1 Where is the problem? No idea.
-
This will spare you some: https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ Many supports it on paper, but on very few SoCs actually works well. On each kernel upgrade, functions breaks down and all users care is complaining about, while we are loosing thousands of hours for keeping devices operational. If they are unable to answer on cheapest possible way to all at once, in public, (community forums are here to provide this support as any other is not possible), do you think they will answer on a lot more expensive private ways? We could easily lost daily 10 hours if we would respond to our users emails / PM. Since we have no option to hire technical support staff, questions are replied with canned message / deleted. I assume vendors receive about 10 - 20 x our quantity and IMO they also can't cover. Welcome!
-
In order to get best possible support status, please help us with testings. This last testing phase is a final check to see if devices boots and if basic functions work. We can only fix minor issues, try to recreate or remove broken images, but its also good if we write down what is wrong https://www.armbian.com/bugs/ Deadline for submitting test report: February 24th Armbian has its own infrastructure for automated testings. But its limited so we need additional help with manual testings. Results: - release candidate testings. Images has been uploaded to: https://stpete-mirror.armbian.com/dl/ -> BOARD/rc/ Publish report to: https://www.armbian.com/rc-testing/ or comment below. (I have manually tested Odroid N2+, Rockpi 4 1Gb) @Contributor/Maintainer In order to get your work into the release log, add a title, URL to commit / PR and set "Fix version" to 23.02
-
You do understand that you can't remove SD card? Not yet, as boot loader for SPI that would be able to boot modern kernel directly is not developed yet. Otherwise it should be plain simple: armbian-install, then SD card boot, nvme root ...
-
Meetings to support development of: https://github.com/armbian/configng @sgjava @D-mo @joekhoobyar @Ameer Dawood @esanya @TRS-80 @TheLinuxBug and anyone interested in some bash coding!
-
Because nobody volunteered to try, check for possible regressions and submit changes? From project perspective, if @Heisathdon't have much time and interest, there is nothing we can do as project is way way too small to follow endless users & HW needs. We don't have a backup.
-
To change display resolution, add below to the /boot/armbianEnv.txt: extraargs=video=HDMI-A-1:1920x1080M@60 -
Kernel is defining hardware features. Which kernel are you using in "Ubuntu"?
-
Migrate Armbian from cubox-i to Raspberry
Igor replied to Alexandre Raguzzoni's topic in Software, Applications, Userspace
We will continue to provide kernel updates for imx6 (Cubox-i and Udoo) and other 32bit devices, just quality assurance won't be applied anymore. For matured support, as in this case, this is usually not a problem. Migration is possible, but not on OS (different arhitecture & different boot process) but application level - copy data and configuration for nginx, then copy data and config for samba/nfs ... -
Some problems has been solved, but not all. Switch to nightly beta repository that is tied to development and see if it helps. Otherwise we invested our private time to research paths that might get us to the solution or at least to the better state, but we also face problems our "customers" don't want to hear about: - we don't have resources for integration or help on integrating this. Voolonteers are scarse and overloaded. We are already over the limits, - with donations https://liberapay.com/armbian hiring help is not possible. Who wants to work for free, already works, others can't afford, - we are also under constant attack by swindlers which waits we solve this so they can take credits or sell it to someone. Remember that its a big difference helping you or helping someone that is making profits out of our generocity. What would you do?
-
1. Checking the progress of Armbian-next Video: https://us06web.zoom.us/rec/share/ly7gbgZBTY1M4eiumUk6Gp357Jl0RV0h7usdUEGN5WcNKXNIwsOoNHbtoLbBeEje.KCku4wdAigfEI7pB Armbian Next Jira: https://armbian.atlassian.net/browse/AR-1451 @Contributor/Maintainer
-
untilThis week meeting topics: 1. Checking the progress of Armbian-next define upgrade path 2. Moving development related topics to GitHub ideas for moving comm 3. Questions around upcoming release 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
-
https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/
-
Just additional measure to divide kernel and user land packages update. If you want to update kernel packages go to armbian-config -> system -> unfreeze (freeze back after) ... do update & upgrade.
-
We are trying to put together an automated test system for various (WiFi) USB devices. Hardware is in place, but software part is in early design phase:
-
Oh, you want to take care of this?
-
Thank you! BTW. We are just about to switch to a completely reworked version of it: https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ This should also help dealing with RT patches. If we had someone around to deal with RT patch discrepancy, we could also generate RT kernels.
-
-
until
@Contributor/Maintainer FYI By looking into Google search statistics I found out that armbian-config documentation is most clicked with around 3000 hits per month (numbers are for 1/2023): https://docs.armbian.com/User-Guide_Armbian-Config/ https://docs.armbian.com/User-Guide_Getting-Started/ following with 600-700 by those https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://docs.armbian.com/User-Guide_Allwinner_overlays/ 300 https://docs.armbian.com/Release_Changelog/ Not having right mindset to explain this , but those are numbers. -
I am sure there will be! We even played with idea to present armbian-next build framework, but I guess next year or at another conference. I'll have to skip it this year. Somehow too busy.
-
1. Checking the progress of Armbian-next Video: https://us06web.zoom.us/rec/share/vq04OFykxpw7nGp8wJxKME7w8uNf1kMrwHRLldQLTCLJCT-zsZY8KP76aCknhBfN.JyvzRmfR9qulexM2 Slides: https://github.com/rpardini/armbian-build/blob/extensions/README.armbian-next.slides.md#update-feb-1st-armbian-next---general-changes Armbian Next Jira: https://armbian.atlassian.net/browse/AR-1451 2. Moving development related topics to GitHub Summed here: https://armbian.atlassian.net/browse/AR-1529 3. Questions around upcoming release Today is the code freeze. Actions: notify maintainers and prepare them to be ready on testings in two weeks from now notify developers: their code gets into release log only if exists in Jira. Minimum requirement is Jira issue or Jira story with Name, short description and field "Fix versions" set to 23.02 that code freeze is a milestone when we change our focus into code stabilisation and fixing bugs. It is not expected to drop existing work in progress at once but gradually close it. in the code freeze period, there is additional restriction on code merge: pull requests approval from 1 person to 2 persons @Contributor/Maintainer
-
We have DTS, I even tested it few days ago, but don't have the energy nor time to open PR ...
-
Kernel headers on this particular kernel are not in good shape as kernel is not in good shape RK3588 is using changed Linux kernel fork used by Rockchip to bring the hardware up - focus is their hardware functions only. More or less only they maintain it without general purpose fixes. Many standard functions are broken or unmaintained. Volunteers and people at board vendors can only try to fix most critical things to make hardware usable ... until this is not working decently (1Y+), there will be many strange problems to find. Both is good I guess, but can't say how vendor takes care on PR. With Armbian - if its clear what it is about, tested, came from trustful author, ... its merged pretty fast https://github.com/armbian/build/pulls
-
until
😆 OMG. I saw it now Fixed, thanks. -
Not familiar with. You mean you have tried, but it didn't work? So far, booting from USB key always worked, but am not familiar much how Ventoy is combining distributions. If it doesn't work, we must be missing some small details in this UEFI structure or Ventoy is too rigid. I have recently found a bug which could affect UEFI booting, but this is related to the install part. https://github.com/armbian/build/pull/4758/files
until