-
Posts
14582 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Igor
-
FYI. We build all targets in automated way, once per week: https://github.com/armbian/community
-
Armbian still supports /etc/rc.local startup way: #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. YOUR_COMMAND exit 0
-
Linux Kernel Packages on edge rockchip64 naming scheme?
Igor replied to Michal Fita's topic in Advanced users - Development
Armbian is hardware oriented Linux where Debian like userspace is attached on it. In embedded Linux none of this has much value ... and also people who sold you hardware provides Armbian Linux (branded as Orangepi OS) with their Rockchip private static kernel which will never be updated. Its there to die off. This is the norm. There is a long path from that toward some traditional norm. Millions of dollars or thousands of hours of community and business that are investing their time here. tl;dr; Complexity. We needed several years to fix all garbage code in all kernels, where headers compilation is a matter of randomness already on native compilation. When you add different compilers (different debian / ubuntu package base) and cross-compilation ... on 50 different kernel forks, which some, have so many custom code that its hard to say its a Linux kernel. Upstream Ubuntu/Debian usually only deal with clean mainstream world. We provide around 50 different kernels. From UEFI generic down to per SoC and further per vendor. Naming convention, current, edge (and several more) provides some simplicity in this world. And helps you to not think much. Supported hardware is tested daily: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Which means you are generally safe - if you stick to supported hardware! Our hardware support is significantly better then Debian / Ubuntu. There users tests (except generic x86), bug response cycle is significantly longer. Our system was designed from bigger picture then Debian way (Ubuntu just copy this tool as they have no other option). It works perfectly fine and all our secondary tools are adopted to it. We looked into and even trial flash-kernel with Raspberry Pi and I am more than happy we recently drop it. Its unreliable amateur maintained tool which IMO is not very useful when you go outside RPi world. On the other hand, most of Armbian engineers comes from embedded Linux. We have significantly wider know-how about embedded Linux (which is needed to maintain such tool) then generic desktop server Debian / Ubuntu world. We checked that tool and there is nothing to learn / take from there. We have several ideas for improvement and changes here, there are 3rd party special industrial grade solutions too ... but all those ideas quickly dies due to complex and expensive integration. We can't finance this and amateurs don't work on long term complex integrations. No. If HW is not on supported list, we have no information if this hardware boots or what works. This is on you to determine and share withing the community if you like. More can ofc be done, but someone needs to volunteer and assembly this information. Until then, it does not exists, its just a GitHub commit log(s) ... If you do it right, big, if you give this task to maintainers, small, ... hundreds of people are asking for something useful all the time and there is a few people that does something on the other side and are not supported by community. Study build framework, make a PR and make sure it gets to the documentation is the right and friendly way. I hope this at least partially answers. If I would had hours, I could write a lot more on the topic Yes, we have reasons why this is so, but things can always be improved. -
compile.sh PREFER_DOCKER=no - documenting the flag
Igor replied to ag123's topic in Advanced users - Development
There is ongoing activity to set some top level re-design and prepare ground base. I doubt random person would start to do that, so this is what we have to do. I also already answered on similar topic in Documentation tickets: https://github.com/armbian/documentation/issues/390 -
You are delusional? Offer? From you? You asked a question about the topic you clearly don't understand well, @ag123 sponsored you answer / education / FYI and that's about it. You clearly have no clue what we do. Do your homework. Insulting us is not going into your favor. What are you waiting? If its free for you, invest your time. Ours is not free, so ... good luck.
-
-
-
It is important that you understand what I am talking about. We don't represent Linux kernel. Actually nobody does. Linux corporation https://www.linuxfoundation.org/ is the closest entity doing that and even they are considered small and poor in the corporate world they are in. What Armbian (a few people that maintains this place) does? We provide tools and build kernels with small but important changes focused into specific single board computers. We add valuable code that this generic kernel code (https://lwn.net/Articles/915435/) becomes usable. Sometimes only to some degree. And that's it. You want to develop something but you seek sponsors of your idea? No problem, just find someone else. We already burned all yearly budget. Negativity is shaped by your (over)expectations. From our perspective, they are totally off the chart. Once you get it, you will perhaps even support us. Until then, you will treat us like sh* and we will both be unhappy.
-
Never did. We sponsor your consumerism to the degree we want. It seems you don't understand what open source is. Download what we give you and do whatever you want with that. What is the definition of poor? Can poor people invest into software development that you can consume it for free? We are already investing millions into open source, but everyone has spending limits. Since you (public) will never understand yours, we have to stop your nonsense in some way. But if you finance, we can hire, if not, you can hire yourself and do whatever you want. If you succeed, we will download and use your idea. Welcome to open source world.
-
This is open source world. Once we have it, everyone else will have it to. To maximize our time, emotional and financial loss? We are already loosing tens of thousands of hours every year for what we provide now. Donations, as only source to cover this wish, supports our current work in around 0.5%, which means yearly budget for 2024 R&D is already long gone. Most of HW dealers and predatory users & competitors not just steal (take) in regular ways, but also generate damages however they can, for fun or to make profits for themselves. Re-thing your question. Before you suggest us what we (anyone that operates in open source) need, we we need something from general public: understanding and funding.
-
... those sources are not compatible with modern Linux anymore. This documentation was written 4-5 years ago, so this example worked with kernel v4, perhaps v5. Mechanism wise, things works. https://paste.armbian.com/axeveqolex.bash
-
If you didn't improve anything ... we provide daily / weekly automated builds for everything, supported or non-supported. https://github.com/armbian/os/releases/latest https://github.com/armbian/community/releases/latest Leeboby is Xunlong employee which made those fake and broken Armbian / Kali / * images ... to trick you that Armbian support this hardware. No, we don't. Yearly budget is far less then zero. This is fake Linux / "Android kernel" you don't want to use in production. It shows HW features, nobody maintains it. You can see leeboby commits there too. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
-
https://docs.armbian.com/Process_Release-Model/#agenda Is this list still valid? Supported: WIP Community supported where we could also look for re-enabling supported status. Criteria for Supported must be beneficial to the Armbian project Armbian team must confirm and agree upon all supported boards statuses a named individual as “maintainer” with GitHub ID must be preset in the BOARD_MAINTAINER within Board Configuration File a named individual must commit to providing “best effort” support for their SBC on the Armbian forums maintainer must participate in the Release Process maintainer must sign-off that device has been tested, is stable, and ready for release during release process maintainer must have physical access to the SBC they are supporting maintainer can operate under pseudonym but must reveal his identity to Armbian management maintainer should attend developers meetings held every Wednesday 7:00 PM CET when whole support burden is carried by maintainer and Armbian team, it will be labelled as “Pro bono” More here: https://docs.armbian.com/User-Guide_Board-Support-Rules/#criteria-for-supported Example of maintainer proposal: - add or remove board X from supported. Reason: its broken and I don't have time / I confirm it works, will monitor and collaborate ... - upgrade board X from WIP to supported. It works decently / well, I steal dealing with it, there is upstream support ... or remove as there is no progress, too many issues - board X from community section should become supported because ...
-
sudo armbian-config -> software -> headers install
-
encrypted Root disk - be careful with upgrading kernel
Igor replied to bushw's topic in Pinebook Pro
Also on 1st class hardware it does not go without issues: https://www.google.com/search?q=why+kernel+upgrades+breaks+features On trash ultra cheap and forgotten hardware, where Armbian is trying to make a difference, breakage % is significantly bigger. Every kernel, that is work of thousands of people (some forget to test changes), breaks features even we invest tens of thousands of hours into stabilizing it. There is virtually no support from industry and no support from end users, but we still managed to build automated monitor for upgrades on many boards in automated way: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Sadly, we don't test Pinebook, not complex functions as this and not all possible upgrades. Expanding testing to that and patching would cost additional few millions which is simply not possible to secure from this. In past year, nobody applied to serve as test engineer to develop this further. Other Linux distributions are far far away even from this. Install Armbian on a desktop PC. -
We also have plenty of memory nowadays and memory is still significantly faster then ssds and does not wear out. sudo apt install --reinstall profile-sync-daemon This is probably all we do here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L215-L237
-
Download Armbian with HA (v25.2) Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual) Home Assistant Supervised is, more or less, a full blown Home assistant. Install Home Assistant on any Armbian Bookworm (experimental) Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build. I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation. Tested on: Odroid N2/N2+ Odroid M1 Nanopi R4S Rock 5B Uefi-x86 Orangepi 5 Nanopi M6 Rpi400 Khadas VIM1S Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection) Bananapi M2 Pro Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞 DIY Contribute Support: The supervised installation method on Armbian is not officially supported by the Home Assistant project. Additionally, installation on hardware that is not officially supported is also outside the scope of support provided by the Armbian team. You are welcome to report high-level application issues that are reproducible on the official Home Assistant Operating System (HAOS) within the Home Assistant community or here on this forum. For any hardware-related topics, you may use the this forum; however, please be aware that official support from the Armbian team is not guaranteed. single board computer hardware https://www.armbian.com/bugs home assistant functions https://community.home-assistant.io/ (make sure to bring up only issues that are application related, high level issues, that are likely present in official HAOS software)
-
Another possible infra related issue. This mirror is temporally out of service, possible out of sync / order. You should always start with beta.armbian.com or dl.armbian.com directly. They are behind redirector which gets data from database while (double) checking for health and sync status.
-
Yes and no. I would say its just a bug, nobody to blame in particular. Try their official Ubuntu image with this 6.1 kernel if this also manifest there, so it can be narrowed. Open source projects are far from ideal circumstances We only provide email support for partners, where we have some control and don't need to pay 99.5% of hard cash costs that conversation (and previous hard and frustrating research work) will generate. With 0.5% of general public support (share of end user donations in this project), we already have problems to maintain a lot cheaper segments of this project. Providing email support is super expensive. Its not just you. Its thousands of often frustrated and angry customers of somebody else that would rather talk to an expert directly and not to anonymous forum. In human population we also have a small percentage of people that never respect any rules, act predatory, play dirty ... They would destroy mental health of people on such support and subsequently project in no time if we would provide / allow this. This can also be observed on forums ... Email support is not possible, even you would be willing to pay for it. Most of open source projects explicitly asks their users "please do not contact us for technical support, use community forum for support". Neither do developer without investing his time into research. Nothing here was meant personal. I just tried to "visualize" this communication. I do understand your frustration, but we are already doing the impossible. Odroid XU4 is having vendor kernel made around latest LTS. It was never true LTS ...
-
v4l2 Webcam Error "Inappropriate ioctl for device"
Igor replied to Bones558's topic in Software, Applications, Userspace
You get anything from: v4l2-ctl --list-devices -
Expected behavior (unless process breaks in the middle and files are not there for some other reason) - we only provide last kernels. Easier way to change - providing more kernels at repository - have great impact on build time, while doing it smarter would require a person to focus only on this part of infrastructure for some time ... alternatively, we could drop all deb packages to some location, but again someone (not me) would need to code and maintain this automation.
-
Maintainers don't work for Armbian, that’s an open source project. We are volunteering our free time ... and you are kindly asked to not call us on "home phone". This should be clear. I am solicitation developers and maintainers to ignore all private (and in majority emotional blackmailing) communication. Sometimes abuse still works and they got vandalized and you could even break them eventually ... and they stop helping you. Please don't take this personal. Its a relationship between open source end users and developers / maintainers. Fork the code, fix it (probably just need to enable something https://github.com/armbian/build/tree/main/config/kernel) and submit a PR. Or wait that this complains you posted on forum is heard by someone that has time and will do this. Instead of you. You can file a bug to Jira, but makes almost no difference. Maintainer will address this issue when he find the time and if he wants to. This is how things works in (non Desktop *NIX OS) open source world. Embedded (especially with vendor kernel as in this case) Linux is (far) away from simple and unified x86 Desktop *NIX OS. Many things has changed, but primary problem is that vendor (Hardkernel) switched their primary kernel from 5.4.y to 6.1.y ... and feature breaking is what always happens at such kernel changes.
-
Package 'mysql-server' has no installation candidate
Igor replied to RaymondDay's topic in Software, Applications, Userspace
ARM was perhaps not in good shape in Jessie / Buster era. Today, Bullseye and Bookworm should be in perfect state. I suggest you to upgrade to and then try again. Or start with a clean image.

until