From owner-freebsd-stable Mon Nov 20 16:29:28 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 2FBAF37B4CF for ; Mon, 20 Nov 2000 16:29:25 -0800 (PST) Received: (qmail 13032 invoked by uid 101); 21 Nov 2000 00:29:24 -0000 Message-ID: <20001121002924.13031.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 18:29:23 -0600 To: John Baldwin Subject: Re: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 Cc: Francisco Reyes , freebsd-stable@FreeBSD.org Reply-To: gerti@BITart.com References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 20-Nov-00 Gerd Knops wrote: > > Hi Gang, > > > > Since I updated from 4.1 to 4.2RC1, my Belkin OmnieView Pro > > (F1D108-OSD) is not working properly anymore. The symptoms: If the > > system is rebooted while selected on the KVM switch, everything is > > fine. If the system is rebooted while another system is selected, > > the keyboard is not found: > > > > System selected: > > atkbdc0: at port 0x60,0x64 on isa0 > > atkbd0: flags 0x1 irq 1 on atkbdc0 > > kbd0 at atkbd0 > > > > Other system selected: > > atkbdc0: at port 0x60,0x64 on isa0 > > > > In an EMail to questions someone reported a similar problem. > > > > As I assume quite a number of people use Belkin KVMs, this is a > > 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. > > 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). Granted, this switch is > using PS/2 keyboard and mouse ports. Perhaps it is something finicky > with AT keyboards? Regardless, removing the 'flags 0x1' will fix your > problem. The flag is needed so that people with USB keyboards have > their keyboards recognized as the primary keyboard by the console > driver on boot. > Thanks, that solved it! Might warrant a note in /usr/src/UPDATING. Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message