Evolution-Data Optimized or EvDO yet another wireless telecommunications technology to offer you better internet connectivity on the Go! It offers more mobility and advantages over your WiFi. Learn more about EvDO here.


I always wanted wireless connectivity which is cheap, affordable and reliable. Reliance and TATA Indicom did come out with various solutions with their CDMA products like PCMCIA card for laptop and then USB modules which can be plugged into any computer to gain access to internet. Now almost every one provides one or the other solutions for internet. I always enjoyed the internet on my laptop via reliance CDMA connection on my Nokia cell phones (6255 and 2112) and they were ok and better than the dial-up connections which I used to use at home. It was easy for me to configure the cell phones to work on Linux. Still it was very costly.

I found BSNL EvDO solution much affordable and I could make it work on my Dell M1210 which runs on Ubuntu 7.10 (Gutsy Gibbon). It will just cost you 500 + tax every month and you have to give 1000 Rs as initial payment for the device. Once you have the device in your hand, you have unlimited access to internet 24×7. Depending on proximity and the line of sight to the tower EvDO device would give 2.4 MBPS connections. At present in Bangalore average connection speed is 144 kbps. 1X CDMA network towers are still evolving in various parts of the city. In near future we can expect a better connectivity and high bandwidth via these cute little devices which would match broadband speed.

bsnl-evdopreview.jpg

Image by hpn :)

Lets see how I started using this device on my Linux distribution (You can follow the same steps to configure this device on any Linux distribution) :

Device : ZTE EV-DO AC8700 800M

Product Vendor : Qualcomm, Inc.

1) Insert the EvDO device into USB port

2) Check whether the device is getting detected on your system or not. You can issue the following command in console :

#sudo tail -f /var/log/messages

This will result in following messages if the device is detected

Mar 4 09:27:42 techfiz kernel: [ 8251.024000] usb 4-1: configuration #1 chosen from 1 choice
Mar 4 09:27:42 techfiz kernel: [ 8251.028000] usbserial_generic 4-1:1.0: generic converter detected
Mar 4 09:27:42 techfiz kernel: [ 8251.028000] usb 4-1: generic converter now attached to ttyUSB0

In the above lines ttyUSB0 is the device file for your modem. This file gets created automatically if the required modules are available. Else you will see some error messages.

Note :You might face an issue while activating this device on Ubuntu 7.04 and 7.10 as there have made some modifications to the USB serial device mappings. To resolve this issue, edit the file /etc/init.d/mountdevsubfs.sh.

Find the function do_start () and ensure that you have all the following lines.

#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb

The complete function looks like this

do_start () {
#
# Mount a tmpfs on /dev/shm
#
SHM_OPT=
[ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT=”-osize=$SHM_SIZE”
domount tmpfs shmfs /dev/shm $SHM_OPT

#
# Mount /dev/pts. Create master ptmx node if needed.
#
domount devpts “” /dev/pts -ogid=$TTYGRP,mode=$TTYMODE

#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs “” /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount –rbind /dev/bus/usb /proc/bus/usb
}

The above change creates a file called /proc/bus/usb/.usbfs/devices which is missing in the new Ubuntu releases.

After making these changes run /etc/init.d/mountdevsubfs.sh restart at consoel or restart system before continuing with the other steps.

4) Now, your system can easily identify the new USB device which you have inserted into your PC. You can confirm this by running lsusb command.

# lsusb
Bus 005 Device 004: ID 046d:08c6 Logitech, Inc.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 027: ID 05c6:6000 Qualcomm, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 413c:8126 Dell Computer Corp.
Bus 002 Device 004: ID 0a5c:4502 Broadcom Corp.
Bus 002 Device 005: ID 0a5c:4503 Broadcom Corp.
Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver
Bus 001 Device 001: ID 0000:0000

Here Bus 004 Device 027: ID 05c6:6000 Qualcomm, Inc. is the new device which started showing up for me on my laptop.

5) Your Linux kernel need to know which company’s driver need to be used with device. Most of the new kernels comes with the Qualcomm drivers inbuilt. Else you need to insert the driver module into your kernel.

Run this at the console to activate the module based on the vendor id and product id (You can find them in the previous step ID 05c6:6000. As we need to pass these numbers in hex format, I’m adding 0x).


# modprobe usbserial vendor=0x05c6 product=0x6000

(Goto step 2 and check if your USB device gets detected or not. You can even try replugging your USB device)

PS : You can permanently add this line to ensure that the module gets loaded to your kernel each time you restart your system by adding the following line into /etc/modules

usbserial vendor=0×05c6 product=0×6000

Finally you must get the following output, showing the Vendor name, ID, Device id , Device Bus used by your kernel to interact with the device.

#lsusb -v | grep Qualcomm
Bus 004 Device 022: ID 05c6:6000 Qualcomm, Inc.
idVendor 0×05c6 Qualcomm, Inc.

Now, your Linux PC is capable of creating the device files /dev/ttyUSB0 automatically without any issues.

6) Now its time for us to create the dialup profile. Its so simple with “wvdialconf” command.

#wvdialconf /etc/wvdial.conf

This creates a file called /etc/wvdial.conf with following output :

# wvdialconf /etc/wvdial.conf
Writing `/etc/wvdial.conf’.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0 S1 S2 S3
WvModem<*1>: Cannot get information for serial port.
ttyUSB0<*1>: ATQ0 V1 E1 — OK
ttyUSB0<*1>: ATQ0 V1 E1 Z — OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 — OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 — OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 — OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 — OK
ttyUSB0<*1>: Modem Identifier: ATI — Manufacturer: QUALCOMM INCORPORATED
ttyUSB0<*1>: Speed 4800: AT — OK
ttyUSB0<*1>: Speed 9600: AT — OK
ttyUSB0<*1>: Speed 19200: AT — OK
ttyUSB0<*1>: Speed 38400: AT — OK
ttyUSB0<*1>: Speed 57600: AT — OK
ttyUSB0<*1>: Speed 115200: AT — OK
ttyUSB0<*1>: Speed 230400: AT — OK
ttyUSB0<*1>: Speed 460800: AT — OK
ttyUSB0<*1>: Max speed is 460800; that should be safe.
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 — OK
WvModem<*1>: Cannot get information for serial port.
ttyUSB1<*1>: ATQ0 V1 E1 — failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 — failed with 9600 baud, next try: 115200 baud
ttyUSB1<*1>: ATQ0 V1 E1 — and failed too at 115200, giving up.
WvModem<*1>: Cannot get information for serial port.
ttyUSB2<*1>: ATQ0 V1 E1 — failed with 2400 baud, next try: 9600 baud
ttyUSB2<*1>: ATQ0 V1 E1 — failed with 9600 baud, next try: 115200 baud
ttyUSB2<*1>: ATQ0 V1 E1 — and failed too at 115200, giving up.

Found a modem on /dev/ttyUSB0.
/etc/wvdial.conf<Warn>: Can’t open ‘/etc/wvdial.conf’ for reading: No such file or directory
/etc/wvdial.conf<Warn>: …starting with blank configuration.
Modem configuration written to /etc/wvdial.conf.
ttyUSB0<Info>: Speed 460800; init “ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0″

Your /etc/wvdial.conf will have the following entries.

# cat /etc/wvdial.conf

[Dialer Defaults]
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
; Phone = <Target Phone Number>
ISDN = 0
; Username = <Your Login Name>
Init1 = ATZ
; Password = <Your Password>
Modem = /dev/ttyUSB0
Baud = 460800

Change the target phone no. to #777 and Username and password need to be set to the EVDO number provided by BSNL.

And you require an another magical line added to this file. i.e.

Stupid Mode = 1

More about Stupid Mode (from man pages):

When wvdial is in Stupid Mode, it does not attempt to interpret any prompts from the terminal server. It starts pppd immediately after the modem connects. Apparently there are ISP’s that actually give you a login prompt, but work only if you start PPP, rather than logging in. Go figure. Stupid Mode is (naturally) disabled by default.

Your /etc/wvdial.conf should look like this :

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN = 0
Phone = #777
Modem = /dev/ttyUSB0
Username = 22222222
Password = 22222222
Baud = 460800
Stupid Mode = 1

22222222 is just an example id, replace this with your EvDO number.

7) You’re all set to get connected now. just execute the following command again at the console

# wvdial

output :

# wvdial
WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot get information for serial port.
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Modem initialized.
WvDial<*1>: Sending: ATDT#777
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATDT#777
WvDial Modem<*1>: CONNECT
WvDial<*1>: Carrier detected. Starting PPP immediately.
WvDial<Notice>: Starting pppd at Tue Mar 4 16:26:53 2008
WvDial<Notice>: Pid of pppd: 14536
WvDial<*1>: Using interface ppp0
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: local IP address 10.1.0.169
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: remote IP address 10.64.64.64
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: primary DNS address 218.248.240.23
WvDial<*1>: pppd: ��[06][08]��[06][08]
WvDial<*1>: secondary DNS address 218.248.240.135
WvDial<*1>: pppd: ��[06][08]��[06][08]

There should be a smile at your face after looking at it as you’re connected to internet. Start browsing unlimited.

7) To terminate the connection issue CTRL + C command and then remove EvDO device.

Note: If you still love windows, you have a bad news. BSNL does not provide you with the Windows Vista drivers for this device. I haven’t found one so far even for testing it.

You have just hacked into Linux to make a device work. Isn’t it fun.
If you have any questions, don’t hesitate to comment on it. I shall help you understand it better.

Tags: , , , , , , , , , ,

81 Responses to “Hacking BSNL EvDO on Linux”

  1. Priyadarshi Narayan says:

    I am done with the nm applet.
    please suggest how to reload the evdo card. it is not being recognized.

  2. Priyadarshi says:

    My problem is solved. I did some changes in the passphrase with seahorse command.

  3. TechFiz says:

    Good to know that you got the issue resolved. :)

  4. Priyadarshi says:

    The same problem has reappeared.Please suggest something. It is greatly annoying.the device works ok on my windows machine.
    I used to connect to the net using this command and then put my PW to compleate. But for last few days this is what comes up when i try to connect. Can you give me a solution for this.

    pn@pn-laptop:~$ sudo wvdial
    [sudo] password for pn:
    –> WvDial: Internet dialer version 1.60
    –> Cannot open /dev/ttyUSB0: No such file or directory
    –> Cannot open /dev/ttyUSB0: No such file or directory
    –> Cannot open /dev/ttyUSB0: No such file or directory

  5. Techfiz says:

    Once you plugin your usb modem, tail /var/log/messages and send me the last 100 lines. Let me see whats happening. Also post the OS distro name and OS once again so that I can point you to the fix.

  6. Priyadarshi says:

    pn@pn-laptop:~$ tail /var/log/messages
    Dec 19 17:06:15 pn-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
    Dec 19 17:06:15 pn-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name
    Dec 19 17:06:15 pn-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
    Dec 19 17:06:15 pn-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
    Dec 19 17:06:15 pn-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.interface_mtu
    Dec 19 17:07:09 pn-laptop chat[4545]: alarm
    Dec 19 17:07:09 pn-laptop chat[4545]: Failed
    Dec 19 17:11:24 pn-laptop kernel: [ 263.712537] pccard: card ejected from slot 0
    Dec 19 17:11:24 pn-laptop kernel: [ 263.803362] ndiswrapper: device wlan0 removed
    Dec 19 17:11:24 pn-laptop kernel: [ 263.803420] ACPI: PCI interrupt for device 0000:02:00.0 disabled
    pn@pn-laptop:~$

    I am using ubuntu 8.04.
    waiting for reply.Thanks

  7. sunil says:

    iam using ubbubtu 8.04 after doing the steps igit
    hacker@hacker-laptop:/$ sudo wvdial
    –> WvDial: Internet dialer version 1.60
    –> Cannot get information for serial port.
    –> Initializing modem.
    –> Sending: ATZ
    ATZ
    OK
    –> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    OK
    –> Modem initialized.
    –> Sending: ATDT#777
    –> Waiting for carrier.
    ATDT#777
    CONNECT
    –> Carrier detected. Starting PPP immediately.
    –> Starting pppd at Sat Jan 3 23:02:55 2009
    –> Pid of pppd: 6958
    –> Using interface ppp0
    –> local IP address 10.2.0.15
    –> remote IP address 10.64.64.64
    –> primary DNS address 218.248.240.79
    –> secondary DNS address 218.248.240.135

  8. TechFiz says:

    Priyadarshi,

    I recommend you to remove the modem, check the output in /var/log/messages. and the plug it back in and once again see the device being initialized in /var/log/messages. Only then you can go ahead and get connected. Other wise, you once again have to go through the steps mentioned in my article.

  9. Priyadarshi says:

    Thank you Shiv,
    I sorted it out yesterday. The whole thing had issues with Passphrase. And the moment i made a change with seahorse command in a pop up window,sorrow was over. It got connected in no time. thanks a lot again.

  10. mahendra says:

    I’ve done everything……..whenever i run wvdial…..all the steps were carried out fine except the lat two line which says…..

    primary dns address 4.2.2.2
    secondary dns address 4.2.2.3

    I dont think it should be like this…….where am i going wrong….

    please help me…..iam getting frustrated now

  11. mahendra says:

    and yes……i cannot surf internet

  12. Eshant says:

    now , BSNL is providing new ZTE device with calling feature. I got y shape usb xtension cable with it. i m facing pro in this method:

    1. done

    2. done

    3. done but nothing is inside /proc/bus/usb/.usbfs

    4.Qualcomm is not being described.

    stopped

  13. Eshant says:

    Feb 13 19:13:33 eshant-desktop kernel: [ 531.480016] usb 1-2: new full speed USB device using uhci_hcd and address 4
    Feb 13 19:13:34 eshant-desktop kernel: [ 532.156016] usb 1-2: new full speed USB device using uhci_hcd and address 5
    Feb 13 19:13:35 eshant-desktop kernel: [ 532.888020] usb 1-2: new full speed USB device using uhci_hcd and address 6
    Feb 13 19:13:35 eshant-desktop kernel: [ 533.416015] usb 1-2: new full speed USB device using uhci_hcd and address 7
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.044031] usb 1-2: new full speed USB device using uhci_hcd and address 8
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.203740] usb 1-2: configuration #1 chosen from 1 choice
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.206468] option 1-2:1.0: GSM modem (1-port) converter detected
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.206889] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.210906] option 1-2:1.1: GSM modem (1-port) converter detected
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.211296] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.214110] option 1-2:1.2: GSM modem (1-port) converter detected
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.214231] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.222654] option 1-2:1.3: GSM modem (1-port) converter detected
    Feb 13 19:13:39 eshant-desktop kernel: [ 537.222920] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3

  14. TechFiz says:

    Let me know which OS Distribution you’re using. I recommend you to my new post – http://platonic.techfiz.info/2.....-on-hardy/ – here you need not worry about the usb files mentioned in earlier articles.

  15. Eshant says:

    I am using ultimate ubuntu 2.0(based on 8.10 intrepid), browsing is very-very slow than vista(1 Mbps approx), please help,

    one more pro- How to install updates b/c device is giving only 10-20 kBps and become unknown after some secs.

  16. [...] http://platonic.techfiz.info/2.....-on-linux/ Written by Nyjil in: Notebook Computers | Tags: Automobile broadband.CDMA Automobile broadband, [...]

  17. Sanath says:

    Hi ,
    I bought the EVDO card newly , found that by default it is making use of CDMA 1 x network which is very slow, how can I configure the card to use EVDO network, OS is Ubantu
    On the card orange colour light is blinking which tells its using CDMA 1X nerwork, it should show Green colour for EVDO network, my house is nearby EVDO tower only.

    Thanks,
    Sanath

  18. TechFiz says:

    Sanath,

    I’m not sure about BSNL. I have used BSNL EvDO when they were providing CDMA connectivity. Not really sure about their new network support.

    If you’re promised with a better with bandwidth, try it from some other place. You might be facing problem with the signals.

    Regards,
    Shiv

  19. Naveen says:

    Hi, I checked that BSNL is providing ZTE MY39 which is rev.0 and would only offer 2.4 Mbps.. but reliance and tata have better cards on offer.

    My question is if i purchase evdo card from BSNL, can i configure it to be used with reliance or tata later and vice versa.. how does it work??

  20. TechFiz says:

    Hi Naveen,

    The procedure of setting up the data card is same.. take the backup of wvdial.conf and setup the device again…
    You have instructions on my blog for Reliance card as well.. I will put up one for TataIndicom in a day or two after testing its performance.

  21. Naveen says:

    Thanks for the speedy response.. But im not sure if I was clear enough on what I intend to do.
    Let me explain it better.

    I wanted to buy a BSNL EVDO CARD (AC8700) and use it with the BSNL service for sometime but i would be spending about Rs. 3500 to buy the card. Now at a later point in time if i want to use the same AC 8700 card with a reliance netconnect service, would it be possible??

    So in plain terms, is it possible to purchase a EVDO card of my choice from service provider A (BSNL/RELIANCE/TATA) and then use the same card with service provider B in case i wish to change service providers without the necessity of buying a new EVDO card?

    Also, do you know if there is a PCMCIA card to USB adapter available? I’m thinking of a possiblity to connect the MY39 PCMCIA card to USB slot of my desktop/laptop.

    A fast response would be appreciated again..
    Thanks much in advance. Please keep up the good work.

  22. Naveen says:

    Also, I want to know what measure the service providers take to prevent unauthorized usage.. Do they register the card hardware ID with the username and password before providing service OR would anyone who knows the username and password connect with different EVDO cards??

    Thanks!!

  23. TechFiz says:

    I don’t think there is an option available for us to switch between the providers as of now. I shall verify on this with some one. You can give a try and talk to some one at customer support.

    Regarding unauthorized usage…. Yes, if you use a wrong phone number you will not be able to get connected. Its better than BSNL user id and passwords :)

  24. Naveen says:

    I spoke to someone at customer support and they said it is not possible.. While u verify the info, i will try to find some hacks too.. ;-)

    Thanks again for all the help!!

    C ya!

  25. Haroon says:

    I tried the config…
    It shows connected but i cannot load pages
    What I did:
    http://pastebin.com/m7d91b832
    wvdial.conf
    http://pastebin.com/f4e2e0950
    please help.
    .

  26. TechFiz says:

    Haroon,

    Check for the nameservers in /etc/resolv.conf If you don’t find any add the following line into that

    nameserver 4.2.2.2

    If you still don’t get to work with it, get back to me with the out put of the following command

    route -n

  27. Mugo FM says:

    Hallo Shiv,

    i am writing from Kenya and find you eloquence very commendable…thanks for sharing so much with a wider audience out there.

    i recently installed Ubuntu 9.10 with kernel 2.6.31-14-generic and have been trying to configure my ZTE EV-DO AC8710 modem to get online. i followed your instructions/experience on this page to the letter, changing respective parameters where necessary in order to fit my situation. i paste the systems response…the modem does not get recognized for reasons i dont know. here we go:

    root@Mybabe:~# tail -f /var/log/messages
    Mar 2 10:16:31 Mybabe kernel: [ 13.072532] iwl3945 0000:02:00.0: firmware: requesting iwlwifi-3945-2.ucode
    Mar 2 10:16:31 Mybabe kernel: [ 13.373687] iwl3945 0000:02:00.0: loaded firmware version 15.32.2.9
    Mar 2 10:16:31 Mybabe kernel: [ 13.457257] Registered led device: iwl-phy0::radio
    Mar 2 10:16:31 Mybabe kernel: [ 13.457353] Registered led device: iwl-phy0::assoc
    Mar 2 10:16:31 Mybabe kernel: [ 13.457399] Registered led device: iwl-phy0::RX
    Mar 2 10:16:31 Mybabe kernel: [ 13.457442] Registered led device: iwl-phy0::TX
    Mar 2 10:16:32 Mybabe kernel: [ 13.477137] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Mar 2 10:16:33 Mybabe kernel: [ 14.825546] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Mar 2 10:16:34 Mybabe kernel: [ 16.282010] ppdev: user-space parallel port driver
    Mar 2 10:20:00 Mybabe kernel: [ 221.488605] CE: hpet increasing min_delta_ns to 15000 nsec

    copied and saved your script to change usb to modem, inserting vedor&product ids; then

    root@Mybabe:~# lsusb
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 002: ID 19d2:ffff ONDA Communication S.p.A.
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    root@Mybabe:~#

    root@Mybabe:~# modprobe usbserial vendor=0×19d2 product=0xffff
    root@Mybabe:~#
    (no output)

    root@Mybabe:~# lsusb -v | grep ONDA
    Bus 002 Device 002: ID 19d2:ffff ONDA Communication S.p.A.
    idVendor 0×19d2 ONDA Communication S.p.A.

    root@Mybabe:~# wvdialconf /etc/wvdial.conf
    Editing `/etc/wvdial.conf’.

    Scanning your serial ports for a modem.

    Modem Port Scan: S0 S1 S2 S3
    WvModem: Cannot get information for serial port.
    ttyUSB0: ATQ0 V1 E1 — failed with 2400 baud, next try: 9600 baud
    ttyUSB0: ATQ0 V1 E1 — failed with 9600 baud, next try: 9600 baud
    ttyUSB0: ATQ0 V1 E1 — and failed too at 115200, giving up.

    Sorry, no modem was detected! Is it in use by another program?
    Did you configure it properly with setserial?

    Please read the FAQ at http://open.nit.ca/wiki/?WvDial

    If you still have problems, send mail to .
    root@Mybabe:~#

    root@Mybabe:~# insmod /lib/modules/2.6.31-14-generic/kernel/drivers/usb/serial/airprime.ko
    insmod: can’t read ‘/lib/modules/2.6.31-14-generic/kernel/drivers/usb/serial/airprime.ko’: No such file or directory
    root@Mybabe:~#

    thanks for taking your time ;-)

  28. TechFiz says:

    Hi Mugo,

    Thanks for your response.

    As you’re using Ubuntu 9.10, Right click on Network Manager (Network Icon on the top bar) and select Edit connection. Visit Mobile Broadband tab and create a connection for your service provider and save the settings. Also, you can set this connection to auto connect so you need not have to click on the network manager and then enable the connection manually. Once this is done, remove your ZTE card and put that back online. This should let you get connected. If you don’t find it working, ensure that you have the latest kernel on the system.

    Also while checking your previous message, I found that the file which you’re trying to use for insmod is not available and also /var/log/messages are not showing the device being detected.. You should check /var/log/messages while you’re inserting the USB drive to capture the system messages. That should tell you whats wrong with your device.

    Let me know how my suggestions work for you.

    All the best.

  29. Mugo FM says:

    Hallo Shiv,

    1). After looking around for sometime, i found one script which changes the modem status from a mass storage device into a modem. I copied and saved it under: /etc/udev.d/15-zte-mf622.rules

    http://blog.ufsoft.org/zte-mf6.....nder-linux

    #——————————————————–
    ACTION!=”add”, GOTO=”ZTE_End”

    # Is this the ZeroCD device?
    SUBSYSTEM==”usb”, SYSFS{idProduct}==”ffff”,
    SYSFS{idVendor}==”19d2″, GOTO=”ZTE_ZeroCD”

    # Is this the actual modem?
    SUBSYSTEM==”usb”, SYSFS{idProduct}==”ffff”,
    SYSFS{idVendor}==”19d2″, GOTO=”ZTE_Modem”

    LABEL=”ZTE_ZeroCD”
    # This is the ZeroCD part of the card, remove
    # the usb_storage kernel module so
    # it does not get treated like a storage device
    RUN+=”/sbin/rmmod usb_storage”

    LABEL=”ZTE_Modem”
    # This is the Modem part of the card, let’s
    # load usbserial with the correct vendor
    # and product ID’s so we get our usb serial devices
    RUN+=”/sbin/modprobe usbserial vendor=0×19d2 product=0xffff”,
    # Make users belonging to the dialout group
    # able to use the usb serial devices.
    MODE=”660″, GROUP=”dialout”

    LABEL=”ZTE_End”
    #———————————————————–

    (2).then checked whether the modem device was being recognized

    root@Mybabe:~# lsusb
    Bus 002 Device 002: ID 19d2:ffff ONDA Communication S.p.A.
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    (3). then checked on system log messages as you advised:

    root@Mybabe:~# tail -f /var/log/messages
    Mar 3 11:10:45 Mybabe kernel: [ 13.218707] iwl3945 0000:02:00.0: firmware: requesting iwlwifi-3945-2.ucode
    Mar 3 11:10:46 Mybabe kernel: [ 13.504833] iwl3945 0000:02:00.0: loaded firmware version 15.32.2.9
    Mar 3 11:10:46 Mybabe kernel: [ 13.538673] Synaptics Touchpad, model: 1, fw: 6.3, id: 0×1a0b1, caps: 0xa04713/0×200000
    Mar 3 11:10:46 Mybabe kernel: [ 13.578596] Registered led device: iwl-phy0::radio
    Mar 3 11:10:46 Mybabe kernel: [ 13.578622] Registered led device: iwl-phy0::assoc
    Mar 3 11:10:46 Mybabe kernel: [ 13.578683] Registered led device: iwl-phy0::RX
    Mar 3 11:10:46 Mybabe kernel: [ 13.578704] Registered led device: iwl-phy0::TX
    Mar 3 11:10:46 Mybabe kernel: [ 13.590041] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Mar 3 11:10:46 Mybabe kernel: [ 13.625645] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7
    Mar 3 11:10:46 Mybabe kernel: [ 14.165848] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    Mar 3 11:13:33 Mybabe kernel: [ 180.488659] CE: hpet increasing min_delta_ns to 15000 nsec

    (4). after failing to see the modem, i disconnected and reconnected it from/into its usb port

    Mar 3 11:13:34 Mybabe kernel: [ 181.936198] usb 2-2: USB disconnect, address 2
    Mar 3 11:13:34 Mybabe kernel: [ 181.936554] generic ttyUSB0: generic converter now disconnected from ttyUSB0
    Mar 3 11:13:34 Mybabe kernel: [ 181.936592] usbserial_generic 2-2:1.0: device disconnected
    Mar 3 11:13:37 Mybabe kernel: [ 184.492160] usb 2-2: new full speed USB device using uhci_hcd and address 3
    Mar 3 11:13:37 Mybabe kernel: [ 184.646642] usb 2-2: configuration #1 chosen from 1 choice
    Mar 3 11:13:37 Mybabe kernel: [ 184.649712] usbserial_generic 2-2:1.0: generic converter detected
    Mar 3 11:13:37 Mybabe kernel: [ 184.649839] usb 2-2: generic converter now attached to ttyUSB0

    (5). i then copied and saved your script, making it an executable file through chmod with midnight commander

    do_start () {
    #
    # Mount a tmpfs on /dev/shm
    #
    SHM_OPT=
    [ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT=”-osize=$SHM_SIZE”
    domount tmpfs shmfs /dev/shm $SHM_OPT

    #
    # Mount /dev/pts. Create master ptmx node if needed.
    #
    domount devpts “” /dev/pts -ogid=$TTYGRP,mode=$TTYMODE

    #
    # Magic to make /proc/bus/usb work
    #
    mkdir -p /dev/bus/usb/.usbfs
    domount usbfs “” /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
    ln -s .usbfs/devices /dev/bus/usb/devices
    mount –rbind /dev/bus/usb /proc/bus/usb
    }

    (6). root@Mybabe:~# /etc/init.d/mountdevsubfs.sh restart

    (7). then initiated wvdial.conf

    root@Mybabe:~# wvdialconf /etc/wvdial.conf

    Editing `/etc/wvdial.conf’.

    Scanning your serial ports for a modem.

    Modem Port Scan: S0 S1 S2 S3
    WvModem: Cannot get information for serial port.
    ttyUSB0: ATQ0 V1 E1 — failed with 2400 baud, next try: 9600 baud
    ttyUSB0: ATQ0 V1 E1 — failed with 9600 baud, next try: 9600 baud
    ttyUSB0: ATQ0 V1 E1 — and failed too at 115200, giving up.

    Sorry, no modem was detected! Is it in use by another program?
    Did you configure it properly with setserial?

    Please read the FAQ at http://open.nit.ca/wiki/?WvDial

    If you still have problems, send mail to .

    The problem of modem recognition is still there.

    Question: could there be a reason as to why the modem is not being recognized by Wvdial? Could it be that it is regarded as a generic converter and not a modem (see sys msgs)?
    Thank you again for taking your time to help out here ;-)

  30. vinayak says:

    Nice article…

    Can you please help me set Iptables rules in centos + cpanel server..I have to flush iptables each time to connect my server via http://ftp..

    Thanks!

  31. Hi Vinayak,

    Thanks for liking the article.

    Please flush the iptables and save the rules. Following commands should help you.

    iptables -F
    service iptables save

    Regards,
    Shiv

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">