RE: For next step : about wvdialconf and wvdial

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Okay, So at this point if I keep getting NO DIAL TONE, what is my next troubleshooting step? How do I see if it’s a driver or hardware issue?

Andrew

-----Original Message-----
From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] 
Sent: Sunday, June 24, 2012 1:43 PM
To: Jacques Goldberg
Cc: Andrew Merczynski-Hait; Philippe Vouters; Antonio Olivares; Linmodems
Subject: Re: For next step : about wvdialconf and wvdial

ATI is the first query in the wvdialconf test which accesses the modem hardware.

MarvS

On Sun, Jun 24, 2012 at 1:29 PM, Jacques Goldberg <goldberg@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Sorry Andrew, wrong, this is a very common mistake.
> You can send any AT command to the DRIVER (SOFTWARE) and it will 
> answer an OK This does not prove that a command which acts on HARDWARE 
> has been uderstood and executed by the hardware device ...
>
> Jacques
>
>
> On 06/24/2012 08:12 PM, Andrew Merczynski-Hait wrote:
>
> Ugh. An AT string to my modem responds "OK" but when trying to dial 
> minicom, Kermit, respond "no dial tone". Efax responds "Error: dial 
> command failed", and then "done, returning 2 (unrecoverable error).
>
> I am pretty sure creating the link on /dev/ttyS4 worked, because using 
> minicom on port /dev/ttyS4 AT returns OK.
>
> Gnome-PP does not detect a modem on /dev/ttyS4.
> Wvdial conf shows this:
>
> andrew@ubuntu-11:~$ sudo wvdialconf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> Modem Port Scan<*1>: S0   S1   S2   S3
> WvModem<*1>: Cannot get information for serial port.
> ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S5   S6   S7   S8
> Modem Port Scan<*1>: S9   S10  S11  S12  S13  S14  S15  S16
> Modem Port Scan<*1>: S17  S18  S19  S20  S21  S22  S23  S24 Modem Port
> Scan<*1>: S25  S26  S27  S28  S29  S30  S31
>
>
> Sorry, no modem was detected!  Is it in use by another program?
> Did you configure it properly with setserial?
>
> Please read the FAQ at http://alumnit.ca/wiki/?WvDial
>
> In summary: I think the driver is working because (certain programs 
> on) the computer can talk to the modem. Wvdial and Gnome-PPP still 
> don't know there is a modem there, and the utilities that can talk to 
> the modem (minicom, Kermit, efax) return a "NO DIAL TONE" error when 
> they try to call anything (for efax error see above).
>
> Thanks,
> Andrew
>
> -----Original Message-----
> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
> Sent: Saturday, June 23, 2012 1:34 PM
> To: Andrew Merczynski-Hait
> Cc: Antonio Olivares; Linmodems; Marvin Stodolsky
> Subject: For next step : about wvdialconf and wvdial
>
> [philippe@victor ~]$ ls /dev/ttyS*
> /dev/ttyS0  /dev/ttyS1  /dev/ttyS2  /dev/ttyS3 [philippe@victor ~]$ ls 
> -l /dev/modem lrwxrwxrwx. 1 root root 10 Jun 23 18:11 /dev/modem -> 
> /dev/536ep [philippe@victor ~]$ ls -l /dev/536* crw-rw-rw-. 1 root 
> root 240, 1 Jun 23
> 18:51 /dev/536ep crw-------. 1 root root 240, 1 Jun 23 18:11 
> /dev/536ep0 [philippe@victor ~]$ sudo ln -s /dev/536ep0 /dev/ttyS4 
> [philippe@victor ~]$ sudo wvdialconf Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S1   S2   S3
> WvModem<*1>: Cannot get information for serial port.
> ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS4<*1>: ATQ0 V1 E1 -- OK
> ttyS4<*1>: ATQ0 V1 E1 Z -- OK
> ttyS4<*1>: ATQ0 V1 E1 S0=0 -- OK
> ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
> ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
> ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
> ttyS4<*1>: Modem Identifier: ATI -- OK
> ttyS4<*1>: Speed 230400: AT -- OK
> ttyS4<*1>: Speed 460800: AT -- OK
> ttyS4<*1>: Max speed is 460800; that should be safe.
> ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
>
> Found a modem on /dev/ttyS4.
> Modem configuration written to /etc/wvdial.conf.
> ttyS4<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
> [philippe@victor ~]$ ls -l /dev/ttyS*
> crw-rw----. 1 root dialout 4, 64 Jun 23 19:18 /dev/ttyS0 crw-rw----. 1 
> root dialout 4, 65 Jun 20 21:54 /dev/ttyS1 crw-rw----. 1 root dialout 
> 4, 66 Jun
> 20 21:54 /dev/ttyS2 crw-rw----. 1 root dialout 4, 67 Jun 20 21:54 /dev/ttyS3
> lrwxrwxrwx. 1 root root       11 Jun 23 19:18 /dev/ttyS4 -> /dev/536ep0
> [philippe@victor ~]$ sudo chown root:dialout /dev/ttyS4 
> [philippe@victor ~]$ sudo wvdial
> --> WvDial: Internet dialer version 1.61 Cannot get information for 
> --> serial port.
> --> Initializing modem.
> --> Sending: ATZ
> ATZ
> OK
> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> 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.
>
> --
> Philippe Vouters (Fontainebleau/France)
> URL: http://vouters.dyndns.org/
> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>
>




[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux