| 2008-08-18 10:18:04 |
Arne Goetje |
bug |
|
|
added bug |
| 2008-08-18 10:18:04 |
Arne Goetje |
bug |
|
|
added attachment 'usb_modeswitch.conf' (usb_modeswitch.conf with config for MU-Q101 enabled.) |
| 2008-08-18 10:18:51 |
Arne Goetje |
bug |
|
|
added attachment 'lshal_dump.txt' (lshal dump) |
| 2008-08-18 10:19:16 |
Arne Goetje |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-08-22 14:05:39 |
Arne Goetje |
description |
Binary package hint: network-manager
A lot of USB 3G modems also carry a USB storage device, which contains the Windows drivers. These devices are detected as usb-storage and mounted automatically when plugged in.
In order to be able to use the modem instead, the USB product ID needs to be switched.
There is a tool to do this: http://www.draisberghof.de/usb-modeswitch/
Example (MU-Q101):
The device shows has a vendor ID of 0x0408 and a product ID of 0x1000 when plugged in.
It needs to switch the product ID to 0xea02 to enable the modem.
The following steps need to be done to do this:
1. When first plugged in, the device will be recognized as usb-storage device and automatically mounted. Unmount the device.
2. As root:
2.1. run usb-modeswitch
2.2. tell the kernel that the device product ID has changed:
2.2.1. get the port number where the device is connected by looking into the dmesg output, e.g.: 1-2
2.2.2. send a "suspend" to that device: echo "suspend" > /sys/bus/usb/devices/1-2/power/level
2.2.3. the device will wake up again and then carry the correct product ID (confirm with lsusb)
2.3. Load either the option module, or the usbserial module, depending on the device (for MU-Q101 usbserial is necessary): modprobe usbserial vendor=0x0408 product=0xea02
3. Now, 4 ttyUSB devices should have been created: ttyUSB0~3.
3.1. For MU-Q101 only: send the following AT command to /dev/ttyUSB2 (I currently do this manually with minicom): AT+CFUN=1
4. Use ttyUSB0 to connect with ppp.
The affected devices are listed in the attached usb_modeswitch.conf file. |
Binary package hint: network-manager
A lot of USB 3G modems also carry a USB storage device, which contains the Windows drivers. These devices are detected as usb-storage and mounted automatically when plugged in.
In order to be able to use the modem instead, the USB product ID needs to be switched.
There is a tool to do this: http://www.draisberghof.de/usb_modeswitch/
Example (MU-Q101):
The device shows has a vendor ID of 0x0408 and a product ID of 0x1000 when plugged in.
It needs to switch the product ID to 0xea02 to enable the modem.
The following steps need to be done to do this:
1. When first plugged in, the device will be recognized as usb-storage device and automatically mounted. Unmount the device.
2. As root:
2.1. run usb-modeswitch
2.2. tell the kernel that the device product ID has changed:
2.2.1. get the port number where the device is connected by looking into the dmesg output, e.g.: 1-2
2.2.2. send a "suspend" to that device: echo "suspend" > /sys/bus/usb/devices/1-2/power/level
2.2.3. the device will wake up again and then carry the correct product ID (confirm with lsusb)
2.3. Load either the option module, or the usbserial module, depending on the device (for MU-Q101 usbserial is necessary): modprobe usbserial vendor=0x0408 product=0xea02
3. Now, 4 ttyUSB devices should have been created: ttyUSB0~3.
3.1. For MU-Q101 only: send the following AT command to /dev/ttyUSB2 (I currently do this manually with minicom): AT+CFUN=1
4. Use ttyUSB0 to connect with ppp.
The affected devices are listed in the attached usb_modeswitch.conf file. |
|
| 2008-09-17 01:06:27 |
Alexander Sack |
title |
0.7, 3G - USB devices not detected |
0.7, 3G - USB devices not detected/need modeswitch but as usb-storage device |
|
| 2008-09-17 01:17:30 |
Alexander Sack |
title |
0.7, 3G - USB devices not detected/need modeswitch but as usb-storage device |
0.7, 3G USB devices detected by usb-storage maybe need modeswitch |
|
| 2008-09-18 14:51:08 |
Runar Ingebrigtsen |
bug |
|
|
added attachment '99-telenor.rules' (udev rule for telenor (option modem)) |
| 2008-10-07 01:07:09 |
Alexander Sack |
network-manager: status |
New |
Confirmed |
|
| 2008-10-07 01:07:09 |
Alexander Sack |
network-manager: importance |
Undecided |
Medium |
|
| 2008-10-07 01:07:09 |
Alexander Sack |
network-manager: statusexplanation |
|
|
|
| 2008-10-07 01:07:24 |
Alexander Sack |
bug |
|
|
assigned to network-manager |
| 2008-10-19 23:00:08 |
Laurent GUERBY |
bug |
|
|
added attachment 'lshal.txt' (lshal on my PC) |
| 2009-09-03 22:11:30 |
Victor Vargas |
bug watch added |
|
http://bugzilla.gnome.org/show_bug.cgi?id=594085 |
|
| 2009-09-03 22:11:30 |
Victor Vargas |
network-manager: importance |
Undecided |
Unknown |
|
| 2009-09-03 22:11:30 |
Victor Vargas |
network-manager: status |
New |
Unknown |
|
| 2009-09-03 22:11:30 |
Victor Vargas |
network-manager: remote watch |
|
GNOME Bug Tracker #594085 |
|
| 2009-09-03 23:03:52 |
Bug Watch Updater |
network-manager: status |
Unknown |
Invalid |
|
| 2009-11-13 12:19:14 |
Przemek K. |
network-manager (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2010-09-15 21:46:01 |
Bug Watch Updater |
network-manager: status |
Invalid |
Unknown |
|
| 2010-09-15 21:46:01 |
Bug Watch Updater |
network-manager: importance |
Unknown |
Medium |
|
