I'm trying to setup bcache for my openmediavault. But it seems the `bcache` module is not installed?

Quote

root@rpi5b:~# uname -a
Linux rpi5b 6.18.10-current-bcm2711 #12 SMP PREEMPT Fri Feb 13 11:56:58 UTC 2026 aarch64 GNU/Linux
root@rpi5b:~# modprobe bcache
modprobe: FATAL: Module bcache not found in directory /lib/modules/6.18.10-current-bcm2711

Which means I cannot use `bcache` at the moment with openmediavault.
I do know that the bcache has been added only recently:
* https://github.com/armbian/build/pull/9550?ref=blog.armbian.com

*  "Enable BCACHE on Raspberry Pi build"

But no go so far..

Is there anything I can do?

I installed Armbian Noble with gnome desktop, specifically "Armbian_26.2.1_Rpi4b_noble_current_6.18.9_gnome_desktop.img" on a Raspberry Pi 5. Updated system and installed chrome since I need to play some media from inside chromium browser. However, I checked to see that hardware accelerated video decode is not actually supported within Armbian currently.

Previously I had official Raspberry Pi OS installed when I first had a look at the device and there it was enabled. It's kind of a minor thing but I've used different hardware with Armbian before and it would make things a lot easier for me if I can keep using Armbian on Raspberry Pi 5 as well.

Only hint I've found on forum so far was a post from 2024 but it seemed to affect hardware acceleration in system overall and was a known issue, so I believe this is a new topic.

Other thing I still tried was to go with a rolling release instead of Standard support, in this case "Armbian_26.2.0-trunk.679_Rpi4b_noble_current_6.18.20_gnome_desktop.img" but same issue.

Any ideas on what can be done here, perhaps a setting or package I might have missed?

Armbian_25.5.1_Rpi4b_bookworm_current_6.12.28 broken after last upgrade.
I run apt upgrade which installed kernel 6.18.10. It breaks ZFS.
Provided ZFS version, 2.3.2, supports kernels up to 6.14.

Don't forget a snapshot before "apt upgrade" 🙂

Regards,

Chris

I'm having a problem with my Raspberry Pi 5, which I describe below.

I have a DVR connected to it via Ethernet.

If I connect both at the same time, dmesg reports a failure and I can't ping the DVR to establish a connection; I have to run `ifconfig eth0 down` and `ifconfig eth0 up`.

Can anyone help or know if there's a bug in the kernel version? I'm using Ubuntu 22.04. jammy

root:~# dmesg | grep eth0

[    1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a)

[    3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0.

[    3.453483] systemd[1]: Started ifup for eth0.

[    3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)

[    3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode

[    6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

[   11.560707] macb 1f00100000.ethernet eth0: Link is Down

[   13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

root:~# ping 192.168.200.201

PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data.

^C

--- 192.168.200.201 ping statistics ---

6 packets transmitted, 0 received, 100% packet loss, time 13305ms

root:~# ifconfig eth0 down

root:~# ifconfig eth0 up

root:~# dmesg | grep eth0

[    1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a)

[    3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0.

[    3.453483] systemd[1]: Started ifup for eth0.

[    3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)

[    3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode

[    6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

[   11.560707] macb 1f00100000.ethernet eth0: Link is Down

[   13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

[  147.034711] macb 1f00100000.ethernet eth0: Link is Down

[  151.855860] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)

[  151.855871] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode

[  152.869842] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

root:~# ping 192.168.200.201

PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data.

64 bytes from 192.168.200.201: icmp_seq=1 ttl=64 time=1.01 ms

64 bytes from 192.168.200.201: icmp_seq=2 ttl=64 time=1.01 ms

^C

--- 192.168.200.201 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1001ms

rtt min/avg/max/mdev = 1.007/1.007/1.007/0.000 ms

I noticed, when I go to the Raspberry Pi page on Armbian, the url refers to the Pi 4b, not the 5. I also found some articles online linking to a specific Pi 5b page (which I thought was weird since that model doesn't exist), but it just redirects to the 4b page.

Then, I went searching in the archive and found that, at some point, there were specific 5b images available (https://armbian.hosthatch.com/archive/rpi5b/archive).

Which of these should I use? Is the 4b image okay to use on a Pi 5? Or do you not support the Pi 5 at all?

Sorry if this has been answered before, it is kind of impossible to search this forum for similar questions with the super aggressive rate limiting.

E: The repository 'http://apt.armbian.com bookworm Release' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

How can I fix this or was signing simply forgotten?

Thank you!

Environment

• Raspberry Pi 4B (headless)
• DietPi (recently installed)
• Armbian (previously used)
• Both systems use default settings

Observations

• SSH login to DietPi is consistently faster than Armbian by a few seconds with default settings.
• Initially suspected MOTD settings, tested files under /etc/update-motd.d/. Discovered that 10-armian-header adds approximately 1 second to login time. Disabled this component but SSH login to Armbian still remained slow.
• Found related discussion on Raspberry Pi forums: SSH speed limit?
• Used the following command for testing which revealed significant speed differences:

• dd if=/dev/zero bs=1K count=1M | ssh localhost 'dd of=/dev/null'

and console log

root@DietPi:~# dd if=/dev/zero bs=1K count=1M |ssh localhost 'dd of=/dev/null'
root@localhost's password:
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 12.9425 s, 83.0 MB/s
2097152+0 records in
2097152+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.35135 s, 115 MB/s
root@DietPi:~# uname -snrvm
Linux DietPi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64

root@rpi4b1:~# dd if=/dev/zero bs=1K count=1M |ssh localhost 'dd of=/dev/null'
root@localhost's password:
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 29.5451 s, 36.3 MB/s
2097152+0 records in
2097152+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 20.0137 s, 53.7 MB/s
root@rpi4b1:~# uname -snrvm
Linux rpi4b1 6.12.19-current-bcm2711 #1 SMP PREEMPT Thu Mar 20 17:34:53 UTC 2025 aarch64

kernel config attachments

dietpi: 

raspberrypi-config-6.12.47+rpt-rpi-v8.zip  raspberrypi_proc_crypto.zip

armbian on rpi4b:

armbian-rpi-config-6.12.19-current-bcm2711.zip  armbian_rpi_proc_crypto.zip

I'm having trouble with the raspberry omv builds.

The latest build I can get working is 24.11.1 which doesn't survive an upgrades (I've tried holding the various packages that seem to cause issues which used to work but doesn't work anymore. The suggested trouble shooting on the download page doesn't work either.

Currently the  25.11.1 build is stuck in a bootloop, the only irregularity I can identify is failure to load console-setup.service message.

I had a working system that lost my soundcard/DAC-hat after trying to address update error messages which's what started this whole refresh process

Hi,

I successfully installed and tested PiClone (or also called SD Card Copier) in Armbian 25.8.1 Trixie on a Raspberry PI 4b with SD cards and SSD via USB adapter and vice versa. Might also work on other Debian based distro's. I just leave my personal instructions here in case others need PiClone too to make copy of good working Armbian install and configuration. To be clear I am not a very advanced user, so others may know to do more efficient. But it is working here without issue.

Moved to Armbian because was fed up with annoyances in DietPI, certain things being too different from pure Debian that I use on "regular" computers. Raspberry PI OS is too much slower than DietPI, Raspberry PI OS Lite with custom DE install too many bugs and errors. Armbian so far seems best option. Very close to "real" Debian and seems even faster than DietPI. 

In DietPI based on Bookworm could install app PiClone via apt, but in Armbian Trixie not, probably not in official Debian repo for Trixie anymore. But in Bookworm based Debian instead of building and compiling PiClone at step 3 could try: sudo apt install piclone.

SO I INSTALLED PICLONE LIKE THIS:

1) DEPENDENCIES:

-NEEDED VIA TERMINAL: sudo apt-get install debhelper dh-autoreconf libglib2.0-dev libgtk-3-dev parted dosfstools e2fsprogs coreutils mount uuid zenity dbus-x11 libgtk-3-0

-ALSO NEEDED: sudo apt-get install libtool automake autoconf nasm pkgconf

2) INSTALL APP VIA TERMINAL:

wget https://github.com/raspberrypi-ui/piclone/archive/refs/heads/master.zip -O piclone.zip
unzip piclone.zip
cd piclone-master

THEN: 

-sudo apt install meson
-meson setup builddir
-cd builddir
-meson compile
-sudo meson install

3) START APP

Now can start PiClone app via application menu or in terminal type "piclone" and enter.

Sources:

1) LAST STEP INSTALL PICLONE ITSELF WAS NOT WORKING: https://www.childs.be/articles/post/how-to-install-raspberry-pis-sd-card-copier-on-your-non-raspian-linux-machine 

2) LAST STEP INSTALL PICLONE APP VIA THIS LINK: https://github.com/raspberrypi-ui/piclone#

Hello!

I have an RPi5 8GB board that I bought off of AliExpress, along with a Waveshare PoE M.2 HAT+ ( https://www.waveshare.com/poe-m.2-hat-plus-b.htm )

Initially I tried to use the Noble XFCE image, by following the recommended installation procedure via rpi-imager via a USB drive, hoping to install the system to a Toshiba (Kioxia) NVMe drive.

The RPI5 was connected to a CrowView Note.

What I saw was that the firmware loaded up the necessary files from the USB drive (then later the micro-SD card), and the initramfs loaded up too, then systemd started up, and probably when the screen usually goes blank for a short time (probably switching to KMS), here, the signal completely drops, and apparently nothing happens.

(The messages scroll too fast, and then disappear, and I can't make out anything from the screen content.)

I tried looking on the network to see whether the RPi5 comes up at all, but no.

Since then, I tried to eliminate elements from my setup to see whether that makes any difference:

• I removed the Waveshare HAT
• Swtiched to using a micro-SD card instead of the USB thumb drive
• Tried to boot it without the CrowView Note
• Tried using the Noble Server image to eliminate any possible problems with the graphical UI 

but none of these helped.

I now have the bare RPi5 with an active heatsink, and it's still not booting properly.

What should I try? Should I try to get serial console working so that I at least see the boot messages?

Is there an activity LED on the RPI5 where I could at least configure a heartbeat so that I could check whether the OS is alive at all?

Since the OS can't be installed, I can't really submit much diagnostic information.

Error trying to run apt upgrade.

Here is the error I receive:

The following packages have unmet dependencies:
 armbian-bsp-cli-rpi4b-current : Depends: base-files (>= 25.8.2) but 25.8.1-12.4+deb12u11-bookworm is to be installed
E: Unable to correct problems, you have held broken packages.

I am not sure how to resolve this.  Help will be greatly appreciated.

```

Summary:                                                                                                                                                                                  
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 2                                                                                                                              
  2 not fully installed or removed.                                                                                                                                                       
  Space needed: 0 B / 27.9 GB available                                                                                                                                                   
                                                                                                                                                                                          
Setting up linux-image-6.12.48+deb13-rt-arm64 (6.12.48-1) ...                                                                                                                             
/etc/kernel/postinst.d/initramfs-tools:                                                                                                                                                   
update-initramfs: Generating /boot/initrd.img-6.12.48+deb13-rt-arm64                                                                                                                      
WARNING: Unsupported initramfs version (6.12.48+deb13-rt-arm64) - skipping setup                                                                                                          
NOTE: Manual boot configuration may be required                                                                                                                                           
/etc/kernel/postinst.d/z50-raspi-firmware:                                                                                                                                                
WARNING: Unsupported kernel version (6.12.48+deb13-rt-arm64) - skipping setup                                                                                                             
NOTE: Manual boot configuration may be required                                                                                                                                           
/etc/kernel/postinst.d/zzz-copy-new-files:                                                                                                                                                
cp: cannot stat '/usr/lib/linux-image-6.12.48+deb13-rt-arm64//overlays': No such file or directory                                                                                        
run-parts: /etc/kernel/postinst.d/zzz-copy-new-files exited with return code 1                                                                                                            
dpkg: error processing package linux-image-6.12.48+deb13-rt-arm64 (--configure):                                                                                                          
 installed linux-image-6.12.48+deb13-rt-arm64 package post-installation script subprocess returned error exit status 1                                                                    
dpkg: dependency problems prevent configuration of linux-image-rt-arm64:                                                                                                                  
 linux-image-rt-arm64 depends on linux-image-6.12.48+deb13-rt-arm64 (= 6.12.48-1); however:                                                                                               
  Package linux-image-6.12.48+deb13-rt-arm64 is not configured yet.                                                                                                                       
                                                                                                                                                                                          
dpkg: error processing package linux-image-rt-arm64 (--configure):                                                                                                                        
 dependency problems - leaving unconfigured                                                                                                                                               
Errors were encountered while processing:                                                                                                                                                 
 linux-image-6.12.48+deb13-rt-arm64                                                                                                                                                       
 linux-image-rt-arm64                     

```

It looks like the linux-image-6.12.48+deb13-rt-arm64 (6.12.48-1 package is trying to install an overlay in '/usr/lib/linux-image-6.12.48+deb13-rt-arm64//overlays' but that directory does not exist.

The description of this package says: "This package depends on the latest Linux kernel and modules for use on 64-bit ARMv8 machines. " 

```

ic  linux-image-6.12.48+deb13-rt-arm64 6.12.48-1                      arm64        Linux 6.12 for 64-bit ARMv8 machines (signed), PREEMPT_RT
ii  linux-image-current-bcm2711        25.8.2                         arm64        Armbian Linux current kernel image 6.12.56-current-bcm2711
rc  linux-image-rt-arm64               6.12.48-1                      arm64        Linux for 64-bit ARMv8 machines (meta-package)

```

Any suggestions on how to resolve this?

fastfetch output:

sudo armbian-upgrade
Hit:1 https://mirrors.ustc.edu.cn/armbian trixie InRelease
Hit:2 https://mirrors.ustc.edu.cn/debian trixie InRelease
Hit:3 https://mirrors.ustc.edu.cn/debian trixie-updates InRelease
Hit:4 https://mirrors.ustc.edu.cn/debian-security trixie-security InRelease
Hit:5 https://github.armbian.com/configng stable InRelease
Get:6 https://apt.syncthing.net syncthing InRelease [24.2 kB]
Fetched 24.2 kB in 2s (14.8 kB/s)
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
The following packages will be upgraded:
  armbian-config  raspi-firmware

Summary:
  Upgraded: 2, Newly installed: 0, To remove: 0, Not upgraded: 0
  Download size: 13.2 MB
  Space required/available: 272 kB / 553 GB

Get:1 https://mirrors.ustc.edu.cn/armbian trixie/trixie-utils arm64 raspi-firmware all 1:1.20250915-1~bookworm [13.0 MB]
Get:2 https://github.armbian.com/configng stable/main arm64 armbian-config all 25.11.0-trunk.234.0923.175957 [157 kB]
Fetched 13.2 MB in 2s (5,967 kB/s)
(Reading database ... 46602 files and directories currently installed.)
Preparing to unpack .../raspi-firmware_1%3a1.20250915-1~bookworm_all.deb  ...
Unpacking raspi-firmware (1:1.20250915-1~bookworm) over (1:1.20250430-4~bookworm) ...
Preparing to unpack .../armbian-config_25.11.0-trunk.234.0923.175957_all.deb  ...
Unpacking armbian-config (25.11.0-trunk.234.0923.175957) over (25.11.0-trunk.192.0915.191809) ...
Setting up armbian-config (25.11.0-trunk.234.0923.175957) ...
Setting up raspi-firmware (1:1.20250915-1~bookworm) ...
Installing new version of config file /etc/initramfs/post-update.d/z50-raspi-firmware ...
Installing new version of config file /etc/kernel/postinst.d/z50-raspi-firmware ...
WARNING: Unsupported kernel version (6.12.44-current-bcm2711) - skipping setup
NOTE: Manual boot configuration may be required
Processing triggers for initramfs-tools (0.148.3) ...
update-initramfs: Generating /boot/initrd.img-6.12.44-current-bcm2711
WARNING: Unsupported initramfs version (6.12.44-current-bcm2711) - skipping setup
NOTE: Manual boot configuration may be required
Summary:
  Upgraded: 0, Newly installed: 0, To remove: 0, Not upgraded: 0

How exactly should I do in this case? In the past, I normally invoke update-intramfs to perform the  the intramfs update.

Thanks,

Hello, I have installed NextcloudPi on my Raspberry PI5. Current OS is installed currently:

Now, I would like to make an upgrade and get the following issue.

What can I do?  I am very grateful for any help.

unable to login (refused ssh). had to switch back to the 25.2.3 build

Well, I was wrong and the RPi5 current stuck in the RPi Logo on a black page. Net address seems to be 0.0.0.0.

I could really use some advice on how to restore this, perhaps some `chroot` method from another Linux machine to get the right kernel package and intramfs.

Here are the steps that got me to the current situation. Maybe a hint on how to restore?

1. Mark `raspi-firmware`, like what was recommended in 1st post.

sudo apt-mark hold raspi-firmware
[sudo] password for pi:
raspi-firmware set on hold.

2.  Remove the old bsp for RPi5b specific package?

pi@nextcloudpi:~$ sudo dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi5b-current
dpkg: warning: ignoring request to remove libraspberrypi0 which isn't installed
(Reading database ... 50983 files and directories currently installed.)
Removing armbian-bsp-cli-rpi5b-current (24.11.1) ...
Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' starting.
Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' finishing.
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152

3. Install the newer RPI4b bsp package, which guessing from the 2nd post, including everything from 3b to 5b.

pi@nextcloudpi:~$ sudo apt install armbian-bsp-cli-rpi4b-current
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  armbian-bsp-cli-rpi4b-current
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,515 kB of archives.
After this operation, 5,411 kB of additional disk space will be used.
Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 armbian-bsp-cli-rpi4b-current arm64 25.8.1 [1,515 kB]
Fetched 1,515 kB in 2s (1,008 kB/s)
Selecting previously unselected package armbian-bsp-cli-rpi4b-current.
(Reading database ... 50867 files and directories currently installed.)
Preparing to unpack .../armbian-bsp-cli-rpi4b-current_25.8.1_arm64.deb ...
Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' starting.
Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' finishing.
Unpacking armbian-bsp-cli-rpi4b-current (25.8.1) ...
Setting up armbian-bsp-cli-rpi4b-current (25.8.1) ...
Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' starting.
Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' finishing.
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152

4. I notice the initrd was still generated for the old kernel image, which is understandable based what is currently installed

pi@nextcloudpi:~$ uname -a
Linux nextcloudpi 6.6.63-current-bcm2712 #2 SMP PREEMPT Wed Nov 27 10:28:46 UTC 2024 aarch64 GNU/Linux
pi@nextcloudpi:~$ dpkg -l | grep linux-image
ii  linux-image-current-bcm2712    24.11.1                                     arm64        Armbian Linux current kernel image 6.6.63-current-bcm2712

5. Therefore, I went ahead to install the new 6.12 kernel package

pi@nextcloudpi:~$ sudo apt install linux-image-current-bcm2711
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  linux-image-current-bcm2711
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 34.5 MB of archives.
After this operation, 212 MB of additional disk space will be used.
Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 linux-image-current-bcm2711 arm64 25.8.1 [34.5 MB]
Fetched 34.5 MB in 5s (7,198 kB/s)
Selecting previously unselected package linux-image-current-bcm2711.
(Reading database ... 51028 files and directories currently installed.)
Preparing to unpack .../linux-image-current-bcm2711_25.8.1_arm64.deb ...
Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' starting.
Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' finishing.
Unpacking linux-image-current-bcm2711 (25.8.1) ...
Setting up linux-image-current-bcm2711 (25.8.1) ...
Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' starting.
update-initramfs: Generating /boot/initrd.img-6.12.44-current-bcm2711
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.12.44-current-bcm2711'
Armbian: Debian compat: linux-update-symlinks install 6.12.44-current-bcm2711 boot/vmlinuz-6.12.44-current-bcm2711
I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.44-current-bcm2711
I: /initrd.img is now a symlink to boot/initrd.img-6.12.44-current-bcm2711
Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' finishing.

6. Everything looked right to me as there are no errors like before got reported during update-initramfs:

pi@nextcloudpi:~$ sudo apt remove linux-image-current-bcm2712
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-image-current-bcm2712
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 155 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 54440 files and directories currently installed.)
Removing linux-image-current-bcm2712 (24.11.1) ...
Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' starting.
Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' finishing.
Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' starting.
update-initramfs: Deleting /boot/initrd.img-6.6.63-current-bcm2712
Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' finishing.

7. As a final check, I ran the upgrade script again
 

pi@nextcloudpi:~$ sudo armbian-upgrade
Hit:1 https://mirrors.ustc.edu.cn/debian bookworm InRelease
Hit:2 https://mirrors.ustc.edu.cn/debian bookworm-updates InRelease
Hit:3 https://mirrors.ustc.edu.cn/debian bookworm-backports InRelease
Hit:4 https://mirrors.ustc.edu.cn/debian-security bookworm-security InRelease
Hit:5 https://mirrors.ustc.edu.cn/armbian bookworm InRelease
Hit:6 https://github.armbian.com/configng stable InRelease
Hit:7 https://packages.sury.org/php bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

8. That's it. After rebooting, I was greeted with a RPi logo on a black page, with some messaging scrolling (trying to attach a photo but failed). It never got to the point to boot the kernel image or systemd booting sequence.

My OS image is: Armbian_25.2.2_Rpi4b_bookworm_current_6.12.15_cinnamon_desktop

Dmesg reveals the following information:

[   13.283052] mipi-dsi 1f00118000.dsi.0: deferred probe pending: mipi-dsi: supplier 2.reg_bridge not ready
[   13.283060] platform 1.panel_disp: deferred probe pending: platform: wait for supplier /axi/pcie@120000/rp1/i2c@88000/reg_display@45

This forum post suggests, that the problem is due to the missing I2C driver "CONFIG_I2C_DESIGNWARE_PLATFORM": https://forums.raspberrypi.com/viewtopic.php?t=375851

And indeed, on the working Raspberry OS image, i find the following files in the directory /lib/modules/.../kernel/drivers/i2c/busses:

- i2c-designware-core.ko.xz

- i2c-designware-platform.ko.xz

These files are not present on the Armbian image, I assume that these are the missing drivers.

Could someone please add the drivers to the build configuration, so that DSI displays will work in the future on RPi5?

https://paste.armbian.com/owihivazuc

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.

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.

Installed Armbian_25.2.3_Rpi4b_bookworm_current_6.12.17-homeassistant_minimal.img

To work around broken packages dependency run:
apt update
dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi4b-current
apt --fix-broken install

At the end I got this:
update-initramfs: Generating /boot/initrd.img-6.12.17-current-bcm2711
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152
ERROR: Unsupported initramfs version (6.12.17-current-bcm2711)

Armbian_25.2.4_Rpi4b_bookworm_current_6.12.22_minimal.img the same.

Any idea anyone what is wrong here?

Thanks
Chris

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

With v25.5.1 up to kernel 6.6.63-current-bcm2711, /dev/i2c-1 is there (activated in /boot/firmware/config.txt with dtparam=i2c_arm=on) and communication with eeprom works fine.

With newer kernel versions, communication works not, /dev/i2c-1 does not exist anymore in this case without changing any configuration, just selected newer kernel using armbian-config

Any ideas why this happens?

What options do I have here ?
 

I buy a new pi, now with pipewire, and more and it has some consistant letdowns on the OS.  When i install across all types ---even kdePlasma the same thing happens!

no audio - still needs a profile or something????

no loopback -- linux kernel header issue

no bt audio -- libspa will work

no screen sharing -- ....i just have a cursor now when i share it...

So, i made an input to fix this..... a terminal input:

echo -e "hdmi_group=1\nhdmi_mode=16\nhdmi_drive=2\nhdmi_force_hotplug=1\nhdmi_force_edid_audio=1\ndisable_fw_kms_setup=0" | sudo tee -a /boot/firmware/config.txt > /dev/null && sudo apt upgrade && sudo apt update && sudo apt install linux-headers-6.12.19-current-bcm2711 linux-headers-current-bcm2712=24.2.1 alsa* pipewire* vulkan-tools mesa-vulkan-drivers xdg-desktop-portal-gnome gnome-remote-desktop libspa-0.2-bluetooth qv4l2 v4l2loopback-dkms obs-plugins obs-studio && snap install chromium && sudo apt install flatpak && flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo && flatpak install flathub com.saivert.pwvucontrol

The outcome was a good start, however, some issues remain.

Mainly i am struggling with pipewire or something?   Likely i need and alsa audio profile for hdmi audio.

Any suggestions as far as enableing audio?

Btw: This is obs running in the term with       sudo MESA_GL_VERSION_OVERRIDE=3.3 obs

it has v4l2loopback working now.

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

```

When I try a 

sudo apt update

it works.

However, when I try a 

sudo apt upgrade

or

sudo apt full-upgrade

they fail,

Here is an example of what I am getting:

sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libraspberrypi0 : Depends: raspberrypi-bootloader but it is not installable or
                            raspi-firmware but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

any help would be appreciated.

Hi,

the title says it all: this is the message I get when booting.

I rebooted several times, to no avail: same message...

The resizing did not seem to occur, as I don't have enough space to install a few packages.

Looking at the armbianmonitor log, it seems that resize2fs is missing... Installing e2fsprogs then rebooting fixes the issue.

It's on trixie Minimal / IOT image.

Best regards.

[Edit] typo: lof->log

having installed Armbian for the first time could someone please confirm or otherwise if WiFi is supposed to be working on the RPI5 internal adapter?

my install does not even see it at all it’s like it does not exist can it be turned on in simple terms for a noob?

One issue is that the vcgencmd is not working. I posted a question about it on the forum and received a reply saying that this would be solved "when possible." However, it is still not resolved. Without this command working, I cannot get the CPU temperature, so I cannot control the cooling fan.

I checked for a newer release today to see if this issue is fixed. I was shocked to see no Bookworm with Cinnamon release available. I'd like to know if it is in the works or has been dropped and will not be offered again.

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

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
 

The SATA hat is not detected:

root@rpi5b:~# lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

I would expect this:
root@raspi:~# lspci
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0000:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

What am I missing.

Thanks for your time.
ChrisO

Silly me. Just found it.

Add those two lines
dtparam=pciex1
dtparam=pciex1_gen=3
to
/boot/firmware/config.txt

and reboot.

Anyone seen these? WiFi is not working.

Any hints for solution other than downgrade to 6.6.31 we already do?

Downgrade instruction:
 

sudo apt install linux-image-current-bcm2712=24.5.1 linux-headers-current-bcm2712=24.5.1

Same symptoms described in https://github.com/aircrack-ng/rtl8812au/issues/1155, they seem to find working patch. Is there any RPi5 maintainer here?

Another related: https://github.com/aircrack-ng/rtl8812au/issues/1169

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 ?

	__overrides__ {
		rotation = <&cam_node>,"rotation:0";
		orientation = <&cam_node>,"orientation:0";
		media-controller = <&csi>,"brcm,media-controller?";
		cam0 = <&i2c_frag>, "target:0=",<&i2c_csi_dsi0>,
		       <&csi_frag>, "target:0=",<&csi0>,
		       <&cam_node>, "VIN-supply:0=",<&cam0_reg>;
	};

Then following use:
 

sudo dtoverlay -v ovaone cam0=on

Overrides proper fields in the overlay fragments on Raspberry Pi OS, but despite overrides being recognized they don't seem to apply and camera driver is starting with wrong I²C attached.

The same problem with with `dtparam` in `config.txt` as it works on Raspberry Pi OS, but not on Armbian (I actually wonder how other `dtparam`s work on Armbian).

I have to patch the `.dts` file prior to compilation with I²C references replaced for `fragment@100` and `fragment@101`. Our `.dts` is just a little stripped version of original for imx219 camera.

Suggestions or explanations welcome.

Attached to it is a 2.5GB Ethernet adapter - this one in particular:  https://www.amazon.ca/dp/B0CD1FDKT1

It lists as having a speed of 2500Mb/s but doesn't in practice:

sudo ethtool enx6c1ff7045a00
Settings for enx6c1ff7045a00:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
                                             2500baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol
        Link detected: yes

However, I am getting less than 1GB data transfer speeds (tested with iPerf3)

Accepted connection from 192.168.4.4, port 53760
[  5] local 192.168.1.10 port 5201 connected to 192.168.4.4 port 53766
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.01   sec  63.6 MBytes   529 Mbits/sec
[  5]   1.01-2.00   sec  63.5 MBytes   537 Mbits/sec
[  5]   2.00-3.01   sec  64.2 MBytes   536 Mbits/sec
[  5]   3.01-4.01   sec  63.6 MBytes   531 Mbits/sec
[  5]   4.01-5.02   sec  63.6 MBytes   532 Mbits/sec
[  5]   5.02-6.01   sec  63.0 MBytes   529 Mbits/sec
[  5]   6.01-7.01   sec  62.1 MBytes   521 Mbits/sec
[  5]   7.01-8.01   sec  63.8 MBytes   535 Mbits/sec
[  5]   8.01-9.01   sec  62.5 MBytes   527 Mbits/sec
[  5]   9.01-10.01  sec  63.8 MBytes   536 Mbits/sec
[  5]  10.01-10.01  sec   128 KBytes   466 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.01  sec   634 MBytes   531 Mbits/sec                  receiver

(however, with another computer I get 2.5GB speed with the same iPerf3 server as was used for the above tests).

The odd thing is that I believe last week I was getting much higher transfer speeds.  I have done sudo updates, upgrades, dist-upgrades and OMV updates since then however.

Suggestions on where to look, what to do to resolve would be appreciated. 

Edit: I tried replacing  /etc/udev/rules.d/50-usb-realtek-net.rules  with the contents of https://raw.githubusercontent.com/wget/realtek-r8152-linux/master/50-usb-realtek-net.rules and rebooting - but that did not help

Edit 2: well that took me all day.  I use OPNSense and had turned on Intrusion Detection with many rules.  Seems as if it really bogged down the network traffic.  I disabled it for testing and then suddenly I could get the expected though-put.

Server listening on 5201 (test #20)
-----------------------------------------------------------
Accepted connection from 192.168.4.4, port 33826
[  5] local 192.168.1.10 port 5201 connected to 192.168.4.4 port 33832
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.01   sec   279 MBytes  2.32 Gbits/sec
[  5]   1.01-2.00   sec   276 MBytes  2.33 Gbits/sec
[  5]   2.00-3.01   sec   280 MBytes  2.33 Gbits/sec
[  5]   3.01-4.01   sec   279 MBytes  2.33 Gbits/sec
[  5]   4.01-5.01   sec   275 MBytes  2.33 Gbits/sec
[  5]   5.01-6.00   sec   276 MBytes  2.33 Gbits/sec
[  5]   6.00-7.01   sec   280 MBytes  2.33 Gbits/sec
[  5]   7.01-8.00   sec   275 MBytes  2.33 Gbits/sec
[  5]   8.00-9.01   sec   280 MBytes  2.33 Gbits/sec
[  5]   9.01-10.00  sec   276 MBytes  2.33 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.00  sec  2.71 GBytes  2.33 Gbits/sec                  receiver

Hope this will be of help to others.

Hi,

New user here - I Just download the current version of Armbian today with the hopes of using it on my Raspberry Pi 5B.

After unzipping it, I created an image on a usb stick using Raspberry Pi Imager - use custom.

However, it is not booting.

It only shows a few lines on the screen, the last being:

Begin: Running /scripts/local-block ... done.

(screen shot below)

What am I doing wrong?

Hello all,

I am using Armbian (Debian Bookworm), Gnome with Wayland. everything is working just fine. The problem is with sharing or presenting screen with OBS-Studio, Jitsi, Google meeting or other. 

If I share a tab in Chromium/Firefox with Jtisi or Google meeting, that's work, but I can't share a window or full screen. I am wondering what is the main cost of that.

This when I share full screen, it doesn't work properly, it shows like this:

This when I share tab, it's working just fine.

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 ?

My system has `linux-image-current-bcm2712` package installed with version 24.2.5 which I believe is the current Arbian release.

I installed `linux-headers-current-bcm2712`, but this package has version 24.2.1. So I end up with system running `6.6.23-current-bcm2712` with headers for `6.6.18-current-bcm2712` and I can't build extra drivers in result.

Any hints?

I love technical forums that don't understand markdown, it makes life so much easier...

Everything went smoothly, but straight-away, I see that dmesg is filled with this error:

brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52

I'm noticing some inconsistencies on the network, and I'm not sure if this is behind it.  I tried installing the firmware-brcm80211, but it didn't help -- in fact, I think it might have made it worse.

I've looked all over, but I cannot see any useful information regarding this.  It has no usb devices attached, not using and gpio pins or anything fancy.  It is just a node on the network that is presenting information on a television screen in our shop.

It looks like the driver is not a good match for the hardware (that's my guess, anyway).  In the past, I've seen errors like this fixed with the firmware I mentioned above.  No such luck this time.  Any way I can fix this?

Thanks.

Raspberry OS has weird quirks that automate the process of setting up the system for using cameras, but I'm looking for clean way to set up the device tree to use the imx219 camera.

Anyone knows what overlays to enable to get this to work on Armbian?

Additionally where's the location of device tree overlays sources for Raspberry Pi 5 on Armbian?

just wanted to know how come this was not included in this release and could someone provide the details to download the most stable version of Chrominum for this please ?

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

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.

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

Already configured with "nmcli c add type ethernet ifname enx00e04c68080d con-name HiQSDR autoconnect yes save yes ip4 192.168.2.196/24"
 

After boot, nothing in lsusb for it and dmesg -T does not show it.

Bus 001 Device 014: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter

Things tried:-

root@rpi4b:~# cat /etc/os-release  
PRETTY_NAME="Armbian 24.2.1 jammy"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
PRIVACY_POLICY_URL="https://www.armbian.com"
UBUNTU_CODENAME=jammy
ARMBIAN_PRETTY_NAME="Armbian 24.2.1 jammy"

root@rpi4b:~# cat /etc/udev/rules.d/40-modeswitch.rules  
# Copyright (C) 2009-2014 Stephan Raue (stephan@openelec.tv)

ACTION!="add|change", GOTO="end_modeswitch"
KERNEL!="sr[0-9]*", GOTO="end_modeswitch"
SUBSYSTEM!="block", GOTO="end_modeswitch"

root@rpi4b:~# vcgencmd bootloader_config
[all]
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0

 

# Realtek RTL8152 chipset USB lan NIC
#   initial cdrom mode 0bda:8152, lan mode 0bda:8153
ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="8152", RUN+="/tmp/setupusblanadapter.sh"

LABEL="end_modeswitch"

https://forums.raspberrypi.com/viewtopic.php?t=336517 doesn't help  ---  didn't try installing the suggested firmware

root@rpi4b:~#  raspi-config nonint do_boot_rom E1
/usr/bin/raspi-config: 1506: [: Illegal number:  
BOOTLOADER: up to date
  CURRENT: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
   LATEST: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
  RELEASE: stable (/lib/firmware/raspberrypi/bootloader-2711/stable)
           Use raspi-config to change the release.

 VL805_FW: Dedicated VL805 EEPROM
    VL805: up to date
  CURRENT: 000138c0
   LATEST: 000138c0

 

After installation, I performed an upgrade/update. I have not yet installed any additional software.

Issues;

1) when cinnamon desktop starts there is message displayed: Your system is currently running without video hardware acceleration 

2) vgencmd always gives an error:  VCHI initialization failed, no matter if I run it with sudo or not, or with which parameter(s) I run it.

armbian monitor -u gave link https://paste.armbian.com/lurunopoyo

This version of Armbian is really usefull because it is the only one that can run a version of ROS natively on a RPi5, but I need the headers to build drivers

Thanks

I've read about "Hardware" option in armbian-config, but it's not showing up in the menu. I've also read that it's a matter of adding a device tree overlay. Does that apply for RPI4? The folder structure in /boot seems different from what documentation and several threads describe for other boards. 

What would be the steps for activating i2c bus on RPI4?

Error while creating U-Boot loader image with mkimage
Error: no u-boot package found, exiting

I've run a full update / upgrade and installed armbian-config with no change.

What's missing here?

$ sudo apt update
$ sudo apt upgrade
$ sudo apt install podman
$ podman run --rm docker.io/library/hello-world
Error: command required for rootless mode with multiple IDs: exec: "newuidmap": executable file not found in $PATH

Podman runs fine with sudo, so for now I can use that as a workaround, but it would be nice to run rootless containers for dev environments.

There is a related issue on the official podman repo, but the solutions there don't seem to apply to armbian. https://github.com/containers/podman/issues/9271

sudo armbian-config does not get it

overlays=spi-spidev
param_spidev_spi_bus=0

Unfortunately it does not work properly, the system does not want to boot with it.... 

The name of the image says that it was generated for Raspi4, but -as I said- the homepage says that this image would also be compatible for the other Raspberry systems mentioned there.

Can anyone tell me what the reason could be, because I would love to use this ingenious image for the Raspi 3.

Best regards from Berlin

Z. Matthias

As I have often said, I am very satisfied with this LINUX implementation on the RASPI PI4 board.

In the meantime, I noticed one small thing and that was somehow related to the 4GB version of my RASPI. I often had to record a KERNEL crash here; this did not happen under the 8GB version until now.

But now to my actual question:
How can I activate the CAMERA port under this Linux version so that I can connect a camera there?

Best regards

Z. Matthias
 

I have installed the image "Armbian 23.02.0-trunk.0176 Lunar with bleeding edge Linux 6.1.6-bcm2711" on my two Raspi 4 systems.

One system runs via cable and the other via WLAN. At the beginning there were some problems with the IPv6 - kernel, if "apt update" was executed.

I got this problem under control with "disable ipv6".... Since then, both systems run flawlessly & without problems.

With the implementation of GPIO you should fall back on an existing GPIO - version, which works in any case also under this image; also for 64bit.

One small thing I would like to know very much, because on the system with the cable the WaveShare PoE - HAT is installed and I would like to monitor via software very much the FAN.

Unfortunately, this does not work because the software does not see "I2C". In the Config - File, however, you see this as "enable" -

What can I do here? Does anyone have an idea how I can enablen the I2C so that this works?

Best regards from Germany.....

Z. Matthias

I've faced  the issue:
Armbian_22.08.7 official image (Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img)
failed to boot on RPi3B plus.
The same image boots fine on RPi 4B

Could not get serial console output (output is empty)

Older official image Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img boots on Rpi3B plus just fine.

As I've found out the reason is incorrect boot partition type set for the image.

Armbian_22.08.1 (boots fine) boot partition type is "c" (W95 FAT32 LBA)
Armbian_22.08.7 (doesn't boot) boot partition type is "ef" (EFI)

After manually changing boot partiton type to "c" (W95 FAT32 LBA)
for the image Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img
it begins to boot
Please check fdisk output
=====================

"Good" image:

$ fdisk -l Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img
Disk Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img: 3 GiB, 3196059648 bytes, 6242304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x79597c7b

Device                                           Boot  Start     End Sectors  Size Id Type
Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img1        8192  532479  524288  256M  c W95 FAT32 (LBA)
Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img2      532480 6242303 5709824  2,7G 83 Linux

=====================

"Bad" image:

$ fdisk -l Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img
Disk Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img: 2,5 GiB, 2680160256 bytes, 5234688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1d7b3f1b

Device                                                   Boot  Start     End Sectors  Size Id Type
Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img1        8192  532479  524288  256M ef EFI (FAT-12/16/32)
Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img2      532480 5234687 4702208  2,2G 83 Linux

=====================

The same story is for manual build from the repo (Armbian 22.08.11)
Image build is fine.
Image doesn't boot on RPi3Bplus
Boots fine on RPi4
Manual compile command is:

#!/bin/bash

BOARD_NAME_PARAM="rpi4b"
LINUX_DISTRO_PARAM="jammy"

ARMBIAN_BUILD_OPTIONS="\
BOARD=$BOARD_NAME_PARAM \
BRANCH=current \
FULL_DESKTOP=no \
BUILD_DESKTOP=no \
BUILD_MINIMAL=yes \
INSTALL_HEADERS=no \
KERNEL_ONLY=no \
KERNEL_CONFIGURE=no \
RELEASE=$LINUX_DISTRO_PARAM \
COMPRESS_OUTPUTIMAGE=\"sha,img,xz\" \
ARMBIAN_CACHE_ROOTFS_PATH=/mnt/armbian-cache/rootfs \
ARMBIAN_CACHE_TOOLCHAIN_PATH=/mnt/armbian-cache/toolchain \
"
sudo ./compile.sh $ARMBIAN_BUILD_OPTIONS

---------------------------

As example - please check out notice from
https://github.com/pftf/RPi3
Create an SD card (or USB drive if you plan to use USB Boot) in MBR mode with a single partition of type 0x0c (FAT32 LBA) or 0x0e (FAT16 LBA). Then format this partition to FAT32.
Note: Do not try to use GPT for the partition scheme or 0xef (EFI System Partition) for the type, as these are unsupported by the CPU-embedded bootloader.

For sure I have problems with newer Armbian_22.11.0-trunk_Rpi4b_jammy_current_5.15.73_xfce_desktop.img.xz and  Armbian_22.11.0-trunk_Rpi4b_jammy_edge_5.19.15_xfce_desktop.img.xz

So where can I download older versions?

Raspberry PI400

Viewsonic VP930 (1280x1024)

I checked the sha-sum and flashed 2 times a Patriot SXDC-128GB-card.

When I boot the PI400 the monitors LED changes from green (power on) to yellow (standbye) for half an hour, when I start the PI400. It looks like there is a problem with this old monitor which supports 1280x1024 only. Don't know, if the boot routine checks the monitor, but the green LED can stay for 2sec, sometimes for 30sec.

BTW Xubuntu 22.04 with an SSD works fine with the same hardware.

Is there an armbian software distribution for the "Broadcom BCM2711" ? (rasberrypi 4)

I would like to build an image for the Rasperry Pi 1, 2 and Zero.

I could not found a download for a RPi on armbian.com. Then I saw that `rpi` is disabled in `/lib/configuration.sh`. Even when enabling it, I get an error during build, saying "[ error ] Building failed, check configuration" .

I wonder why the Raspberry Pi is not supported. Is it due to its closed hardware?

Thanks!