LinuxQuestions.org
Visit Jeremy's Blog.
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 2 of 3 1 2 3
  Search this Thread
Old 10-06-2010, 09:19 AM   #16
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0

Quote:
Originally Posted by maxmiorim View Post
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
I see the tutorial, but Win 7 has no hyperterminal, so I'll have to look for alternatives to this one.
I suppose I'll have to try this method too, although I'm not absolutely sure about it (missing some knowledge in this area), and pray everything will go smoothly.
 
Old 10-06-2010, 09:21 AM   #17
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by GrapefruiTgirl View Post
Ok, no worries!

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

Best regards
Thanks, I will post on the forum if I get some results.
 
Old 10-06-2010, 09:22 AM   #18
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
Quote:
Originally Posted by MadDino View Post
I see the tutorial, but Win 7 has no hyperterminal, so I'll have to look for alternatives to this one.
I suppose I'll have to try this method too, although I'm not absolutely sure about it (missing some knowledge in this area), and pray everything will go smoothly.
You can use putty instead of hyperterminal, that's what i use when i can't have a penguin at hand.

As for the method, it does no harm -- just the annoyance of having to re-enable the cd-mode whenever you want to plug the modem on a windows without the drivers and then disabling it to use on your slack again.
Last edited by maxmiorim; 10-06-2010 at 09:23 AM. Reason: adding quote, i'm in ur forums stalking ur posts
 
Old 10-06-2010, 11:42 AM   #19
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by maxmiorim View Post
You can use putty instead of hyperterminal, that's what i use when i can't have a penguin at hand.

As for the method, it does no harm -- just the annoyance of having to re-enable the cd-mode whenever you want to plug the modem on a windows without the drivers and then disabling it to use on your slack again.
Thank you, I'll try it right away! Hope the Force is strong with this method.
 
Old 10-06-2010, 12:40 PM   #20
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Well, maxmiorim, I've done everything as the tutorial said. And all I got was an error.
Code:
wvdial
--> WvDial: Internet dialer version 1.56 (root@gateway)
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Sending: ATM1L3DT*99#
--> Waiting for carrier.
ATM1L3DT*99#
--> Disconnecting at Wed Oct  6 20:34:07 2010
Clueless I am.
 
Old 10-06-2010, 12:59 PM   #21
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
The reason I asked for trying before using modeswitch is because I see
Code:
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
And then ttyUSB1, ttyUSB2,...

I'm curious about what dmesg says before you go off and try running usb_modeswitch. I have seen a few udev rules for unloading the CD drivers, so I want to know if there is a ttyUSB* mention before running modeswitch.

edit: plug in the modem and run:
Code:
dmesg | tail -30
Have you checked the /dev/ttyUSB? files?
Code:
ls -l /dev/ttyUSB?
Maybe it is just a permission error...
Last edited by janhe; 10-06-2010 at 01:00 PM.
 
Old 10-06-2010, 01:32 PM   #22
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
First, dmesg:
Code:
dmesg | tail -30
[fglrx] Gart USWC size:1192 M.
[fglrx] Gart cacheable size:472 M.
[fglrx] Reserved FB block: Shared offset:0, size:1000000 
[fglrx] Reserved FB block: Unshared offset:f943000, size:3bd000 
[fglrx] Reserved FB block: Unshared offset:3fff4000, size:c000 
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.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)
option 2-1.2:1.0: GSM modem (1-port) converter detected
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
option 2-1.2:1.1: GSM modem (1-port) converter detected
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
option 2-1.2:1.2: GSM modem (1-port) converter detected
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
option 2-1.2:1.4: GSM modem (1-port) converter detected
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
scsi 6:0:0:0: Direct-Access     ZTE      MMC Storage      2.31 PQ: 0 ANSI: 2
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 6:0:0:0: [sdb] Attached SCSI removable disk
Something I noticed: after wvdial ends up with an error
Code:
ls /dev/ttyUSB*
finds nothing, although before running wvdial it would find four files.

LE:
Code:
ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Oct  6 21:48 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Oct  6 21:48 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Oct  6 21:48 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 3 Oct  6 21:48 /dev/ttyUSB3
Last edited by MadDino; 10-06-2010 at 01:53 PM.
 
Old 10-06-2010, 02:02 PM   #23
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
Are you in the dialout group? As the user who is dialing, run:
Code:
groups
If dialout isn't there, run this as root:
Code:
gpasswd -a MadDino dialout
replace MadDino with your linux username if necessary.

Then you should have access to the modem.

Also, do you see a gsmmodem link in /dev/?
Code:
ls -l /dev/gsmmodem*
 
Old 10-06-2010, 02:18 PM   #24
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by janhe View Post
Are you in the dialout group? As the user who is dialing, run:
Code:
groups
If dialout isn't there, run this as root:
Code:
gpasswd -a MadDino dialout
replace MadDino with your linux username if necessary.

Then you should have access to the modem.

Also, do you see a gsmmodem link in /dev/?
Code:
ls -l /dev/gsmmodem*
There is no gsmmodem.
Adding my user to the dialout group didn't help.
 
Old 10-06-2010, 03:01 PM   #25
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
Ok, I think we're going to get somewhere.
If we base ourself loosely on http://wiki.archlinux.org/index.php/..._on_the_device (link provided by maxmiorim earlier in this thread, thank you maxmiorim)

The kernel already loads usbserial, so the udev rules don't have to be changed.

The hal rules are something else. Put this in /etc/hal/fdi/information/10-modem.fdi :
Code:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- xml -*- -->

<deviceinfo version="0.2">
  <device>
    <match key="info.category" string="serial">
        <!-- ZTE MF636DB HSDPA USB dongle -->
        <match key="@info.parent:usb.product_id" int="0x0033">
          <match key="@info.parent:usb.interface.number" int="3">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
    </match>
  </device>
</deviceinfo>
I copied that from the ArchWiki, but changed product_id to 0x0033.

Take the wvdial.conf from the ArchWiki and try to make a connection.
Let me know how it turns out.

EDIT:
It seems that you need to specify /dev/ttyUSB3 instead of /dev/ttyUSB0
source: http://news.softpedia.com/news/How-t...u-158663.shtml
Also, if it fails again after
Code:
--> Waiting for carrier.
ATM1L3DT*99#
then try changing
Code:
Dial Command = ATM1L3DT
to
Code:
Dial Command = ATDT
or
Code:
Dial Command = ATD
Last edited by janhe; 10-06-2010 at 03:35 PM.
 
Old 10-06-2010, 03:30 PM   #26
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
Quote:
Originally Posted by MadDino View Post
Well, maxmiorim, I've done everything as the tutorial said. And all I got was an error.
Code:
wvdial
--> WvDial: Internet dialer version 1.56 (root@gateway)
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Sending: ATM1L3DT*99#
--> Waiting for carrier.
ATM1L3DT*99#
--> Disconnecting at Wed Oct  6 20:34:07 2010
Clueless I am.
Eh, some servers gone wild here today and i couldnt reply earlier... :\

I'm not a wvdial user (never used it) but it seems to me that it's calling the "wrong" number. The AT command that i use in my chat scripts is just ATDT*99# and not ATM1L3DT*99# (what "M1L3" does?).
 
Old 10-06-2010, 03:33 PM   #27
maxmiorim
Member
 
Registered: Sep 2010
Location: Brazil
Distribution: Slackware
Posts: 43

Rep: Reputation: 8
Quote:
Originally Posted by MadDino View Post
There is no gsmmodem.
Adding my user to the dialout group didn't help.
Remember that you have to log out and then log in to be considered a member of the said group (no, it's not the same as closing the terminal emulator and opening it again).

Did you try to connect as root or using su/sudo? It'd tell if this is related to permissions or not.
 
Old 10-06-2010, 08:11 PM   #28
bnguyen
Member
 
Registered: Jul 2010
Distribution: Slackware
Posts: 125

Rep: Reputation: 33
MadDino, did you try NetworkManager as I suggested in a post before?

Don't know about your modem model, but this link may be helpful
http://dgthanhan.blogspot.com/2010/0...th-fedora.html

The modem in that link is exactly what I am using, and the steps in that post for creating a Mobile Broadband Connection is now simpler. I only have to enter the APN.
 
Old 10-06-2010, 08:11 PM   #29
bnguyen
Member
 
Registered: Jul 2010
Distribution: Slackware
Posts: 125

Rep: Reputation: 33
sorry, doubled post...
Last edited by bnguyen; 10-06-2010 at 08:12 PM. Reason: doubled post
 
Old 10-06-2010, 08:24 PM   #30
MadDino
LQ Newbie
 
Registered: Jul 2010
Posts: 25

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by janhe View Post
Ok, I think we're going to get somewhere.
If we base ourself loosely on http://wiki.archlinux.org/index.php/..._on_the_device (link provided by maxmiorim earlier in this thread, thank you maxmiorim)

The kernel already loads usbserial, so the udev rules don't have to be changed.

The hal rules are something else. Put this in /etc/hal/fdi/information/10-modem.fdi :
Code:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- xml -*- -->

<deviceinfo version="0.2">
  <device>
    <match key="info.category" string="serial">
        <!-- ZTE MF636DB HSDPA USB dongle -->
        <match key="@info.parent:usb.product_id" int="0x0033">
          <match key="@info.parent:usb.interface.number" int="3">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
          </match>
        </match>
    </match>
  </device>
</deviceinfo>
I copied that from the ArchWiki, but changed product_id to 0x0033.

Take the wvdial.conf from the ArchWiki and try to make a connection.
Let me know how it turns out.

EDIT:
It seems that you need to specify /dev/ttyUSB3 instead of /dev/ttyUSB0
source: http://news.softpedia.com/news/How-t...u-158663.shtml
Also, if it fails again after
Code:
--> Waiting for carrier.
ATM1L3DT*99#
then try changing
Code:
Dial Command = ATM1L3DT
to
Code:
Dial Command = ATDT
or
Code:
Dial Command = ATD
Sorry for the late reply.
For both ATD and ATDT, using /dev/ttyUSB3 (the only one that seems to work), I get:
Code:
wvdial
--> WvDial: Internet dialer version 1.56 (root@gateway)
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
CONNECT
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Thu Oct  7 04:05:17 2010
--> Pid of pppd: 3564
--> Disconnecting at Thu Oct  7 04:05:19 2010
--> The PPP daemon has died: Fatal pppd error (exit code = 1)
--> 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.
And then I can get this:
Code:
[21][root@qwe: log]$ man pppd (error 1:  1      An immediately fatal error of some kind occurred, such as an essential system call failing, or running out of virtual memory.)
[22][root@qwe: log]$ cat /var/log/messages | grep wvdial
[23][root@qwe: log]$ cat /var/log/messages | grep pppd  
Oct  5 21:58:37 qwe pppd[14724]: pppd 2.4.5 started by maddino, uid 0
Oct  5 21:58:37 qwe pppd[14724]: Using interface ppp0
Oct  5 21:58:37 qwe pppd[14724]: Connect: ppp0 <--> /dev/pts/0
Oct  5 21:58:51 qwe pppd[14724]: Modem hangup
Oct  5 21:58:51 qwe pppd[14724]: Connection terminated.
Oct  5 21:58:51 qwe pppd[14724]: Exit.
Oct  7 03:58:36 qwe pppd[3131]: pppd 2.4.5 started by root, uid 0
Oct  7 03:58:37 qwe pppd[3131]: Exit.
Oct  7 03:59:12 qwe pppd[3170]: pppd 2.4.5 started by root, uid 0
Oct  7 03:59:13 qwe pppd[3170]: Exit.
Oct  7 04:02:43 qwe pppd[3362]: pppd 2.4.5 started by root, uid 0
Oct  7 04:02:44 qwe pppd[3362]: Exit.
Oct  7 04:03:12 qwe pppd[3398]: pppd 2.4.5 started by root, uid 0
Oct  7 04:03:13 qwe pppd[3398]: Exit.
Oct  7 04:03:59 qwe pppd[3457]: pppd 2.4.5 started by root, uid 0
Oct  7 04:04:00 qwe pppd[3457]: Exit.
Oct  7 04:05:17 qwe pppd[3564]: pppd 2.4.5 started by root, uid 0
Oct  7 04:05:18 qwe pppd[3564]: Exit.
 
  


Reply
Page 2 of 3 1 2 3



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 10:37 AM.

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