In article <c80cc499.0410140050.5c821978@posting.google.com >,
andrei tanase <tanase@mail.rdslink.ro> wrote:
>g'day folks. i did a google search on the group for my problem and no
>luck so i thought i'd post it, maybe some of you tangled with this.
>basically, pppd says "/dev/cua00 busy", chat sends "at", expects "ok",
>receives nothing, aborts. HOWEVER, minicom on /dev/cua00 works fine, i
>can talk to the modem, i can dial, everything. what's even more
>frustrating, the pppd conf (/etc/ppp/options, /etc/ppp/isp.chat,
>/etc/ppp/peers/isp) are IDENTICAL (in fact are copied over) to the one
>on another machine where the modem was previously installed and
>worked. since i use a custom kernel on the new machine i thought i
>screwed something up and reverted to GENERIC. nada, same problem, pppd
>can't do anything with /dev/cua00, minicom has no problem. echo
>"atdtXXXXXX\n" > /dev/cua00 makes the modem go off-hook and then
>on-hook again (i can hear the line relay clicking twice), which is
>normal, i say, since echo can't control the DTR and the modem is set
>up to hang up and return to command mode if DTR is low. any ideas?
Hmm ... I don't use ppp at all, but I have some thoughts:
1) Look in /etc/ttys to see whether it is expecting a login
from there. Mine (on a Shuttle SS51G with OpenBSD 3.5) shows:
================================================== ====================
tty00 "/usr/libexec/getty std.9600" unknown off
================================================== ====================
so it is not expecting logins. tty00 is the incoming name for the same
port as cua00 for outgoing. (A ps -ax should not show a getty running
on it. Here is what one look like on a different device:
================================================== ====================
6609 C0 Is+ 0:00.01 /usr/libexec/getty Pc ttyC0
================================================== ====================
I don't know minicom, and don't find it on my system or in the
man pages (perhaps it needs to be installed from the packages?), but
programs like "cu" are designed to gracefully shoulder getty aside (if
the port is not actually in use at that moment) so the same port can be
used for both incoming calls (/dev/ttyxx) and outgoing (/dev/cuaxx).
However, I don't know that pppd is able to do the same.
Another thing which I just spotted in the man page for pppd is
the following:
================================================== ====================
modem_chat
Use the modem control lines during the chat script. The default
is to ignore the state of the CD (Carrier Detect) signal from the
modem during the chat script. If you are using a cua(4) device
(as opposed to a tty(4) device) you should set this option. You
should not use this option with a dialback setup as it will cause
the chat script to exit when carrier drops.
================================================== ====================
Good Luck,
DoN.
--
Email: <dnichols@d-and-d.com> | Voice (all times): (703) 938-4564
(too) near Washington D.C. |
http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---