From owner-freebsd-current Thu Apr 26 11:33: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from reuben.meganet.net (reuben.meganet.net [209.213.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A3F437B423 for ; Thu, 26 Apr 2001 11:32:55 -0700 (PDT) (envelope-from estair@computer-exchange.com) Received: from proxy (dial-tnt01-p2-015.bos.ma.meganet.net [209.213.73.15]) by reuben.meganet.net (8.9.3/8.9.1-BW0200.01SP) with SMTP id OAA02105 for ; Thu, 26 Apr 2001 14:32:28 -0400 From: estair@computer-exchange.com Message-ID: <00c001c0ce7f$7e7a8120$4900a8c0@mshome.net> To: Subject: Keyboard controller locks up during kernel initialization with Belkin KVM switch... Date: Thu, 26 Apr 2001 14:34:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a Belkin OmniView SE 4-port PS/2 KVM switch at home to toggle between my 4 Unix boxen. The problem I'm having is that on the machine running 5-CURRENT if I power on the system (or reboot) when the active switch port is anything other than the BSD box the system boots ok but I cannot log in or safely shut down from the console. All keyboard/ mouse functions are inaccessible and I have to log in via ssh to shut it down gracefully. This problem does not occur if the machine is running any other OS (previously Solaris 8, and linux 2.4) and I *do* recall it happening on another machine that was running 4.2_Release. I'm not a programmer :(, but IMO I'm guessing that when the kernel initializes the console devices (kbd/mouse/vga) it is polling it in a method that is incompatible with the emulation of the KVM switch... ?? Note that I do not have this problem with any of the other systems on this switch running Solaris 8, 2x Linux (2.4.x), Windows 2000. The only reference I've seen to a similar problem is this post: http://www.monkey.org/openbsd/archive/misc/0009/msg00180.html If there is a simple fix that I'm unaware of, I'd love to know it. If not and it is an open/unresolved issue I'd be more than happy to test fixes and give feedback. Thanks to the hackers, Cheers, /eli To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message