BPI M1+ SATA Support

[comp2000]

Good morning

I have a BPI M1 and M1+ currently running an image from https://banana-pi.org/. Everything works, except it's Ubuntu 16.04. Since yesterday, I've been testing the Armbian images, which are great and up-to-date, but none of them recognize the SATA connection on my SSD.

`

fdisk -l

` shows no SATA SSD.

Since I absolutely need this connection, I'm stuck. What am I doing wrong, or where do I need to activate the SATA connection?

The SATA connection is what makes the BPI M1+ unique.

With Ubuntu 16.04, the SATA connection is recognized with both SSD and HDD on the BPI M3.

Can someone please help me? I'm completely lost.

Regards, Henry

[Igor]

Feature regressions are sadly something that happens all the time. There are many variants out there and (part of) Armbian OS is different for every board ... First resolve confusion - do you have M1 (we call it just bananapi) or M3. You mention M3 in the text, while title says M1+. Those are totally different boards.

 

Proceed from older images and find out when this feature stopped working:
https://fi.mirror.armbian.de/archive/
https://fi.mirror.armbian.de/oldarchive/

[comp2000]

For your information, I have a

BPI M1

BPI M1+

BPI M3
All three are currently running Ubuntu 16.04, where SATA works, but it's a very old version. All tests with Armbian were performed using the BPI M1+, although SATA did not work.

[comp2000]

BPI M1+ tested with:

Armbian_23.8.1_Bananapim1plus_jammy

Armbian_24.11.1_Bananapi_noble

Armbian_26.2.0-trunk.342_Bananapi_noble
and the SATA interface doesn't work on any of the three.

Does nobody use a BPI M1+ with an Armbian image where the SATA interface works?

[comp2000]

fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mmcblk0: 14.84 GiB, 15931539456 bytes, 31116288 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: 0x4c58faaa

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1       8192 30801920 30793729 14.7G 83 Linux

Disk /dev/zram0: 483.1 MiB, 506564608 bytes, 123673 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Out of desperation, I plugged in an SSD via USB adapter, and it is recognized as:

/dev/sda:

Detected

One might think the SATA connection is defective, but when I boot with the Ubuntu 16.04 image without changing anything, the SATA SSD is recognized! So the SATA connection on the BPI M1+ works, and so does the SSD. It's definitely the Armbian image that's the problem, but where exactly is it?

[Igor]

1 hour ago, comp2000 said:

but where exactly is it?

Probably, my guess, issue with a boot loader - fail to / disabled by mistake power SATA port? We don't have anyone actively maintaining this kind of (10+years) hardware anymore. Support is "community / upstream" maintained "as is". But this forum / community can provide some assistance to fix this. I gave a tip - where I think is the problem.

Not working feature on particular hardware is not Armbian problem. This is custom hardware world and our work is tooling https://github.com/armbian/build and best effort hardware maintenance on this principle https://docs.armbian.com/User-Guide_Board-Support-Rules/ If we try to fix everything, everyone would be long burned out ...