From owner-freebsd-stable Mon Nov 20 21:35: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 85B9A37B4CF; Mon, 20 Nov 2000 21:35:00 -0800 (PST) Received: from zoraida.reyes.somos.net (zoraida.reyes.somos.net [10.0.0.15]) by sanson.reyes.somos.net (8.9.3/8.9.3) with ESMTP id AAA98859; Tue, 21 Nov 2000 00:28:50 -0500 (EST) (envelope-from fran@reyes.somos.net) Date: Tue, 21 Nov 2000 00:36:10 -0500 (EST) From: Francisco Reyes To: John Baldwin Cc: Gerd Knops , freebsd-stable@FreeBSD.ORG Subject: RE: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Nov 2000, John Baldwin wrote: > On 20-Nov-00 Gerd Knops wrote: > > Hi Gang, .......... > > serious problem. It could be argued that it is Belkin's problem, but > > considering the large base of installed KVMs I think FreeBSD should try > > to be KVM friendly. I agree. > Compile a custom kernel and take 'flags 0x1' (detection of keyboards) out of > the atkbd0 line. It is a weird problem with your KVM. My 4-port KVM (Belkin > OmniCube) has no problems finding the keyboards on my 4 testboxes (2 stable and > 2 current). My understanding is that some KVMs are able to "virtualize" the keyboard when it is not there so the machine never detects it is not on that port. FreeBSD would not detect a keyboard loss on a KVM like that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message