Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!garnett
From: garnett@cs.utexas.edu (John William Garnett)
Newsgroups: comp.sys.next
Subject: device busy errors using tip and kermit
Message-ID: <14903@cs.utexas.edu>
Date: 20 Nov 90 22:18:32 GMT
Organization: UT at Austin, Dept. of CS
Lines: 53

Hello...  I'm having modem difficulties and hoping for some net.help:

the setup --  original 030 cube, NeXTStep 1.0.

the problem --

When I attempt to use NeXT's tip to dial in to a system, I usually get the
following message:

>  /dev/cua: Device busy
>  link down

When I attempt to use kermit 4E(072) to dial in to a system, I usually
get this message:

>  /dev/ttya: Device busy
>  Sorry, can't open line: Device busy

After a period of time, tip and kermit will begin to work correctly
(the error messages do not appear).

There doesn't appear to be any way to predict how long I will have
to wait.  Sometimes even powering off the machine and restarting it
does not prevent the error message from occuring.

I am using a Mac II serial-to-modem cable and I'm using an external
Everex 24E+ (2400 baud) modem (Hayes compatible).

The relevant entries in /etc/remote are as follows:

dial2400|2400 Baud Hayes attributes:\
    :dv=/dev/cua:br#2400:at=hayes:du:
UNIX-2400|2400 Baud dial-out to another UNIX system:\
    :el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D:tc=dial2400:
utmicom|UT Austin Dial-in line:pn=@:tc=UNIX-2400:

The relevant entries in /etc/ttys are as follows:

ttya    "/usr/etc/getty std.2400"   unknown     off secure
ttyda   "/usr/etc/getty D2400"      dialup      on

Can anyone suggest a solution?  Is there a way to manually recycle
the port? (hopefully there is a solution that doesn't require continued
manual intervention)

BTW, no one else is using the machine when these messages occur.

Thanks.
-- 
John Garnett
                              University of Texas at Austin
garnett@cs.utexas.edu         Department of Computer Science
                              Austin, Texas