NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device

I'm using a Huawei E169. It's not being recognized at all. Not even USB storage.

Linux testing 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:47:58 UTC 2009 x86_64 GNU/Linux

lsusb -v

Bus 004 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x12d1 Huawei Technologies Co., Ltd.
  idProduct 0x1001 E620 USB Modem
  bcdDevice 0.00
  iManufacturer 1
  iProduct 2
  iSerial 1
  bNumConfigurations 1

For whatever reason, the modemmanager package dependency was not resolve or installed by aptitude with the network-manager update.

After installing modemmanager, there are now different symptoms and a new bug has been been filed:

https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/410634

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: network-manager 0.8~a~git.20090804t185522.4bab334-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

Attached is the modem-manager debug log for my Verizon UM150 CDMA modem. This issue is clearly affecting other makes / models and is discussed on the Ubuntu karmic testing forum here:

http://ubuntuforums.org/showthread.php?t=1234128

tekstr1der, thanks for the detailed information. I'm in the process of reporting an upstream bug.

What are the exact steps you take to reproduce this bug?

Besides not connecting, what other visible symptoms occur? Does the applet just spin and never connect?

tekstr1der, one more question...

What version of network-manager worked for you? I'm trying to determine if you were using modem manager at all previously, or just network-manager alone. In order to use modem manager, you would have had to be using a version of network-manager from the modem manager PPA ( probably had .mm in the version string ).

Tony, thanks for picking this up.

The visible symptoms are the network manager applet just spins indefinitely with both lights green. I receive an IP and DNS nameserver information from ISP, but the connection is never fully established.

0.7.1.git.5.272c6a626-0ubuntu1 WITHOUT the modemmanager package installed is the most recent version which works for me.

Right now, if I remove the modemmanager package and downgrade to 0.7.1, the device works as expected as an auto mobile broadband. Any other information I can provide to assist in debugging this please let me know.

I'm seeing very similar symtoms with a UM175. I have the extra wrinkle that if I unplug the device while NM is "spinning" I get a kernel panic.

nm-tool shows it in state "connecting" forever.

Rob, the unplugging freeze/panic was reported seperately here:

https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/412605

Could you please post a log of your debug results from following these steps:

1) Stop NetworkManager
2) run /usr/sbin/modem-manager --debug
3) Start NetworkManager
4) Plug in your modem

And tell us what log output ModemManager spews out.

Output from modem manager is attached.

This shows plugging in the modem and then clicking the connection in nm-applet.

At the end, I have two green nm-applet bubbles with the spinner animation going and no additional progress.

This appears to be fixed with latest build:
network-manager - 0.8~a~git.20090817t203502.3e22183-0ubuntu1~nmt2
modemmanager - 0.2.git.20090817t181641.ca767e4-0ubuntu1~nmt2

Found here:
https://edge.launchpad.net/~network-manager/+archive/trunk

CDMA modem is connecting as expected with the only difference from .7.1 being that instead of "auto mobile broadband", now user must select provider from list to set up connection.

Confirmed fixed in latest builds from edge.launchpad.net as tekstr1der said.

Oops spoke too soon. Problem is just different now.

OK what happens now is that it works the first time, but if I plug it in, connect, then disconnect and unplug it, I can no longer ever get it working again until I reboot.

I can confirm the reconnect problem. To workaround, I killed modem-manager and restarted networking. This allows the device to connect again without the need to log out.

Should the failure to reconnect be filed as a separate bug?

Yes, please file the re-connect problem as a separate bug, thanks!

Oops, can't file the bug using apport since I'm using the trunk build version from the PPA. I was under the impression it is bad form to file a bug against a package not yet released to updates? Should I wait on this until network-manager hits karmic updates?

See also Bug 414604, which may be a duplicate of this one, and provides detailed information. And my UM175 is most definitely NOT working with today's updates.

please be sure you have username/password (often just anything) and APN set in the mobile broadband configuration.

Marking FixReleased as the original problem was fixed upstream and released to Karmic as version:

0.8~a~git.20090820t182117.cb60390-0ubuntu3

tekstrider, per your comment #26, you should be able to file the re-connect bug via apport now.