SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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
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.
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
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.
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
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?).
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.