express broadband card GE442 connects on every second attempt with Lucid

Bug #576658 reported by Thorsten Hesemeyer on 2010-05-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

Binary package hint: network-manager

The mobile broadband card:
Option Globetrotter EXPRESS 442 UMTS Modem Card (GE442)

which show up in lsusb as:
Bus 003 Device 002: ID 0af0:7381 Option

Fails to connect on every second attempt.
Different card, but symptoms are similar to GE0301 card. See my other launchpad bug #575736.

1. Successful connect
2. Disconnects with network-manager error message:
    nm.log.txt:NetworkManager: <WARN> check_one_route(): (hso0) error -34 returned from rtnl_route_del(): Sucess
    nm.log.txt:-- Error received: Numerical result out of range
3. Fails to connect on following attempt
4. "Disconnects" without error message

These logs done with Ubuntu 10.04 are appended to view the details:
nm.log.txt network-manager log with multiple connection attempts
modem.log.txt modem-manager log (same session)
mm-test.log output of script

Kind regards,

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae
Uname: Linux 2.6.32-21-generic-pae i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Thu May 6 23:40:41 2010
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
IpRoute: dev eth0 proto kernel scope link src metric 1 dev eth0 scope link metric 1000
 default via dev eth0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
SourcePackage: network-manager

Looking through the attached modemmanager logs I can't see the case where the second connection attempt causes MM to start establishing a connection.

Seeing the messages:
** Message: (ttyHS2) closing serial device...

Maybe what happens is that MM puts the modem into a mode this specific device doesn't like upon closing the connection, unless this was caused by the device being pulled. Either way, it will require some more investigation, so I'm marking this Triaged/Low. We may need to ask for some more information in the future.

In parallel, could you test the same device on a LiveCD of the latest Ubuntu release - Maverick Meerkat, just to make sure this can still be reproduced? There has been a ton of changes between the MM version in Lucid (0.3) and the version that was shipped with Maverick (0.4+git.20100809t153145).

Thanks in advance!

Changed in network-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.