connections-problems with huawei e230

[karlrt]

Binary package hint: network-manager

my huawei e230 G3 modem works usually well after a fresh restart. Once the connection is lost (doesnt happen wery often) or after suspend, reconnection doesnt work at all! If i disconnect the modem physically, it usually doesnt show up again in network-manager until fresh restart.

Allthough i dont know what caused the problem, i am happy to provide more information if you ask (syslogs etc)

oh, using karmic amd64, fresh alpha6 install

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Sep 23 15:29:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.64.64.64 dev ppp0 proto kernel scope link src 77.117.117.158
 169.254.0.0/16 dev ppp0 scope link metric 1000
 default via 10.64.64.64 dev ppp0 proto static
Package: network-manager 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: network-manager
Uname: Linux 2.6.31-10-generic x86_64

[karlrt (karlrt)]

the next attachment is a prepared daemon-log with
1) disappearance of the modem in networkmanager
2) connection established after restart, but no ping
3) how it should be allways, not after at least 3 tries and one restart

[Neurocid (joni-kaki)]

This affects me also, i can also help on triaging. Sometimes modem doesn't show up on network manager even after fresh boot. I have removed "connect automatically" from connection properties. This seems to make modem more likely to appear.

[GeorgeVita (8-launchpad-mhnyma-com)]

The 'suspend/resume' problem is reproducible with my Huawei E169 on EeePC1000H if I suspend without manually disconnected (from network manager icon). After resume, broadband connection option is NOT appearing at nm icon. This can be 'solved' with:
sudo killall modem-manager
which 'kills' modem-manager process and a new process is created automatically.

After resume I checked one by one all running processes (using ps -A) before and after 'sudo killall modem-manager' and did not found any difference except the new mm process number (from #912 to #3044).
The same problem rarely appears on cold boot with modem attached (3-5%) but could not be reproducible to report it.

Generally it is not a 'good manner' to suspend without disconnecting first but it happens. Also most times we remove the external USB 3G modem as it could be broken accidentally. At this case the problem rarely appears (3-5% noted above) but cannot be done with internal 3g modems.

This 'bug' seems to me similar to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/416913
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405053

Below is dmesg after resume:

[ 2306.876081] usb 3-2: reset full speed USB device using uhci_hcd and address 2
[ 2307.030136] option 3-2:1.0: no reset_resume for driver option?
[ 2307.030148] option 3-2:1.1: no reset_resume for driver option?
[ 2307.030157] option 3-2:1.2: no reset_resume for driver option?
[ 2307.030434] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 2307.030465] option 3-2:1.0: device disconnected
[ 2307.030584] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 2307.030622] option 3-2:1.1: device disconnected
[ 2307.030739] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 2307.030776] option 3-2:1.2: device disconnected
[ 2307.140082] usb 5-1: reset full speed USB device using uhci_hcd and address 2
[ 2307.863142] btusb 5-1:1.0: no reset_resume for driver btusb?
[ 2307.863154] btusb 5-1:1.1: no reset_resume for driver btusb?
[ 2308.112763] option 3-2:1.0: GSM modem (1-port) converter detected
[ 2308.112912] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 2308.113111] option 3-2:1.1: GSM modem (1-port) converter detected
[ 2308.113231] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2
[ 2308.113401] option 3-2:1.2: GSM modem (1-port) converter detected
[ 2308.113516] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB3
[ 2308.113743] PM: resume devices took 4.144 seconds
[ 2308.113810] PM: Finishing wakeup.
[ 2308.113814] Restarting tasks ... done.

Regards,
George

[karlrt (karlrt)]

for me, this is a regression from jaunty, i just tried the livecd and everything works fine:

plugged in from the start: detecting/connecting works
suspend/resume: detecting/connecting works
plug out/plug in again while sys is up: detecting/connecting works

so no problems under jaunty!

[Lance Stuetzle (lancestu-gmail)]

Huawei E620 Modem- CDMA
Network Manager regression from Jaunty. (worked excellent there)
Network Manager not picking up modem.
Forced to reboot to get connected to 3G.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Lance Stuetzle,
for 'Network Manager not picking up modem' without reboot try:

sudo modprobe -r option
sudo modprobe option

Regards,
George

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