Nodes not booting

[User 18962]

When booting from SD, how does the emmc show up?

I assumed it would be /dev/mmcblk1 as the SD seems to be /dev/mmcblk0 and USB disks show up as /dev/sda, but I can't seem to find that on my Sopine connected to slot 0.

Edit: with the lsblk command it looks like the 128gb emmc is not recognized at all on my Armbian focal system when booting from SD. Normally I would have assumed only 64gb is supported, but since you have it working, it would be interesting to hear any suggestions. I used the emmc usb adapter to format it as a blank ext4 disk.

Edit2: Using the USB adapter the emmc on a USB2 port gets recognized as /dev/sda1, but for actual speed improvement I need to use the emmc slot next to module 0 I would guess.

Hola, sorry for the long wait time for a response. lifes been crazy. hopefully this helps, should be more active now.
here is the output for my first node:

Code:

here is the output for my first node:james@pine1:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mtdblock0     31:0    0    16M  0 disk
mmcblk0      179:0    0  14.9G  0 disk
└─mmcblk0p1  179:1    0  14.7G  0 part /
mmcblk2      179:32   0 116.5G  0 disk /data
mmcblk2boot0 179:64   0     4M  1 disk
mmcblk2boot1 179:96   0     4M  1 disk
zram0        252:0    0    50M  0 disk /var/log
zram1        252:1    0 962.9M  0 disk [SWAP]

[poVoq]

Thanks for the reply.

Which version of Armbian are you using? Or are you using a different image?

I run the Armbian Ubuntu Focal release with the network fix and I can't get it to recognize the emmc at all. I tried now both a 128GB and a 64GB emmc module, both of which are confirmed to run on my PinebookPro and via the usb adapter.

Really quite frustrating.

Edit: on which kernel version? I guess it might be a Kernel 5.4 issue, as that is the default of Focal?

[User 18962]

Thanks for the reply.

Which version of Armbian are you using? Or are you using a different image?

I run the Armbian Ubuntu Focal release with the network fix and I can't get it to recognize the emmc at all. I tried now both a 128GB and a 64GB emmc module, both of which are confirmed to run on my PinebookPro and via the usb adapter.

Really quite frustrating.

Edit: on which kernel version? I guess it might be a Kernel 5.4 issue, as that is the default of Focal?

Armbian 20.08.5 Focal with Linux 5.8.11-sunxi64

just to make sure, but you are checking the correct pine slot yeah?

[poVoq]

Yeah, for sure the right slot (next to the emmc right?).

I now tried the Armbian Bullseye image with Kernel 5.8.5, but no emmc detected at all.

How did you change the Kernel to 5.8.11? I tried through the "armbian-config" menu to switch to a newer kernel, but that always fails. I also tried to switch to the nightly builds through the menu (not a new image) but the Kernel version seems to stay the same.

Maybe I'll try to make another focal image, as my previous one was still on an older Armbian version and hence kernel 5.4.x, but it all feels a bit futile If it wasn't for you having it working I would have given up already on the emmc...

[User 18962]

Yeah, for sure the right slot (next to the emmc right?).

I now tried the Armbian Bullseye image with Kernel 5.8.5, but no emmc detected at all.

How did you change the Kernel to 5.8.11? I tried through the "armbian-config" menu to switch to a newer kernel, but that always fails. I also tried to switch to the nightly builds through the menu (not a new image) but the Kernel version seems to stay the same.

Maybe I'll try to make another focal image, as my previous one was still on an older Armbian version and hence kernel 5.4.x, but it all feels a bit futile If it wasn't for you having it working I would have given up already on the emmc...

yep, closest to the EMMC, was a long shot, but worth a double check.

as for the kernel, i just downloaded the latest image and it had that kernel.

link just in case: https://redirect.armbian.com/pine64so/Focal_current

its strange it doesnt show up... what does your DMESG say about mmc2? can you post your dmesg?

[poVoq]

its strange it doesnt show up... what does your DMESG say about mmc2? can you post your dmesg?

Ah, dmsg does indeed give an error:

[    2.486688] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    2.487483] sunxi-mmc 1c11000.mmc: send stop command failed
[    2.487518] mmc2: switch to bus width 8 failed
[    2.487854] mmc2: unexpected status 0x400800 after switch
[    2.494397] mmc2: power class selection to bus width 4 ddr 4 failed
[    2.521669] mmc2: error -110 whilst initialising MMC card

Any idea what this could mean?

[poVoq]

https://bugzilla.redhat.com/show_bug.cgi?id=1745265
Seems like a related/same bug.

Edit: Which hardware version of the Clusterboard do you have? Mine says 2.2 on the on the back.

[poVoq]

Found two related discussion from other SBCs that seems to have similar issues, the one points to an hardware issue:
http://forum.banana-pi.org/t/sunxi-mmc-1...error/9891

Hence, maybe you have a different hardware revision of the clusterboard, or a different / older type of eMMC? My 64GB module says "A64-DB-E MMC-v1_0" on the back.

The other discusses a possible software workaround by switching from the faster but buggy "HS200" to slower the "DRR52" mode:
https://184.105.72.32/forum/index.php?topic=7452.0

I'll try the proposed software fix later today.

Edit: Hmm, I still have a super old 16GB eMMC from an Odroid board. Seems to use the same connector. Maybe that one works?

---

Hmm, maybe some progress, but still not working. I applied the above mentioned fix with "drr" mode and now the dmesg looks like this:

[ 2.509337] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode
[ 2.614059] mmc2: error -110 whilst initialising MMC card

[poVoq]

Funny, with the old 16gb emmc from Odroid, it also doesn't work, but it seems to fall back to the "drr" mode even on system images without the above mentioned software fix applied. So there I get the above new dmesg error message on stock sopine64 armbian images.

Edit: -110 seems to indicate a time-out error...

[User 18962]

Funny, with the old 16gb emmc from Odroid, it also doesn't work, but it seems to fall back to the "drr" mode even on system images without the above mentioned software fix applied. So there I get the above new dmesg error message on stock sopine64 armbian images.

Edit: -110 seems to indicate a time-out error...

it very well could be cluster board version, im on 2.3

interestingly enough my 128gb also says A64-DB-E MMC-v1_0 on the back, which i guess is just for the interposer board from the emmc to the connector on the cluster board.

i dont think it would have anything to do with the board version however, since the traces would stay the same as would the chip.

have you check the DTS config for mmc2? this is likely where the issue is, heres some cli to convert it if that helps:
sudo dtc -I dtb -O dts -o /tmp/temp.dts /usr/lib/linux-image-current-sunxi64/allwinner/sun50i-a64-sopine-baseboard.dtb

then just put it in vim and you can read the output, were looking for anything relating to mmc2 as thats whats controlling the gpio for it, as well as what does the init process, mine is /soc/mmc@1c11000.

i can also share my DTS file with you if that helps

here is my DMESG init of the mmc:

Code:

[    2.603079] mmc2: mmc_select_hs200 failed, error -74

Code:

[    2.658828] mmc2: new MMC card at address 0001

Code:

[    2.660156] mmcblk2: mmc2:0001 DA4128 116 GiB

Code:

[    2.660783] mmcblk2boot0: mmc2:0001 DA4128 partition 1 4.00 MiB

Code:

[    2.661428] mmcblk2boot1: mmc2:0001 DA4128 partition 2 4.00 MiB