From owner-freebsd-stable Mon Nov 20 21:47: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id 10DCA37B4CF for ; Mon, 20 Nov 2000 21:47:06 -0800 (PST) Received: (qmail 13429 invoked by uid 101); 21 Nov 2000 05:47:04 -0000 Message-ID: <20001121054704.13428.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Mon, 20 Nov 2000 23:47:04 -0600 To: Francisco Reyes Subject: Re: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 Cc: John Baldwin , freebsd-stable@FreeBSD.ORG Reply-To: gerti-freebsds@BITart.com References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Francisco Reyes wrote: > 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. > The Belkin OmniView Pro8 (8 PS2 ports, stackable to 128 ports) is supposed to do just that. It seems the way FreeBSD 4.2 probles triggers something the Belkin people did not anticipate. Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message