On 12/19/2019 17:05, Aleksander Morgado wrote:
Hey Bjørn & all,
I wonder if you have any idea why this issue is happening?
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/165#note_368404
We can see how the kernel driver reported as managing the device that
owns the cdc-wdm port changes from cdc_mbim (original one after boot)
to qmi_wwan (after a suspend/resume cycle). This makes ModemManager
attempt QMI probing instead of MBIM probing on the port, and that
fails, so the modem is no longer used after the suspend/resume cycle.
Any hint?
Can only be one reason, the card has been configured to have both qmi
interface and mbim interface in the composition.
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel