Support for BSNL 3G (Teracom USB devices)

Bug #673459 reported by Amit Mendapara
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
usb-modeswitch-data (Ubuntu)
Fix Released
Undecided
Didier Raboud

Bug Description

Binary package hint: usb-modeswitch-data

I have added support for Teracom HSDPA datacard distributed by BSNL. Here I am attaching the patch against the recent upstream revision.

Tags: patch
Revision history for this message
Amit Mendapara (cristatus) wrote :
tags: added: patch
Revision history for this message
Amit Mendapara (cristatus) wrote :

This patch is tested with Teracom (Linktop / LW273) usb datacard. I am not sure about LW272 model though.

Revision history for this message
Mandar Vaze (mandarvaze) wrote :

Tested this patch with LW272 - works.

Revision history for this message
Amit Mendapara (cristatus) wrote :

The patch works with both Linktop/LW272 and Linktop/LW273 distributed by BSNL.

Changed in usb-modeswitch-data (Ubuntu):
status: New → Confirmed
Revision history for this message
Bhavani Shankar (bhavi) wrote :

Same here

regards

Revision history for this message
Amit Mendapara (cristatus) wrote :

Here is the lsusb output.

Revision history for this message
Amit Mendapara (cristatus) wrote :

And here is for LW272. The previous one is for LW273 and both are identical.

Revision history for this message
nagaraj (hamlet32) wrote :

hi, i too have a detection problem with teracom lw272. how do i use/apply this patch to usb_modeswitch?
thanks

Revision history for this message
nagaraj (hamlet32) wrote :
Download full text (8.5 KiB)

sorry, forgot to attatch lsusb.txt
actually the command returned
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

but a .txt file appeared on desktop and it had the following contents.

Bus 004 Device 005: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 8
  idVendor 0x03eb Atmel Corp.
  idProduct 0x3301 at43301 4-Port Hub
  bcdDevice 3.00
  iManufacturer 0
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 4
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 64mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 9 Hub
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0 Full speed (or root) hub
      iInterface 5
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 255

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 64
  idVendor 0x1d6b Linux Foundation
  idProduct 0x0001 1.1 root hub
  bcdDevice 2.06
  iManufacturer 3
  iProduct 2
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower ...

Read more...

Revision history for this message
Amit Mendapara (cristatus) wrote :

The patch is already accepted upstream. You can get upstream copy using git as:

git clone git://git.debian.org/collab-maint/usb-modeswitch.git
git clone git://git.debian.org/collab-maint/usb-modeswitch-data.git
git clone git://git.gnome.org/mobile-broadband-provider-info

Also, try the latest versions of ModemManager and NetworkManager from the NetworkManager daily PPA (https://launchpad.net/~network-manager/+archive/trunk) for better experience. I have implemented ModemManager driver for Linktop devices which is accepted upstream.

sudo add-apt-repository ppa:network-manager/trunk
sudo update
sudo upgrade

Then restart your computer and enjoy!

Revision history for this message
nagaraj (hamlet32) wrote :

thanks,
but no luck for me,
my comp refuses to show the modem. i ran all the commands above and did what the tweaking you have suggested in http://amit-mendapara.blogspot.com/2010/11/amazing-bsnl-3g.html. still no luck. any suggsetions?
one more thing sudo update and sudo upgrade did not work for me. had to 'sudo apt-get update' and 'sudo apt-get upgrade'.
waiting for your response.

Revision history for this message
Amit Mendapara (cristatus) wrote :

Oh, sorry. The commands should be:

sudo apt-get update
sudo apt-get upgrade

BTW, both the models are reported working well with these updates. Would you attach few more information here? Please, don't paste the output but attach txt files of the output of following commands:

sudo lsusb -v > ~/Desktop/lsusb.txt
sudo usb-devices > ~/Desktop/usb-devices.txt

After issuing `usb_modeswitch -v 230d -p 0001 -u 3` command, run the `usb-devices` again.

sudo usb-devices > ~/Desktop/usb-devices-2.txt

Thanks

Revision history for this message
Amit Mendapara (cristatus) wrote :

I have backported the latest upstream version of usb_modeswitch to Ubuntu Maverick (10.10). You can find the packages with this PPA (https://launchpad.net/~cristatus/+archive/nm-ppa).

Revision history for this message
nagaraj (hamlet32) wrote :

added your ppa. now the network manager simply returns 'gsm network disconnected' after connecting the modem. i am attaching the response to usb_modeswitch -v 230d -p 0001 -u 3
Looking for default devices ...
 Found devices in default mode or class (1)
Accessing device 000 on bus 001 ...
Getting the current device configuration ...
Error: getting the current configuration failed (error -1). Aborting.

and 'sudo usb-devices > ~/Desktop/usb-devices-2.txt' returned

/usr/bin/usb-devices: line 79: printf: 08: invalid octal number
/usr/bin/usb-devices: line 79: printf: 09: invalid octal number.

i am attatching the lsusb.txt and usb-devices.txt

these were all run while the teracom modem was connected and the red LED was flashing

Revision history for this message
nagaraj (hamlet32) wrote :
Revision history for this message
Amit Mendapara (cristatus) wrote :

After looking at your usb-devices-2.txt, I confirm it's switched successfully and now it should work without any issue. That error stating `Error: getting the current configuration failed (error -1). Aborting.` seems to be from the latest changes in usb_modeswitch package but just ignore them.

Revision history for this message
nagaraj (hamlet32) wrote :

thanks a lot, it seems to be working now. though few strange things happened initially -the first couple of times it would try to connect and then stop recognising the modem. then i tried using my airtel sim (gprs) with teracom modem amd it connected alright without any problems. i tried again with bsnl 3g sim but it failed. after a couple of atempts it connectd and is working now. i dont understand the strange behaviour, but i am happy that it is working. thanks a lot for your prompt help and assistance.

Changed in usb-modeswitch-data (Ubuntu):
status: Confirmed → Fix Committed
status: Fix Committed → Confirmed
Revision history for this message
nagaraj (hamlet32) wrote :

hi amit,
i am back here again with more troubles.
the teracom modem worked well for 2days and then again it was back to its adamant behaviour. the modem is not seen at all and althouigh everytime i re plug the modem in, the network manager strts searching but fails to register anything. how do i use the modem manger and network manager as suggested in your post #10 above?

Revision history for this message
Amit Mendapara (cristatus) wrote :

nagraj,

It could be due to service outage in your area. I am seeing frequent disconnection problem here (device disconnects regularly on 250mb of data usages). BTW, follow this guide (https://wiki.ubuntu.com/DebuggingNetworkManager) and attach the debug info here.

Revision history for this message
nagaraj (hamlet32) wrote :

i need help on the following to use the debugging network manager guide -
i am supposed to run " sudo modprobe -r DRIVER" but i dont know what the driver is. "sudo modprobe -r" returned a lot of options, which i could not understand.
in the paragraph on debugging 3G, i need to run "$ /lib/udev/nm-modem-probe --verbose --export /sys/class/tty/ttyUSB" or "$ /lib/udev/nm-modem-probe --verbose --export /sys/class/tty/ttyACM" , both return "command not found".
other things i tried are - i inserted the 3G sim to my mobile (nokia E62) to check signals and signals are quite fine.
i added the daily update ppa from 'network manager' page (https://launchpad.net/~network-manager/+archive/trunk); it did not make any difference!
another thing i have noticed is, i also have a wireless router connected to an adsl modem ( bsnl broadband) connects through 'auto eth0', which of course is the default connection. when i have 'auto eth0' active and connect the 3G modem, the network manager detects it and connects but i cant use that connection. the moment i disconnect 'auto eth0' the 3G connection also drops.

plese let me know how to find out what driver is installed and i will post the result of "sudo modprob -r DRIVER".
thanks a lot
nagaraj

Revision history for this message
nagaraj (hamlet32) wrote :

forgot to mention one more thing.
is there any way of using wireless router so that other computers can connect to the network wirelessly and can use the internet connection of 3Gmodem ( that is if at all it starts functioning). in other words is there anything like 'share this internet connection'?
thanks amit

Revision history for this message
Amit Mendapara (cristatus) wrote :

nagaraj,

See the notes on that page. I actually forgotten to mention (https://wiki.ubuntu.com/DebuggingModemmanager). That modprobe stuff was required with old NetwormManager 0.7 release.

FYI, with this and other related fixes (available via my network manager ppa), my LW273 device is working perfect.

BTW, you can share your internet connection by creating ad-hoc wifi connection if your wireless adapter supports it else you should try with any wifi router that supports OpenWRT or dd-wrt firmware. There are also few models available in market with built in 3G SIM slot.

Revision history for this message
nagaraj (hamlet32) wrote :

i ran the debuggingmodemmanager commands and got the following logs (attatchments)

Revision history for this message
nagaraj (hamlet32) wrote :

and this. on running the last command 'sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log.txt' to restart nm and to save the log files, the network manager restarted and now it detects my teracom modem and connects but it is not connecting to my wired connection 'auto eth0'.

Revision history for this message
nagaraj (hamlet32) wrote :

forgot to mention - now my bsnl 3g connection is displayed as 'bsnl connection1 (BSNL/cellone HSDPA). hopefully this will stay. but i also need to connect to my auto eth0.
thank you so much. let me know if the log files mean anything.

Revision history for this message
nagaraj (hamlet32) wrote :

i rebooted and tested again- my network manager shows both auto eth0 and bsnl 3g as available but connects only to bsnl 3g now and does not connect to auto eth0. have i fired some conf files in the process?
thanks for your patience and help.

Revision history for this message
Amit Mendapara (cristatus) wrote : Re: [Bug 673459] Re: Support for BSNL 3G (Teracom USB devices)

Nagaraj,

Looking at your logs, I am sure your BSNL 3G connection is now working
however I am not sure about the issue with your eth0 (wireline connection).

BTW, I have used wireline connection along with my BSNL EVDO connection
previously (with multihoming). So it should work with 3G also.

Regards
--
Amit

On Tue, Dec 21, 2010 at 10:39 PM, nagaraj <email address hidden> wrote:

> i rebooted and tested again- my network manager shows both auto eth0 and
> bsnl 3g as available but connects only to bsnl 3g now and does not connect
> to auto eth0. have i fired some conf files in the process?
> thanks for your patience and help.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/673459
>
> Title:
> Support for BSNL 3G (Teracom USB devices)
>

Revision history for this message
nagaraj (hamlet32) wrote :

sorry,
you must be wondering where have i disappeared. no secret - both my internet accesses had stopped working ( auto eth0 and bsnl 3g) when i tried to correct the isssue of 'auto eth0 disconnect'. tried various things but nothing seemed to work. realised for the frst time how difficult it gets if one is cut off from the net . finally did a clean reinstallation of maverick to get the broadband working. (3g still not working) again went through your bug fix and added your ppa and ran in debugging mode but it did not work. but the same actions have made my laptop ( again maverick) recognise and connect through bsnl 3g. thanks a lot for all your help. looks like i will leave at it. just wanted to let you know what happened. regards and thanks again.

Revision history for this message
Amit Mendapara (cristatus) wrote :

Nagajar,

I just fixed few more bugs (reported upstream) in modem-manager and uploaded
the patched version to my ppa. Now my LW273 modem is working like a charm.
Try upgrading to the latest version from my ppa. BTW, I am not sure what's
happening in your case but I haven't faced any such issue since I started
using this device.

Regards
--
Amit

On Sat, Dec 25, 2010 at 5:41 PM, nagaraj <email address hidden> wrote:

> sorry,
> you must be wondering where have i disappeared. no secret - both my
> internet accesses had stopped working ( auto eth0 and bsnl 3g) when i tried
> to correct the isssue of 'auto eth0 disconnect'. tried various things but
> nothing seemed to work. realised for the frst time how difficult it gets if
> one is cut off from the net . finally did a clean reinstallation of maverick
> to get the broadband working. (3g still not working) again went through your
> bug fix and added your ppa and ran in debugging mode but it did not work.
> but the same actions have made my laptop ( again maverick) recognise and
> connect through bsnl 3g. thanks a lot for all your help. looks like i will
> leave at it. just wanted to let you know what happened. regards and thanks
> again.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/673459
>
> Title:
> Support for BSNL 3G (Teracom USB devices)
>

Revision history for this message
Didier Raboud (odyx) wrote :

Tagging as "fix committed" as package is available in Debian experimental

Changed in usb-modeswitch-data (Ubuntu):
status: Confirmed → Fix Committed
assignee: nobody → Didier Raboud (odyx)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package usb-modeswitch-data - 20101222-2

---------------
usb-modeswitch-data (20101222-2) experimental; urgency=low

  * Add a usb-modeswitch-data-packed package that ships the compressed
    switching data (Closes: #578024)
  * Add 02_umdp_archive_in_usr.patch to install the archive to /usr/share
    instead of /etc

  * Use my new @d.o address and remove the DMUA flag.

usb-modeswitch-data (20101222-1) experimental; urgency=low

  * New upstream release
    + New devices
     [0e8d:7109] MediaTek Wimax USB Card
     [16d8:6281] C-motech CHU-628S
    × Devices updates
     [1a8d:1000] BandRich BandLuxe C100, C120, C170, C270
  * Remove 02_no_tclsh_overhead patch; merged upstream.
  * Bump Standards to 3.9.1 without changes needed.

usb-modeswitch-data (20101202-1) experimental; urgency=low

  * New upstream release
    + New devices
     [12d1:1553] Huawei E1553
     [12d1:1c0b] Huawei E173s
     [230d:0001] Linktop LW272/LW273 (BSNL Teracom) (LP: #673459)
    × Devices updates (see ChangeLog for details)
     [0471:1210] Vodafone MD950 (Wisue Technology)
     [0471:1237] Philips TalkTalk (NXP Semiconductors "Dragonfly")
     [05c6:2001] D-Link DWM-162-U5, Micromax MMX 300c
     [0930:0d46] Toshiba G450
     [0fce:d103] Sony Ericsson MD400G
     [1004:607f] LG HDM-2100 (EVDO Rev.A USB modem)
    - Refresh patches.

usb-modeswitch-data (20101128-1) experimental; urgency=low

  * New upstream release
    + New devices
     [0421:0622] Nokia CS-17
     [0421:0627] Nokia CS-18
     [05c7:1000] Qtronix EVDO 3G Modem (for TianYi)
     [0d46:45a1] Kobil mIdentity 3G (1)
     [0d46:45a5] Kobil mIdentity 3G (2)
     [0fd1:1000] GW D301 (Advinne AMC)
     [1004:6190] LG AD600
     [106c:3b05] Pantech / UTStarcom UMW190 (Verizon) (LP: #657129)
     [1edf:6003] AirPlus MCD-800
    × Devices updates (see ChangeLog for details)
     [0482:024d] Kyocera W06K CDMA modem
     [12d1:****] Huawei devices
     [1410:5010] Novatel Wireless devices
     [19d2:****] ZTE devices
     [1a8d:1000] BandRich BandLuxe C100, C120, C170, C270 (merge)
     [1bbb:f000] Alcatel X200/X200L/X060S
    - Refresh patches.

  * Bump usb-modeswitch Recommends and Breaks against to 1.1.5
 -- Mathieu Trudel-Lapierre <email address hidden> Fri, 04 Feb 2011 12:06:03 +0000

Changed in usb-modeswitch-data (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.