Huawei E620 USB modem no longer works in 9.10

[Michael Olberg]

Binary package hint: network-manager

My Huawei E620 (sold by Vodafone in NL) works flawlessly in Ubuntu 9.04, but no longer works in 9.10. The device is apparently no longer recognized and I am no longer given the option by network manager to access internet via a broadband connection. Again, this worked like a charm in Jaunty.

$ uname -a
Linux aspire 2.6.31-14-generic #46-Ubuntu SMP Tue Oct 13 16:47:59 UTC 2009 i686 GNU/Linux

All packages updated to Karmic Koala beta release.

Here is the output from dmesg (note the option_instat_callback: error -108),
followed by the relevant part of lsusb -v:

dmesg:
------
[ 1269.743692] usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 1269.744060] option 2-2:1.1: GSM modem (1-port) converter detected
[ 1269.744400] usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 1269.744784] option 2-2:1.0: GSM modem (1-port) converter detected
[ 1269.745234] usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
[ 1269.767143] option: option_instat_callback: error -108
[ 1269.772312] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1269.772371] option 2-2:1.0: device disconnected
[ 1269.772535] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1269.772584] option 2-2:1.1: device disconnected
[ 1269.772739] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1269.772788] option 2-2:1.2: device disconnected
[ 1269.884141] usb 2-2: reset full speed USB device using uhci_hcd and address 3

lsusb -v
--------
Bus 003 Device 003: 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 HUAWEI Mobile
  iSerial 1 ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 108
    bNumInterfaces 4
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3 Data Interface
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 128
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3 Data Interface
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x03 EP 3 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 2
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3 Data Interface
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x85 EP 5 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x05 EP 5 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 3
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x04 EP 4 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
Device Status: 0x0002
  (Bus Powered)
  Remote Wakeup Enabled

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Oct 20 22:35:22 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 129.16.208.0/24 dev eth0 proto kernel scope link src 129.16.208.217 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 129.16.208.1 dev eth0 proto static
Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:

[igneer (ignacio-puyol)]

I have exactly the same problem. I'm thinking about going back to ubuntu 9.04 until this problem is solved. I need that connection.

[Pavel (pavemial)]

The same problem for me with Vodafone K3520 (E620) in Ireland... So upset with new relies of Ubuntu 9.10...

[ClaudioRJ (cmirandarj)]

My modem: ONDA MSA501HS
Worked fine with 8.10 and 9.04
Does not work anymore with 9.10, it appears as pendrive.

[TomasHnyk (sup)]

is not this a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446146

[achab (gzmorell)]

I have had the same problem with Novatel MC950D 1410:4400.
After updating the system with networkmanager from trunk ppa and with not realesed updated (2.6.31-15-generic-pae)
the problem have not dissapeared.
Following the instructions in https://wiki.ubuntu.com/DebuggingModemmanager I noticed that the call number was *99***1#***1#
instead of what I have inserted in knetworkmanager config (*99***1#), I changed the number to *99#, and now it works.
I have had also problems with usb-switch, following this instructions "http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=247&view=next&sid=4e40a70b2235b2e73caaa95451ca898b" now it works. In kubuntu 9.10 the problem seems to be /lib/udev/rules.d/61-modem-switch.rules file.

[Richard de Rivaz (richard-mdr)]

I have the same problem with a Huawei K3520 (Vodafone) dongle. I upgraded from 9.04 UNR to 9.10 and the dongle stopped working. I then did a full new installation of 9.10 UNR with the same result. For a distribution aimed at mobile netbook use this is a very poor situation and IMHO 9.10 UNR should not have been released in this state without a health warning! The options atm seem to be to reinstall 9.04 or to try Moblin 2.1 which says that it now supports 3G.

[Michael Olberg (michael-olberg)]

After having upgraded to linux-image-2.6.31-15-generic, the USB-stick seems to be recognized as a modem (*and* as a storage device). Now, network manager is offering the mobile broadband Vodafone connection, which I had configured before the upgrade to 9.10. However, I am unable to make the connection work. The network manager presents a password dialog (see attachment), but whatever I fill in (neither password nor pincode defined for this connection will work) I don't get a network connection.

[Pieter (diepes)]

Let me try the upgrade to linux-image-2.6.31-15-generic

[Pieter (diepes)]

I had to pick the kernel form the updates.
Rebooted, and all is fine.

I can see the CDROM icon, and the 3G works perfectly.

[Bengt Grahn (bengt-vikingsw)]

I have found that if I restart the system after booting, the modem connection works fine. However, I find restarting one extra time is a bit silly. I reported this bug quite some time ago, before I upgraded from 9.04 to 9.10 (in November), but the problem still remains. What was wrong with the old version of Network manager, since it needed to be modified?

[Bengt Grahn (bengt-vikingsw)]

Of course, it COULD be a kernel problem. How do you install a different kernel, and which one is the one to use?

[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.