My Huawei EM770 behaves highly irregularly with Ubuntu

[Nicholas Christian Langkjær Ipsen]

Binary package hint: network-manager

My PCI-mini EM770 3G card(Reported as Huawei Technologies Co., Ltd. E620 USB Modem by lsusb and not shown anywhere else.) Is behaving very irregularly. Sometimes, the network-mananger keeps spinning for several minutes, before giving up. When I then click connect again, it either spins for a few seconds or does nothing other than report that I've been disconnected.

But sometimes, if I click connect again while it's trying the first time, I'll get through and be connected for up to 15 minutes(usually shorter).

If I turn the modem on and off using a hotkey on my Gigabyte T1028, which I installed it in, it sometimes doesn't show up in nm-applet again, and sometimes does nothing. It shows up in lsusb in both cases.

Restarting nm-applet and NetworkManager does nothing.

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
CheckboxSubmission: bcc9fd490776751af95c899d27f094c3
CheckboxSystem: a08dc205096b01b638ef8ad02cad52cb
Date: Sat Oct 3 10:30:51 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.125 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu2
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RfKill:
 1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
Tags: ubuntu-unr
Uname: Linux 2.6.31-11-generic i686

[Andrew (andrew-cranna-gmail-deactivatedaccount)]

I have a Huawei K3715 and it does the same thing.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446146, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.