On Wed, 24 Feb 1999, Robert Baines wrote:
> the line is one that works for me, so it probably not mgetty itself which
> has a problem with 115200. there are a few things you could check:
>
> when the modem answers, is it doing it by itself by being set to
> autoanswer, or is mgetty actually working it? what do mgetty log files
> say?
Where do I find those log files? From what I read, I expected them to be
in /tmp. Even though I run mgetty with -x 5 now, I see nothing there.
Well, at least nothing mgetty related. I'm pretty sure that mgetty is
running the modem, though, since the modem does not answer if I comment
the mgetty line out in inittab.
> do you have some confusion by referring to /dev/modem or /dev/cua1 in some
> programs and ttyS1 in mgetty? its best to use only ttyS1. even if lock
> files are ok, maybe modem is left in an unsuitable state.
I don't think I'm using amything but ttyS1 anymore. Kernel 2.2.1 has a way
of discouraging you from using cua1...
> try talking to modem with minicom. see if its possible to tell modem to
> answer when phone rings or if it does it by itself. when mgetty is
> running, minicom should be unable to use modem because lock file exists.
I don't have minicom installed at the moment. BUT: Does that mean that
pppd shouldn't be able to run, either? Because I'm running pppd with UUCP
style locks. Kinda sounds like this shouldn't work. Should it?
> robert
Thanks,
Juergen
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
