From owner-freebsd-stable Mon Nov 20 21:43:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id A3A6437B4C5; Mon, 20 Nov 2000 21:43:27 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA15384; Tue, 21 Nov 2000 16:12:06 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 21 Nov 2000 16:12:06 +1030 (CST) From: "Daniel O'Connor" To: Francisco Reyes Subject: RE: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 Cc: freebsd-stable@FreeBSD.ORG, Gerd Knops , John Baldwin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Nov-00 Francisco Reyes wrote: > > 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). I don't have the original mail so I am replying to the reply :) I have a keyboard (no switch or anything) which consistantly fails to detect unless a kernel is rebuilt without 'flags 0x1' for atkbd0. It is a Mitsubishi Diamond Touch, Model number - 6511-PA, Ext number - 41/MIT. The keyboard has those (annoying) Power/Sleep/WakeUp buttons, a version of the keyboard without those buttons doesn't exhibit the problem. The motherboard is Apollo MVP3 based Epox. It is running FreeBSD-4.1. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message