- hostapd does not install a default configuration file at `/etc/hostapd.conf`
- hostapd is installed masked by default
- dnsmasq fails to start because systemd-resolvd launches first as the default DNS resolver

I can write patches to fix this utility, but I'm wondering if it will ultimately be worth it.  I noticed this access point utility doesn't exist in the `armbian-configng` repository.  Is that because Armbian is dropping this utility, or no one has gotten around to it yet?  (There's not even a placeholder for it.)  What's the status of `armbian-configng` anyhow?  Will it eventually replace `armbian-config`?

The initial Armbian config has Europe -> and then places in Europe, in this list then it even has exotic places like Jan Mayen and or Swalbard (I forgot which ?). But it does not have Iceland at all. 

I know at this point in time (at initial install you can manually enter in some time zone format also).

If you go in Armbian Config after it has been installed then the Armbian Config tool only displays Cities, so at this point in time you have missed the chance to enter it in the time zone format.

Iceland uses UTC / GMT0, as in same time as London half of the year, but differs by one hour the other half since we do not have daylight savings like they have.

I guess what I am asking for is something equal to this in the setup windows both in intial setup and in the Armbian Config

sudo timedatectl set-timezone Atlantic/Reykjavik

I am working on a project to use the Orange Pi Zero 2W as a USB UVC (Webcam) gadget via ConfigFS.

I am currently using a newer image with Kernel 6.12/6.1, but I am facing critical issues. Specifically, I am getting 'Permission Denied' errors when trying to write to resolution parameters (like hHeight/wHeight), and even after bypassing that, I encounter 'Device or resource busy' errors when binding the UDC.

Based on my research, these UVC functions were much more stable on the Legacy 5.10 kernel. However, I cannot find any official Debian Bullseye/Bookworm images for the Zero 2W that still use the 5.10 kernel, as most archives have been updated to 6.1+.

Does anyone have a working link or a mirror for an image like: Orangepizero2w_1.0.0_debian_bullseye_server_linux5.10.110.7z?

Any help or directions to a reliable archive would be greatly appreciated. Thank you!

for 2 day i am searching for set a bootlogo on the screen while loading klipper but all i get is the linux text that fly by.

I set bootlogo= true in armbianEnv.txt does not help i can't find any other option. There should also be Splash can find any decent information about that either

So is it possible to show a logo at booting klipper, if yes is it also possible to change it to custom logo or video because it would be nicer to show a logo or video then al these linux lines 

And i am not a professional programmer so easy language if possible

I found armbian by chance and it's the best supporting linux solution for my orangepizero3 - will later start tinkering with orangepizero2w and orangepi5plus

I'd love, along with Debian and Ubuntu, to have Kali selectable as distribution option - linux kernel, dtb, headers, u-boot, overlays and armbian-config would be the perfect base for it (and every other distribution imho)

Being inspired by GoVanguard/karmbian, which is based on armbian's previous framework, I tried grossly "injecting" kali support into armbian branch v24.02 - but I'm lost; definitely no developer, just playing around

specifically I'm stuck with "lib/functions/general/apt-utils.sh" function "apt_find_upstream_package_version_and_download_url()" - I don't know how to get kali deb packages url - kali tracker doesn't behave like Debian/Ubuntu - my clumsy approach is available at https://github.com/alexl83/build.git branch v24.02

I think orange pi boards are nice and hold potential, but manufacturer is stuck at an old forked armbian framework, old kernel and hacky dtbs - Armbian is great and I hope to get kali tools on it without "Frankensteining" Debian with overlapping repos, conflicts and pinnings

Would love to get some proper support - sunxi64-current (6.6) works a charm, injection patches are ok, but even when deployed on trixie and using a kali extension script, the are overlapping packages - It would be great to have Kali distro just integrated in this framework

Thanks for those who read all this

Fingers crossed

Alex

I built an image for SDCARD on the rockchip3568 board using the project
from here https://github.com/armbian/build
This framework creates an image for SDCARD, consisting of two
partitions:

1 - boot (Fat32 - 256 MiB)
2 - root file system (ext4)

(all remaining capacity on SDCARD, I use a 16GiB card)
I need a different, custom, file system partition.

How can I make three partitions, for example of these sizes:
1. boot - 256MiB
2. root - 2GiB
3. work - the entire remaining capacity of the SDCARD
while the size of the image file is not all 16GiB,
but 256MiB (boot) + 2Gib (root) + 256MiB (work) = 2.5GiB
and the last partition would take up all the remaining space on the card?

I managed to modify two scripts:
partitioning.sh and rootfs-to-image.sh
and, as I understood, to make the last partition for the entire remaining capacity of the card, when forming the script for marking
partitions for sfdisk (in the partitioning.sh file), you do not need to specify the size
of the partition, which is what I did. However, the desired result did not work.

Can someone help with this problem?
Thanks in advance.

I'm big fun of the Armbian project a long time and checking its progress time to time cos its seems perfect for IOT usage and the NanoPi R3S was specially chosen by me for my ongoing project because of the Platinum support of the product as it seemed to be perfect fit with good enough video support to make IOT server with remote app for admin functions.

Sadly as it seems the hardware acceleration is not supported i guess because there is no HDMI port on the product but with Panfrost + VirtualGL it could be a capable remote desktop solution and i have checked that on "BigTreeTech CB2" its already there so that could be added for that as well.

For me it would be enough if i get some help to add that to the build script for only me for now!

But maybe there are other people who could have good use of some kind of remote desktop solution for an app or a whole desktop. I almost got it working with the official driver but it is not possible sadly without forking VirtualGL to make it compatible with the gl4es faker, and also that limits to OpenGL 2.X apps only so with Panfrost (3.1) could much better and it won't need the faker either.

Update: I have the non LTS version cos that's the only one i was able to buy but i just checked the LTS version which is the Platinum support for and it has HDMI so it could be useful even more.

Anyway, I was wondering if there was some way to handle installing and configuring Wifi access to the BBAI-64 that anyone around here knew of currently. 

Ethernet works. I can get online. Also, there is a set up in `armbian-config` that may allow OctoPrint to be installed. It seems one needs to add support for Docker first. The Docker install from Trixie is not available on kernel 6.6.x so far.

Seth

P.S. Um, I understand that some people now are short handed on replies and adding additional support without compensation. I understand completely. Things are not free in life. Maybe just a couple ideas and/or placements of ideas directing could help. For instance, is there a particular SS (subsystem) in Linux where I would need to gather specific files to handle the available configuration on the e-key M2 that makes Wifi available on the BBAI-64? Any and all ideas are welcomed. 

Current bug:

Failed to process avif file version: unable to call heifsave_target
heifsave: Unsupported compression

It's not a HEIC image, this is how LibVIPS encodes AVIF files.

I’m a big fan of your work and use Armbian on all my single-board computers, including Orange Pi, Banana Pi, and Raspberry Pi. However, I’ve noticed a recurring issue during bootstrapping: identifying the device on the network. Enabling the avahi-daemon could make it easier to connect to or discover the device using mDNS. What are your thoughts on this?

	vars:
      board_build:
        rpi4b: "BOARD=rpi4b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        rpi5b: "BOARD=rpi5b BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no \
          DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet multimedia remote_desktop' DESKTOP_ENVIRONMENT=xfce \
          DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=jammy"
        rock3a: "BOARD=rock-3a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        rock5b: "BOARD=rock-5b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        opi5: "BOARD=orangepi5 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        opi5p: "BOARD=orangepi5-plus BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        nanopct6_edge: "BOARD=nanopct6 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        nanopct6_legacy: "BOARD=nanopct6 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"
        vim4: "BOARD=khadas-vim4 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm"

	[...]
    - name: Compile images
      ignore_errors: true
      ansible.builtin.shell: |
        ./compile.sh {{ board_build[item] }}
      args:
        executable: /bin/bash
        chdir: build
      register: compile_output
      changed_when: true
      loop: "{{ board_build.keys() }}"
      loop_control:
        label: "{{ item }}"

Thank you, 

Stefanita Vilcu
 

Even if I'm completely wrong and babbling nonsense... I believe this should be a decent option for recently released sbc's that have zero support "out of the box" and could use "anything" to get em running asap.

...and theres a git repo that provides proprietary gpu/vulkan support via .deb files -- https://github.com/tsukumijima/libmali-rockchip

Quote

[ 4866.179834] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2
[ 4866.260829] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal lock ok, i:23!
[ 4866.897145] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio
[ 4870.556651] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x32315559, cur_fmt:0x3631564e!
[ 4870.556667] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x32315559, cur_fmt:0x3631564e!
[ 4870.556669] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x32315659, cur_fmt:0x3631564e!
[ 4870.556672] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x50323234, cur_fmt:0x3631564e!
[ 4870.556674] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x56595559, cur_fmt:0x3631564e!
[ 4870.556676] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x59565955, cur_fmt:0x3631564e!
[ 4870.556679] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x50313134, cur_fmt:0x3631564e!
[ 4870.556681] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x39565559, cur_fmt:0x3631564e!
[ 4870.556683] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x39555659, cur_fmt:0x3631564e!
[ 4870.556684] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x4f424752, cur_fmt:0x3631564e!
[ 4870.556686] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x51424752, cur_fmt:0x3631564e!
[ 4870.556688] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x50424752, cur_fmt:0x3631564e!
[ 4870.556690] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x52424752, cur_fmt:0x3631564e!
[ 4870.556693] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x33524742, cur_fmt:0x3631564e!
[ 4870.556695] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x33424752, cur_fmt:0x3631564e!
[ 4870.556697] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34325258, cur_fmt:0x3631564e!
[ 4870.556699] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34325842, cur_fmt:0x3631564e!
[ 4870.556701] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34325241, cur_fmt:0x3631564e!
[ 4870.556703] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34324142, cur_fmt:0x3631564e!
[ 4870.556705] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34524742, cur_fmt:0x3631564e!
[ 4870.556707] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x34424752, cur_fmt:0x3631564e!
[ 4870.556709] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x59455247, cur_fmt:0x3631564e!
[ 4870.556711] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x20363159, cur_fmt:0x3631564e!
[ 4870.556712] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x2036315a, cur_fmt:0x3631564e!
[ 4870.556714] fdee0000.hdmirx-controller: hdmirx_s_fmt_vid_cap_mplane: err, set_fmt:0x3432564e, cur_fmt:0x3631564e!
[ 4870.583506] fdee0000.hdmirx-controller: hdmirx_start_streaming: delay_line:720
[ 4871.779810] fdee0000.hdmirx-controller: rcv frames
[ 4876.512192] fdee0000.hdmirx-controller: stream start stopping
[ 4876.563926] fdee0000.hdmirx-controller: hdmirx_stop_streaming wait last irq timeout, return bufs!
[ 4876.563972] fdee0000.hdmirx-controller: stream stopping finished
[ 4877.580032] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2
[ 4877.679342] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal lock ok, i:23!
[ 4878.043928] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio
[ 4878.273579] fdee0000.hdmirx-controller: hdmirx_format_change: New format: 1920x1080p30.00 (2200x1125)
[ 4879.413396] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2
[ 4879.514266] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal lock ok, i:23!

as a hobby project I forked Armbian repo to add support of someone "new" hardware, mostly around 3D printing and mostly because no support from the vendor side.

At this moment I have following almost independent components:

1. a kernel module for ST7796 (LCD controller connected via SPI and working as frame buffer module/device)
2. a patch for HDMI configuration to support MKS IPS50 screen (800x480, 5:3 aspect ration with some weird EDID)
3. configuration with related patches for MKSPI, SKIPR and a few derivatives boards + some DTS overlay for one related/specific use case. It's a "Renegade ROC-RK3328-CC" based board(s) which was adapted for some specific use cases (kinda "cost effective" alternative of Raspberry PI with pretty deep adaptions for for 3D printers)

Is there are any interest to contribute these changes to official Armbian code base? If yes, which of these parts?

Additional remarks:
1. At the moment, these changes have been tested on real equipment (to the best of my knowledge and capabilities ) and have proven stable enough for everyday usage.
2. I am not a Makerbase/MKS developer and have no any connection with this company. It's my "weekends project" for my personal purposes.
3. Fork repo: https://github.com/redrathnure/armbian-mkspi

Best regards and thank you for your efforts,

Maxim

Just wanted to ask if there is any plan on making a version of armbian for the orange pi 5 Max. I have one and am using the official image but am having problems with hardware acceleration when attempting to use it in jellyfin docker. So I thought some files might be the issue and I previously set up my system with armbian in the orange pi 5 and it worked. If you guys did or are planing to make one, please let me know.

Key Advantages

• Lightweight: Minimal dependencies for optimal performance.
• Flexible: Supports JSON, TUI, CLI, and API interfaces.
• Modern: A fresh approach to configuration.
• Low entropy: Byte clean uninstall for most targets.

Features

• System Configuration:
  • Kernel management, headers, hardware tweaks.
  • NFS and ZFS storage management.
  • SSH user access tweaks.
  • System updates, rolling / stable, containers update.
• Network Management:
  • Fixed / dynamic IP configuration.
  • Connecting to wireless network.
  • Access point management.
• Localization Settings:
  • Configure time zone.
  • Set language and locales.
  • Change hostname.
• Software Management:
  • Software installation and removal.
  • Native and containerized environment.
  • Standardised, updatable, maintained.

Compatibility

This tool is tailored to works best with Armbian Linux but it has also been automatically tested on:

• Debian Bookworm
• Debian Trixie
• Ubuntu Jammy
• Ubuntu Noble

In theory it should work on all systemd APT based Linux distributions: Linux Mint, Elementary OS, Kali Linux, MX Linux, Parrot OS, Proxmox, Raspberry Pi OS, ...

Getting Started

Armbian config is preinstalled on Armbian. Open or login into your terminal and run:

armbian-config

End users:

Request new software title

Documentation:
Armbian config | Optimised software
 

Developers:

Adding a new feature or software install title

Context

systemd's cloud-init.target and armbian-firstrun.service will be started concurrently (both are wanted by multi-user.target). Both will try to create SSH host keys by default:

 - armbian-firstrun will always delete SSH host keys and then generate new ones

 - cloud-init.target (by default) will always delete SSH host keys and then generate new ones.

Problem

When one must run armbian-firstrun and cloud-init, there is no deterministic ordering between the 2 files execution and therefore no one can guarantee which will be last to setup host keys. In my current scenario, host keys are explicitly setup in cloud-init and I would expect armbian-firstrun to not delete keys + no ssh host key generation.

Proposed Solution

armbian-firstrun support user defined config to control SSH host keys deletion + generation:

- on: ssh host key deleted + generated (compatibility: current armbian behaviour)

- off: no ssh key deleted + no ssh host key generated. Allow cloud-init to take over this behaviour deterministically.

Question

I am seeking guidance on where the user config setting should be added. Then I can write the if/else condition in the armbian-firstrun script.

I cannot exactly say why, but I never liked the 'emptyness' of the IP-Address on the SSH welcome message

System load:   0.82 0.29 0.10  	Up time:       1 min		
Memory usage:  3 % of 3867MB 	IP:            192.168.11.7

So I thought it needs a lot of space for a long Up time. So, the space is reasonable. Looking at the other information provided, which needs as well many letters?

My suggestion to move it like this  and adding: -Address  (IP is not the complete term  (Internet-Protocol):

IP-Address:    192.168.11.7  	Up time:       1 min		
Memory usage:  3 % of 3867MB 	System load:   0.82 0.29 0.10

adding 'Address'  might fix the emptyness as well:

System load:   0.82 0.29 0.10  	Up time:       1 min		
Memory usage:  3 % of 3867MB 	IP-Address:    192.168.11.7

It is just the welcome display  but  the first thing you see  (you have only one chance for a first impression   )

Your thoughts on that, I am curious?

Note that the Armbian Station M3 latest UEFI image boots unmodified on an SD card on this hardware, with working picture on one of the HDMI ports. (But no USB) So the partition structure is ok.

20230428-EDK2-EFI-current/Armbian_23.04_Station-m3_sid_current_6.2.0.img.xz

So it is already close to a usable image once the relevant device tree bits are swapped out.

I am not 100% sure the details yet of the uboot they ship, or even how to just install the uboot part to emmc but when I flashed the complete Debian 11 "firmware" they provide on the website link to the EMMC (using the linux command line loader program over usb-c) it has the uboot that will boot the uefi image from SD card.

Note that 32G RAM+256G EMMC configuration is now shipping also on FireFly 3588 hardware. I asked them nicely way back in like November to give us 256GB emmc instead of 128GB. 🙂

May be it is easy or not. I don't know. Mldonkey Server has fallen from Debian repositories about one year ago.

How much $help$ do you need? 

Thanks. 

Thanks 

I would like to propose a change to the default kernel config for the r4s.

Currently in .config

#
# USB HID support
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y

This should be altered to 

CONFIG_USB_HID=m 
 

This change has been requested previously for other boards: here and is also explained properly.

To summarise : the change would allow those using APCUPSD to communicate with their APC UPS device.

TiA!

Well, ladies and gentlemen, I done it, becoz I can't live without it when quitting cinnamon for xfce.
It is like the thunar-archive-plugin (file-roller equivalent) that should be enabled by default imho.
I decided to release it here , this is my gift to armbian team to thanks for their work.

INSTALLATION

If you follow the README.md, you will have the magic custom action added

The demo:

Enjoy

                         SoSie

thunar-open-as-root-plugin.zip

i have the wish for the integration of

- GPIO Support for RockPi 5b to the Edge Kerne

- dtb's which are aviable for Kernel 5.10.160 mostly importend for me are the UARTS

  ( if tryed to compile the DTS files form 5.10.160 for the 6.8.2 .. ends after sending some to the UART with a Kernel segfault 😞 )
 

Thanks a lot for the good Work 🙂
René

I enabled "multi factor authentication" for my forum account (ie. "the code thingy that changes with time"), but the window to ask for the code doesn't show up with Firefox (this is the latest version of Firefox 115.0.3 (64-bit) on MacOS). It does with with Safari though.

hi everybody...  are you planning to migrate the IO scheduler to the NPU?  in most cases, it is not involved on the devices that your operating system serves.  This would give space for new perspectives.

The empty files all have the timestamp of a run of armbian-ramlog at a recent reboot. In armbian-ramlog.log I found this for the run that created the empty files:

rsync: [receiver] write failed on "/var/log/journal/0d4b1c13b9a14b6d9c746402b7d7ef6f/user-1000@0005d37f46f9961b-23c015a66b68d086.journal~": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(378) [receiver=3.2.3]
rsync: [sender] write error: Broken pipe (32)

Seems that journal has become too big to fit on the log/ramdisk. That is strange, as I defined a maximum of 20MB for the journal and the ramdisk has 50MB.

I guess this is what happened: When syncing to sd armbian-ramlog uses rsync without --delete. So if some older files have been already delete by journald (because of the 20 MB limit) on the ramdisk, they will still stay in the log on sd. Therefore the journal on the sd will become bigger and bigger. Which is not a problem because there is plenty of space on the sd. However, when rebooting everything is copied from the sd to the ramdisk. Including the bloated journal. Thus the ramdisk is full and additional files will not fit (see error message from rsync).

I think in this case rsync just creates empty files and that is the reason for my empty logs. And on next sync the empty files are copied back to sd so both versions are empty.

There is another potential problem I see in the implementation of armbian-ramlog: on reboot only recent files (so no *.gz or *.[0-9]) are copied to ramdisk. After som runtime logrotate will rotate the logs and create new *.gz or *.[0-9]. However, these might already exist on the sd. They will be overwritten when the logs are written back to sd. So you loose old logs.

I think both problems are due to the fact that simple rsync is used without --delete and without copying even the old files to the ramdisk. To overcome these problems I see two ways:

• use rsync --delete and dont exclude *.gz and *.[0-9]. Then the ramdisk holds all logs and when copying to sd nothing is lost. But this may requier a bigger ramdisk
• dont use rsync but use an overlay fs instead. I found this discussion on the topic. The described solution looks superior to me than what we are using now:
  https://unix.stackexchange.com/questions/424341/mount-var-logs-as-tmpfs-with-help-of-overlayfs-to-save-changes-sometimes

What do you think about it? Would it make sense to use an overlay fs?

I am not that deep into linux hacking and therefore are not sure if I would be able to implement it in a nice way. But I would like to support this process and do some tasks.

Regards,

jba

More info 

I appreciate it's a lot of work to support new boards, but I wondered if anyone was interested in forking this https://github.com/TechNexion-customization/ubuntu-tn-imx/tree/master?tab=readme-ov-file#technexion-ubuntu-lts-image-builder and doing a Armbian build for it?

I'm not sure if this is the right place, but I used the contact form twice back in august and september and haven't received any reply  The mirror list on the github page is not updated either

Anyway, as a raspberry pi lover, I've set up a mirror to support the development of armbian:

http://repo.jing.rocks/armbian-apt

https://repo.jing.rocks/armbian-apt

rsync://repo.jing.rocks/armbian-apt

http://repo.jing.rocks/armbian-dl

https://repo.jing.rocks/armbian-dl

rsync://repo.jing.rocks/armbian-dl

sync frequency: every 4 hrs

upstream: rsync://rsync.armbian.com/{apt,dl}

armbian-archive coming soon(TM)

Bandwidth: 10Gbit/s, not metered. Currently serving about 10TB per day.

Admin contact: Jing Luo <szmun.luoj a.t. gmail.com> or <jing a.t. jing.rocks>

Geolocation: Tokyo, Japan

IPv6: yes

Thank you for your trust and support.

I noticed in the past some requests were made already in regards to supporting i.MX platforms. This did not work out are there is no budget for such developments ($)

We plan to bring an i.MX93 and i.MX95 board to the market early next year, and support for Armbian is one of my requirements

Would it be possible to treat this as a paid request to get 2 boards supported by the Armbian releases?

let me know where i should post this, if not in the right section 

Could you please:

• update the kernel image to include the 'lvm2' package, load the required modules at boot,
• upgrade armbian-install script to propose an option in the dialog menu to install the root file system on a volume group (VG) and logical volume (LV) that you will create, instead of directly on a primary disk partition?

Please, at least if you are interested or not by this feature can you let a comment?

Your feedback will help!

Sincerely, 

Frederic

Neither of current categories are exactly suitable for such questions on this forum. Off-topic category doesn't receive much attention as I would guess.

Proposal: create "general discussions" category.

example: recovery bootloader on the router board
 

• Orange Pi 4 configuration
  
  1. Recompile orange pi 4 linux kernel to enable spi-nand driver (linux-5.10 or above is required). Make sure spinand, mtd and nandcore are built as modules
  2. sudo armbian-config, go to “System → DTC” and replace spidev with spinand
  3. install the following packages: mtd-utils
  4. reboot board to apply changes
   
• Connect spi-nand chip to orange pi4 board
  
  Testpoint Meaning Where to connect
  3.3V 3.3V power supply pin 17 of orange pi 4 connector
  DI SPI Data In pin 19 of orange pi 4 connector
  DO SPI Data Out pin 21 of orange pi 4 connector
  CLK SPI Clock pin 23 of orange pi 4 connector
  GND Ground pin 25 of orange pi 4connector
  CS# SPI Chip Select pin 24 of orange pi 4 connector
  WP# Write Protect short with HOLD# and 3.3V testpoints
  HOLD# Hold short with WP# and 3.3V testpoints
   
• restart spinand and mtd modules
  
  rmmod ofpart spinand mtd nandcore
  modprobe spinand
  modprobe mtd
  
  make sure the flash was detected
  
  dmesg | tail -n 6
  [ 237.055291] spi-nand: probe of spi0.0 failed with error -524
  [ 383.913569] spi-id: 00, ef, aa, 21
  [ 383.913729] spi-id: ef, aa, 21, 00
  [ 383.913878] spi-id: ef, aa, 21, 00
  [ 383.913936] spi-nand spi0.0: Winbond SPI NAND was found.
  [ 383.913965] spi-nand spi0.0: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 64
   
• Recovering bootloader
  
  Add partitions of your choice using
  
  mtdpart add /dev/mtd0 <PART_NAME>
  
  Erase & flash partition
  
  flash_erase /dev/mtd 0 0
  nandwrite /dev/mtd image_file
  
  Disconnect flash from orange pi board and test it

I would like to request that this overlay be updated for the Armbian kernel and included as an optional overlay into the Meson 64 / BananaPi CM4 distribution.

dts-v1/;

/ {

        fragment@0 {
                target = <0xffffffff>;

                __overlay__ {
                        controller-type = <0x01>;
                };
        };

        fragment@1 {
                target = <0xffffffff>;

                __overlay__ {
                        otg = <0x00>;
                };
        };

        __fixups__ {
                dwc2_a = "/fragment@0:target:0";
                usb3_phy_v2 = "/fragment@1:target:0";
        };
};

Thank you!

```APT::Periodic::Enable: "0"```

I suspect many credit-card servers just chug along with default settings for years without manual upgrades (myself included until i reinstalled a fresh image the other day).

Should't that be enabled by default so people can stay up to date with security updates etc.?

Would be nice to have a separate forum for Nanopi Duo2.

   T.

Alternate being an ISO installer, but that would probably take a bunch of work to get going.

Any news when it could be included in Armbian?

As I see 4 years we have been waiting for it...

Kindly

I would like to see the armbian installation script configure BTRFS in this same manner.

Are there any plans to add support for this board?

Thanks,

Gustavo

I am no graphics guru...but can we either get that little guy below converted into something we can use for other things



 

Could you add the keyboard layout configuration as the first operation in the first startup, before creating the password.

That would be realy helpful.

Regards.

I found it very useful to backup my Khadas images as well as installing different os.   The description is as follows:

'Krescue is an extremely small (21mb) operating system that you can boot directly from a micro-SD card or your EMMC. It is a “Swiss Army knife”, and you can use it to perform a variety of low-level SBC maintenance tasks. Most notable of which are backing-up your EMMC by dumping a raw-compressed .img.gz, and rapidly installing a new OS via flashing a .img.gz back into the EMMC. Krescue can download and install OS images directly from the web via wired Ethernet.'

I've finally got my Heliios64 about 2 weeks ago and have it setup to the point I believe its ready for primetime but would like to ensure I have an easy way to backup/restore my emcc image.  Any thoughts?

--lowest-speed-limit=500K

As I build my first image, I hit a lot of times this limit 🙈

Wouldn't be nice if this limit was configurable? I'm willing to try to implement it myself.

• Should I create an issue on Jira or GitHub or is the forum the right place to discuss it?
• Where would be the right place to add this parameter? userpatches/config-default.conf?

I work for a company in the industrial automation field and last year a small revolution picked up. At the SPS in Nürnberg/Germany (the biggest European fair in our field) last November, a ton of industrial hardware constructors unveiled their new ARM-based compact devices running Linux: essentially modified SBCs. This is really unusual because industrial automation has been traditionally more oriented toward Microsoft. But thanks to different technological evolutions that have occurred in recent years, Linux has become more accessible to machine constructors with less know-how in software development and Linux. What I mean is that I see the opportunity that you guys attract this kind of people and companies who have money and can financially support you with Armbian.

My experience with Armbian has been so far positive in this context. What I'm missing is a more industrial flavored installation. CLI is perfect for devices without a monitor. For HMI and POS, Desktop is already overkill. For this kind of application (HMI and POS) it would be perfect to have a Debian based installation with the following software working OOB:

• Terminal
• SSH
• VNC
• XFCE
• Text editor (i.e. nano)
• Chromium
• Git
• Docker

There is no need of things like:

• Kernel headers
• LibreOffice
• Thunderbird
• Firefox
• FileZilla
• Gimp
• VIM
• VPN
• IPTV
• Plex
• Cloud
• ...

It would also be absolutely perfect to have the ability to start a GUI application with arguments, i.e. from armbianEnv.txt (i.e. Chromium in kiosk mode with a URL), or the ability to configure it from armbian-config.

This is another topic, but related: I also see a lot of confusion on the forum (I was confused too) between enabling the desktop and auto-login. Currently the auto-login feature is hidden behind "Enable desktop" in armbian-config. In a first step, I would extend the menu description to "Enable desktop or auto-login" to make it clearer. In a second step, I would provide the possibility to enable/disable the auto-login independently from the desktop.

I hope you guys appreciate these feedabacks and I'm sorry that I can't immediately help with developing features and solving issues, my know-how with Bash, Linux and GitHub is too limited. But I hope to be able to fill this gap quickly.

https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts

after searching for a solution (because i'd like not to waste 80$ to get a new board and my BGA soldering skill are far from whats needed to change the RAM module) there seems to be one that is called badram. It basically tell the kernel not to use a set of known bad addresses. saddly this is not a standard package but a kernel patch made for debian and ubuntu that i have no idea how to install on ARMBIAN.

I was wondering if it would be interesting and possible to add this option to armbian.

the way i see it it would be a module in the armbian-config tools that check the RAM and if badblock are found the user is promoted if they can be added to a blacklist.

Particularly, the linux.config file is expected, better to enable kernel 6.0  ?

Cheers

I am a long time Debian Testing user, and would like to use the testing repo on armbian as well.

Currently however, I only get the choice between stable and unstable. apt.armbian.com also seems to only house packages for stable and unstable, not for testing.

I would think that when you are already supporting stable and unstable, testing wouldn't be much more than just flicking a switch to turn it on. However, I assume people here know better than me. I barely know what is in the armbian repos.

Quote

Starting from Linux kernel v5.4, the HAVEGED inspired algorithm has been included in the Linux kernel (see the LKML article and the Linux Kernel commit).

Fedora and Arch both have a test for the kernel version in haveged.service:

ConditionKernelVersion=<5.6

I put a complete example of haveged.service in this GitHub Gist for the convenience of anyone reading this post.

https://gist.github.com/ambiamber/0d99cc5c8f79a72633acf39c443f5f2f

I got here because on a fresh installation "systemctl status" showed "degraded" because haveged failed to start (which is correct because it shouldn't start).

Upstream bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999811

Options are ATH11K_PCI and ATH11K(ATH11K_PCI depends on ATH11K)

please move this thread to the correct place in case I misplaced it.

Does the armbian image for generic Intel/AMD x86 also support PCs with the old BIOS (non-UEFI)?

I ask because I have a pretty old Notebook from 2013 which still works good as general purpose Internet or Office workhorse and this only has the old BIOS.

The armbian image for the Intel/AMD looks pretty nice and I would like to install it no the Notebook eventually when Windows 10 runs out.

If it does not support this, is there an image for the old BIOS?

Thanks!

Best regards, Udo

Why has the 5 kernels led to the drop in support for eMMC?  

I am looking for a Minimal Armbian for H3 chip with kiosk feature. I don't need desktop interface but still need a web browser to open at startup. 

Is there any version like this? I need it minimum because i will install on eMMC of the Orange Pi PC Plus and it has only 8GB.

Thanks

Hi all

I have been using https://github.com/billw2/rpi-clone to clone sd cards as it uses rsync. It's much quicker than imaging and will clone larger cards to smaller if there is space. The thing is it expects a raspberrypi and so doesn't update the UUID in the armbianEnv.txt and fstab. If I manually do this then the clone is bookable and works fine. I cant script (yet), so if anyone could take a look at the script on git and suggest how this could be changed to work with armbian also i would be really grateful.

This is not the case with RockPro64 latest current images. I get even with the focal cinammon the warning about being a nightly build and old initial steps.
Not as posted here posted by Igor in the Armbian Download RockPro64 page

Just a note as many of us would like to see similar. 
If Im missing something my apologies and please point me to the right place

While building a custom image that needs to do some things at the end of the first bootup and reboot, I ran into some issues with armbian-firstrun.service. It currently has Type=simple, which means dependencies will be started when armbian-firstrun is *started*, and there is no clean way to wait until after it has *finished*. Looking to fix this, I noticed some other things that could be improved in this area, such as using systemd's first-boot-complete.target and ConditionFirstBoot to more simply manage first-boot-only services.

I'm considering implementing some changes and submitting them in a PR, but before I do that, I'd like to get some feedback on the approach and whether it seems worth investing time into. I considered creating a github issue about this, but given it is sort-of a feature request and the github new issue wizard seems intended to redirect away from github issues, I thought to instead post here. If a github issue seems more appropriate, I'll gladly repost there.

In any case, to solve the particular problem I was having (a service that needs to run after the full first boot has completed, including resizing and firstrun script), here's three incremental changes that I would think would make sense (just 1. would be the minimal to solve this problem, 1. + 2. would solve it more generally, and 1. + 2. + .3 would simplify the code a bit maybe).

1. Make armbian-firstrun.service `Type=oneshot`, so you can declare `After=armbian-firstrun.service` and `After=armbian-resize-filesystem.service`. This also means that system boot is delayed until this service is completed, but it does not prevent other boot services to run in parallel, so I would not consider this an issue (if it is, then removing the `Before=getty...` stuff could be considered, which is currently pointless anyway (you will not get a login prompt until armbian-firstrun.service is started, but it will not wait for completion). Note that using `Type=simple` in armbian-firstrun.service originates from https://github.com/armbian/build/commit/ee8d396fa639cd89e08fdd6646c32308f3b25f4f, but there is no rational for this choice.

2. Give armbian-firstrun.service and armbian-resize-filesystem `Wants=first-boot-complete.target` and `Before=first-boot-complete.target` so `first-boot-complete.target` does not fire until `armbian-firstrun` is done, allowing others to just do `After=first-boot-complete.target` without having to explicitly reference specific services.

3. Give armbian-firstrun.service and armbian-resize-filesystem `ConditionFirstBoot=yes` to let systemd ensure they are only called on the first boot. This allows removing the `systemctl disable` calls in these respective scripts as well, but needs the `/etc/machine-id` file to be removed (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900366#20), but that's probably a good idea anyway (to be regenerated on first boot, currently all machines using the same image have the same machine id).

One thing (feature or seeming problem maybe) with using ConditionFirstBoot as suggested above, is that systemd ensures that if the first boot is interrupted, the first boot services are ran again on the subsequent boots, until they have all ran completely (to ensure they all had a chance to ran). This is implemented by (roughly) running ConditionFirstBoot services only if `/etc/machine-id` does not exist, and only writing it to disk *after* all `first-boot-complete.target` services have completed (also when they failed, I think). This means that if the boot is interrupted before *all* first-boot services are ran, all of them will be ran again on the next boot and needs these services to be ok with being ran twice (this is also currently the case when the boot is interrupted when either or both services are still running, except that if either service completes, then that particular service will not be retried, but others might be). See also https://man7.org/linux/man-pages/man5/machine-id.5.html

As a related optimization, if 1. above is applied I think we could also add a `Before=ssh.service` to armbian-firstrun.service and remove the sshd restart from `armbian-firstrun`, so systemd just delays sshd startup until the keys are generated (but only if armbian-firstrun is active, so on subsequent boots sshd is started as normal).

Also, regardless of all of the above, I see that the armbian-firstrun deletes the ssh host keys and then forces regenerating them by calling dpkg-reconfigure. However, it would seem safer to me to actually delete the ssh keys at the end of image generation somewhere (maybe in `post_debootstrap_tweaks()`?), to really rule out the possibility of machines all using the same (publicly known) keys from the image file.

So, how do these sound?

That would save so much time and bandwidth.  Most of us are able to obtain and install the Linaro and other dependencies for our build systems on our own.  Let's figure out how to avoid doing this on each and every clean build of Armbian.

I have lots of bandwidth and the build doesn't even start after it takes ten to twenty minutes downloading these packages.

Thanks, and I appreciate any comments on this request.

My observation is that we seem to be building the entire kernel tree, but correct me if I'm wrong.

Let's see if we can only build hardware that actually exists on the device instead of building everything.

For example, my Pine64 doesn't even have WiFi but dozens of WiFi drivers are built. 

Same with my Orange Pi 3 LTS, it has BlueTooth and WiFi, but doesn't need the several dozen other BlueTooth and WiFi devices built into its kernel modules directory.

Thanks!

I have been out of the loop for quite some time...

Therefore did not update my armbian dev env either for quite a while, was a bit "surprised" after a " git pull " most boards went to CSC, but read the story why...

Anyway I was wondering rgd the "new" OP1 Rockpi4+ boards, if same image can be used for these boards ?

Most likely a new entry to compile, armbian building script,  will appear sooner or later. Also noticed current kernel 5.16 holds commits for 4A+ and 4B+ :

Rockchip
...
Add RK3399 ROCK Pi 4A+ board commit
Add RK3399 ROCK Pi 4B+ board commit
...

In +/- two months like to start a PoE ROCK Pi 4A+ board project , checking current status I most likely should start building for "rockpi-4a" and change kernel config a bit.

Hopefully by then a "Bleeding edge" ( 5.16 kernel ) can be compiled for these boards ... 

Currently compilation.log shows ( see below ) and suspecting these patches :

Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] board-rockpi4-0005-arm64-dts-enable-es8316-audio.patch  info
Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] general-fix-es8316-kernel-panic.patch  info

Grtz! 

the kernel modules have problems on latest kernels so would be great to have them included already. maybe that makes the kernel "too big" and isn't acceptable, but that's up to you to consider it or not.

best regards, Salvador.

Given that most devices supported by Armbian are underpowered, it would be great to get this installable via apt.

I found out here https://stackoverflow.com/questions/19926802/mariadb-crash-table-doesnt-exist-in-engine-cant-recover-tables that I can make dump with Mysql only

Could you please consider possibility to change default kernel config, used in release versions of Armbian, so it enable to forcefully unload of kernel modules ( to do this config option CONFIG_MODULE_FORCE_UNLOAD needs to be enabled). This is seldom but regular needs for me and I beleive for many others in case of external hardware malfunctions, for example.

Previosly  I have used selfcompiled version of Armbian 5.15 where named option was enabled and anything was fine. Now I have upgraded to Armbian 21.08.1 Buster by installing release version of it because it seems dramatically more complicated to compile by myself.

Now in case of freezes of my bluetooth adapter which connects to gsm phone to send some alerts, the only way to restore its functioning is to do system restart, while uloading an reloading (rmmod -f btusb; moprobe btusb) bluetooth driver was enough. 

I need i2s audio output on the Odroid C2. Have the required kernel modules snd-soc-pcm5102 and snd-soc-odroid-dac

made it into any Armbian C2 images?

When I switch back to docker, the build is ok.

Can Armbian dev team consider support podman? since podman is popular nowadays. :-P

I have a tv box (mxq pro 4k 5g with rk3228a chipset). The wifi chipset is sv6152p.

The armbian image "Armbian_21.08.1_Rk322x-box_buster_legacy_4.4.194_xfce_desktop.img.xz" works on it with the wifi driver ssv6x5x.

I want to use librelec on it. When i install unofficial libreelec for rk3229/rk3228 box (kernel 4.4.194) the wifi don't works. The driver for ssv6051 is loading at startup but wifi don't works.

Can somebody say to me how to compile ssv6x5x for libreelec.

I don't know how to cross compile it.

which source do i use :

https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx

or

https://github.com/paolosabatino/ssv6x5x

How to proceed.

Thank's a lot.

Bests regards.

It is my personal opinion that armbian should be distributed without default packages from the Debian non-free archive area.

I think that the only package that is pre-installed from that area is iozone3.

I wanted to stress that I believe that the armbian developers chose to pre-install iozone3 in good faith.

So I don't mean to cause any undue trouble - If removing the tool is not appropriate at this time, I understand.

I just wanted it out there that this is something that is 'nice to have'.

Thanks,

LD

there has been a linux kernel issue in the pci part. The symptoms are Armbian kernel panics. This has already been discussed in the armbian forum:

A patch has been supplied by @Pali and Marek Behún in the drivers/pci/quirks.c file. Thank you guys very much for that!

Bug report can be found here:https://bugzilla.kernel.org/show_bug.cgi?id=212695

And patch can be found here: https://lore.kernel.org/linux-pci/20210317115924.31885-1-kabel@kernel.org/

This is the actual patch content:

---
 drivers/pci/quirks.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 653660e3ba9e..a561136efb08 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -3251,6 +3251,11 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SOLARFLARE,
 			 PCI_DEVICE_ID_SOLARFLARE_SFC4000A_1, fixup_mpss_256);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SOLARFLARE,
 			 PCI_DEVICE_ID_SOLARFLARE_SFC4000B, fixup_mpss_256);
+/*
+ * For some reason DECLARE_PCI_FIXUP_HEADER does not work with pci-aardvark
+ * controller. We have to use DECLARE_PCI_FIXUP_EARLY.
+ */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_ASMEDIA, 0x0612, fixup_mpss_256);
 
 /*
  * Intel 5000 and 5100 Memory controllers have an erratum with read completion
-- 

As proposed by @Pali, I'd like to kindly ask that this patch gets included into Armbian as this affects several boards using ASMedia chip ASM1062 on ARM.

If this report lacks any information I'd be happy to supply them.

Thank you very much in advance.

Rötti

Can you add this TV-out feature to the new armbian focal release for orange pi H2+ / H3 ?

For example I want to get system with deb-src packages. Of cause I can add deb-src via userpatches/customize-image.sh but it is not so easy.

May be armbian add option like INSTALL_KSRC that allow user to get OS with uncommented deb-src in /etc/apt/sources.list

It also helps in customize-image.sh For example:

Main() {   
    apt-get install libxcb-xinerama0-dev -y

It will Error: You must put some 'deb-src' URIs in your sources.list

The solution may be:

./compile.sh REPOSITORY_INSTALL=deb-src

general.sh

$BOOTSOURCE

in armbian docs. But nothing. But I know that armbian docs use a lot of words with $!

I suggest allow users to find words with $ in armbian docs.