Search the Community

Hello ! I'm trying to build my custom Armbian image for a Raspberry Pi. When I build it with these settings, I get a rolling release, which I don't want. compile.sh BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes DISABLE_IPV6=true INCLUDE_HOME_DIR=yes KERNEL_CONFIGURE=no NETWORKING_STACK=network-manager RELEASE=trixie EXPERT=yes BOARD=rpi4b But when I boot with the official armbian minimal image (Armbian_25.8.1_Rpi4b_trixie_current_6.12.41_minimal.img) It's not on the rolling release. Do I miss a setting ? edit: I've tried with building the image on the main and the v25.08 branch.

mihanson@armbi400:~$ sudo poweroff Broadcast message from root@armbi400 on pts/0 (Thu 2025-09-04 07:29:16 PDT): The system will power off now! mihanson@armbi400:~$ [41893.451514] reboot: Power down [41893.454658] ------------[ cut here ]------------ [41893.459337] Voluntary context switch within RCU read-side critical section! [41893.459354] WARNING: CPU: 0 PID: 1 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x4e0/0x530 [41893.475859] Modules linked in: sg rfcomm cmac aes_arm64 algif_hash algif_skcipher af_alg bnep zram zsmalloc binfmt_misc hci_uart btbcm bluetooth ecdh_generic ecc bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem vc_sm_cma(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_bcm2835(C) videodev snd_pcm videobuf2_common snd_timer mc raspberrypi_hwmon snd raspberrypi_gpiomem i2c_dev drm drm_panel_orientation_quirks backlight fuse bonding ipv6 brcmfmac_wcc brcmfmac cfg80211 rfkill brcmutil uio_pdrv_genirq uio nvmem_rmem [41893.527454] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Tainted: G C 6.12.44-current-bcm2711 #1 [41893.537603] Tainted: [C]=CRAP [41893.540606] Hardware name: Raspberry Pi 400 Rev 1.0 (DT) [41893.545989] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [41893.553048] pc : rcu_note_context_switch+0x4e0/0x530 [41893.558080] lr : rcu_note_context_switch+0x4e0/0x530 [41893.563112] sp : ffff80008002b770 [41893.566466] x29: ffff80008002b770 x28: ffff2262c6ffb3c0 x27: ffff2262c0c5f8c0 [41893.573707] x26: ffff2262c0260000 x25: ffffcc22d85831f4 x24: 0000000000000000 [41893.580947] x23: 0000000000000000 x22: ffff2262c0260000 x21: ffffcc22d98b3070 [41893.588187] x20: 0000000000000000 x19: ffff22637b779fc0 x18: 0000000000000006 [41893.595426] x17: ffffcc22d97fb000 x16: 00000000a53a0512 x15: ffff80008002b0d0 [41893.602666] x14: 0000000000000000 x13: 216e6f6974636573 x12: 206c616369746972 [41893.609905] x11: 6320656469732d64 x10: ffffcc22d96d7a28 x9 : ffffcc22d7724ed8 [41893.617145] x8 : 00000000ffffefff x7 : ffffcc22d96d3960 x6 : 00000000000002b3 [41893.624384] x5 : 00000000000002b4 x4 : 40000000fffff2b3 x3 : 0000000000000000 [41893.631623] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff2262c0260000 [41893.638863] Call trace: [41893.641336] rcu_note_context_switch+0x4e0/0x530 [41893.646016] __schedule+0xb4/0xe70 [41893.649463] schedule+0x3c/0x148 [41893.652733] schedule_timeout+0x98/0x1a0 [41893.656709] wait_for_completion_timeout+0x80/0x160 [41893.661653] mbox_send_message+0xf8/0x140 [41893.665716] rpi_firmware_property_list+0x104/0x298 [41893.670662] rpi_firmware_property+0x78/0xc8 [41893.674988] rpi_exp_gpio_get_polarity+0x68/0x100 [41893.679760] rpi_exp_gpio_dir_out+0x6c/0x120 [41893.684089] gpiod_direction_output_raw_commit+0x6c/0x348 [41893.689562] gpiod_direction_output+0xa8/0x1b8 [41893.694065] gpio_poweroff_do_poweroff+0x2c/0xd0 [41893.698747] sys_off_notify+0x48/0x80 [41893.702458] notifier_call_chain+0x80/0x140 [41893.706699] atomic_notifier_call_chain+0x44/0x70 [41893.711468] do_kernel_power_off+0x5c/0x80 [41893.715618] machine_power_off+0x40/0x58 [41893.719594] kernel_power_off+0x88/0x98 [41893.723479] __do_sys_reboot+0x1e0/0x240 [41893.727452] __arm64_sys_reboot+0x2c/0x40 [41893.731514] invoke_syscall+0x50/0x120 [41893.735314] el0_svc_common.constprop.0+0x48/0xf0 [41893.740083] do_el0_svc+0x24/0x38 [41893.743441] el0_svc+0x38/0x120 [41893.746622] el0t_64_sync_handler+0x120/0x130 [41893.751037] el0t_64_sync+0x190/0x198 [41893.754745] ---[ end trace 0000000000000000 ]--- 25.8.1 Trixie Armbian image and EXT4 FS. Does not happen on reboot, just poweroff. The below also produce the same result. $ sudo shutdown -H now $ sudo systemctl poweroff mihanson@armbi400:~$ armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... Failed grabbing info (pipe 3 result 22) and sending to server paste.armbian.com. Collecting info and sending to paste.next.armbian.com, wait... https://paste.next.armbian.com/oxawoposil Please post the URL in the forum where you've been asked for.

Hi everyone, I'm new to creating my own images and I'm learning this just because I'm interested in it. I am trying to build ubuntu 24.04 for my rpi3b using the build configuration for rpi4b. Now I'm trying to automate the process of the first launch (skip the selection of bash, zsh, creating a password for root, creating a regular user, etc.). In one of the topics, I found out that I can delete "rm -rf/root/.not_logged_in_yet" And the system will not ask for the initial setup, but to make all the necessary changes for me, I wrote a small function in customize-image.sh: SettingSystemFirtsRun() { #disable defaut script sudo rm -rf /root/.not_logged_in_yet #setting regul user echo "add user $_userName" sudo useradd -m -c -s /bin/bash "$_userName" "$_userName" -p "$_userPass" #change root pass echo 'change root passssss' echo "root:$_rootPass" | sudo chpasswd # Set hostname permanently echo "Setting hostname to $_Hostname" echo "$_Hostname" > /etc/hostname hostname -b "$_Hostname" # Update hosts file sed -i "s/127.0.1.1.*/127.0.1.1\t$_Hostname/g" /etc/hosts } But when the system starts, I still do not see the directory of the user I am creating in /home, while the user himself is being created. The most important thing is that I really want to implement user creation at the assembly stage, although I am less and less convinced that this is even possible... I do not rule out that there are more concise ways to solve this problem, so I will be glad of any advice, good luck to all. P.S. I read the documentation, but I couldn't find a solution there.

I am currently developing an application that requires using monitor mode with RT8821CU chipset (rtw88 kernel driver). Previously I was using RaspberryPi OS and everything worked great, but I am moving to Armbian mainly to be able to target more SBCs. The problem is in Armbian, the WiFi monitoring performance is much much worse (at least with the RT8821CU) than with RaspberryPi OS and with my Arch laptop, and I cannot guess why could this be. I have tested on the rpi4b the following: * Build the rtw88 driver with debug and debugfs enabled just in case. * Test with all the three kernel versions available (edge 6.16, current 6.12, legacy 6.6). None of them achieves decent performance. * Test the 8821cu driver (**a different driver than the rtw88**): seems to have better perf, but doesnt support the fcsfail feature I need and is quite unstable (for example creating a new interface on the device phy using iw, causes the system to freeze and requires a hard reset, and on some circumstances, calling iwconfig also freezes the system). * Try all of the above on the community supported OrangePi 3 LTS: same result, I have the same poor WiFi monitoring performance as with the rpi4b * Cross compile the Raspberry Pi kernel myself (I tried with version 6.6) with rtw88 driver enabled, and manually install it in my rpi4b Armbian SD card (copy the kernel, dtb files and modules, and create appropriate symlinks): I get the same perf as in Raspberry Pi OS! So there must be something with the kernel built with Armbian that is causing this monitoring performance degradation. Unfortunately I am clueless about what could be causing the problem. I have reviewed the kernel configuration, and all options related to the RTW88 driver are the same. But there must be something elsewhere that I cannot find. Any suggestion about what could be the problem or how to debug it? Thanks in advance!

I'm trying to run the following on edge devices, the remote interface to which does not support a traditional terminal (i.e. no interactivity): armbian-config --cmd ROO001 At the conclusion of this command running, the user is prompted through the UI/TUI to reboot the device. How can I avoid this reboot prompt, and just proceed with the reboot immediately? e.g. the Raspberry Pi OS raspi-config tool allows for the nonint parameter to be passed: raspi-config nonint enable_overlayfs The intent is to automate enabling of the read-only fs. Hardware is various Raspberry Pi and ROCK Pi devices running Armbian. I've already confirmed the command works fine with user input. I just need to understand how to interact with the tool without user input. Thank you

rpi4b8gb device. I am trying to disable wifi, bluetooth and ipv6 like I do on raspberry pi OS, but it won't play nice with me. Bluetooth & wifi I read https://docs.armbian.com/User-Guide_Armbian_overlays/ (it says it's WIP so that might be why?) and looked for the dtolverlays I use on rpiOS: $ ls -1 /boot/dtb/overlays/disable* | cut -d / -f 5 disable-bt.dtbo disable-bt-pi5.dtbo disable-emmc2.dtbo disable-wifi.dtbo disable-wifi-pi5.dtbo $ ls -1 /boot/dtb-6.12.31-current-bcm2711/overlays/disable* | cut -d / -f 5 disable-bt.dtbo disable-bt-pi5.dtbo disable-emmc2.dtbo disable-wifi.dtbo disable-wifi-pi5.dtbo They are there, ie disable-bt and disable-wifi, so I edited /boot/armbianEnv.txt and added: overlays=disable-bt disable-wifi But after reboot they are still active (see wifi interface below about ipv6): $ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Thu 2025-06-05 18:17:32 CEST; 4min 3s ago Docs: man:bluetoothd(8) Main PID: 610 (bluetoothd) Status: "Running" Tasks: 1 (limit: 8723) Memory: 3.1M CPU: 102ms CGroup: /system.slice/bluetooth.service └─610 /usr/libexec/bluetooth/bluetoothd Yes, I know, I can just disable and mask the service, but this way should work too right? IPV6 And for ipv6 I edited armbianEnv.txt and added: extraargs=ipv6.disable=1 But still available (you can also see wifi not disabled): $ ls -l /proc/sys/net/ipv6/conf/all/disable_ipv6 # this should not be available -rw-r--r-- 1 root root 0 Jun 5 18:19 /proc/sys/net/ipv6/conf/all/disable_ipv6 $ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether <redacted> brd ff:ff:ff:ff:ff:ff inet 192.168.99.60/24 metric 100 brd 192.168.99.255 scope global dynamic end0 valid_lft 42013sec preferred_lft 42013sec inet6 <redacted>/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether <redacted> brd ff:ff:ff:ff:ff:ff The strange thing is on my OrangePi-PC2 disabling ipv6 this way works... Any advice?

I tried to follow below guide, but I wasnt able to install as the model isn't listed in it. I tried cups and gutenprint but even when the printer was added to cups dashboard, but when I send "Print Test" then nothing prints out. What options do I have here ?

I'm on the most recent Armbian 25.2.3 Noble version. When I try the command $ yes | sudo apt dist-upgrade I get the following error: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: ... Learn more about Ubuntu Pro at https://ubuntu.com/pro The following upgrades have been deferred due to phasing: gnome-shell gnome-shell-common ubuntu-drivers-common The following packages will be upgraded: thunderbird 1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 68.6 MB of archives. After this operation, 453 kB of additional disk space will be used. Get:1 http://apt.armbian.com noble/noble-desktop arm64 thunderbird arm64 9:128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1 [68.6 MB] Err:1 http://apt.armbian.com noble/noble-desktop arm64 thunderbird arm64 9:128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1 File has unexpected size (68620562 != 68620660). Mirror sync in progress? [IP: 2a01:4f9:3b:4943::2 80] Hashes of expected file: - SHA512:e49ee18c96333c4dfbb188458a3fb8ce271874d1aaf830ce4aed2ff5b3f59220cc4ead01243323047a6d7ef7258b6f2f66f5d231ea83dfc53356e4d9aeeef0d6 - SHA256:581efd7ac140c5c416648efad6fcea96ed4cccc9db6e8300b6200860399d9f5c - SHA1:de05de93f62cf5b298bddbdc65fcb95fe0c4062e [weak] - MD5Sum:91c1809c8ca059ebdfb71787b02f3b4b [weak] - Filesize:68620660 [weak] E: Failed to fetch http://fi.mirror.armbian.de/apt/pool/noble-desktop/t/thunderbird/thunderbird_128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1_arm64.deb File has unexpected size (68620562 != 68620660). Mirror sync in progress? [IP: 2a01:4f9:3b:4943::2 80] Hashes of expected file: - SHA512:e49ee18c96333c4dfbb188458a3fb8ce271874d1aaf830ce4aed2ff5b3f59220cc4ead01243323047a6d7ef7258b6f2f66f5d231ea83dfc53356e4d9aeeef0d6 - SHA256:581efd7ac140c5c416648efad6fcea96ed4cccc9db6e8300b6200860399d9f5c - SHA1:de05de93f62cf5b298bddbdc65fcb95fe0c4062e [weak] - MD5Sum:91c1809c8ca059ebdfb71787b02f3b4b [weak] - Filesize:68620660 [weak] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? It seems like some checksum or some other validation data doesn't match the actual data. Thanks for any guidance on this matter.

I am building a custom image for rpi4b and everything works great so far. I only want to customize the installed packets and configuration, but I do not need a custom kernel. Since building the kernel is what takes by a wide margin most of the image generation time, I was wondering if there's a way to build the image without building the kernel (using the one from the official builds). I have browsed the documentation and found no way, so maybe it is not supported and building the kernel is mandatory?

WiFi is missing in "Armbian_25.5.0-trunk.428_Rpi4b_trixie_current_6.12.22_minimal.img" Solved by following commands ``` sudo apt update sudo apt install firmware-brcm80211 --fix-broken sudo reboot ```

I am new to armbian, and so far I managed to build a working image with some custom packages added and some removed by customizing `userpatches/lib.config`. Easy stuff and it's working great so far! Now I need to build some packages from sources and get them added to the resulting image. The usual way I would do this, would be installing a cross toolchain, having a staging dir with includes and libs from the dev packages I add to the image, etc. But after building the base armbian image, on my system I see I have two docker images related to armbian (ghcr.io/armbian/docker-armbian-build and armbian.local.only/armbian-build), and I wonder if maybe the "local only" image is somehow like a "staging" image or how does this work. So far I have not been able to find documentation about the procedure, is there any guide explaining how to achieve this?

Hello guys! Probably some of you know me as the MadEDoctor from Youtube. For those of you who don't know my channel and don't know what I am doing at the moment - Long story short I got my hands on a 16GB RAM chip that should be compatible with the Raspberry Pi 4 hardware. But there is a problem I am facing... That is I am unable to boot any OS different from VMware (arm version) and RISC OS (that is pretty much useless). When I try to boot Raspbian for example - It shows the rainbow square and then gets stuck on a completely black screen and it draws around 500mA... I contacted Jeff Geerling with the hope he could help with this project. He wrote a post on the official RPi forum. As it seems the engineers of the Pi just don't want to help and even worse are lying that the hardware doesn't support 16GB of RAM... Then one guy in the comments suggested I write here and ask for help... and here I am I will be pretty thankful if somebody could help me with this project. Here I provide datasheets for both the 16GB chip I got and the 8GB OEM one so you can compare them. 8GB - Micron D9ZCL | MT53E2G32D4NQ-046 WT:A :https://www.farnell.com/datasheets/3681594.pdf 16GB - Micron D8CBG | MT53E4G32D8CY-046 WT:C :https://4donline.ihs.com/images/VipMasterIC/IC/MICT/MICT-S-A0017462930/MICT-S-A0017465122-1.pdf?hkey=52A5661711E402568146F3353EA87419 And this is the video where I show what I have done to this point: https://youtu.be/vtym0TAWNto

For Armbian-24.11.0 RPi ubuntu noble based builds wlan interface is missing Issue is present in Rpi3 B plus, RPi4 for current (kernel 6.6.x) and edge (kernel 6.10.x) armbian builds OS info ================ pi@rpi4b:~$ cat /etc/os-release PRETTY_NAME="Armbian-unofficial 24.11.0-trunk noble" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://duckduckgo.com/" SUPPORT_URL="https://community.armbian.com/" BUG_REPORT_URL="https://armbian.atlassian.net/" PRIVACY_POLICY_URL="https://duckduckgo.com/" UBUNTU_CODENAME=noble LOGO="armbian-logo" ARMBIAN_PRETTY_NAME="Armbian-unofficial 24.11.0-trunk noble" pi@rpi4b:~$ uname -a Linux rpi4b 6.10.10-edge-bcm2711 #1 SMP PREEMPT Fri Sep 13 15:35:16 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux ================ wlan interface is missing (at all): =============== pi@rpi4b:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether d8:3a:dd:8e:79:9a brd ff:ff:ff:ff:ff:ff inet 192.168.1.139/24 metric 100 brd 192.168.1.255 scope global dynamic end0 valid_lft 25034sec preferred_lft 25034sec inet6 fe80::da3a:ddff:fe8e:799a/64 scope link valid_lft forever preferred_lft forever =============== The reason is incorrect firmware files format inside /lib/firmware. Firmware files are zstd packed (has *.zst extensons). Broadcom driver is unable to load such files =================== pi@rpi4b:~$ dmesg|grep -i brcmfmac [ 4.387851] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 4.395645] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 4.403229] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2 [ 4.403347] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin failed with error -2 [ 5.407124] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 =================== Files from /lib/firmware: ============================ ls -l /lib/firmware/brcm | egrep "raspberrypi,4-model-b" lrwxrwxrwx 1 root root 17 Sep 21 22:27 BCM4345C0.raspberrypi,4-model-b.hcd.zst -> BCM4345C0.hcd.zst lrwxrwxrwx 1 root root 35 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.bin.zst -> ../cypress/cyfmac43455-sdio.bin.zst lrwxrwxrwx 1 root root 40 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob.zst -> ../cypress/cyfmac43455-sdio.clm_blob.zst lrwxrwxrwx 1 root root 26 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.txt.zst -> brcmfmac43455-sdio.txt.zst ls -l /lib/firmware/cypress | egrep "cyfmac43455*" lrwxrwxrwx 1 root root 38 Sep 21 22:27 cyfmac43455-sdio.bin.zst -> /etc/alternatives/cyfmac43455-sdio.bin -rw-r--r-- 1 root root 1261 Apr 11 00:46 cyfmac43455-sdio.clm_blob.zst -rw-r--r-- 1 root root 384405 Apr 11 00:46 cyfmac43455-sdio-minimal.bin.zst -rw-r--r-- 1 root root 453440 Apr 11 00:46 cyfmac43455-sdio-standard.bin.zst ls -l /etc/alternatives/cyfmac43455-sdio.bin lrwxrwxrwx 1 root root 55 Apr 11 00:46 /etc/alternatives/cyfmac43455-sdio.bin -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin.zst ============================ To fix this issue following steps have to be done: 1) install zstd package 2) unpack *.zst files inside /lib/firmware using unzstd 3) recreate all symlinks inside /lib/firmware from symlink_src(*.zst) => to symlink_dst(*.zst) to (no *.zst) 4) recreate /etc/alternatives/cyfmac43455-sdio.bin symlink /etc/alternatives/cyfmac43455-sdio.bin -> -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin.zst to /etc/alternatives/cyfmac43455-sdio.bin -> -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin The recipe is proven to be working - wlan interface is back. Tested for Rpi3 B plus, RPi4 current (kernel 6.6.x) and edge (kernel 6.10.x) armbian builds

Today I imaged 'Armbian_24.8.0-trunk.542_Rpi4b_noble_current_6.6.44_gnome_desktop.img' on to an SD card and then put it in my Raspberry Pi 4 GB. It booted up first time no issues and I went through the setup flow. I am using wired ethernet and was able to reach it remotely immediately. I installed all the updates. When I do "sudo shutdown -h -r now" on the command line (either via SSH or locally in the terminal) it does not reboot. The device stops responding to pings and no longer has HDMI output. If I power cycle the board once, it does not boot up. On the second power cycle it boots up. This seems really odd. Is this some known issue with the raspberry pi 4 ?

Hi All, I wanted to add some dtoverlay lines to the pi's config.txt which was in /boot/firmware/config.txt and I notice the folder is empty ? WTF the pi is running ok - how can this be ?

Hey all... Looking to put something a LOT more lightweight than RaspiOS (and not-modern-desktoppy at all, please) on my Pi4Bs. Found out about armbian from the Wikipedia page and downloaded the Jammy CLI image, but I can't get either gitlab or github to talk to me for downloading either of the recommended imagers; gitlab just gives me a blank page (no HTMl at all, per Firefox "view source") and github outright refuses connections. If it's important I do not have accounts on either system, and am loath to create same, although I could if necessary. I don't have Internet at home so I'm doing this from a Win10 PC at my public library; it's running the current Firefox (122.0). (My Pis will also live offline; I don't currently have a portable screen/mouse/KB to haul down here to do online installs, so I know I'll be stuck with only whatever's already in your images, for now anyway.) Can I just dd the image to a new/blank uSD card (Sandisk class 10, A1)? I'm fully capable of verifying the result, been admining UNIX systems since the 80s and Linux since 0.99pl6 or so... (I'll surely have more questions about making any resulting system work without internet connectivity, but first things first.)

Hello, I am planning to create a Kubernetes cluster from 5 Raspberry PI and one of the alternatives mentioned in tags, 9 hosts in total. I want to mount and customize the installation images with ssh keys, static IP address, etc, and to skip the initial script offered at login by the CLI images. Can you point me to the right piece of documentation? Thank you, Stefanita Vilcu

Hello, I have a bunch of boards (rpi4b, rpi5, orangepi5, orangepi5-plus, nanopct6, rock3a, rock5b, vim4) in a Kubernetes cluster using Cilium. Cilium requires CONF_SCHEDSTATS=y in the kernel, which is dependent on CONFIG_DEBUG_KERNEL=y but... in build/lib/functions/compilation/armbian-kernel.sh we have # DONE: Disable: debug option kernel_config_set_n DEBUG_KERNEL # Armbian doesn't know how to package a debug kernel. Which invalidates the option I enabled during ./compile.sh BOARD=... BRANCH=... kernel-config Except for the VIM4, with DEBUG_KERNEL enabled in build/config/sources/families/meson-s4t7.conf Is there a way to enable DEBUG_KERNEL for the rest of the boards? Thank you! Stefanita Vilcu

I have a RasPi 4b, I'm trying to understand how the device tree is modified so I can use the methodology eventually for a board that has a CM4 on it. So from a virgin clone of the build repo: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full install image on SD card and boot the device, go through Armbian-setup. All well and good, then varify device tree used for the boot: cat /proc/device-tree/model gets me a: Raspberry Pi 4 Model B Rev 1.5 OK so now lets modify the device tree: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full kernel-patch When the build pauses, we open another terminal and change the device tree file (note in the build log below I had modified all the CM4 device tree files): sudo nano ./arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts Only change is to modify the model line with a marker, like my initials, new line is: model = "Raspberry Pi 4 Model B AJW"; close editor, and hit enter to restart the build, then copy resulting patch file to: userpatches/kernel/archive/bcm2711-6.7/0010-simple-device-tree.patch rebuild as before, then burn new image to SD card and retest the device tree model, but no change is apparent. So how do you change the device tree for a RasPi 4? log-build-e9849e69-98be-4710-b3be-e05a30285a44.log

I need to get an armbian focal image for the Rpi4b. I've checked in https://archive.armbian.com and it only shows the current jammy variant. If anyone could tell me where I can download the deprecated images, it would be much appreciated.

Hi friends, I use armbian for long time, but these days I change my borad to RaspberryPi 4B. However I can not get kernel startup serial output from RPI as usual on the board. Does anyone has more information about that? What I want to do is a atonomy driving experiment environment. And I don't have monitor or keyboard attach to it. I will patch preempt_RT to get the RT linux kernel, so it's difficult for me to pull the RPI out of the test bench everytime and put back after setting the ssh or something everytime I flash new kernel or image. The armbian version I use is Armbian_23.11.1_Rpi4b_jammy_current_6.1.64.img Thanks in advance.

Hi All, as all my other boards run armbian I thought it only right that my raspberry 4b should run it, has anyone here successfuly installed Armbian on one ? I don't want to use Bookworm as it has Audio problems - my main use of the pi is to host Logitech media server running squeezelite TIA

Is there some shell script file inside /boot directory that gets called on system startup? Alternatively, is there any way to make such a script run by modifying only files inside /boot (like some config setting)?

Hi, I recently noticed that after updating to 24.02 the package "linux-libc-dev" did not receive a update. I have checked the current armbian archives and couldn't find anything for any arch. Just to be sure i've also built armbian 24.5 images for bananapi (noticed this on a bananapi board) and rpi4b (as a well supported board) and no linux-libc-dev[...].deb was built. It seems that with the buildsystem change the files packages/armbian/mkdebian and packages/armbian/builddeb were retired (commit e98c66b, v23.11.1) which previously handled building the kernel packages and included linux-libc-dev. Unfortunately linux-libc-dev is a dependency for libc6-dev and in turn also linux-headers... To build such a package i think one would have to add the function to lib/functions/compilation/kernel-debs.sh, similar to the way linux-dtb is built and add it to artifact_map_packages in lib/functions/artifacts/artifact-kernel.sh to be built in the process. Does anyone agree with this observation? I'm not sure as I am pretty new to the armbian build system... Is anyone aware of this and working on it? Thanks, valium

The versioning within Armbian seems to be inconsistent. On a up to date RPi4 The login message states that it is running Armbian 23.11.1: Welcome to Armbian 23.11.1 Jammy with Linux 6.6.18-current-bcm2711 /etc/os-release is listing both 22.04 and 24.2.1: PRETTY_NAME="Armbian 24.2.1 jammy" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" ARMBIAN_PRETTY_NAME="Armbian 24.2.1 jammy" /etc/armbian-release says it is 23.11.1: VERSION=23.11.1 REVISION=23.11.1 So these are three different versions, making it confusing. Any idea what is going on here?