9.10-final / kernel 2.6.31-14-generic / NetworkManager doesn't recognise Huawei E1692
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
The usb 3g modem is nowhere to be seen as a cd-rom nor as a modem.
Simply **nothing** happens when I plug in the modem.
Tried:
# dmesg|tail
[ 3587.254727] usbserial_generic 2-1:1.1: generic converter detected
[ 3587.254825] usb 2-1: generic converter now attached to ttyUSB1
[ 3587.428650] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 3587.428684] usbserial_generic 2-1:1.0: device disconnected
[ 3588.449597] Initializing USB Mass Storage driver...
[ 3588.452463] scsi10 : SCSI emulation for USB Mass Storage devices
[ 3588.452581] usbcore: registered new interface driver usb-storage
[ 3588.452585] USB Mass Storage support registered.
[ 3588.453272] usb-storage: device found at 8
[ 3588.453274] usb-storage: waiting for device to settle before scanning
# lsusb | grep Huawei
Bus 002 Device 007: ID 12d1:1446 Huawei Technologies Co., Ltd.
sudo rmmod usb-storage
sudo modprobe -r option
sudo modprobe -r usbserial
sudo modprobe usbserial vendor=0x12d1 product=0x1446
sudo pppd ttyUSB0 (also ttyUSB1)
No way to get the modem working as on 8.10 and 9.04
| description: | updated |
| summary: |
- 9.10-final / kernerl 2.6.31-14-generic / NetworkManager doesn't - recognise Huawei E1692 + 9.10-final / kernel 2.6.31-14-generic / NetworkManager doesn't recognise + Huawei E1692 |
| Brian Murray (brian-murray) wrote | #1 |
| Changed in network-manager (Ubuntu): | |
| status: | New → Confirmed |
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.