Bug 103747

Summary: Sierra Wireless MC7455 Not Supported
Product: ModemManager Reporter: exovaria
Component: generalAssignee: ModemManager bug user <modemmanager>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium    
Version: 1.4   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: lshw, lsusb, nmcli -m 0, debug mode for MM and NM

Description exovaria 2017-11-14 23:22:19 UTC
Created attachment 135475 [details]
lshw, lsusb, nmcli -m 0, debug mode for MM and NM

Attempting to use a mPCIe Sierra Wireless MC7455 modem on Ubuntu 16.04 and am experiencing a variety of issues. 

1) System reports that sim card is missing when sim card is inserted. Removing power to the system for > 30 seconds appears to properly detect the sim card on next boot, however a reboot does not seem to fix the issue. Sent AT!RESET to modem which did not appear to resolve the issue, either.

2) Network Manager GUI shows Mobile Broadband as "not enabled," "searching," or one time showing a placeholder for signal strength despite "mmcli -m 0" showing "signal quality: '0' (cached".

3) Modem never connects to network. Gathered logs as best I could, following the instructions here (https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/). 


System is running Ubuntu 16.04 x86_64 with both kernel 4.4.0-rc8+ and kernel 4.13.0-16. Modem is using a Sprint SIM card with the latest Sprint firmware from Sierra Wireless (SWI9X30C_02.26.01.00_Sprint_002.029_000) having been flashed using their firmware utility.
Comment 1 Aleksander Morgado 2017-11-15 08:23:48 UTC
Ubuntu 16.04 has an extremely old ModemManager version.

Please use this PPA instead, which comes with ModemManager 1.6.10:
https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-xenial

And also, make sure you use a kernel >= 4.5 as the MC7455 support was added in 4.5.

The MC7455 has been running nicely since a very long time in ModemManager.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.