ChrisO

I started from scratch. Installed Armbian_25.2.2_Rpi4b_bookworm_current_6.12.15_minimal.img Having in mind what @eselarm suggested as culprit, I put raspi-firmware on hold root@rpi5b:~# apt-mark hold raspi-firmware then dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi4b-current apt --fix-broken install apt install armbian-bsp-cli-rpi4b-current everything OK apt upgrade everything OK Reboot root@rpi5b:~# uname -a Linux rpi5b 6.12.31-current-bcm2711 #1 SMP PREEMPT Wed Jun 4 14:00:53 UTC 2025 aarch64 GNU/Linux Tried the same with raspi-firmware unhold and got this . . Setting up raspi-firmware (1:1.20250430-1) ... ERROR: Unsupported kernel version (6.12.15-current-bcm2711) Setting up libraspberrypi0:arm64 (1:2+git20231018~131943+3c97f76-1) ... Setting up libraspberrypi-bin (1:2+git20231018~131943+3c97f76-1) ... Processing triggers for libc-bin (2.36-9+deb12u9) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.12.15-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.15-current-bcm2711) I then did apt-mark hold raspi-firmware apt purge raspi-firmware and apt upgrade went through but the system is not in a good shape. root@rpi5b:~# uname -a Linux rpi5b 6.12.15-current-bcm2711 #1 SMP PREEMPT Wed Feb 19 13:49:50 UTC 2025 aarch64 GNU/Linux The /boot/firmware/initrd.img was not updated. Then I installed Armbian_25.2.4_Rpi4b_bookworm_current_6.12.22_minimal.img First thing after boot: root@rpi4b:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.12.22-current-bcm2711 ERROR: Unsupported initramfs version (6.12.22-current-bcm2711) The same with Armbian_25.5.1_Rpi4b_bookworm_current_6.12.28_minimal.img I don't have anymore a clean 25.2.3 but the homeassistant_minimal.img one has the same problem. No idea how to fix it. raspi-firmware has status optional and the 25.2.2 works OK without it, I think I will go this way hoping somebody with better skills then me will fix it one day. Regards, Chris

Hi 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

Hi I installed https://dl.armbian.com/rock-5c/Bookworm_current_minimal-homeassistant, configured it to my liking (OS on a mirrored ZFS pool) to discover there is no WiFi, no Bluetooth. It's now kernel 6.12.17-current-rockchip64. Anybody managed to get WiFi and BT working with this kernel? Thanks, Chris

I also downgraded to 6.6.63 and everything is working OK.

Hi Installed Armbian_25.2.3_Odroidhc4_bookworm_current_6.12.17-homeassistant_minimal.img an a HC4 and noticed that USB doesn't work. lshw shows: *-usbhost:0 product: xHCI Host Controller vendor: Linux 6.12.17-current-meson64 xhci-hcd physical id: 1 bus info: usb@1 logical name: usb1 version: 6.12 capabilities: usb-2.00 configuration: driver=hub slots=2 speed=480Mbit/s *-usbhost:1 product: xHCI Host Controller vendor: Linux 6.12.17-current-meson64 xhci-hcd physical id: 2 bus info: usb@2 logical name: usb2 version: 6.12 capabilities: usb-3.00 configuration: driver=hub slots=1 speed=5000Mbit/s Nothing in syslog when I connect anything to USB port, just once I saw this: kernel: [ 2113.840333] usb usb1-port2: connect-debounce failed Any idea what could be wrong? Thanks Chris

I wanted to try Armbian on a Raspberry Pi-5 with a Radxa penta SATA hat. Installed: Armbian_community_25.2.0-trunk.86_Rpi5b_bookworm_current_6.6.63_minimal.img 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.

I've just tried Armbian_24.11.1_Rock-5c_bookworm_edge_6.11.7_minimal.img wlan works. No ZFS, however. Building zfs-dkms fails, from /var/lib/dkms/zfs/2.2.5/build/make.log: 93 | #error "Unsupported kernel" According to https://github.com/openzfs/zfs/releases: zfs-2.2.5 is compatible with 4.18 - 6.9 kernels zfs-2.2.6 is compatible with 4.18 - 6.10 kernels zfs-2.3.0 would be compatible with Linux kernels 4.18 - 6.11 Armbian_24.8.4_Rock-5c_bookworm_vendor_6.1.75_minimal.img - ZFS OK, wlan after 'apt upgrade' not anymore. But $ /sudo dkms install aic8800-usb/3.0+git20240327.3561b08f-2 does the trick. ------- Sign command: /lib/modules/6.1.75-vendor-rk35xx/build/scripts/sign-file Binary /lib/modules/6.1.75-vendor-rk35xx/build/scripts/sign-file not found, modules won't be signed Creating symlink /var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/source -> /usr/src/aic8800-usb-3.0+git20240327.3561b08f-2 Building module: Cleaning build area...(bad exit status: 2) make -j8 KERNELRELEASE=6.1.75-vendor-rk35xx -C /lib/modules/6.1.75-vendor-rk35xx/build M=/var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/build/USB/driver_fw/drivers/aic8800 && make -C /lib/modules/6.1.75-vendor-rk35xx/build M=/var/lib/dkms/aic8800-usb/3.0+git20240327.3561b08f-2/build/USB/driver_fw/drivers/aic_btusb....... .... depmod... -------- root@rock-5c:~# iw phy0 info Wiphy phy0 wiphy index: 0 max # scan SSIDs: 3 max scan IEs length: 200 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) .... Regards, Chris

It looks like there is a linux-headers mismatch in those two images: Armbian_24.11.1_Odroidhc4_bookworm_current_6.6.60_minimal.img Armbian_24.11.1_Odroidhc4_noble_current_6.6.60-kisak.img Installed those linux-headers: apt install linux-headers-current-meson64 I tried then to install ZFS module, and it failed: Setting up zfs-dkms (2.2.5-1~bpo12+1) ... Loading new zfs-2.2.5 DKMS files... Building for 6.6.60-current-meson64 Module build for kernel 6.6.60-current-meson64 was skipped since the kernel headers for this kernel do not seem to be installed. root@odroidhc4:~# dpkg -l | grep linux-headers ii linux-headers-current-meson64 24.8.2 arm64 Armbian Linux current headers 6.6.47-current-meson64 The Armbian_24.8.1_Odroidhc4_bookworm_current_6.6.47_minimal.img is OK. Finally I see both SSDs and ZFS works! 🙂 Regards, Chris

Sorry, it will be quite long 🙂 I have three HC4 devices: odroid1: Linux odroid1 5.10.57-meson64 #21.05.8 SMP PREEMPT Mon Aug 9 12:44:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ata-Samsung_SSD_870_QVO_1TB ata-Samsung_SSD_870_QVO_1TB odroid2: Linux odroid2 5.19.17-meson64 #22.08.7 SMP PREEMPT Thu Oct 27 18:34:08 CEST 2022 aarch64 aarch64 aarch64 GNU/Linux ata-Samsung_SSD_870_QVO_1TB ata-Samsung_SSD_870_QVO_1TB They run the kernel which recognized both discs AND there was ZFS support when I installed them. odroid3, currently used for some experimenting: Linux odroid3 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux odroid3 recognises those disks: ata-Samsung_SSD_840_EVO_120GB_S1D5NEAD710633R ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R I replaced the ata-Samsung_SSD_840_EVO_120GB_S1D5NEAD710633R by another Samsung SSD_860_EVO_250GB It is not recognized, and in the /var/log/kern.log I see this: odroid3 kernel: [ 2.692110] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 27 odroid3 kernel: [ 2.692124] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 27 odroid3 kernel: [ 3.005134] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.478833] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Disconnected the ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R and rebooted NO ssd! /var/log/kern.log: odroid3 kernel: [ 2.901128] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.213129] ata2: SATA link down (SStatus 0 SControl 300) Tried both SATA slots, same results. Tried another Samsung SSD_860_EVO_250GB, same results, no SSD. The same "SATA link down" message. I bought a Crucial 1TB just to change manufacturer: ata-CT1000MX500SSD1_2249E68F3955 Works in both SATA slots. Rebooted again with ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R and ata-CT1000MX500SSD1_2249E68F3955 The last one in not there, the same messages in /var/log/kern.log. Two days later I rebooted it to try libata.force=noncqtrim kernel parameter and both disks are there. Removed libata.force=noncqtrim from armbianEnv.txt rebooted again, both disks are there. Then shutdown, power off/on and boot, no CT1000MX500SSD1. I tried the SD-card from odroid3 in the odroid2 and there both Samsung_SSD_870_QVO_1TB are there. Rebooted few times, just in case 😉 they were always there. Then disconnecte those two disks and connected the CT1000MX500SSD one: no disk after reboot. Put the SD-card in odroid1, only one disk, Samsung_SSD_870_QVO_1TB, is there. Replaced one of Samsung_SSD_870_QVO_1TB by CT1000MX500SSD, both are not there: kern.log: odroid3 kernel: [ 2.940933] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.252903] ata2: SATA link down (SStatus 0 SControl 300) I like the HC4 (when it works 😉 so I ordered another one hoping it will not have any problems. Got it today (I must be one of the best HK's custommers: H3, H3+, 4 x HC4 🙂 booted with a EVO 860 250GB SSD: uname -a Linux odroid4 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux No SSD there. Re-plug it (I know the riscs) and lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232.9G 0 disk Rebooted. lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232.9G 0 disk Rebooted again and the SSD is there. Aha, rebooted, not powered off/on. init 0 remove power 10 seconds connect power The SSD is there. init 0 Connected the CT1000MX500SSD, boot. lsblk -> no SSD. Somehow it doesn't make any sense, I don't see any regularity in all this. Did again hotplug ~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931.5G 0 disk Some time ago I already reported the problem with SSD's not being recognized. And the strange thing is, some of the events are quite random. The SSD is there, than not there. Now I would say: HC4 and kernels newer than 5.19.17-meson64 don't want to cooperate correctly. Who is the culprit? I don't know, don't have the necessary skills to debug it. However, I would love to provide all infos needed which HK needs to analyze the problem. Screenshots, etc. BTW, rebooted odroid4 again, no SSD. Regards, Chris

Haven't got any help in HardKernel Forum: https://forum.odroid.com/viewtopic.php?f=205&t=45941&p=366587#p366587 As I said, I just want to find out what is the cause of the problem, the few $ for the now useless hc4 is not the problem. I don't have the skills to do necessary diffs on some kernel versions to find out what and when originated the problem. If anybody feels like challenged, let me/us know 🙂

Thanks! 👍

The zfs-dkms included in Armbian_22.11.1_Odroidhc4_jammy in version 2.1.4 is to old for 5.19.17 kernel. It should be 2.1.6 like in Armbian_22.08.7. Loading new zfs-2.1.4 DKMS files... Building for 5.19.17-meson64 Building initial module for 5.19.17-meson64 configure: error: *** None of the expected "blk_queue_discard" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 http://paste.debian.net/1267188/

As the original thread, which was closed by moderator for obvious reason, did attract attention of few peoples having the same problem as me, it would be a waste not to follow up on this, I think. Let me sum up: I have two HC4, one bought in 8.2021 and other one 11.2022, both have two SSDs each. The older one after a kernel upgrade didn't see a second disk any more. I've just tried few kernels I could find with the following results: OK: Linux odroidhc4 5.12.10-meson64 #21.05.4 SMP PREEMPT Wed Jun 16 08:19:35 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux OK: Linux odroidhc4 5.13.12-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:35:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Not OK:Linux odroidhc4 5.15.4-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:46:10 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Couldn't find any kernel between 5.13.12 and 5.15.4, so it's not clear which is exact the version where the problem started. Here is what I found in /var/log/syslog: Nov 22 14:40:46 odroidhc4 kernel: [ 2.355049] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.355060] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.358363] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.564017] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.830521] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830799] ata1.00: FORCE: horkage modified (noncq) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830854] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.830860] ata1.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.830865] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (not used) Nov 22 14:40:46 odroidhc4 kernel: [ 2.832778] ata1.00: Features: Trust Dev-Sleep Nov 22 14:40:46 odroidhc4 kernel: [ 2.833128] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.835140] ata1.00: configured for UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835408] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 2B6Q PQ: 0 ANSI: 5 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835890] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.836066] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Nov 22 14:40:46 odroidhc4 kernel: [ 2.836102] sd 0:0:0:0: [sda] Write Protect is off Nov 22 14:40:46 odroidhc4 kernel: [ 2.836108] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 22 14:40:46 odroidhc4 kernel: [ 2.836159] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 22 14:40:46 odroidhc4 kernel: [ 2.850916] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.872432] sda: sda1 sda9 Nov 22 14:40:46 odroidhc4 kernel: [ 2.872842] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.886688] sd 0:0:0:0: [sda] Attached SCSI disk Nov 22 14:40:46 odroidhc4 kernel: [ 3.148738] ata2: SATA link down (SStatus 0 SControl 300) The newer HC4 doesn't show this problem which leads me to the conclusion: their hardware (firmware?) must differ. Asked about it on the HardKernel Forum, didn't get a clear answer (yet?). I don't know how to proceed i.e. where to look for further help. Any idea anyone? I'm to old for an advanced GIT class 😉 Thanks for your time. Chris