Juergen Fiedler <[EMAIL PROTECTED]> writes:
> 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.
it *will* make log files. enable mgetty, get someone to phone you and wait
while it fails to connect. then run a 'find' if you need to, to get the
log file. if you don't have a log file it means mgetty did not go into
action.
> > 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...
that's good, but also a possible difference that matters. i am using
kernels 2.0.34 and 2.0.35. you should maybe have a look in
/usr/src/linux/Documentation to see if there is anything relevant.
> > 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?
i'm not 100% sure what ought to work with uucp locks, but heres what i can
tell you about systems that i have set up with RH5.1:
1) you *should* have minicom or similar to check out ports and modems.
2) when i enable mgetty minicom will not start. it reports device in use.
when i disable mgetty i can start minicom and talk to modem with at
commands. i think this is wrong, because if i understand the docs, i
should be able to start a program to talk to the port/modem unless it is
actually in use. the idea is that mgetty comes to life after a
ring signal is detected. probably my own lock files system is deranged. i
can in fact start a ppp connection to the internet while mgetty is enabled
in inittab. the reason i have not sorted this out is that the system works
well enough for now, but i will get round to it.
keep trying. remember the most wierd thing involved is probably the modem
itself. i remember seeing somewhere that someone had put up a web site
with specs and init strings and other info on modems. might be good if you
can find it.
robert
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
