Igor
Administrators
-
Joined
-
Last visited
Everything posted by Igor
-
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.
-
-
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 ...
-
-
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)
-
Some users may experience issues when downloading new v23.11 images from our website or also sometimes with apt not having the new packages. The reason is that we had a (not so) small whoopsie at the very last minute and the infra is still recovering and syncing. Easiest workaround would be to simply try multiple times until the redirector hits a mirror that has the files you want to download. Alternatively go directly to https://fi.mirror.armbian.de/ which (seems to) have all the files atm. Will work with apt as well.
-
This week's meeting topics: - Check remaining Jira tickets https://www.armbian.com/participate/ - Review issues https://github.com/armbian/build/issues - Review pull requests https://github.com/armbian/build/pulls The 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 A weekly developers' meeting aims to coordinate the development of the build engine, continuous integration, operating system features, and low-level support. Meetings are hosted on Jitsi (Video), IRC, and Discord (Text). While we would prefer you attend on Jitsi when possible, we will also monitor text chat during the call for those unable to join Jitsi. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused on developers' top-level topics, and it's expected that they understand embedded software development, software testing, or operating system management. Knowledge of at least BASH & Python is expected in terms of programming languages. 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 yourself. This is needed to communicate efficiently and to give you access to our organization infrastructure Jira, Github, hardware lab, and servers. @Contributor/Maintainer
-
-
-
Many of us are using Armbian not just on ARM single board computers but also on servers (bare metal & virtual). We use our builds since we trust it more then Debian, Ubuntu, not to mention other distributions that are recklessly updating and one ends up as an OS tester and not OS user. Personally I use Armbian Jammy on Ryzen 9 workstation with great success. My primary use case is development / productivity. For the road I used to have 13" Dell notebook which recently suddenly died. It was out of warranty so I had to get something new. After some testings of various devices I settled with 12th Gen Intel i5-1240P powered Lenovo. Then I tried many general purpose distros to see how well they work and all had some (minor) troubles ... We are having UEFI images (common image) since some time, but UEFI nor desktops were fine tuned nor ready for such performance daily driver desktop usage. We were close, but not close enough to just run it. Past two weeks we have been lifting general UEFI support, fixed many bugs and what came out is "Armbian ultimate developers desktop build". - improved support in GRUB (armbian wallpaper) & HiDPI GRUB support - all preinstalled applications are normal apt packages - current 5.15.y kernel, Jammy userland (5.19.y has some strange issues) - snapd is not installed (user can install it) - HiDPI support (automated adjustments on big screen resolutions) - NVIDIA graphics acceleration with proprietary driver (x86 only) - Intel graphics acceleration also works out of the box - preinstalled Google Chrome (x86 only) - preinstalled Microsoft Visual Studio Code (x86 only) - ZFS 2.1.5 ready (apt install zfsutils-linux zfs-dkms) - face unlock works perfectly fine on this laptop - installation to SSD drive to dual boot with Windows 10/11 is supported Armbian classical way by transferring actual live image to the prepared partition via nand-sata-install. All you need to do is prepare spare space on your drive, Windows 10/11 or Linux, UEFI support (most if not all hardware for past 10 years has it). I have tweaked images (XFCE, Gnome, Cinnamon) a bit to my personal needs, but making changes is welcome. Nice to have: disk encryption within nand-sata-install, small bug fixing, additional DEs. Currently we have CLI, XFCE, Gnome and Cinnamon. Others are too buggy. https://www.armbian.com/uefi-x86/ https://www.armbian.com/uefi-arm64/ Please report where it works and how (well)!
-
-
If you are running Armbian desktop and you like to use Visual Studio Code, open a terminal and run: sudo apt update sudo apt install code
[WIP] Schematics Pros: - board vendor provides dev samples and documentation - working with latest mainline kernel - many variants by the same vendor - official SDK/BSP currently on 4.4 - no unreliable shitty Micro USB for DC-IN but GPIO by default Cons: - new platform needing more initial work - not many active developers
Preparation Supported build environment is Ubuntu Focal 20.04 x64 (minimal iso image). a guest inside a VirtualBox or other virtualization software, a guest managed by Vagrant . This uses Virtualbox (as above) but does so in an easily repeatable way. Please check the Armbian with Vagrant README for a quick start HOWTO, inside a Docker , systemd-nspawn or other container environments (example), running natively on a dedicated PC or a server (not recommended), 20GB disk space or more and 2GB RAM or more available for the VM, container or native OS, superuser rights (configured sudo or root access). Execution apt-get -y install git git clone https://github.com/armbian/build cd build ./compile.sh This will download all necessary sources, execute compilation and/or build a boot-able image. Most of things will be cached so next run will be extremely faster! Real time examples: Documentation
