These usually indicate an issue communicating with the chip. This can be caused by signal integrity problems, poor supplies, the chip not coming out of reset, amongst many others.
How are you connecting your Alfa module to your board? Do you have any details on the hardware which you can share?
Can you share the device tree file for the libre board?
I mean the .dts file Linux uses to configure hardware. You should be able to extract this from the device by installing dtc on the device and running dtc -I fs -O dts /sys/firmware/devicetree/base -o librem5.dts.
While the MM6108 can support a 1.8V I/O voltage for the SDIO lines, the RESET line needs to operate in the “VBAT” domain, 3.3V.
Unfortunately at this stage the solution may require a pull-up resistor to be inserted on the RESET line to 3.3V, as well as some device tree adjustment to configure the SD2_RESET pin as an open drain GPIO, and finally adding an mm6108 specific child node in the usdhc2 controller to provide a reset-gpios to the Morse driver so it can control that GPIO.
Are you in a position where you can add a hardware pullup to that RESET line? Does the bootloader allow you to load an alternative device tree binary?
I may on module land, not on phone land as it may malfuntions on others working modules. Also on phone side it needed disassembling the case. So pull-up on Phone land it not viable.
Yes there is a option to load a different device tree.
At the moment i want to test same mm6108 module to Laptop Librem 14 as it support sdio via M2-E too.