From owner-freebsd-current Mon Aug 13 3:10:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id BCEAB37B406 for ; Mon, 13 Aug 2001 03:10:29 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.143.29.Dial1.SanJose1.Level3.net [209.245.143.29]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id DAB07386; Mon, 13 Aug 2001 03:09:53 -0700 (PDT) Message-ID: <3B77A796.7D4C22E0@mindspring.com> Date: Mon, 13 Aug 2001 03:10:30 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Dillon Cc: Kazutaka YOKOTA , Sean Kelly , current@FreeBSD.ORG Subject: Re: FreeBSD's aggressive keyboard probe/attach References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris Dillon wrote: > Occasionally I'll have mouse sync problems when I switch between > FreeBSD and NT when the NT box has had difference mice (wheel vs. > non-wheel MS mice, apparently) used on it via the dual-user KVM > switch. NT seems to handle that case fairly well by resetting the > PS/2 port and/or the mouse (not sure which) and redetecting the mouse > type. There is actually a Cybex-specific "Microsoft Knowledge Base" article which discusses the registry setting you need to pound on to make NT not attempt to detect the mouse wheel (FWIW). > FreeBSD doesn't like when NT has done that to the mouse, > though, and spews sync errors when I switch back. Usually I can kill > moused and restart it to fix the problem. The 0x8000 flag fixes exactly this problem! > > and the local wiring (non-ethernet version) of the Belkin OmniView > > switches work if the FreeBSD mouse/keyboard is selected at boot > > time, so that the aggressive probe/attach can satisfy itself. > > That is the KVM switch's fault, not FreeBSD's. On all but the most > expensive KVM switches which offer true "keyboard and mouse emulation" > on all ports, even NT (or actually the BIOS, I assume) can fail to > enable keyboard and mouse support in that case. The dual-user Belkin > OmniView seems to handle this correctly. I can't recall any problem > booting FreeBSD on it even when its console isn't active. Yes, it has to to support the dual use case; we have one of those in the lab, as well... > > Belkin went out of its way to support FreeBSD specifically, > > actually: their firmware version 1.9 fixes the local wiring > > switches, so that they can pass FreeBSD's aggressive probe, even > > if the FreeBSD mouse/keyboard is _not_ selected. > > Hmm... I'll have to check, maybe thats why mine works. :-) Little square sticker with rounded corners on the bottom, about 1/2" by 1/4", with just the version, e.g. "1.9"... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message