Bug 85725 - Gobi 3000 incorrect reover from rfkill software lock
Summary: Gobi 3000 incorrect reover from rfkill software lock
Status: RESOLVED MOVED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: general (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: ModemManager bug user
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-01 06:29 UTC by Oleksii Shevchuk
Modified: 2018-06-10 09:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
`mmcli -m 0 -e` output (6.68 KB, text/plain)
2015-07-07 16:11 UTC, Andrea Scarpino
Details
qmicli commands output (1.03 KB, text/plain)
2015-07-07 16:12 UTC, Andrea Scarpino
Details

Description Oleksii Shevchuk 2014-11-01 06:29:09 UTC
manufacturer: 'Sierra Wireless Inc'
       model: 'Sierra Wireless MC8355 - Gobi 3000(TM) Module'
     drivers: 'qcserial, qmi_wwan'
      plugin: 'Gobi'

The problem is simple. When I disable Modem in nm-applet, it enables rfkill. When I enable Modem in nm-applet, it doesn't try to register in home network, because of:
 NetworkManager[545]: <warn>  (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.libqmi.Error.Protocol.HardwareRestricted: Couldn't set operating mode: QMI protocol error (83): 'HardwareRestricted

When I click on connection menu item, it registers and starts connecting.

So, the desired behaviour after enabling modem should be - registering to the network.
Comment 1 Andrea Scarpino 2015-04-24 07:50:45 UTC
Confirmed. Happens here too, but I'm unable to connect to any network.

# mmcli -m 0 -e
failed to enable modem: GDBus.Error:org.freedesktop.libqmi.Error.Protocol.HardwareRestricted: Couldn't set operating mode: QMI protocol error (83): 'HardwareRestricted
Comment 2 Dan Williams 2015-07-07 14:45:24 UTC
What versions of ModemManager, libqmi, and the kernel do you have?  Could you run:

mmcli --set-logging=DEBUG

and then reproduce the issue, and attach the system logs from ModemManager so we can take a look at what's going on?  When you get the "HardwareRestricted" message, could you then:

mv /usr/sbin/ModemManager /
killall -TERM ModemManager
rfkill list
qmicli -p -d /dev/cdc-wdm0 --dms-get-power-state
qmicli -p -d /dev/cdc-wdm0 --dms-get-operating-mode
qmicli -p -d /dev/cdc-wdm0 --nas-get-signal-strength
qmicli -p -d /dev/cdc-wdm0 --nas-get-serving-system
mv /ModemManager /usr/sbin/

Feel free to edit the logs to remove your SIM's IMSI, phone number, text messages, etc since those may be in the ModemManager logs.
Comment 3 Andrea Scarpino 2015-07-07 16:11:48 UTC
Created attachment 116995 [details]
`mmcli -m 0 -e` output
Comment 4 Andrea Scarpino 2015-07-07 16:12:09 UTC
Created attachment 116996 [details]
qmicli commands output
Comment 5 Andrea Scarpino 2015-07-07 16:21:17 UTC
kernel is 4.1.1
libqmi 1.12.6
modemmanager 1.4.8

Thanks!
Comment 6 GitLab Migration User 2018-06-10 09:06:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/79.


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.