Problem Internet connection with 3G Dongel Runing 11.4 Classic (Resolved)

Linux Support
1

Having seen another post, I installed USB Modeswitch but this did not help.

Below is the readout of attached usb devices.

userone@office2:~$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 009: ID 05c6:1000 Qualcomm, Inc. Mass Storage Device
Bus 002 Device 006: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT73]
Bus 002 Device 003: ID 0c45:627b Microdia PC Camera (SN9C201 + OV7660)
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
userone@office2:~$

Device 9 is the 3G modem the maker is Qualcomm, Inc model Globesurfer i CON 7.2S

(strange that it installed in Peppermint out of the box but not in Ubuntu)

2

Hmm… very odd, it seems 05c6:1000:sVe=GT is missing from the usb-modeswitch-data package in Natty.

There are a number of ways to fix this, but lets try this first…

I’ve added it to a custom configPack.tar.gz, as used in the newer version of usb-modeswitch-data … So download the custom version:

cd ~
wget http://dl.dropbox.com/u/11876059/configPack.tar.gz

Now rename your old configPack.tar.gz to backup-configPack.tar.gz:

sudo mv -v /usr/share/usb_modeswitch/configPack.tar.gz /usr/share/usb_modeswitch/backup-configPack.tar.gz

Now copy the new configPack.tar.gz to /usr/share/usb_modeswitch:

sudo cp -v ~/configPack.tar.gz /usr/share/usb_modeswitch/configPack.tar.gz

Now you may have to reboot, or you may only have to unplug the dongle, wait a few seconds, then replug it… I’m not sure.

Let me know if this works or not, and we’ll take it from there.

3

Problem resolved reboot was not required.

Thanks for your help.