[0.7] [3G] "PIN secret invalid" even though PIN is correct

Binary package hint: network-manager

I am using a Sierra Aircard MC8781. When I try to connect to the network, I get asked for my PIN (which I enter correctly) but it is not accepted. I know this from the logs - I am attaching relative log and console output to this bug report.
As a feature request, it would be nice if the user were informed why he is getting asked for the PIN once more.

Note: It will also ask me for the PIN when I enter it statically into the "saved networks" dialogue.

dennis@Computer:~$ hal-find-by-capability --capability modem
/org/freedesktop/Hal/devices/usb_device_1199_6856_noserial_if0_serial_usb_0

could you please stop nm like: sudo /etc/init.d/NetworkManager stop

then tail -f -n0 /var/log/syslog > /tmp/syslog.txt

and start NetworkManager like:

export NM_SERIAL_DEBUG=1
sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.txt

then reproduce your problems and when done please attach your syslog.txt and your nm.txt.

NOTE: remember to remove any sensible information like PIN from both logs before submitting!

Thanks for the quick response. I am attaching the output as requested. Hope this can get sorted out before release.

On Tue, Oct 21, 2008 at 04:02:06PM -0000, Dennis Heinson wrote:
>
> ** Attachment added: "nm.txt"
> http://launchpadlibrarian.net/18771466/nm.txt
>

hm ... unfortunately the NM_SERIAL_DEBUG=1 environment was not enough
to get your serial debug. A bit strange I would say. Are you sure you
are running latest network manager package?

 - Alexander

I think so. But I must add that before my recent distro-upgrade I was runnning a network manager from the PPA that included UMTS support. But that has been removed in the upgrading process, correct? Or do I need to delete some old configuration data? Is there any other way of obtaining the serial data?

dennis@Computer:~$ apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20081018t105859-0ubuntu1
  Candidate: 0.7~~svn20081018t105859-0ubuntu1
  Version table:
 *** 0.7~~svn20081018t105859-0ubuntu1 0
        500 http://de.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

could you test the patch posted by Jerone in bug 278992 ?

I discovered something new:
Via #290177 there was a hint to manually unlock the 3G modem. I tried this to no avail with ttyUSB0. However, using ttyUSB2 did the job. Then, the connection fails with a message: Could not set APN.

My conclusion is that NM is talking to the Sierra Modem via the wrong ttyUSB port. Could someone with the necessary knowledge check whether NM is initializing on the wrong USB port?

I am using sierra driver v.1.3.2, kernel 2.6.27-7-generic

Thanks!

Update: https://bugzilla.novell.com/show_bug.cgi?id=392600

After manually setting the PIN and APN, and removing the APN entry in the network config, everything works and NM connects instantly.

So the problem is, I suppose, that NM talks to the Aircard on the wrong USB port (as can be seen in the logs).

Thanks!

On Tue, Nov 18, 2008 at 10:02:05AM -0000, Dennis Heinson wrote:
> After manually setting the PIN and APN, and removing the APN entry in
> the network config, everything works and NM connects instantly.
>
> So the problem is, I suppose, that NM talks to the Aircard on the wrong
> USB port (as can be seen in the logs).
>

please open a bug against hal-info, adding the output of lsusb -v
.... and stating that interface.number 2 works better.

you could also try to adjust the 10-modem.fdi to validate that moving
your products mapping to interfaces.number 2 helps.

 - Alexander

I confirm this on Ubuntu 8.10. N-M keeps asking for PIN and PUK codes although the SIM is unlocked.

Please give me a hint on how to tweak the ppp and chat scripts used with N-M?

Thanks,
/AMIII

PS: I am having problems with Network Manager and a Huawei E600 (PCMCIA) for mobile internet connections through 3G. It is recognized as E620 and the connection process is stuck at a PIN question for an unlocked SIM card.

Some reference information N-M 0.7~~svn20081018... & N-M-Gnome 0.7~~20081020... on the very same system work fine with a Huawei E169. Furthermore, the E600 works fine on GNU/Linux directly with ppp scripts or under win.

On Wed, Jan 14, 2009 at 10:42:58AM -0000, Antonio Macchi III wrote:
> I confirm this on Ubuntu 8.10. N-M keeps asking for PIN and PUK codes
> although the SIM is unlocked.
>
> Please give me a hint on how to tweak the ppp and chat scripts used with
> N-M?
>
>
> Thanks,
> /AMIII
>
>
> PS: I am having problems with Network Manager and a Huawei E600 (PCMCIA) for mobile internet connections through 3G. It is recognized as E620 and the connection process is stuck at a PIN question for an unlocked SIM card.
>
> Some reference information N-M 0.7~~svn20081018... & N-M-Gnome
> 0.7~~20081020... on the very same system work fine with a Huawei E169.
> Furthermore, the E600 works fine on GNU/Linux directly with ppp scripts
> or under win.
>

sorry for the absense. I think i made a mistake on my intial
instructions you have to become root first i think.

sudo su
export NM_SERIAL_DEBUG=1
NetworkManager --no-daemon 2>&1 | tee /tmp/nm.serial.txt

and attach the serial txt file after reproducing this twice please.

Thanks ... sorry for that.

 - Alexander

I could find a way to make NM work on Intrepid with my f$*g Sierra card:
 * boot windows and use the Sierra tools to "deactivate PIN security" (set the card not to ask the PIN code at each usage)
 * re-boot intrepid and set nothing in the PIN field of my broadband card setting
 * launch NM broadband connection - OK

Sure it's not perfect, but helped me use this 3G card...

On Tue, Feb 03, 2009 at 08:51:12PM -0000, Olivier Lemaire wrote:
> I could find a way to make NM work on Intrepid with my f$*g Sierra card:
> * boot windows and use the Sierra tools to "deactivate PIN security" (set the card not to ask the PIN code at each usage)
> * re-boot intrepid and set nothing in the PIN field of my broadband card setting
> * launch NM broadband connection - OK
>
> Sure it's not perfect, but helped me use this 3G card...
>

Getting the SERIAL log as posted before would still be
appreciated. Thanks!

 - Alexander

Here's the result of a lshal -u `hal-find-by-capability --capability modem` :
udi = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0_serial_usb_0'
  info.capabilities = {'serial', 'modem'} (string list)
  info.category = 'serial' (string)
  info.parent = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0' (string)
  info.product = 'MC8780 Device' (string)
  info.subsystem = 'tty' (string)
  info.udi = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0_serial_usb_0' (string)
  linux.device_file = '/dev/ttyUSB0' (string)
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'tty' (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1d.2/usb3/3-2/3-2:1.0/ttyUSB0/tty/ttyUSB0' (string)
  modem.command_sets = {'GSM-07.07', 'GSM-07.05'} (string list)
  serial.device = '/dev/ttyUSB0' (string)
  serial.originating_device = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0' (string)
  serial.port = 0 (0x0) (int)
  serial.type = 'usb' (string)

Hope this'll help.

On Mon, Feb 23, 2009 at 11:40:20PM -0000, Olivier Lemaire wrote:
> Here's the result of a lshal -u `hal-find-by-capability --capability modem` :
> udi = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0_serial_usb_0'
> info.capabilities = {'serial', 'modem'} (string list)
> info.category = 'serial' (string)
> info.parent = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0' (string)
> info.product = 'MC8780 Device' (string)
> info.subsystem = 'tty' (string)
> info.udi = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0_serial_usb_0' (string)
> linux.device_file = '/dev/ttyUSB0' (string)
> linux.hotplug_type = 2 (0x2) (int)
> linux.subsystem = 'tty' (string)
> linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1d.2/usb3/3-2/3-2:1.0/ttyUSB0/tty/ttyUSB0' (string)
> modem.command_sets = {'GSM-07.07', 'GSM-07.05'} (string list)
> serial.device = '/dev/ttyUSB0' (string)
> serial.originating_device = '/org/freedesktop/Hal/devices/usb_device_1199_6832_noserial_if0' (string)
> serial.port = 0 (0x0) (int)
> serial.type = 'usb' (string)
>
> Hope this'll help.
>

I asked for the serial log as described in the previous posts, but
thatnks anyway.

 - Alexander

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.

This bug was marked Incomplete some time ago and was supposed to autoclose after 90 days. Another bug prevented that so I'm closing it now.