Search the Community

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

Running a home NAS using Armbian/meson bullseye and openmediavault. After apt upgrade today, my SATA disks are no longer spinning up or showing up in "fdisk -l". The system is on an SD card and still boots fine. This is what I'm seeing: [ 2.270633] scsi host0: ahci [ 2.272861] scsi host1: ahci [ 2.273074] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 27 [ 2.273090] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 27 ... [ 2.584971] ata1: SATA link down (SStatus 0 SControl 300) [ 2.896948] ata2: SATA link down (SStatus 0 SControl 300) Both disks work fine in another system. I have tried to upgrade the firmware, no change. Moved to nightly and booted into linux-image-edge-meson64 (6.1.0), same issue. Next, I tried booting into kernel 5.19.17-meson64, but the problem persists. I wonder what has happened here? Could it be a userspace problem (since I didn't downgrade userspace here, only the kernel)? Any hints very much welcome!

I'm trying to complete the installation of Armbian onto the HC4 (HC4-P if that changes anything). With a fresh SD card I run sudo dd if=Armbian_22.11.1_Odroidhc4_bullseye_current_5.19.17.img of=/dev/sdb status=progress plug in the card to the board, plug in the ethernet cable, hold down the boot switch, and plug it into power. It all seems to run correctly: I can SSH into the board and I complete the initial steps to set-up the installation (root pass, default shell, username, real name, and locale). However it does not seem as I can access the SPI FLASH device. Running the following commands from the HC4 page do not work as there are no mtd devices. root@odroidhc4:~# ls -ltr /dev/mtd* ls: cannot access '/dev/mtd*': No such file or directory Here's a paste of the files available under /dev: https://paste.tildeverse.org/?aa94ecb514ce9e50#E5qD2kbTFiQzaHRrgnBLfMw8PMfspfVsCFrxhPATYDyi

Hello, Bluetooth stopped working in kernel 5.19.17-meson64 #22.11.1 root@nextcloudpi:~# hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:14 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:3 errors:2 root@nextcloudpi:~# hcitool dev Devices: root@nextcloudpi:~# dmesg | grep Bluetooth [ 10.005353] Bluetooth: Core ver 2.22 [ 10.010561] Bluetooth: HCI device and connection manager initialized [ 10.010582] Bluetooth: HCI socket layer initialized [ 10.010589] Bluetooth: L2CAP socket layer initialized [ 10.010621] Bluetooth: SCO socket layer initialized [ 10.273422] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [ 11.647454] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.647474] Bluetooth: BNEP filters: protocol multicast [ 11.647489] Bluetooth: BNEP socket layer initialized [ 15.326913] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [ 15.327136] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [ 15.327149] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [ 15.327153] Bluetooth: hci0: HCI Set Event Filter command not supported. [ 17.341929] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42900.593231] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42900.922097] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42900.923021] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42900.923040] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42900.923044] Bluetooth: hci0: HCI Set Event Filter command not supported. [42902.934227] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42905.073243] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42905.661928] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42905.662099] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42905.662108] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42905.662112] Bluetooth: hci0: HCI Set Event Filter command not supported.

Hi, i have armbian bullseye (headless) installed on my odroid-hc4. petitboot is disabled. The boot-partition lies on a sd-card while the root-partion is on a ssd. this configuration worked fine. After upgrading to armbian bullseye 22.11 the boot process stucks in initramfs cause the root file-system is not found anymore (ALERT! UUID=xxx does not exist. Dropping to a shell. The sd-card with the boot partition as well as the ssd with the root-partition can be mounted on another PC and seem to be flawless. the UUID shown in fstab and initramfs are identical. In initramfs ls /dev/sd* shows no devices while ls /dev/mm* shows the sdcard (mmcblk01...). I don't really know how the boot process works on an arm-system. What steps can I do to narrow down the problem. Thanks in advance. Hardware: odroid-hc4, samsung 870 EVO 1TB (sda), WD60EFZX (sdb), BS: armbian-bullseye with OMV 6.0.46-5 fs: ext4 no raid

Hi, I'm trying to use ZFS but the kernel I'd like to use doesn't support loadable modules. The version is 22.08.4 at the moment (5.10.147) Can I use zfs-dkms on linux-image-current-meson64? And I'm curious why loadable modules are not supported by default for linux-image-current-meson64, is it same with every model? or probably Odroid-HC4 is one of the models in which loadable modules are not build by default? System diagnosis information: https://paste.armbian.com/ezisijedob Thank you, Gunwoo Gim

Some time ago a I was desperate to have ZFS on an Odroid HC4 and after some trying found Armbian 21.05.8 Buster with Linux 5.10.57-meson64 on which I could compile ZFS module. Then I moved everything from the SD card to filesystems in a ZFS pool. It boots from SD card, though. And has been working fine for several months. Recently I bought another HC4 and took the current Armbian image for it: Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 Everything works fine. Tried this image on the older HC4 and it doesn't see the second SSD. In the syslog I found this message: ata1: SATA link down (SStatus 0 SControl 300) Is it a firmware problem? Googling hasn't help. Any idea anyone? Thanks for your time. Chris BTW Does anybody know how to disable the "Clear Screen" after the "Starting kernel" message? I would like to see what u-boot has to tell me, especially if I have some problems.