-
Posts
13936 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Igor
-
Soon, in less then two weeks.
-
This forum is related to Armbian. For general Orangepi questions consider asking in their forums. We don't use Android nor Batocera here.
-
Testing ... 3588 vendor 6.1: Do we have a working? 3D hw support via panfork wiringpi support? npu? 4k youtube video playback under Chromium? 4k under MPV video player? https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml other rockchips. Enabling extensions? - v4l2loopback-dkms,mesa-oibaf What about amlogic, allwinnner? - v4l2loopback-dkms,mesa-oibaf Nice to have: rock-5-itx edge kernel Manually tested: - Bananapi M2PRO Gnome desktop with 4l2loopback-dkms and mesa-oibaf
-
I would not use ZFS with this kernel if I were you. This kernel is provided by hw vendor, by people / business that only cares about (selling) hardware features to work. Everything else is unmaintained and open source community (not just Armbian) developers are not even thinking to maintain this kernel outside that as its concorde fallacy. FYI - it is highly possible ZFS implementation is affected, but you are FREE to do whatever. 90% of solutions, not workarounds, Armbian team (a few people) is unable to integrate into OS with their private resources, public (thousands of you) are simply not there. I can estimate, we could integrate about 30% of resolved suggestions this community generate with few full time engineers. Which costs money. Until you are satisfied with reporting problems only, until you don't care that a lot of value is wasted, there is nothing we can do but keep trying to provide "best effort" support with what we have and explaining this situation. Users perspective will always be like we refuse to help ... but people that are working on / helping Armbian are already long maxed out in efforts of helping everyone, even our competitors. Also. Hardware vendors have exploit of open source community build into their business model. If it happens that you are using hardware with terrible vendors reputation, bugs can be written, but are last to be resolved, some bugs are never resolved ... If you really wanna help everyone, start here: https://github.com/armbian/os/wiki/Import-3rd-party-packages Study and implement a solution. We also have automated dependency testing, which should prevent this problem in first place, but ain't working well and it wouldn't help much in this case. ZFS package is imported from Trixie and yes I understand that upstream package dependency has been recently changed. Until a month ago, we didn't have this problem, everything was working right and now, there is little we can do except disabling importing (which will also delete packages from repository). We don't compile those packages on our own and I am aware that this is not the best way. There are more workarounds - like using Trixie or Noble user space ... Its sadly under-powered, too small. Math is simple - I would very much like to help, but costs are the one that are killing us. Imagine that fixing a problem costs 1000 USD. You are willing to pay 5 USD (or not even that), which is fair if there would be more people contributes their share that you cover all costs. This never happens. They come with another and another problem for 1000 USD (often a lot more, sometimes a lot less) instead. Then its expected that we pay the rest, 995 USD for costs of resolving community software problem, this is simply not sustainable way of cooperation. Even the bug was made by us. I am trying to keep ZFS available. Do you have any idea how much time loss this service already caused with no benefits whatsoever? There are thousands of bugs in open source software and most of people pin everything on us after they download "Armbian image" and images that are produced by copycats as they claim "its Armbian". This particular problem was introduced by us, yes, but alternatively would be not providing ZFS that is capable of working with recent kernels. Which touches to the core of embedded Linux experience and logic. Often we can't match user space and kernel like this is done on 1st class x86 desktop / server / hw Linux world. Even they, often breaks critical things too, even with thousands of full time employees (Redhat). We can't provide that level of services with close to nothing from your side.
-
Which SoCs and on which branch can have extensions enabled? 4l2loopback-dkms mesa-oibaf here: https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml#L40-L95 Mapping config: https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map
-
Oh, yes. This must also work. or "commit:xxxxxxxxxxxxxxxxx"
-
Hasn't changed. https://github.com/armbian/build/tree/main/patch/kernel Just symlinking of subfolder are perhaps adding some confusion.
-
Welcome! Remember that this is forum, not a professional technical support service that waits on problems. We are on the same side. Problems takes years to be resolved as there is nobody behind. They don't invest, you don't invest, we can't invest into support service you might with or expect. We didn't produce this hardware and manufacturer doesn't work with us. They almost literally throw hardware like bone to a dog. Armbian ultra small team have to deal with other things then this hardware / 3rd party (copy of) OS clients problems. Now you know. You came from a project that has bad reputation, you are using hardware from manufacturer that does not support open source software. They are not alone. More makers are abusing community to generate software, support and sales. But some genuine help and there our focus goes. Sometimes we made wrong judgements ... If you mentioned RPi. They are far from being modest example, but they are returning about 2M USD annually back to community. Here small dealers, who have no affection and understanding how non profit community works, are competing how well they will abuse this community. The more the more they will profit - that is why there is so much bad vibes here. Some are doing everything to optimise this abuse. Not talking just about Armbian, but developers community at large. No need to mention, that Dietpi is not a part of this game. They don't suffer as nobody never took anything from them in past 10 years. What did you expect? Truth or fake happiness and prompt resolving of your problem? With our private money and in private time? "Case number 125323". Perhaps weeks of research is needed. Not just trolling on forums? I believe you didn't know nothing about this and it feels me bad that I have to tell you this. But this is your problem too and I hope now you see why. If open source developers are not happy, you will not move them with anything. Just trying to draw you a bigger picture. Raspbian / RaspberryPi has IMO 20-30 full time engineers for supporting clients and they have classes easier job then we do. We have not a single one.
-
You might insult many people if you compare Armbian with Dietpi. They download Armbian (firmware is binary copy), run BASH script to re-brand, add their script junk and sell as "supported". When bug is found they say "oh, this trash Armbian", when someone say compliment, they take it. This is how piracy works in open source. Compliment and recognition of work is everything. They contribute nothing to Armbian, nor its possible to take anything. Where we would, as community, progress, if we would just steal and pretend? Board manufacturer is responsible to fix this problem. They know how and where change is needed. But ... they compete with OS we made with us. Are you sure, you are long enough around to see it all?
-
Actions: updating template for building standard support images. Keeping Jammy CLI and Jammy XFCE desktop, upgrade other Jammy to Noble. Keeping old stable user-land with more recent kernel is actually a perfect combination. download pages were adjusted to current status. branching to 24.5 freezing sources merging all board status changes making RC builds updating application builds lists updating 3rd party packages import regenerating repository with Ubuntu oracular switching nightly build targets to Ubuntu oracular generating RC images for application deployments returning armhf to Noble / Trixie RC0 RC1 (is in making) for testing: HomeAssistant, OpenHab, Security (Kali) https://github.com/armbian/distribution/releases/tag/24.5.RC0 Nightly images https://github.com/armbian/os/releases/tag/24.5.0-trunk.580 Stable builds (RC) https://k-space.ee.armbian.com/incoming/ https://fi.mirror.armbian.de/incoming/ Automated testings https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Report: - problems Suggest: - images that needs to be added, changed status @Contributor/Maintainer
-
Orange Pi Lite. problem with latest firmware.
Igor replied to AlexTransit's topic in Allwinner sunxi
apt install armbian-config -
Switch to nightly kernels (those are becoming stable in two weeks anyway), update, reboot. Remove / Add kernels and it will work. Use armbian-config -> software to make this easy way. Welcome!!!
-
Armbian with preinstalled Home Assistant supervised
Igor replied to Igor's topic in Software, Applications, Userspace
Thank you! https://github.com/armbian/os/pull/184 In case anyone can verify if this works / test this assembly, before end of this month, it would be awesome! Edit: tested -
Armbian team has very limited resources, we can't pick this up, and I doubt there will be a pileup of people from community doing this. If you (or anyone reading this) is interested to maintain CB1 and/or CB2, sent me PM, and I will ask Bigtreetech for help.
-
Each code change represent danger that some feature out of tens of thousands will stop working. One bug is fixed, something else can and do break down ... Nobody knows when this happens as nobody can't test all features. Testing is expensive and we run this - for public good service - mainly with our private money. Since information does not exists, we will not be keeping list of working / not working features for you. Especially not if this require additional expensive manual work. I told you to verify with latest image from development as this might just work. You didn't and there is little we can do from here. If you didn't know, we provide users results of automated testing, which is sadly primitive and can't test complex functions as in this case, but it will stay that way as we have not enough support/interest from anyone (but everyone would like to have this info) If you need better info that this https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results apply here: and start working for us as a full time volunteer. I know you will not, but this request is on same level as yours. So far, in one year, we didn't get anyone.
-
I am not your personal assistance. Orangepi (mainly as they are chepest) customers are demanding thousands of fixes, changes and improvements. Personally I can't answer to this and other thousands of issues that are found in code / text. I would love to but its impossible even as a team and I have to run the project and sometimes I chat on forums. Mainly for fun and providing hints. I can't be your partner in resolving your (clearly business) problem. I would love to, but Orangepi treat as not good and we treat their clients accordingly. Use other board and you will get help. Isn't that stupid? Yes, but this is one of ways we fight abuse that is targeted toward open source developers. In this segment of open source, there are things you might never experienced with your work in open source. Isn't it better to be open for other perspectives? I believe in yours. Perhaps this will give you a picture on resources you are addressing? You are not the only one that is requesting support. Our resources are 1/1000 of needed. We are developers, we maintain serious and complex system and we don't have much time for individual problems. Regardless if you think we should be more attractive. We can be, but then we have to kill R&D. Which is source of sorrow, frustration and costs. Why do you even try to be accepted over the line? And why you think this problem is important enough to be even discussed? Why don't you resolve a problem you find? And on and on. I told you already that we only loose if we fix a bug. We have competitors, that invest nothing, while they can provide the same. In order to catch them, we have to invest less and less. And be more attractive at the same time, agree with that. This means we should invest into sales a lot more, where again you know what has to suffer. Absolutely. We love that, me included. But I have to run this development on totally different level. If you would set our priorities, we would already be long dead. Imagine users, who in big majority have no clue about how much time some problem is needed, they don't care how many problems are already been worked on, what is team capacity, and on and on. Remember also that, at the end, support goes under "best effort" principle. If serious and life important problems are not done, your will wait. A week, month, year ... never. This is how it goes and this won't be changed. Not sure what you mean by that, but open source is like freedom.
-
If you care so much about people not wasting time, documentation is open source, invest your time https://github.com/armbian/documentation and stop wasting my time. Our project is saving all of you years, not just months. And you still don't get it and want more and more. Remember that not you, not the one that generates problem contributes virtually nothing. Buy a PC, which works well with our product.
-
You are using a lot of our work also if you use images for Orangepi 5 with different name, from different DJs and / or even official ones. Official Debian and Ubuntu images are shameless copy of Armbian, assembled with old tools and slightly different - some features will work better, some not. As they are never upgraded, they never breaks. We work together with Joshua-Riek on kernel and other things. Images should behave more or less the same, but as they were not released at the same time, diff exists. If your problem is fixed in our images, nobody will check this for you because this is not a commercial product and you are not a customer - there are daily automated builds at the download page. Try them. We can't spoil you with writing fancy manual and make better support as we will gain nothing. Competitors (Orangepi and copycats) are not copy pasting code we made (remember this is open source world), they also copy pasting instructions we make. Ask Orangepi to cover those costs (they will ofc not) or you cover them. Problem is that for 99% of projects costs we have to find elsewhere (most people have jobs somewhere) or do it for free (slave work when abuse is used. And this exists in large scale). Donations only cover 0.5% ... Asking for more, from end user perspective, is rude. Mitigating your debt first? Every donation counts. Complex software without active maintaining will start to fall apart, but people that made money with you will be long gone by then. Regressions will happen and again we will be the one behind ...
-
Because some features on website still has to be done manually. For which we don't have sufficient man power, org resources or coding resources to complete automation. If you are PHP / Python coder and want to contribute resolving this problem, PM.
-
1st sentence: https://github.com/armbian/community/blob/main/README.md once per week
-
In most cases, Armbian has full control over hardware. We don't need and avoid closed source manufacturer flashing tools. Where this is not possible (example), we recommend using 3rd party manual. End users doesn't need this feature to work and RKflashtool should just work, but its not officially supported. Consider (Gold) professional assistance in case you expect someone will fix bugs in your software. Or contact Orangepi to fix this for you.
-
Armbian with preinstalled Home Assistant supervised
Igor replied to Igor's topic in Software, Applications, Userspace
I will look into this when time permits but I don't promise to stick in researching very long. Kernel behind this specific hardware, this image, is developed with a solo purpose - to sell hardware and its dead end. For amateur usage, running desktop and similar toying this is usually enough. Rockchip cares only that hardware features works, everything else is unmaintained. We are looking at possible impossible tasks, weeks of work, which is something I can't afford to do in exchange for compliments. This is not Armbian problem. Try switching to normal mainline kernel (named EDGE, 6.8.y, that should not have those errors and that I know where to look for fixing if warnings will pop up. Also I can predict I will not lost more then few hours). -
Armbian with preinstalled Home Assistant supervised
Igor replied to Igor's topic in Software, Applications, Userspace
This is hard to say as we are talking about non standard Linux kernel. If HA works, IMO you can safely ignore those problems or: New kernel is being developed for several years and it might already be working for this use case. You can try by switching to it (armbian-config -> system -> alternative kernels -> select EDGE 6.8.something), but I give you no warranty that it will work. You might need to start with a new image. If it works well, report back and we will generate images by using that kernel. I know many things in graphical areas are missing there, but for this uses case we don't need HDMI output anyway ... -
Armbian with preinstalled Home Assistant supervised
Igor replied to Igor's topic in Software, Applications, Userspace
Try this image https://github.com/armbian/distribution/releases/download/24.2.2/Armbian_24.2.2_Khadas-edge2_bookworm_vendor_6.1.43-homeassistant_minimal.oowow.img.xz 5b https://github.com/armbian/distribution/releases/download/24.2.2/Armbian_24.2.2_Rock-5b_bookworm_vendor_6.1.43-homeassistant_minimal.img.xz 5c https://github.com/armbian/distribution/releases/download/24.2.2/Armbian_24.2.2_Rock-5c_bookworm_vendor_6.1.43-homeassistant_minimal.img.xz None of those was tested. -
Headers package version mismatch 24.2.5 vs 24.2.1
Igor replied to Michal Fita's topic in Raspberry Pi
Usually research (or active sponsoring of our team) is needed to determine what is wrong. This can take half an hour or several weeks. As active sponsoring is still way below 1% of our costs, I have absolutely no interest to cover expenses of any research and then provide findings in exchange for nothing. This is deadly for the project and our mental health. Usually additional questions / research are requested, which only makes developers more frustrated. This is quite common delusion here - that open source developers are stupid and just happy to work for free. Yes, limited to things they like to work on. There are thousands of problems and they are not ours. They are yours, even "sold" under Armbian assembly. If you can tell who will pay research for you or for everyone, I will find someone that will do it. Or not. I have no budget to spent. Since this is open source, anyone can finance to tell what is wrong. This is the essence of this forums. ... and perhaps another week that solution is developed, implemented and tested? Perhaps a lot more. Ain't simple to answer to this question. All this require serious investment from our side to support worse customer there is Don't take this as an offence as this is a part of the game. This only have ends at different point. You can donate, or not. If you want that this is fixed, this has different procedure. It require establishing business relation, which procedure is by default expensive and for resolving one problem ... its a lot better to skip it anyway. However, starting point is trying to make a support contract, make large enough donation that we don't need to pay for everything as we will not move. This is not something granted as I need to be sure that I can keep my promise and meet your expectations. Armbian CI can only be executed by Armbian staff member with sufficient privileges. I am talking about CI that is auto remaking all our code (kernel, headers, ...) on code change. This is dropped to APT repo http://beta.armbian.com, which is updated daily and at every code change.