Path: utzoo!mnetor!tmsoft!dptcdc!jarvis.csri.toronto.edu!mailrus!uflorida!haven!aplcen!wb3ffv!ebeser
From: ebeser@wb3ffv.UUCP ( K3UHF)
Newsgroups: comp.unix.microport
Subject: Re: Internal serial ports under AT&T 3.2
Summary: enix serial ports
	 me too
Keywords: serial ports, UNIX 3.2
Message-ID: <836@wb3ffv.UUCP>
Date: 3 Mar 89 16:04:56 GMT
References: <595@pmafire.UUCP> <396@intek01.UUCP>
Organization: Fast Computer Service, Inc. - Middle River, MD
Lines: 29

In article <396@intek01.UUCP>, mark@intek01.UUCP (Mark McWiggins) writes:
> 
> I have Enix 3.2 and AT&T 3.2.  I first installed Enix.  Had serial port
> problems.  Couldn't run getty at all on the port; got a flickering DTR
> light and "respawn is happening too rapidly; check this line in your
> inittab."  Couldn't reliably dial out via uucp with my Telebit; sometimes 
> it worked (usually just after a reboot), sometimes not.  Kermit mostly
> worked fine, strangely enough, although I noticed that I couldn't change
> line speeds without getting out of Kermit and back in.

I had the same problem with my serial port. The catch-22 was that getty
with a modem expected modem controls. The call to enix solved the problem.
I made a new node with the modem controls. It seems their drivers support
it. 

type:

mknod /dev/ttyM00 c 3 128

then respawn /usr/lib/uucp/uugetty ttyM00.

That will work fine.

> 
> So ... I backed up my data and installed AT&T on my big hard disk.  Running
> uucico -x4 I get "lost line - error 0" and finally CALLER SCRIPT FAILED.
> Kermit hangs when I do "set line /dev/tty00".
> 
I still haven't solved this problem. Anyone else?