After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 602253 - Cannot use e169 Huawei modem in Ubuntu Karmic.
Cannot use e169 Huawei modem in Ubuntu Karmic.
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: ModemManager
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-11-17 22:12 UTC by Mark Thiele
Modified: 2010-06-04 20:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mark Thiele 2009-11-17 22:12:05 UTC
The e169 worked great in ubuntu 9.04, but won't in 9.10.

In Karmic the e169 does not appear in the drop-down menu, but sometimes after plugging in the device, network-manager says that the network was disconnected.

When plugging in the USB modem this error appears:

Unable to mount Optus Wireless  
Error mounting: mount exited with exit code 32: mount: block device /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1 already mounted or /media/Optus Wireless   busy
Comment 1 Mark Thiele 2009-11-17 22:15:17 UTC
Bug also reported by another person @ launchpad https://bugs.launchpad.net/network-manager/+bug/476466
Comment 2 Dan Williams 2009-11-18 00:58:15 UTC
What is the output of 'dmesg' after plugging the device in, and what does 'ls /sys/class/tty/" say about 1 minute after plugging the device in?

Do you have usb_modeswitch set up to switch the device to modem mode?
Comment 3 Dan Williams 2009-11-18 00:59:43 UTC
If the device never gets into modem mode (huawei devices *usually* don't need usb_modeswitch, but it doesn't hurt to try) it could also be a kernel bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446146
Comment 4 André Klapper 2010-06-04 20:29:17 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!