Arch Linux

ruth

Member

Registered: 2010-02-17

Posts: 11

O2 Surfstick ZTE MF 190

Hi all,
I got a new Surfstick, unfortunately it doesnt work *sad*...
after plugging in, dmesg says:

usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 8:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
sr1: scsi-1 drive
sr 8:0:0:0: Attached scsi CD-ROM sr1
sr 8:0:0:0: Attached scsi generic sg2 type 5

Ok, so i have the famous Data partition available, lets switch the Device...
The Surfstick is quite a new model; I found a working configuration for usb_modeswich:

modeswitch.conf

DefaultVendor=  0x19d2
DefaultProduct= 0x0083
TargetVendor=   0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0066,0091,0108,0117,0128,2002"
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
CheckSuccess=20

root@RedQueen[~] $ usb_modeswitch -c modeswitch.conf
output is:

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("dummy")
 OK, driver "dummy" detached

SCSI inquiry data (for identification)
-------------------------
  Vendor String: ZTE     
   Model String: USB SCSI CD-ROM 
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE WCDMA Technologies MSM
  Serial No.: XXXXXXXXXXXXXXXXX
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to message 2 ...
 OK, response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to message 3 ...
 Response reading got error -32, can probably be ignored
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
 Searching for target devices ...

Found target device, now opening
 Found correct target device

Mode switch succeeded. Bye.

So, everything is ok so far...

dmesg at this stage is:

usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
option 1-5:1.0: GSM modem (1-port) converter detected
usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0
option 1-5:1.1: GSM modem (1-port) converter detected
usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
option 1-5:1.2: GSM modem (1-port) converter detected
usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
scsi 9:0:0:0: Direct-Access     ZTE      MMC Storage      2.31 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk

Now, accessing the Device via /dev/ttyUSB0 didnt work, so i tried wvdial in config mode.
It was able to access the Modem on /dev/ttyUSB1(!!!)

My /etc/wvdial.conf looks like that:

[Dialer o2]
Modem = /dev/ttyUSB1
ISDN = off
Modem Type = USB Modem
Baud = 115200
Init = ATZ
Init2 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 AT+CGDCONT=1,"IP","pinternet.interkom.de"
# Init4 = AT+SYSCFG=2,2,3FFFFFFF,2,4
Init5 =
Init6 =
Init7 =
Init8 =
Init9 =
Phone = *99#
Phone1 =
Phone2 =
Phone3 =
Phone4 =
Dial Prefix =
Dial Attempts = 100
# Dial Command = ATM1L3DT
Ask Password = off
Password = o2
Username = o2
Auto Reconnect = on
Abort on Busy = off
Carrier Check = on
Check Def Route = on
Abort on No Dialtone = on
Stupid Mode = on
Idle Seconds = 0
Auto DNS = on

[Dialer pin]
Modem = /dev/ttyUSB1
Init3 = AT+CPIN=xxxx

I unlocked the SIM card via wvdial pin

root@RedQueen[~] $ wvdial pin
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT+CPIN=xxxx
AT+CPIN=xxxx
OK
--> Modem initialized.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
--> Configuration does not specify a valid password.

So it worked fine, accessed the Modem via /dev/ttyUSB1, SIM card is unlocked now.

Finally, i tried to dial in:

root@RedQueen[~] $  wvdial o2
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT 7200000
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Sat Mar  5 06:11:59 2011
--> Pid of pppd: 4924
--> Using interface ppp0

At this point it fails somewhere:
Here's the Console output:

--> Disconnecting at Sat Mar  5 06:12:30 2011
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 5 seconds

relevant excerpt from /var/log/messages.log

Mar  5 06:12:00 RedQueen kernel: PPP generic driver version 2.4.2
Mar  5 06:12:00 RedQueen pppd[4924]: Using interface ppp0
Mar  5 06:12:00 RedQueen pppd[4924]: Connect: ppp0 <--> /dev/ttyUSB1
Mar  5 06:12:30 RedQueen pppd[4924]: LCP: timeout sending Config-Requests
Mar  5 06:12:30 RedQueen pppd[4924]: Connection terminated.
Mar  5 06:12:30 RedQueen pppd[4924]: Modem hangup
Mar  5 06:12:30 RedQueen pppd[4924]: Exit.

The Device doesnt connect and i get this error:

Mar  5 06:12:30 RedQueen pppd[4924]: LCP: timeout sending Config-Requests

After that, the Device is basically dead and i have to replug and reinitialize the Surfstick.
I am sure, the Surfstick works, because i am on Windows right now an i am using this Surfstick to write this Posting...
Any Hints? please help me ;-)

ruth

Member

Registered: 2010-02-17

Posts: 11

Re: O2 Surfstick ZTE MF 190

Ok,
I found out that upgrading to the latest usb_modeswitch gives me the needed Modem Devices automagically(at Boot Time).
After unplugging and replugging, UDEV seems not to handle the Stick again.
I also found out, that a simple eject /dev/sr1 on the commandline switches the Stick from Memory mode to Modem Mode in that case.
So manually switching the Stick is not needed anymore(in my Case)
BUT:
It still doesnt work, still the same Error about the LCP thingy...
Hmmm....

Last edited by ruth (2011-03-06 16:28:17)

davvil

Member

Registered: 2008-05-06

Posts: 165

Re: O2 Surfstick ZTE MF 190

I also got a surfstick from O2 (Germany), and had problems getting it to work, too. I don't have it with me at the moment, so I cannot check if it's the same model.

The easiest solution I found was to use sakis3g, an all-in-one tool for surfsticks. It is not the "arch way" to do things, but it worked for me, and I only needed it for one month while moving from one city to another.

Last edited by davvil (2011-03-07 19:28:12)

gaucho

Member

Registered: 2009-04-24

Posts: 6

Re: O2 Surfstick ZTE MF 190

Hi,

I am currently running the ZTE MF190 successfully on Arch using almost the same configuration as ruth. Changing the "Modem" parameter of the wvdial.conf from "/dev/ttyUSB1" to "/dev/ttyUSB2" did the magic trick. Before I also tried using "/dev/ttyUSB1" but after running the stick successfully with sakis3g I saw that the script used USB2 instead of USB1. So you may give this a try and I hope you will succeed.

ruth

Member

Registered: 2010-02-17

Posts: 11

Re: O2 Surfstick ZTE MF 190

OMG!
That worked.
ttyUSB1 -> ttyUSB2 did the trick.
Thank you, guys...

ruth