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 631897 - PIN2 support for 0af0:5000 Option UMTS Card
PIN2 support for 0af0:5000 Option UMTS Card
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: ModemManager
git master
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-10-11 16:31 UTC by Mathieu Trudel-Lapierre
Modified: 2014-11-14 11:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mathieu Trudel-Lapierre 2010-10-11 16:31:20 UTC
As initially reported here: https://bugs.edge.launchpad.net/ubuntu/+source/modemmanager/+bug/575778

It looks like the broadband card:
Bus 009 Device 002: ID 0af0:5000 Option UMTS Card

requires a second PIN at initialization:

** (modem-manager:4296): DEBUG: (ttyUSB0): <-- '<CR><LF>+CPIN: SIM PIN<CR><LF><CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled -> disabled)
** (modem-manager:4296): DEBUG: (ttyUSB0): --> 'AT+CPIN="1234"<CR>'
** (modem-manager:4296): DEBUG: (ttyUSB0): <-- '<CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)

[...]

** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled)
** (modem-manager:4296): DEBUG: (ttyUSB0): --> 'AT+CPIN?<CR>'
** (modem-manager:4296): DEBUG: (ttyUSB0): <-- '<CR><LF>+CPIN: SIM PIN2<CR><LF><CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled -> disabled)
** (modem-manager:4296): DEBUG: (ttyUSB0): --> 'AT+CPIN="1234"<CR>'
** (modem-manager:4296): DEBUG: (ttyUSB0): <-- '<CR><LF>+CME ERROR: 16<CR><LF>'
** (modem-manager:4296): DEBUG: Got failure code 16: Incorrect password
[...]

"
e.g. if your PIN is 1234 the correct sequence for initialization is:
at+cpin="1234"
at+cpin="0000"

The card will acknowledge both command with "OK". The current modem-manager implementation does the first at+cpin="1234" step only, which is sufficient for most cards, except this one.

If you initialize this card using "minicom" or setup and use "wvdial" for initialization only, you can continue using the network-manager and modem-manager as usual.
"
Comment 1 Dan Williams 2010-10-12 21:17:48 UTC
I suppose we need better PIN2 support; which usually controls fixed dialing and such.  But this is also the first time I've heard of a device that requires the PIN2 be entered; apparently the PIN2 is enabled on this SIM when it's usually disabled.
Comment 2 Thorsten Hesemeyer 2010-10-18 16:11:24 UTC
It's not a SIM card setting, it's a device "feature".

I used the same SIM card with multiple broadband devices, the "Option UMTS Card" 0af0:5000 is the only one that refuses to operate until PIN2 has been given.
Comment 3 Aleksander Morgado 2013-04-01 14:47:29 UTC
I've seen modems requiring PIN2 after PIN, but they will be able to connect normally even if PIN2 is not entered. PIN2-locked is therefore now considered as 'unlocked' for MM purposes...

Is anyone able to retest this issue with MM git master?
Comment 4 Aleksander Morgado 2014-11-14 11:37:29 UTC
I'll close the bug as ModemManager 1.x doesn't require PIN2 unlock to manage the device properly. i.e. if modem asks for PIN2 we'll just ignore and continue.