@CyberHaZard Thanks for the feedback. Yes, the internal eMMC is untouched. You can mount these Android partitions in your file system if you want to access them. Thank you for the offer. I already have access to the Android OS, but tests are apriciated Usb3 is not fully implemented yet . It might just be a Linux configuration issue. I still need to investigate. Maybe it's also acting as a device. there could be a switch via GPIO. The front LED display uses the HT1628 chip. There's a driver available at https://github.com/venkatesh4009/TM1628_LED_Driver It's worth a try.

I believe you have managed to overcome the majour Espressobin culprits, i.e. frequency scaling resulting in instability. It was a deadlock for me in the kernel choice and uboot frequency build version. At some moment I was compelled flashing uboot with frequency downgraded to 1GHz and 800 MHz in order to get stable setup for production. Good catch! Your use of Arch Linux is also interesting. Which flavor have you installed ? Is it from https://archlinuxarm.org/platforms/armv8/marvell/espressobin ? I routinely out of curiosity try alternative builds for testing and comparison when making new setups despite that Armbian remains a preferred one so far with general score of usability.

Hey, I am really happy there is someone else with M1S - just got it today in the mail and after first boot received notification that ubuntu 20.04 server is no longer supported (shocker!). It would be nice to be able to run later kernel (you've mentioned 6.12) on the machine. I was not able to follow your steps to get it working, unfortunately. I don't care for desktop performance at all. Would it be possible to get the image of ubuntu noble server? Or is there some place with idiot-proof step-by-step guide for noobs? Thanks in advance!

@johlnx I have tried your recently built image from here Github Page and it booted fine. Boots fine. Wifi and Ethernet works. USB port only one is working. The blue one and I assume that that is wired for USB3. So I find this strange. I have still not touched the original eMMC. Here is the output from blkid. Note I am using a 16GB micro SD to boot and that is at /dev/mmcblk0 cyberhazard@x88pro:~$ blkid /dev/mmcblk0p1: LABEL="armbi_boot" UUID="d312472c-e5d3-4ef4-9a72-4d38e367fa7c" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="bootfs" PARTUUID="c7a9a714-e024-406b-a111-dbf5782bfd06" /dev/mmcblk0p2: LABEL="armbi_root" UUID="ead9d55f-9f5d-4db3-84af-1b4c0807169c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6acc9d55-8827-45f0-bb5f-3b864952abfa" /dev/mmcblk1p11: UUID="da8b6f4f-89cc-4ed5-8bd6-aa0ef3b881e8" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="metadata" PARTUUID="b85e0000-0000-4752-8000-0c2400004469" /dev/mmcblk1p10: UUID="790cebf2-3e31-464d-bf22-00bea1cb7eb6" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="cache" PARTUUID="cb490000-0000-4c68-8000-157e000041fe" /dev/zram1: LABEL="log2ram" UUID="d0a97d5c-6f8c-41e3-863b-f7fdf23d9288" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram0: UUID="334781b1-ee36-425e-819a-6796d4f4f36a" TYPE="swap" /dev/mmcblk1p3: PARTLABEL="trust" PARTUUID="71760000-0000-4537-8000-2f8f00000c08" /dev/mmcblk1p13: PARTLABEL="super" PARTUUID="94030000-0000-4f58-8000-234700004169" /dev/mmcblk1p1: PARTLABEL="security" PARTUUID="e9430000-0000-4579-8000-4da800000c18" /dev/mmcblk1p8: PARTLABEL="recovery" PARTUUID="8a190000-0000-457d-8000-74a10000796b" /dev/mmcblk1p6: PARTLABEL="vbmeta" PARTUUID="e02c0000-0000-496d-8000-062400006ffa" /dev/mmcblk1p4: PARTLABEL="misc" PARTUUID="8d390000-0000-472e-8000-3dc60000506d" /dev/mmcblk1p14: PARTLABEL="userdata" PARTUUID="134d0000-0000-4d40-8000-71540000188f" /dev/mmcblk1p2: PARTLABEL="uboot" PARTUUID="523b0000-0000-4275-8000-4a4700000883" /dev/mmcblk1p12: PARTLABEL="baseparameter" PARTUUID="e3430000-0000-4f7b-8000-3af900005bf5" /dev/mmcblk1p9: PARTLABEL="backup" PARTUUID="d31e0000-0000-4930-8000-76c000007aec" /dev/mmcblk1p7: PARTLABEL="boot" PARTUUID="a61c0000-0000-4708-8000-75db00002fb2" /dev/mmcblk1p5: PARTLABEL="dtbo" PARTUUID="f0710000-0000-412e-8000-58350000717b" Can I help you with something? Do you require any files from the original emmc partitions? Maybe this would allow to use all the HW. Also do you think the front LED segment display can be functional?

A service was created to fix the issue, should be this added to official BPI-M7 image? sudo nano /etc/systemd/system/btattach.service sudo systemctl daemon-reload sudo systemctl enable btattach.service sudo systemctl status btattach.service sudo systemctl start btattach.service sudo systemctl status btattach.service cat /etc/systemd/system/btattach.service [Unit] Description=Bluetooth UART Attach Service After=network.target Before=bluetooth.service [Service] Type=simple ExecStartPre=/usr/sbin/modprobe bluetooth ExecStartPre=/usr/sbin/modprobe hci_uart ExecStart=/usr/bin/btattach -B /dev/ttyS6 -P bcm -S 115200 Restart=always [Install] WantedBy=multi-user.target