After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726613 - Sierra Wireless EM7305 not working
Sierra Wireless EM7305 not working
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: ModemManager
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-03-18 07:49 UTC by Gergely Dömsödi
Modified: 2014-10-14 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ModemMaanger debug log (44.71 KB, text/plain)
2014-03-18 07:49 UTC, Gergely Dömsödi
Details
lsusb device inormation (9.90 KB, text/plain)
2014-03-18 07:51 UTC, Gergely Dömsödi
Details
ModemManager debug log after sleep -> bad (111.08 KB, text/plain)
2014-07-09 05:26 UTC, Gergely Dömsödi
Details
ModemManager debug log after reboot -> good (106.77 KB, text/plain)
2014-07-09 05:27 UTC, Gergely Dömsödi
Details
ModemManager debug log after sleep -> good (111.10 KB, text/plain)
2014-07-09 05:28 UTC, Gergely Dömsödi
Details

Description Gergely Dömsödi 2014-03-18 07:49:11 UTC
Created attachment 272245 [details]
ModemMaanger debug log

I have an embedded Sierra Wireless EM7305 3G card ID: (1199:9041), but it is not working in ModemManager. ModemManager sees the modem, but can't use it.

Debug logs attached.

It is on:

/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6
Comment 1 Gergely Dömsödi 2014-03-18 07:51:05 UTC
Created attachment 272246 [details]
lsusb device inormation
Comment 2 Aleksander Morgado 2014-03-21 10:21:38 UTC
Moved discussion to libmbim-devel mailing list:

http://lists.freedesktop.org/archives/libmbim-devel/2014-March/000198.html
Comment 3 Gergely Dömsödi 2014-03-25 14:51:16 UTC
Please, let me know if I can help by providing any further info, debug logs or testing.
Comment 4 Gergely Dömsödi 2014-05-03 13:54:09 UTC
I did a little research and it seems to me that this is not an MBIM but a Gobi (QMI?) device.

http://m2msupport.net/m2msupport/sierra-wireless-pcie-m-2-em7305-4g-lte-module-2/
http://www.4gltemall.com/sierra-wireless-airprime-em7305.html

According to the pages above, the modem uses the Qualcomm MDM 9215 Chipset, which can be found on http://www.qualcomm.com/gobi/modems .

My opinion is that libmbim has nothing to do with this one, it is just pulled in because the generic plugin tries to communicate with the modem through MBIM, but fails.
Comment 5 Gergely Dömsödi 2014-07-09 05:26:34 UTC
Created attachment 280204 [details]
ModemManager debug log after sleep -> bad
Comment 6 Gergely Dömsödi 2014-07-09 05:27:15 UTC
Created attachment 280205 [details]
ModemManager debug log after reboot -> good
Comment 7 Gergely Dömsödi 2014-07-09 05:28:29 UTC
Created attachment 280206 [details]
ModemManager debug log after sleep -> good
Comment 8 Gergely Dömsödi 2014-07-09 05:31:13 UTC
With a recent kernel, the device started working, but unfortunately just until the computer goes to sleep. After waking up from the sleep, it is still unable to connect.

I did a little research, and it turned out, that it only goes bad if ModemManager is running when the computer goes to sleep. If I shut down ModemManager before the computer sleeps, and restart it afterwards, everything is good.

I did two tests (debug logs attached).

Case 1:

Reboot my computer -> start ModemManager -> connect to the net with the device, disconnect -> stop ModemManager (ModemManager-afterreboot-good.log)  -> sleep, wake up -> start ModemManager -> connect to the net -> stop MomdemManager (ModemManager-aftersleep-good.log)

Everything is right this in this case (except that I wouldn't want to stop ModemManager each time when the computer sleeps)

Case 2:

Reboot my computer -> start MomdemManager -> connect to the net -> disconnect -> sleep -> wake up -> try to connect to the net again (not working) -> stop ModemManager (ModemManager-afterreboot-bad.log)

--

I also played with it a little, trying the bad state to get work again normally without a reboot, but I did not succeed. Tried restarting ModeManager, reloading the kernel modules, neither of this helped.
Comment 9 Aleksander Morgado 2014-10-14 12:20:21 UTC
Could you retry to run the error situation but this time getting both ModemManager and NetworkManager debug logs at the same time? Steps to do so here:
http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/

Also, if you could also modify the debug logs adding lines like "here I click connect", "here I click disconnect" or whatever, that would be good. In one of the last debug logs you sent (the one with sleep -> bad), there is a "Disconnection" message which I believe is triggered via DBus, which doesn't make much sense unless NetworkManager is actually reporting an error back to ModemManager.

If you can gather these extra debug logs, please add them to this new bugreport we have in fd.o, and subscribe to the new bugreport to get new updates:
https://bugs.freedesktop.org/show_bug.cgi?id=84992

Closing this report as NOTGNOME.