Date: 14 Nov 1998 10:54:14 -0600 From: Dave Marquardt <marquard@zilker.net> To: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/8666: X blocks serial port with getty process on it Message-ID: <85pvaqfc5l.fsf@localhost.zilker.net> In-Reply-To: Tim Allman's message of "Thu, 12 Nov 1998 09:51:53 -0500 (EST)" References: <199811121451.JAA00653@sherman.softpulse.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85pvaqfc5l.fsf>