From owner-freebsd-questions Sun Dec 7 08:59:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA08188 for questions-outgoing; Sun, 7 Dec 1997 08:59:03 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from tok.qiv.com (+owES10+jOdOIERJTWDMDv/GyOnhYZwW@[204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA08172 for ; Sun, 7 Dec 1997 08:58:54 -0800 (PST) (envelope-from jdn@qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id KAA29386; Sun, 7 Dec 1997 10:58:21 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.5) with SMTP id KAA00290; Sun, 7 Dec 1997 10:57:42 -0600 (CST) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Sun, 7 Dec 1997 10:57:41 -0600 (CST) From: Jay Nelson To: jbutt@mwci.net cc: questions@FreeBSD.ORG Subject: Re: Console Questions.. In-Reply-To: <199712070636.AAA02172@subcellar.mwci.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just a thought... Some PC bioses can be set to halt on errors, one of which is a dead keyboard. It might be worth checking. -- Jay On Sun, 7 Dec 1997, James D. Butt wrote: > > We have just moved from BSDI machines to FreeBSD machines.. > > In some of our remote locations we have FreeBSD servers and when > these servers were BSDI we un-hooked the keyboard so that they would > redirect the console to the serial port. Well I have done quite a bit > of searching and I am unable to find a solution to make this happen > with freeBSD. We are running FreeBSD 2.2.5-release. > > I compiled the following into the kernel: > > options COMCONSOLE > options FORCE_COMCONSOLE > > On the test machine that I did this on it locked on boot..I think > that I read that this is the reason that they took it out... > > Now I tried to get a normal terminal session to come up.. > > We have com1 on all of our servers hooked to Livingston portmasters > just incase we have some problem that we would need to access the > machine that way.. > > I know that there are no cable problems.. I can attach to the port on > the portmaster and see the echoed characters in minicom on the > FreeBSD box.. For some reason the FreeBSD box will not spawn login > prompt.. When I use stty -f /dev/ttyd0 chocol chocol wrong I have correct command written down at work> anyway this > would make the port thing that it has CD... On the terminal side I > see the login prompt pop up after I send the above command 2 times... > > On a ps I get > > 9948 d0 Is+ 0:00.03 /usr/libexec/getty std.9600 ttyd0 > > After the login prompt pops... I can not type at all.... The only > thing I can think is it is because their is not a constant Carrier > Detect... > > My ttys looks like > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > I know that this should work.. I have the portmaster and FreeBSD Box > connected via Null modem cable. > > Does anyone have any ideas?? > ----------------------------------------------------------- > James 'J.D.' Butt Voice 319.557.8463 > Network Engineer pager 319.557.6347 > MidWest Communications, Inc. fax 319.557.9771 > 241 Main St. noc@mwci.net > Dubuque, IA 52001 jbutt@mwci.net > ----------------------------------------------------------- > "I used up all my sick days... so I'm calling in dead" > "Lets fight against continental drift!" >