Date: Thu, 8 Feb 2001 10:19:29 -0700 From: Jason F Wells <jason+freebsd@routermonkey.com> To: simond@irrelevant.org Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Keyboard detection in 4.2-RELEASE, 4.2-STABLE Message-ID: <20010208101929.A443@fry.routermonkey.com> In-Reply-To: <20010208100727.A91375@irrelevant.org>; from simond@irrelevant.org on Thu, Feb 08, 2001 at 10:07:27AM %2B0000 References: <006c01c09128$735f2af0$1200a8c0@gsicomp.on.ca> <8106.981565690@cs.ucl.ac.uk> <20010207101923.B6097@fry.routermonkey.com> <20010208100727.A91375@irrelevant.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 08, 2001 at 10:07:27AM +0000, simond@irrelevant.org wrote: > On Wed, Feb 07, 2001 at 10:19:23AM -0700, Jason F Wells wrote: > > On Wed, Feb 07, 2001 at 05:08:10PM +0000, Greg MATTHEWS wrote: > > > would i be right in assuming that freebsd works like other unixen > > > (sunos/solaris in my exp) in that booting without k/b forces the i/o through > > > the console (serial) port. therefore plugging a kb in has no effect. > > > > I don't think this is the case, as the console output still goes to the > > monitor. I've also played with the settings in /boot.conf (using -D as the > > flag) to force console to always go to screen / keyboard. > > > > As I said before; it used to work, until 4.2; I'm just looking for > > what has changed, and if there's any way to set it back. > > Try removing the flags 0x1 from the atkbd0 line of your config file, that > fixed my problems with the same sort of thing, basically it means that if > it can't detect any keyboard then it doesn't install the keyboard device. > Thank you. That makes it work the same as it used to in previous versions. After you mentioned this, I noticed that the LINT kernel documents this fairly well. Jason. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010208101929.A443>