Fedora 20 dosen’t accept correct PIN for mobile broadband

fedoramobilenetworking

I have a problem with the WWAN (Qualcomm Gobi 2000) in my Lenovo ThinkPad W510.
I can not unlock my SIM card with the correct PIN. I enter the PIN in this dialog
and after this
SIM PIN

I get immediately this dialog

SIM PIN2

After I enter the SIM PIN2 the only thing that happens is that I get a notification that says that the connection is disabled.

I know that this is not a problem with the PIN or the SIM card because I checked both with my Windows 8 notebook.

What I have to do to use the WWAN in my notebook.

Update from 2014-04-29

Just found this via journalctl

Apr 29 17:43:32 NetworkManager[1022]: <info> Activation (cdc-wdm0) starting connection 'O2'
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 29 17:43:32 NetworkManager[1022]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 29 17:43:32 NetworkManager[1022]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) started...
Apr 29 17:43:32 NetworkManager[1022]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete.
Apr 29 17:43:32 ModemManager[900]: <info>  Simple connect started...
Apr 29 17:43:32 ModemManager[900]: <info>  Simple connect state (3/8): Enable
Apr 29 17:43:32 ModemManager[900]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
Apr 29 17:43:32 ModemManager[900]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> disabled)
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0) modem state changed, 'enabling' --> 'disabled' (reason: unknown)
Apr 29 17:43:32 NetworkManager[1022]: <warn> (cdc-wdm0) failed to connect modem: Couldn't set operating mode: QMI protocol error (60): 'InvalidTransaction'
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Apr 29 17:43:32 NetworkManager[1022]: <warn> Activation (cdc-wdm0) failed for connection 'O2'
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 29 17:43:32 NetworkManager[1022]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
Apr 29 17:43:32 firewalld[887]: 2014-04-29 17:43:32 ERROR: UNKNOWN_INTERFACE: cdc-wdm0
Apr 29 17:43:32 NetworkManager[1022]: <warn> (cdc-wdm0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: cdc-wdm0
Apr 29 17:45:52 PackageKit[2687]: daemon quit
Apr 29 17:46:40 dbus-daemon[928]: dbus[928]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Apr 29 17:46:40 dbus[928]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Apr 29 17:46:40 systemd[1]: Starting PackageKit Daemon...
Apr 29 17:46:40 PackageKit[3672]: daemon start
Apr 29 17:46:40 dbus-daemon[928]: dbus[928]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Apr 29 17:46:40 dbus[928]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Apr 29 17:46:40 systemd[1]: Started PackageKit Daemon.
Apr 29 17:46:44 PackageKit[3672]: get-updates transaction /395_dedbecee from uid 1000 finished with success after 4026ms

Update from 2014-05-02

AFAIK the WWAN firmware is loaded and the device is successfully initialized:

nmcli -p n
============
  Netzwerk
============
NETZWERK  
------------
aktiviert 
[root@uss-titan marceljanus]# nmcli -p d
======================================
          Status der Geräte
======================================
GERÄT     TYP       STATUS          
--------------------------------------
wlp3s0    wifi      verbunden       
cdc-wdm0  gsm       nicht verbunden 
em1       ethernet  nicht verfügbar 
lo        loopback  nicht verwaltet 

lsusb
Bus 002 Device 004: ID 05c6:9205 Qualcomm, Inc. 
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 003 Device 002: ID 04b3:310d IBM Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 17ef:480f Lenovo Integrated Webcam [R5U877]
Bus 001 Device 004: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output from /var/log/messages after trying to enable the connection:

May  2 15:11:34 NetworkManager[889]: <info> Activation (cdc-wdm0) starting connection 'O2'
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May  2 15:11:34 NetworkManager[889]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled...
May  2 15:11:34 NetworkManager[889]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) started...
May  2 15:11:34 NetworkManager[889]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete.
May  2 15:11:34 ModemManager[793]: <info>  Simple connect started...
May  2 15:11:34 ModemManager[793]: <info>  Simple connect state (3/8): Enable
May  2 15:11:34 ModemManager[793]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
May  2 15:11:34 ModemManager[793]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> disabled)
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0) modem state changed, 'enabling' --> 'disabled' (reason: unknown)
May  2 15:11:34 NetworkManager[889]: <warn> (cdc-wdm0) failed to connect modem: Couldn't set operating mode: QMI protocol error (60): 'InvalidTransaction'
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0): device state change: prepare -> failed (reason 'unknown') [40 120 1]
May  2 15:11:34 NetworkManager[889]: <warn> Activation (cdc-wdm0) failed for connection 'O2'
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
May  2 15:11:34 NetworkManager[889]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
May  2 15:11:34 firewalld: 2014-05-02 15:11:34 ERROR: UNKNOWN_INTERFACE: cdc-wdm0
May  2 15:11:34 NetworkManager[889]: <warn> (cdc-wdm0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: cdc-wdm0

Best Answer

I've never used one of these modems but am interested in trying to help solve your issue. I found this thread which discusses the use of a command line tool called mmcli. The thread is called: Re: Sierra Wireless MC8355 - Gobi 3000 with AT&T. This seemed related since there were a number of mentions of a tool called mmcli.

The Chromium project alos has this page which shows how to use it to debug a cellular modem connection, titled: Modem debugging with mmcli (from the modemmanager-next package).

Listing modems/finding the index number of a modem (The modem index frequently changes during a suspend-resume cycle):
```
$ mmcli -L
```
(Further examples will assume modem index 0. Substitute your own modem index where necessary.)
See the status of a modem:
```
$ mmcli -m 0
```
Enable a modem (useful side effects usually include registering on a network and getting an operator ID and name)
```
$ mmcli -m 0 -e
```

Minimal connection and disconnection:

$ mmcli -m 0 --simple-connect="apn=foo.carrier.com"
$ mmcli -m 0 --simple-disconnect

Set logging level to maximium (equivalent to the old mm_debug debug):
```
$ mmcli -G DEBUG
```
Set logging level to minimum (equivalent to the old mm_debug err):
```
$ mmcli -G ERR
```
Arbitrary AT commands - available if ModemManager is started with the --debug flag:
This is a good test command to see if ModemManager is speaking to the modem. The modem should already be in state E0 (no command echo); you should immediately get an empty reply. You can check /var/log/messages for the message exchange if you've previously turned up the logging level to maximum.
```
$ mmcli -m 0 --command="E0" 
```
Do a network scan and list the carriers found - this requires a longer-than-default timeout.
```
$ mmcli -m 0 --command-timeout=120 --command="+COPS?" 
```

I believe this tool is included in the package ModemManager.

References

Features/MoreMobileBroadband

Related Solutions

Mobile broadband repeatedly connects/disconnects

Okay, I've finally after years of immense frustration managed to solve the problem, which is that NetworkManager is just really buggy about modems. In fact, recently it has gotten worse and even started segfaulting when my broadband modem is up. However, it turns out that if you just configure the modem manually, it works super well, even after a sleep. (You have to reconnect when waking up from sleep, but it reconnects quickly and then works stably.)

The following instructions assume you are running as root. The first step is to get NetworkManager out of the way. To do that, edit the file /etc/NetworkManager/NetworkManager.conf and add the following:

[keyfile]
unmanaged-devices=interface-name:cdc-wdm0

Note that if you want it to ignore multiple devices, you can separate them with a semicolon. Next, you have to configure the APN (and mbim-proxy) as follows. Look at /usr/share/mobile-broadband-provider-info/serviceproviders.xml (or the online git repository) to find the appropriate APN for your network. In the case of verizon wireless, that's vzwinternet. Once you have that, create a file /etc/mbim-network.conf with the following:

APN=vzwinternet
PROXY=yes

Now run the following:

rfkill unblock wwan
mbim-network /dev/cdc-wdm0 start
ip link set wwan0 up
mbimcli -p -d /dev/cdc-wdm0 --query-ip-configuration

If the mbim-network command succeeds, the mbimcli command will subsequently produce output like the following:

[/dev/cdc-wdm0] IPv4 configuration available: 'address, gateway, dns'
     IP [0]: '100.125.243.196/24'
    Gateway: '100.125.243.1'
    DNS [0]: '198.224.173.135'
    DNS [1]: '198.224.174.135'
    DNS [2]: '198.224.173.135'
    DNS [3]: '198.224.174.135'

[/dev/cdc-wdm0] IPv6 configuration available: 'address, gateway, dns'
     IP [0]: 'fe80::69:1c7d:5901/120'
    Gateway: 'fe80::69:1c7d:5902'
    DNS [0]: '2001:4888:68:ff00:608:d::'
    DNS [1]: '2001:4888:61:ff00:604:d::'

Now just manually configure those values on your network interface and it will work. E.g.:

ip addr add dev wwan0 100.125.243.196/24
ip route add default via 100.125.243.1
echo 'nameserver 198.224.173.135' > /etc/resolv.conf

Do not attempt to run DHCP (it won't work). Do not attempt to ping the gateway (100.125.243.1) as that won't work either. The fact that the gateway doesn't respond to any network packets (and might not even exist) made me think that my modem wasn't working, until I finally tried adding the default route and disabling my other network connection.

Best Answer

References

Related Solutions

Mobile broadband repeatedly connects/disconnects

Related Question