Re: Installing modem.
----- Original Message -----
From: "Aaron Hsu" <nmagaen@mac.com>
To: "Hoyt Bailey" <hoyt13@wiredok.com>
Cc: <debian-user@lists.debian.org>
Sent: Saturday, November 15, 2003 01:42
Subject: Re: Installing modem.
> Alright, it doesn't look like we are getting very far, so I am going to
> throw in the way I would diagnose this issue. *sigh*
>
> pppd, this is about the best way I can think of to get things done.
> It's a little harsh, but nothing a good man page can't handle. I am
> including exerts from the pppd man page I am reading. Hopefully it will
> provide some insights on how to appropriately diagnose this issue. It
> is obvious that the problem with the modem is occuring on the software
> level, at least so far, as I assume you have installed it already and
> it has worked in other OSes. So we need to get the software messages
> coming from the dialers. Hopefully this will help.
>
> [Exert 1]
> EXAMPLES
> The following examples assume that the /etc/ppp/options
> file contains the auth option (as in the default
> /etc/ppp/options file in the ppp distribution).
>
> Probably the most common use of pppd is to dial out to an
> ISP. This can be done with a command such as
>
> pppd call isp
>
> where the /etc/ppp/peers/isp file is set up by the system
> administrator to contain something like this:
>
> ttyS0 19200 crtscts
> connect '/usr/sbin/chat -v -f /etc/ppp/chat-isp'
> noauth
>
> In this example, we are using chat to dial the ISP's modem
> and go through any logon sequence required. The
> /etc/ppp/chat-isp file contains the script used by chat;
> it could for example contain something like this:
>
> ABORT "NO CARRIER"
> ABORT "NO DIALTONE"
> ABORT "ERROR"
> ABORT "NO ANSWER"
> ABORT "BUSY"
> ABORT "Username/Password Incorrect"
> "" "at"
> OK "at&d0&c1"
> OK "atdt2468135"
> "name:" "^Umyuserid"
> "word:" "\qmypassword"
> "ispts" "\q^Uppp"
> "~-^Uppp-~"
> [End Exert 1]
>
> [Exert 2]
> DIAGNOSTICS
> Messages are sent to the syslog daemon using facility
> LOG_DAEMON. (This can be overriden by recompiling pppd
> with the macro LOG_PPP defined as the desired facility.)
> In order to see the error and debug messages, you will
> need to edit your /etc/syslog.conf file to direct the mes-
> sages to the desired output device or file.
>
> The debug option causes the contents of all control pack-
> ets sent or received to be logged, that is, all LCP, PAP,
> CHAP or IPCP packets. This can be useful if the PPP nego-
> tiation does not succeed or if authentication fails. If
> debugging is enabled at compile time, the debug option
> also causes other debugging messages to be logged.
>
> Debugging can also be enabled or disabled by sending a
> SIGUSR1 signal to the pppd process. This signal acts as a
> toggle.
> [End Exert 2]
>
> Nice Debian has provided sample scripts and such. pppconfig will also
> set up those scripts for you. What you need to do is to investigate
> those scripts, see what they are doing, then, once you know that, run
> pppd with pon or whatever you need to do, log it, and read the logs; in
> fact, send the logs to this list. Hopefully that will give us a much
> better idea of what is going on.
>
> Again, I also suggest that you try this on ttyS3 and ttyS4, as I think
> that ttyS4 is the modem, but I want to compare it to something else.
> pppconfig and pppd are the most reliable ways to work with your modem,
> and they will hopefully give us the most information, assuming they are
> configured right. That's where the man pages come in.
>
> Now, if I was in your situation, after I had those error logs, and knew
> exactly what was happening, I would take on the rest of things; but
> it's important to see exactly what's happening on the modem, not just
> if any sound comes out of it.
>
> If anyone has a better idea, let me know, because I would love to have
> an easier way of doing things next time around. :-)
>
It is pretty clear to me that the problem is that there is no connection
between the modem and ttyS3 or 4 or most likely there are two connections
being attempted (at least the logs seem to suggest). Setserial seems to
work but dosent clear the problem even after deleting /dev/ttyS3 and
/dev/ttyS4 the same message appears in the log (Redundant entry in serial
pci-table....[ends with ttyS4 at port 0x7fe0 (irq = 10) is a 16550A. I did
try wvdial and wvdial.conf but just reread post and will try
wvdial.conf.test tomorrow or monday. wvdial appears to be configured ok ,
will recheck.
Regards;
Hoyt
Reply to: