Igor

Video Summary: 1. Changes on "about Armbian" An email will sent out to all people mentioned on new "about armbian" to confirm their presence as is, chose anonymization (forum nick instead of "first name l."ast name) 2. Armbian versioning and repository management - we are temporally going back to original versioning (as known from master branch) as its one step to far - repository management was already tested with previously mentioned revert. It is already done, but need cleaning and making PRs - we will drop DTB package and move dtb blobs to the /boot/ Short term to do: - matrix to generate JSON for images and packages generation - add warnings and exists on deprecated functions such as KERNEL_CONFIGURE=yes which is causing users many problems - prepare more design related documents and instructions for developers to join in easier 3. Build framework 1st run configuration We ran out of time, next week. @Contributor/Maintainer

Nothing unexpected. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Porting this feature to mainline? Download SDK, look into the source code, check documentation, ...

I also use it with Jammy / Gnome, image with preinstalled desktop, and it works. tells nothing. Logs or at least telling a lot more then "i am using Armbian". Besides different HW properties that could cause troubles, there are different package releases and different DEs.

IIRC serial on imx6 kernel broke down year(s) ago and it seems it stayed that way. When that happened? No idea. Just saying this is possibility.

I had a discussion with Oleg about packaging. He got rid of DT package long time ago, while we kept it for "don't touch it if its not broken" reasons. Since we already break everything apart and we need to adjust versioning, repository might also need to be changed ... should we get rid of the DT package and place DT blobs to the same /boot/ location as in DT package (as done in media kernel)

Armbian doesn't have problems. We didn't design this wireless chip and we didn't write drivers. We already tried to make the best out of this, we already lost months while you didn't even noticed. Try one of those. Or just switch to kernel 6.1.y where this driver anyway doesn't work (yet).

With working PCI https://github.com/armbian/os/releases (look for Rock5 "midstream")

It has been silent for a year Anyone has thoughts or tried to merge Asahi Linux into Armbian? Apple mini could serve as a nice small Armbian build machine or just general purpose workstation. Well, compilation runs on MacOS, but running native Armbian Linux would be a lot cooler. The task of bringing Asahi family into Armbian https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ probably should not be very difficult anymore https://github.com/AsahiLinux/docs ? Anyone with a strong enough wish & ability?

You need to provide more information: - which image (link) - which hardware revision (perhaps a photo) - where booting ends - is this the only SD card you have ...

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one This is clear, right? Armbian is using mainline kernel, where not all features are developed or worked the same. GPIO's https://www.acmesystems.it/gpiod UART is where it is. If its enabled by default and usually is, then is on the same UART as legacy kernel. Just in some cases its not (for no apparent reason).

What was the install procedure? Strange. Perhaps there was something wrong with burning to USB? Use some other USB key? Usually its something stupid

I have tried yesterday https://github.com/armbian/build/issues/4892#issuecomment-1460176070 and last image + update, everything is fine. At least for me.

1. Start with a brand new UEFI image https://www.armbian.com/uefi-x86/ 2. Flash to USB, go to Bios, change to boot from USB 3. Boot, make 1st run config, then optionally erase eMMC flash partitions to force installer to create new ones 4. Run armbian-install, choose install to eMMC, select second partition when asked for where to install (it should only give you option for installing to 2nd as 1st is small FAT EFI partition where you can't install rootfs too) 5. Reboot and it should work. I just tried this on my test device which is very similar to Rockpi X (UP Square)

Those are developers preview builds, where you can check what works and at some point it will be good enough for some uses cases. In a couple of years, it will be functional on the level of kernel 5.10.y. Download is possible from CI pipeline: https://github.com/armbian/build/releases Boot log: This board is looking for maintainer(s) and (this) forum moderator (contact @Werner).

https://www.armbian.com/radxa-zero2/

https://www.armbian.com/odroid-m1/ - kernel 6.1.y LTS

Just a reminder, if someone wants to fix it.

https://www.armbian.com/rock-5b/

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)!

Samples arrived ♥️ HW looks fascinating, Armbian is yet to be ported so can't comment how good this is in realworld. Its shipped with stock Khadas Ubuntu, kernel 5.4.y, which is good to boot something ... Technical specs at CNX.

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

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