LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page Cheeky ZTE MF636 USB modem
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 1 of 3 1 23
  Search this Thread
Old 10-05-2010, 12:40 PM   #1
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Rep: Reputation: 0
Cheeky ZTE MF636 USB modem

Good evening, folks.

I am trying to get my ZTE MF636DB USB modem to work on Slackware 13.1 multilib to no avail.
I have tried some of the methods I've seen on the forums, but none did the trick.
I have tried usb_modeswitch, but it says it can't find any device, although I have created a proper config file for my device :
Code:
########################################################
# ZTE devices

DefaultVendor=0x19d2
DefaultProduct=0x0033

TargetVendor=0x19d2
TargetProduct=0x0031

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"

NeedResponse=1

CheckSuccess=20
My dmesg | grep -i usb is this:
Code:
usb 2-1.2: new high speed USB device using ehci_hcd and address 4
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
scsi6 : usb-storage 2-1.2:1.0
scsi 6:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
usb 1-1.2: new high speed USB device using ehci_hcd and address 5
usb 1-1.2: New USB device found, idVendor=04e8, idProduct=1f05
usb 1-1.2: New USB device strings: Mfr=1, Product=11, SerialNumber=3
usb 1-1.2: Product: Samsung S2 Portable
usb 1-1.2: Manufacturer: JMicron
usb 1-1.2: SerialNumber: 00000015E093105004DC
scsi7 : usb-storage 1-1.2:1.0
usb 2-1.2: usbfs: process 4133 (usb_modeswitch) did not claim interface 0 before use
usb 2-1.2: USB disconnect, address 4
usb 2-1.2: new high speed USB device using ehci_hcd and address 5
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
scsi8 : usb-storage 2-1.2:1.3
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)
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB3
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
usb 2-1.2: USB disconnect, address 5
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
usb 2-1.2: new high speed USB device using ehci_hcd and address 6
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
scsi9 : usb-storage 2-1.2:1.0
scsi 9:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
usb 2-1.2: usbfs: process 4436 (usb_modeswitch) did not claim interface 0 before use
usb 2-1.2: USB disconnect, address 6
usb 2-1.2: new high speed USB device using ehci_hcd and address 7
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
scsi10 : usb-storage 2-1.2:1.3
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB3
usb 1-1.2: USB disconnect, address 5
usb 1-1.1: USB disconnect, address 3
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
and lsusb is this:
Code:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 006: ID 1532:0003 Razer USA, Ltd Krait Mouse
Bus 001 Device 004: ID 10ab:0816 USI Co., Ltd 
Bus 001 Device 007: ID 04e8:1f05 Samsung Electronics Co., Ltd 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 5986:0190 Acer, Inc 
Bus 002 Device 007: ID 19d2:0033 ONDA Communication S.p.A.
Also, wvdial refuses to compile and it's rather difficult to troubleshoot the little one, having no access to Internet on Slackie and having to actually boot in the-OS-whose-name-shouldn't-be-said.
LE: I've managed to install wvdial, but it gives an error, namely "libuniconf.so.4.2: cannot open shared object file". A quick 'locate' finds the library in its place, and yet wvdial remains stubborn...

I'm looking forward to hearing some ideas and thank you in advance.
--a Slackie padawan
Last edited by MadDino; 10-05-2010 at 02:23 PM.
 
Old 10-05-2010, 06:16 PM   #2
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
So if my google skills haven't failed me, you have a usb 3G modem that acts either as a modem, or as a CD drive.

It provides another "idProduct" when it acts in the other mode.

Now, the output you posted, is it from before, or after the changes you made?

I guess you put the first code you posted in "/etc/usb_modeswitch.conf"?
What happens if you put the original back in place, and enable logging?

Where have you found "DefaultProduct" and "TargetProduct" ?

If you answer these questions, I'll know better where you stand.
Last edited by janhe; 10-05-2010 at 06:17 PM.
 
Old 10-05-2010, 06:25 PM   #3
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Thank you for answering.

DefaultProduct is from lsusb, and TargetProduct is from some post on the Internet where it said that that should be the one. Quite silly to use that, but I had no idea what else to use.
What I've posted is from after I've fiddled with usb_modeswitch, but I doubt it matters, as nothing I'm aware of actually changed.
On the other hand, I managed to get wvdial installed properly. [wvdialconf does not find any modems] I've also installed Gnome-ppp and tried to connect using it. After setting it up, and using 'Detect modem', it is finally able to detect a modem [/dev/ttyUSB1], but fails to connect using it and it's unable to detect it after this error.

I'm still researching this mystery, so any hint would be helpful.
 
Old 10-05-2010, 08:37 PM   #4
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
I have two modems similar to yours (MF622/MF626) and before usb_modeswitch I either ejected the virtual cd and it became a modem until I unplugged it or used minicom and the AT command AT +ZCDRUN=8 to disable the virtual cd (you have to use minicom to run AT +ZCDRUN=9 before using it on a windows box without the driver installed, otherwise you have to pick the driver from elsewhere).

I don't use wvdial but from my experience Kppp and pppd work fine, the hardest part is to get the modem act as a modem. :P

For reference, my pppd scripts:

/etc/pppd/peers/claro (claro is the name of my ISP)
Code:
# General configuration options for PPPD:
-detach
lock
defaultroute
noipdefault
modem
# some people use /dev/modem instead, i never bothered to setup udev to create the link
/dev/ttyUSB2
115200
# hardware flow control seems to SLOW DOWN everything... these crappy modems :(
#crtscts 
novj
noccp
# Uncomment the line below for more verbose error reporting:
#debug

lcp-echo-interval 30
lcp-echo-failure 3

# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do.  To work around this,
# uncomment the line below.  Note that this may have negative side effects
# on system security if you allow PPP dialins.  See the docs in /usr/doc/ppp*
# for more information.
noauth
passive
asyncmap 0
name "CHANGE ME"
user "CHANGE ME"
show-password
connect '/usr/sbin/chat -v -t15 -f /etc/ppp/peers/pppscript-claro'
/etc/ppp/peers/pppscript-claro:
Code:
TIMEOUT 60
ABORT ERROR
ABORT BUSY
ABORT "NO CARRIER"
ABORT "NO DIALTONE"

# Initialize the modem
"" "ATZ"

# Both mf622 and mf626 have an odd "functionality": they keep flooding the control line
# to let the windows user interface know when a new text message arrives.
# The problem is that chat can't see the "OK" among the swarm of cryptic codes that floods
# the control line and after some time it will time out.
# The following command will act as the windows interface when it asks the modem
# "hey, how many text messages have you gotten for me?", which stops the flood. Well done ZTE.
#OK "AT+CPMS?"

# This shouldn't be required for most setups, uncomment and edit accordingly if you
# have to set your APN manually.
#OK "AT+CGDCONT=1,\"IP\",\"bandalarga.claro.com.br\",,0,0"

# Call *99# (edit to fit your ISP config)
#OK "ATDT*99#"

TIMEOUT 75
CONNECT
Both files are based on the ones generated by pppsetup, [1] and [2].

[1] http://www.zte.com.au/downloads/USB_..._Procedure.pdf
[2] http://3g-modem.wetpaint.com/page/ZTE+AT-commands
 
Old 10-06-2010, 12:32 AM   #5
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
From what I read, you want the 0033 idProduct. Have you tried using that, or did you start with modeswitch right away?
 
Old 10-06-2010, 03:14 AM   #6
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by janhe View Post
From what I read, you want the 0033 idProduct. Have you tried using that, or did you start with modeswitch right away?
0033 idProduct is the default one -- lsusb recognizes it as 0033 just as it is plugged it. And changing it to 0033 solves nothing, I'm afraid.
Here you are the output of usb_modeswitch -W -c 19d2:0033, 19d2:0033 being my config file for this program:
Code:
Reading config file: 19d2:0033
 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.1.4 (C) Josua Dietze 2010
 * Based on libusb0 (0.1.12 and above)

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x19d2
DefaultProduct= 0x0033
TargetVendor=   0x19d2
TargetProduct=  0x0031
TargetClass=    not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
MessageEndpoint=  not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check enabled, max. wait time 20 seconds
System integration mode disabled


Looking for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
   found matching product ID
   adding device
 Found devices in default mode or class (1)
Accessing device 007 on bus 002 ...
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)
Not a storage device, skipping SCSI inquiry

USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE CDMA Technologies MSM
  Serial No.: 1234567890ABCDEF
-------------------------
Looking for active driver ...
 OK, driver found ("dummy")
 OK, driver "dummy" detached
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) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 Original device is gone already, not checking
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 1532:0003
  searching devices, found USB ID 10ab:0816
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 8087:0020
  searching devices, found USB ID 5986:0190
  searching devices, found USB ID 19d2:0033
   found matching vendor ID
 No new devices in target mode or class found

Mode switch has failed. Bye.
Also, after this failed thing, dmesg gives me this:
Code:
dmesg | grep -i usb
usb 1-1.2: USB disconnect, address 5
usb 2-1.2: new high speed USB device using ehci_hcd and address 6
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
scsi9 : usb-storage 2-1.2:1.0
scsi 9:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
usb 2-1.2: usbfs: process 5153 (usb_modeswitch) did not claim interface 0 before use
usb 2-1.2: USB disconnect, address 6
usb 2-1.2: new high speed USB device using ehci_hcd and address 7
usb 2-1.2: New USB device found, idVendor=19d2, idProduct=0033
usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 2-1.2: Product: ZTE CDMA Technologies MSM
usb 2-1.2: Manufacturer: ZTE,Incorporated
usb 2-1.2: SerialNumber: 1234567890ABCDEF
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
scsi10 : usb-storage 2-1.2:1.3
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB3
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Therefore, it still recognizes it as a 0033 and Gnome-ppp finds no modem.

As for maxmiorim's suggestion, kppp gives me a nasty error and I can't run it, and having no Internet on Slackie makes it rather difficult to troubleshoot it. I've tried pppsetup, but some of the information required by it are not available to me, unfortunately.

I am open to any other suggestions, having almost depleted my resources of bright ideas.
 
Old 10-06-2010, 07:04 AM   #7
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
What about these "MessageContent"? Have you sniffed the modem like described in [1] or you got it from somewhere else?

Also, have you tried to use "eject /dev/sr1" (or whatever it uses as the virtual cd under /dev) instead of usb_modeswitch? If it works, you could create an udev rule to call eject and then disable usb_modeswitch (see /etc/usb_modeswitch.conf).


[1] - http://www.draisberghof.de/usb_modes....php?p=695#695
 
Old 10-06-2010, 07:29 AM   #8
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Question
This is how it appears to me: link
Rather peculiar, it seems to have the 0033 pID. Would that mean that there's no real need for usb_modeswitch in this case? I am confused. *sob* *sob*
 
Old 10-06-2010, 07:46 AM   #9
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
I don't know about MF636 but the models i have stay in "virtual cd" until i open the ISP app, that would explain why it is still 0033 for you (unless that "orange" thing is the ISP app). These modems are a bit weird, once you switch to modem mode everything - including the virtual cd - switches the pID.

I'm not sure why they didn't just give a CD like every other hardware vendor does. :P
 
Old 10-06-2010, 07:52 AM   #10
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Well, now I'm connected to the Internet using that modem and that program [usbsnoop] still says '0033'. And yet on Slackware it has only been seen as a cdrom. Makes you wonder..
Really can't figure out what I've done wrong. The only thing is left is to probably go again through piles of man pages and documentation and hopefully discover some little detail that once fixed, will solve the problem. (yeah, right). /sigh

LE: And yet, I'm open to any suggestion. Except for the one to buy some other modem.
Last edited by MadDino; 10-06-2010 at 08:10 AM.
 
Old 10-06-2010, 08:38 AM   #11
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
What about disabling the cd mode? The only downside i can see is that you have to use minicom to re-enable it whenever you want to plug the modem on windows that doesn't have the drivers installed yet. If you dump an iso before disabling it, just mount the iso, install the driver and then plug the modem.

[1] explains how to achieve this and i have sent link to a document from ZTE Australia with more details earlier in this thread.



[1] - http://wiki.archlinux.org/index.php/..._on_the_device
 
1 members found this post helpful.
Old 10-06-2010, 09:01 AM   #12
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 556Reputation: 556Reputation: 556Reputation: 556Reputation: 556Reputation: 556
Quote:
Originally Posted by MadDino View Post
Well, now I'm connected to the Internet using that modem ...
MadDino,

Do I understand this correctly that you're now using this modem thing, and are connected to the net with it, and it is working?

If so, how exactly did you get it to connect? E.g. did you use wvdial, or KPPP, or some other tool(s)? And on what OS?

I'm asking because the information may help another member over here:
http://www.linuxquestions.org/questi...dongle-835856/
who's dealing with a similar mode-switching device.

Thanks for any info you can provide.
 
Old 10-06-2010, 09:10 AM   #13
bnguyen
Member
 
Registered: Jul 2010
Distribution: Slackware
Posts: 125

Rep: Reputation: 33
Give NetworkManager a try. I'm using a Huawei E1750 here and it works very well with usb_modeswitch + NetworkManager + ModemManager + mobile-broadband-provider-info.

I even managed to make it work on Slackware 13.0 (old version of NetworkManager 0.7.1).

The important part is that you need to know the APN of your mobile network.
 
Old 10-06-2010, 09:11 AM   #14
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by GrapefruiTgirl View Post
MadDino,

Do I understand this correctly that you're now using this modem thing, and are connected to the net with it, and it is working?

If so, how exactly did you get it to connect? E.g. did you use wvdial, or KPPP, or some other tool(s)? And on what OS?

I'm asking because the information may help another member over here:
http://www.linuxquestions.org/questi...dongle-835856/
who's dealing with a similar mode-switching device.

Thanks for any info you can provide.
Oh my, sorry for the misunderstanding! I am connected on my windows machine.
 
Old 10-06-2010, 09:13 AM   #15
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 556Reputation: 556Reputation: 556Reputation: 556Reputation: 556Reputation: 556
Quote:
Originally Posted by MadDino View Post
Oh my, sorry for the misunderstanding! I am connected on my windows machine.
Ok, no worries!

Well, I hope that you or the other member make some progress anyhow.

Best regards
 
  


Reply
Page 1 of 3 1 23



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ZTE usb Modem mlpa Slackware 5 09-26-2010 08:37 PM
ZTE AC8710 usb dongle modem crazywizard Linux - Newbie 3 12-02-2009 05:36 PM
ZTE MF626 USB Modem adgaydou Linux - Newbie 1 04-03-2009 10:58 PM
Problem with usb pendrive and usb modem ZTE ZXDSL 852 AM33N Linux - Hardware 3 12-10-2008 03:25 AM
zte usb modem not detected on 2.6.23.1 kernel narendra.pant Linux - Hardware 1 12-20-2007 04:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:48 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration