[Huawei E367] cannot connect to 3G

[Kenny Ranerup]

The modem is recognized but when initiating connection in Network Manager it immediately fails to connect.

Modem is recognized by usb_modeswitch and the log seems ok.
Syslog indicates that there's some problem communicating with the modem (it hangs up unexpectedly).

Upgrading to the latest development version of NetworkManager does not fix the bug.

A relevant extract of the log files is:
modem-manager[2392]: <debug> [1322671573.872624] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): --> 'ATD*99***1#<CR>'
modem-manager[2392]: <debug> [1322671573.899074] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): <-- '<CR><LF>CONNECT 28800000<CR><LF>'
modem-manager[2392]: <debug> [1322671573.899341] [mm-port.c:181] mm_port_set_connected(): (ttyUSB0): port now connected
modem-manager[2392]: <info> [1322671573.899643] [mm-modem.c:742] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
modem-manager[2392]: <debug> [1322671573.899788] [mm-generic-gsm.c:4988] simple_state_machine(): (ttyUSB0): simple connect state 6
modem-manager[2392]: <debug> [1322671573.944259] [mm-manager.c:793] device_added(): (net/ppp0): could not get port's parent device
modem-manager[2392]: <debug> [1322671574.194721] [mm-at-serial-port.c:298] debug_log(): (ttyUSB4): <-- '<CR><LF>^BOOT:40286488,0,0,0,99<CR><LF>'
modem-manager[2392]: <debug> [1322671575.360877] [mm-at-serial-port.c:298] debug_log(): (ttyUSB4): <-- '<CR><LF>^RSSI:12<CR><LF><CR><LF>^CSNR:-94,-5<CR><LF>'
modem-manager[2392]: <debug> [1322671575.414620] [mm-serial-port.c:636] data_available(): (ttyUSB0) unexpected port hangup!
modem-manager[2392]: <debug> [1322671575.414781] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close)
modem-manager[2392]: <info> [1322671575.414869] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port...
modem-manager[2392]: <debug> [1322671575.414962] [mm-port.c:181] mm_port_set_connected(): (ttyUSB0): port now disconnected

== Regression details ==
Discovered in version: 11.10
Last known good version: 11.04

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-13-generic-pae 3.0.0-13.22
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6
Uname: Linux 3.0.0-13-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kenny 1513 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8220000 irq 45'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20d6,00100400'
   Controls : 31
   Simple ctrls : 19
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7MHT25WW-1.03'
   Mixer name : 'ThinkPad EC 7MHT25WW-1.03'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Nov 30 07:38:41 2011
HibernationDevice: RESUME=UUID=545bf5b5-c496-488d-8c9f-a3889386d574
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO 766734G
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic-pae root=UUID=36d41344-a385-41a9-af9a-2efb529c0e58 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic-pae N/A
 linux-backports-modules-3.0.0-13-generic-pae N/A
 linux-firmware 1.60
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETB3WW (2.13 )
dmi.board.name: 766734G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NETB3WW(2.13):bd04/30/2008:svnLENOVO:pn766734G:pvrThinkPadX61s:rvnLENOVO:rn766734G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 766734G
dmi.product.version: ThinkPad X61s
dmi.sys.vendor: LENOVO

[Alessandro Menti (elgaton)]

Thanks for reporting.

Could you please upgrade NetworkManager and ModemManager to the latest development build (use the repository located at <https://launchpad.net/~network-manager/+archive/trunk>) and see if the problem still occurs?

In case it does, could you please follow the procedure outlined at <https://wiki.ubuntu.com/DebuggingModemmanager>, in the "Get Debug Logs" section, to get the debug logs specific to your modem, and attach them to this bug report? (The other log files you have already attached are OK, it's just to get the modem-specific messages).

Thanks again for making Ubuntu better!

[Kenny Ranerup (kranerup)]

Latest network manager doesn't work.

[Alessandro Menti (elgaton)]

Thanks for the logs. I am marking again this report as "Confirmed", as per the input from Brian Figg.

Thanks again for making Ubuntu better!

[Michael Basse (michael-alpha-unix)]

But you are not facing this?

https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/927954

[Thomas Hood (jdthood)]

The Huawei E367 is not listed upstream as known to work.

    https://live.gnome.org/NetworkManager/MobileBroadband/

Please file a request upstream asking that this modem be supported by NetworkManager.

    https://bugzilla.gnome.org/browse.cgi?product=NetworkManager

[Mathieu Trudel-Lapierre (cyphermox)]

Setting back the ubuntu task to Confirmed/Medium. There is at least one other instance of this being reported, and we might as well track when an upstream fix will get uploaded.