Make an E173s-1 [12d1:14d1] Huawei usb-UMTS-stick work properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
modemmanager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Dear package-management,
I would like to get a Huawei USB-UMTS-stick to work now and persistently in future releases and avoid a kernel stop/crash at the same time.
My stick is a "ProSieben" (delivery company), Vodafone (UMTS-, IP-provider, websession-
The impact is most likely a broader one, at least for the Huawei family, as its solution needs all the changes made for the "E173" within the kernel (modules: option.ko (in usb/serial) and qmi_wwan.ko (in net/usb)) not to long ago and additional ones in modemmanager. With the modifcations described, "my" stick runs, so bear with me, when I get a little more detailed at the start.
With a 'bare bones' "raring ringtail"-Ubuntu, when you plug the stick in, it will after a little while (about 2 minutes) crash Ubuntu in such a way, that only a hard switch-off of the device will help. The reason is, that USB-port 1 (numbering starts with 0) will get a USB tty device (/dev/ttyUSB3 in my case), and as soon as option.ko and following that usb_wwan.ko tries to operate that device, its "queue" will fill up and finally hang the kernel. For my stick, after the usb-modeswitch the (USB-)ports are labeled (GETPORTS-lookup- with SETPORT?
From that moment on, there will be no more kernel stop/crash.
But it still doesn't work! This is where "modemmanager" comes into play: Because there is no "MDM"-entry, it will assign /dev/ttyUSB0 (ok!) and /dev/ttyUSB2 (no so good!) as modem devices. Now when it comes to connecting to the net it will link /dev/ttyUSB2 to the starting pppd (/dev/ttyUSB2 <-> pppd), which will not succeed! It should have been /dev/ttyUSB0! So "NDIS' is the port to choose, here, instead of the missing modem. When you add "NDIS" in addition to "MDM" - as has been done in a PPA for "quantal" [modemmanager_
The problem isn't really new for "raring", but happened in midtime of "quantal", when the "E173"-
My assumption is, that there are (many) more - at least Huawei - devices affected by that "queue"-phenomenon, not just "mine" [12d1:14d1 -> 14c9].
Should I have been unclear, should you need any additional information or have a question, just contact me. I'll do what I can to fix this thing.
By the way, can you arrange for the necessary kernel-fixes to be made, too? You certainly have a better connection than me to the people responsible. That would be nice.
Thanks for the help!
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.
ProcVersionSign
Uname: Linux 3.8.0-19-generic i686
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Fri May 3 15:31:06 2013
InstallationDate: Installed on 2011-03-05 (789 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
MarkForUpload: True
SourcePackage: modemmanager
UpgradeStatus: Upgraded to raring on 2013-04-26 (7 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.