Date: Tue, 16 Jul 2002 10:33:32 -0700 (PDT) From: paleph@pacbell.net To: freebsd-questions@freebsd.org Subject: Re: When is FreeBSD going to work properly with KVM switches? Message-ID: <200207161733.g6GHXW902103@pacbell.net>
next in thread | raw e-mail | index | archive | help
I also have the problem that the KVM must be set to the machine being booted in order for the mouse and keyboard to work properly. This is a know problem and there was discussion on it. The problem seems to have appeared with 4.2. I saw a fix in the freebsd-stable archives: Message: 4695118, FROM: John Baldwin, DATE: 11/20/2000 16:43:35 SUBJECT: RE: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 Basically the proposed solution was to remove the `flags 0x1' from the atkbd0 device line in the i386/conf/file This fixed the problem I was having with the Omni Cube 4-Port. I have not checked if this problem still occurs with 4.6. Paul Fronberg paleph@pacbell.net >I have no problems with FreeBSD and my Belkin 4 port Pro KVM switch. The >system will boot fine regardless of where the switch is positioned. No >configuration changes to the kernel or nuttin. > >I have had some problems with switching to another device and back to my >W2k machine and not having my M$ trackball not reset all the buttons. But >thats a complaint for another place. > >On Tue, 16 Jul 2002, Ruben de Groot wrote: > >> On Tue, Jul 16, 2002 at 07:31:05AM -0700, Steve Wingate typed: >> > On Tue, 2002-07-16 at 07:06, Tom Limoncelli wrote: >> > > Ruben de Groot wrote: >> > > > On Mon, Jul 15, 2002 at 07:33:31PM -0400, Eric Olsen typed: >> > > > [...] >> > > > >> > > >>I have not had any problems switching between machines, EXCEPT that >> > > >>when a machine is booting up, the KVM must be set to that machine in >> > > >>order for recognition of the mouse and kbd to work properly. I find >> > > >>this to be true for Win, FBSD, and Linux. Once the machine has booted, >> > > >>I can switch away and back with no problems. I believe I was running >> > > >>FBSD 4.3 when I first installed the KVM. >> > > > >> > > > >> > > > This is a kernel configuration issue. Edit the line >> > > > >> > > > device atkbd0 at atkbdc? irq 1 flags 0x1 >> > > > >> > > > in your kernel configuration file, removing the "flags 0x1" part. Recompile >> > > > your kernel and reboot. The machine will now recognize your keyboard even >> > > > when it was switched away at boot time. >> > > >> > > Why isn't this the default for GENERIC kernels? >> > > >> > > And dare I ask... why is there even a flag for this situation? >> > >> > Probably because it isn't always needed, and in my case didn't work >> > anyway. The problem is the mouse, imo. >> >> Yes, I was responding to the no keyboard on boot problem Eric Olsen was >> talking about. This is not related to your mouse problem (I guess). >> >> The reason there's a flag in the GENERIC kernel to only try the >> keyboard once on boot-up has something to do with trying to make the >> GENERIC kernel as generic as possible (so when a check for PS/2 keyboard >> fails, for example, it will continue to look for other keyboards, like >> USB). At least, that's what I'm told. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207161733.g6GHXW902103>