From owner-freebsd-hackers Tue Nov 7 17:16:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 3C75B37B479 for ; Tue, 7 Nov 2000 17:16:23 -0800 (PST) Received: from bellatlantic.net (client-151-198-117-26.nnj.dialup.bellatlantic.net [151.198.117.26]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA22007; Tue, 7 Nov 2000 20:16:02 -0500 (EST) Message-ID: <3A08A951.B9536B7F@bellatlantic.net> Date: Tue, 07 Nov 2000 20:16:01 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Nathan Boeger Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Digi Xem help! References: <3A076622.A12C5979@khmere.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Boeger wrote: > > Sorry if this is the wrong list !! > > Anyway I have a Digi / Xem eisa adapter on 4.1-RELEASE. I have made the > kernel and it see's the card. I have also remade the /dev/ttyD* entries. > > Problem, when I try to access any of the ports I get : > > cu: open (/dev/ttyD00): Device not configured > cu: /dev/ttyD00: Line in use Try to use cua* devices instead of tty*. The tty* devices are for incoming connections, cua* are for outgoing connections. The idea is that if you have a getty listening on tty*, you can still open this port for outgoing connection as cua* and for duration of this connection the tty* port will be transparently locked out. It might be that you have carrier present at this port, so the driver considers it a potentially established outgoing connection and locks out the incoming port. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message