v1.8.2 Autodetect of `dev/mmcblk0` fails due to `/sys/block/mmcblk0/removable` returning 0 about fwup HOT 4 CLOSED

Thanks for the information. I feel like I should be able to reproduce this on my next pass at updating fwup. In the mean time, hopefully manually passing -d mmcblk0 to force the MicroSD card to be used works for you.

from fwup.

All - sorry for the long wait. I looked into this with the help of @mattludwigs who has a Pop!OS system. The issue is due to a change in the Linux kernel and you all hit it first. I have a fix in #162.

from fwup.

It looks like in PopOs they are suing their own systemd
and according to this function they are expecting removable to > 0 for sd cards as well.
I have not found were the mounting of the sd card happens where setting of removable should happen yet.
https://github.com/pop-os/systemd/blob/ddb09573ebb7264538af3f77f16b5d1c252a8551/src/mount/mount-tool.c#L1210

from fwup.

I don't have much to add, but I'm on Pop!OS 18.04 with Fwup v1.8.1 and having the same issue. I've tried with a fresh SD card as well as with one that already had been used to burn a Nerves firmware image.

OS: Pop!_OS 18.04 LTS x86_64  
Host: Meerkat meer4   
Kernel: 5.4.0-52-generic 

➜ ls -al /dev | grep mmcblk  
brw-rw----   1 root   disk    179,     0 Nov  1 11:52 mmcblk0  
brw-rw----   1 root   disk    179,     1 Nov  1 11:52 mmcblk0p1  
brw-rw----   1 root   disk    179,     2 Nov  1 11:52 mmcblk0p2  
brw-rw----   1 root   disk    179,     3 Nov  1 11:52 mmcblk0p3  

➜ cat /sys/block/mmcblk0/removable  
0

from fwup.