From owner-freebsd-bugs  Sat Nov 14 08:55:19 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA26171
          for freebsd-bugs-outgoing; Sat, 14 Nov 1998 08:55:19 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from localhost.zilker.net (jump-tnt-0093.customer.jump.net [207.8.127.93])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26165
          for <freebsd-bugs@freebsd.org>; Sat, 14 Nov 1998 08:55:16 -0800 (PST)
          (envelope-from marquard@zilker.net)
Received: (from marquard@localhost)
	by localhost.zilker.net (8.8.8/8.8.8) id KAA19294;
	Sat, 14 Nov 1998 10:54:57 -0600 (CST)
	(envelope-from marquard)
To: freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/8666: X blocks serial port with getty process on it
References: <199811121451.JAA00653@sherman.softpulse.com>
From: Dave Marquardt <marquard@zilker.net>
Date: 14 Nov 1998 10:54:14 -0600
In-Reply-To: Tim Allman's message of "Thu, 12 Nov 1998 09:51:53 -0500 (EST)"
Message-ID: <85pvaqfc5l.fsf@localhost.zilker.net>
Lines: 25
X-Mailer: Quassia Gnus v0.22/XEmacs 19.16 - "Lille"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Tim Allman <tim@softpulse.com> writes:
> When the OS is booted up without X all is well. The following line in 
> /etc/ttys does exactly what it should. That is it allows logins on the
> serial port.
>        cuaa3   "/usr/libexec/getty std.115200" vt100   on      secure
> 
> However, when X is started either through startx or xdm this port is blocked.
> Logins are impossible and a current user is prevented from using the port.
> The problem remains until the next reboot.
> 
> Interestingly, the modem, setup using the following line is not affected
> by X at all.
> 
>        modem   "/usr/libexec/getty std.115200" dialup  off     insecure
> 
> >How-To-Repeat:
> Boot up without X. Logins through cuaa3 work properly. Start X using startx
> on a console virtual terminal. Serial port is now blocked. Killing X does
> not help.

I wonder if you have some sort of IRQ conflict.  I noticed strange
problems with my screen when my plug-n-play modem was assigned an IRQ
that conflicted with vga0.

-Dave

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message