iBall 3.5G Connect v2.0 setup on Ubuntu 12.04 issues
Posted: 09 Feb 2014, 09:10
- Recently bought a Laptop with Ubuntu 12.04LS(Kernel 3.2.0-39-generic) on it.
- I'm unable to `plug & use` iBall 3.5G Connect v2.0 USB DataCard
- However, on the same OS Huawei E1731 USB DataCard works perfectly 'plug & use(play)'.
- Huawei E1731 comes with separate installer(.bin) for Linux, however doesn't need manual intervention. iBall3.5G comes with only 'scripts' that I'm attaching below.
- both HuaweiE1731 & iBall3.5G have AirTel SIM but different Mobile#(MSISDN/MDN)
- both HuaweiE1731 & iBall3.5G work on WinXP(SP3), thanks to bundled drivers s/w(AutoRun)
/var/log/kern.log excerpt when USB Data Card is plugged in:(Invalid Interface)
And Vendor & Product ID details:
Verbose Details:
Data card has shell scripts to configure & run the MoDem:
dialup shell script; run as root(sudo)
- it's apparent that /dev/ttyUSB2 is used for data
wcdma file which is called from dialup script:
- Telecom Operator doesn't provide username/password
w-connect-chat file which is referred in wcdma
1. After spending hours on Internet I found sudo echo 05C6 0016 > /sys/bus/usb-serial/drivers/option1/new_id
should work and give me some /dev/ttyUSBx.
2. Also cross checked TargetVendor:TargetProduct pair using SniffUSB.exe on winXP, it's 05C6:0016. dialup shell script seems to be in right direction.
PS: I did juggle with suggestions given on over a dozen websites about gnome-ppp, minicom, modprobe, usb_modeswitch etc. None of them worked out for me.
Am I right assuming that first the command sudo echo 05C6 0016 > /sys/bus/usb-serial/drivers/option1/new_id should generate some /dev/ttyUSBx dev files?
Please push me in right direction.
- I'm unable to `plug & use` iBall 3.5G Connect v2.0 USB DataCard
- However, on the same OS Huawei E1731 USB DataCard works perfectly 'plug & use(play)'.
- Huawei E1731 comes with separate installer(.bin) for Linux, however doesn't need manual intervention. iBall3.5G comes with only 'scripts' that I'm attaching below.
- both HuaweiE1731 & iBall3.5G have AirTel SIM but different Mobile#(MSISDN/MDN)
- both HuaweiE1731 & iBall3.5G work on WinXP(SP3), thanks to bundled drivers s/w(AutoRun)
/var/log/kern.log excerpt when USB Data Card is plugged in:(Invalid Interface)
Code: Select all
root@SiRi-Inspiron-3521:~# tailf /var/log/kern.log
kernel: [12598.373601] usb 3-4: USB disconnect, device number 11
kernel: [12607.331240] usb 3-2: new high-speed USB device number 12 using xhci_hcd
kernel: [12607.348772] usb 3-2: config 1 has an invalid interface number: 5 but max is 0
kernel: [12607.348788] usb 3-2: config 1 has no interface number 0
kernel: [12607.352291] scsi21 : usb-storage 3-2:1.5
kernel: [12608.352700] scsi 21:0:0:0: CD-ROM 3G Modem Mass Storage 2.31 PQ: 0 ANSI: 2
kernel: [12608.357251] sr1: scsi-1 drive
kernel: [12608.357554] sr 21:0:0:0: Attached scsi CD-ROM sr1
kernel: [12608.357754] sr 21:0:0:0: Attached scsi generic sg3 type 5Code: Select all
root@SiRi-Inspiron-3521:~# lsusb
Bus 003 Device 012: ID 05c6:f000 Qualcomm, Inc. Code: Select all
root@SiRi-Inspiron-3521:~# lsusb -v -d 05c6:f000
Bus 003 Device 012: ID 05c6:f000 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0xf000
bcdDevice 0.00
iManufacturer 3
iProduct 2 iBall 3.5G Wireless Modem
iSerial 4 1234567890ABCDEF
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 iBall 3.5G Wireless Modem
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 5
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powereddialup shell script; run as root(sudo)
- it's apparent that /dev/ttyUSB2 is used for data
Code: Select all
# after some sanity checks
sudo modprobe option
sudo chmod 777 /sys/bus/usb-serial/drivers/option1/new_id
[b]sudo echo 05C6 0016 > /sys/bus/usb-serial/drivers/option1/new_id[/b]
sleep 3
if [ "$(ls /dev/ttyUSB* |grep "ttyUSB2")" != "" ]
then
echo "now connect to the internet......" -n 1
pppd call wcdma &
read -p "wait for dial up.... " -n 1
else
echo "Please check the datacard is plugged in and the cdrom has been ejected!"
read -p "Press any key to exit.... " -n 1
exit -1
fi- Telecom Operator doesn't provide username/password
Code: Select all
/dev/ttyUSB2
460800
modem
debug
nodetach
usepeerdns
defaultroute
user
password
0.0.0.0:0.0.0.0
lcp-echo-interval 120
asyncmap 0xa0000
connect 'chat -s -v -f /etc/ppp/peers/w-connect-chat'Code: Select all
TIMEOUT 15
'' ATZ
OK ATQ0
OK ATV1
OK ATE1
OK ATS0=0
OK AT&C1
OK AT&D2
OK AT+CGDCONT=1,"IP","airtelgprs.com"
# Set your APN replace airtelgprs.com
#OK AT+CGEQREQ=1,2,0,0,0,0,0,1500,"0E0","0E0",,0,0
OK ATDT*99#
CONNECT ''should work and give me some /dev/ttyUSBx.
2. Also cross checked TargetVendor:TargetProduct pair using SniffUSB.exe on winXP, it's 05C6:0016. dialup shell script seems to be in right direction.
PS: I did juggle with suggestions given on over a dozen websites about gnome-ppp, minicom, modprobe, usb_modeswitch etc. None of them worked out for me.
Am I right assuming that first the command sudo echo 05C6 0016 > /sys/bus/usb-serial/drivers/option1/new_id should generate some /dev/ttyUSBx dev files?
Please push me in right direction.