Author |
Message |
|
kiransuresh
|
|
Posts: 7 Joined: Tue Apr 22, 2014 3:31 pm |
The ZTE MF197 modem is not getting connected in my linux based system. By plugging into a PC the default product id was found to be 0x1225. However no usb switching file was found for a device with that product id. from lsusb in the PC the target id was found as 0x1405. however i donot know the message content to be given in the modeswitch file. What is the actual meaning of that message content. If i give the message contents given for other ZTE models, the switching happens but the modem is not getting connected. I get an error as Script /bin/chat -v -t10 -f /etc/ppp/ppp.chat finished (pid 1553), status = 0x3 Connect script failedHere is my PPP chat script for reference. pls help me solve the problem. Code: ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT 'NO CARRIER' ABORT DELAYED ABORT 'COMMAND NOT SUPPORT'
'' '' '' 'ATZ' 'OK' "ATQ0 V1 E1 S0=0 &C0 &D2"
SAY 'show device infomation...\n' 'OK' 'ATI' SAY 'show SIM CIMI...\n' #'OK' 'AT+CIMI'
SAY 'set APN...\n' 'OK' 'AT+CGDCONT=1,"IP","tata.docomo.internet"'
SAY 'dial...\n\n' 'OK' 'ATD*99#' 'CONNECT' ''
N.B: The Huawei modems are connecting easily without any chat script errors. This error only crops for ZTE modems.
|
Top
|
Offline |
LOM
|
|
Posts: 1261 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH |
You are using an old usb_modeswitch version with an old data package, 19d2:1225 is in the data package since 6 month back.
19d2:1405 is not a ppp dialup modem, it is a direct ethernet adapter with interfaces which should be driven by cdc_ether. There is no serial interface for AT-cmds.
|
Top
|
Offline |
kiransuresh
|
|
Posts: 7 Joined: Tue Apr 22, 2014 3:31 pm |
LOM wrote: 19d2:1405 is not a ppp dialup modem, it is a direct ethernet adapter with interfaces which should be driven by cdc_ether. There is no serial interface for AT-cmds. Oh thanks a lot LOM  Then how can i connect this modem without PPP script. How to drive by cdc_ether please explain. I relatively new to all these. Please
|
Top
|
Offline |
LOM
|
|
Posts: 1261 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH |
google "3g linux cdc_ether" and you will find all you want to know, google is a much better teacher than I am.
|
Top
|
Offline |
kiransuresh
|
|
Posts: 7 Joined: Tue Apr 22, 2014 3:31 pm |
LOM wrote: google is a much better teacher than I am. Ya i googled it though what am not sure is. Will it be enough to just insert the module cdc_ether.ko or is there any additional step? Everything in google seems to be aimed at PCs. Mine is an embedded system. I included the module in Kernel configuration. Is insmod alone enuf during plugin?? Thats my doubt.
|
Top
|
Offline |
kiransuresh
|
|
Posts: 7 Joined: Tue Apr 22, 2014 3:31 pm |
LOM wrote: google "3g linux cdc_ether" and you will find all you want to know, google is a much better teacher than I am. After inserting the cdc_ether module in kernel config. When i plugin the modem the dmesg is <4>[ 125.670000] usb 1-1: usbfs: process 880 (usb_modeswitch) did not claim interface 0 before use <6>[ 131.010000] usb 1-1: USB disconnect, address 2 <6>[ 137.070000] usb 1-1: new high speed USB device using musb_hdrc and address 3 <6>[ 137.210000] usb 1-1: configuration #1 chosen from 1 choice <4>[ 137.210000] #################################################################### <6>[ 137.220000] eth1: register 'cdc_ether' at usb-musb_hdrc-1, CDC Ethernet Device, 34:4b:50:b7:ef:1c <4>[ 174.770000] g_ether: Unknown symbol usb_gadget_register_driver <4>[ 174.790000] g_ether: Unknown symbol usb_gadget_unregister_drivernow this does not show in ifconfig as eth1. from google i tried a solution of editing /etc/network/interface Code: auto usb0 iface usb0 inet static address 192.168.0.2 netmask 255.255.255.0 But still no difference. Please help.  my ifconfig shows only eth0 Link encap:Ethernet HWaddr 00:01:02:03:04:05 inet addr:192.168.1.168 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:52 Base address:0x7000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2616 (2.5 KiB) TX bytes:2616 (2.5 KiB)
|
Top
|
Offline |
LOM
|
|
Posts: 1261 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH |
The usb0 device is created by usbnet which cdc_ether is dependent on, should be loaded before cdc_ether.
|
Top
|
Offline |
kiransuresh
|
|
Posts: 7 Joined: Tue Apr 22, 2014 3:31 pm |
LOM wrote: The usb0 device is created by usbnet which cdc_ether is dependent on, should be loaded before cdc_ether. Ya the usbnet was already loaded b4 loading cdc_ether. Anyway the issue was i had to run a binary for allocating ip dynamically. When done. This worked. It is now recognized as eth1. Code: eth0 Link encap:Ethernet HWaddr 00:01:02:03:04:05 inet addr:192.168.1.168 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1002 errors:0 dropped:0 overruns:0 frame:0 TX packets:2176 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:71661 (69.9 KiB) TX bytes:2951007 (2.8 MiB) Interrupt:52 Base address:0x7000 eth1 Link encap:Ethernet HWaddr 34:4B:50:B7:EF:1C inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1350 (1.3 KiB) TX bytes:1240 (1.2 KiB)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2616 (2.5 KiB) TX bytes:2616 (2.5 KiB) SOLVED
|
Top
|
Offline |
|