broadband card option 3g datacard 0af0:5000 initialization - card needs a second pin

Bug #575778 reported by Thorsten Hesemeyer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ModemManager
New
Undecided
Unassigned
NetworkManager
Expired
Medium
modemmanager (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: modemmanager

The older broadband card: option 3g datacard, that identifies itself using lsusb with
Bus 009 Device 002: ID 0af0:5000 Option UMTS Card

Needs a second pin at initialization, 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.

Appended logs:
1 Failed attempts with the default lucid setup:
  1.1 modem_failed.log.txt
  1.2 nm_failed.log.txt
2 Successful attempts after an external at+cpin="0000" initialization
  2.1 modem_success.log.txt
  2.2 nm_success.log.txt
3. Output of the Python script mm-test.py: mm-test.log

Kind regards,
Thorsten

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: modemmanager 0.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
Architecture: i386
Date: Wed May 5 14:58:52 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: modemmanager

Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :
Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :
Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :
Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :
Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :
summary: - option 3g datacard 0af0:5000 initialization - card needs a second pin
+ broadband card option 3g datacard 0af0:5000 initialization - card needs
+ a second pin
Revision history for this message
Robert Sander (gurubert) wrote :

Hi,

I was able to successfully establish a connection with wvdial and the steps described on http://ubuntuforums.org/showthread.php?t=203342

I even tried the network-manager ppa packages from https://launchpad.net/~network-manager/+archive/trunk but with no luck.

Changed in modemmanager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Robert, if you could connect with the steps in that thread, I don't think it's the same issue. This bug report mentions having to issue a second PIN to complete initialization, and the thread you linked is really old. I would suggest you open a separate bug instead and tell us the number here so we can look into it.

Thorsten, this appears to me as a "new" special quirk for this device, and I don't think it's something that has been seen before upstream. I reported the bug in the GNOME tracker for NetworkManager/ModemManager: it's bgo 631897.

Changed in modemmanager (Ubuntu):
importance: Undecided → Low
Revision history for this message
Robert Sander (gurubert) wrote :

I am sorry but I do not have access to the device any more.

Changed in network-manager:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Bremner (paullinden) wrote : Re: [Bug 575778] Re: broadband card option 3g datacard 0af0:5000 initialization - card needs a second pin

Quoting Robert Sander <email address hidden>:

> I am sorry but I do not have access to the device any more.
>
> --
> broadband card option 3g datacard 0af0:5000 initialization - card
> needs a second pin
> https://bugs.launchpad.net/bugs/575778
> You received this bug notification because you are subscribed to
> NetworkManager.
>
> Status in ModemManager (with NetworkManager support): New
> Status in NetworkManager: Unknown
> Status in ?modemmanager? package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: modemmanager
>
> The older broadband card: option 3g datacard, that identifies itself
> using lsusb with
> Bus 009 Device 002: ID 0af0:5000 Option UMTS Card
>
> Needs a second pin at initialization, 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.
>
> Appended logs:
> 1 Failed attempts with the default lucid setup:
> 1.1 modem_failed.log.txt
> 1.2 nm_failed.log.txt
> 2 Successful attempts after an external at+cpin="0000" initialization
> 2.1 modem_success.log.txt
> 2.2 nm_success.log.txt
> 3. Output of the Python script mm-test.py: mm-test.log
>
> Kind regards,
> Thorsten
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: modemmanager 0.3-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-21-generic-pae i686
> Architecture: i386
> Date: Wed May 5 14:58:52 2010
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.utf8
> SHELL=/bin/bash
> SourcePackage: modemmanager
>
>
>

Changed in network-manager:
status: New → Confirmed
Changed in network-manager:
status: Confirmed → Incomplete
Changed in network-manager:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.