It may be a design issue with the Omniview, but I would assume FreeBSD's checks are more stringent than those of Windows boxes -- I've got NT 4.0 and 2k on the same 8-port and they reboot remotely with no keyboard/mouse problems.
-Yanek. > -----Original Message----- > From: Jim King [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 18, 2002 4:47 PM > To: Christopher Masto; Kenneth D. Merry > Cc: Yanek Korff; '[EMAIL PROTECTED]' > Subject: Re: Belkin 8-port KVM = keyboard inactive > > > "Christopher Masto" <[EMAIL PROTECTED]> wrote: > > > On Wed, Apr 17, 2002 at 07:48:58PM -0600, Kenneth D. Merry wrote: > > > I don't know if this has anything to do with your > > > problem, but some of the Belkin Omniview 8 port KVM switches > > > were manufactured with two EEPROMs swapped. See John Polstra's > > > description of the message on -hackers: > > > > No, he had it right; it's the atkbd flags. It's a pain in the ass. > > I'm completely ignorant in this area, but obviously there is a > > difference between "no keyboard" and "KVM switched to different port". > > The BIOS, for example, complains about the former but not the latter. > > I'd guess FreeBSD is requiring more of the keyboard than whatever > > the cheap KVM "trick" keyboard is providing. > > > > I wonder if FreeBSD's probe could be made less demanding so that it > > doesn't kill the keyboard driver in the KVM case. That would > > hopefully satisfy both the USB keyboard situation and those of us > > using these KVM switches. > > Is the problem in the FreeBSD probe or this particular KVM > switch? I don't recall having this problem with my Belkin Omnicube. > Is anybody having problems with other KVM switches besides the Omniview > 8-port? > > Jim > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
