From owner-freebsd-hardware Sun Aug 9 12:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15655 for freebsd-hardware-outgoing; Sun, 9 Aug 1998 12:42:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15649 for ; Sun, 9 Aug 1998 12:42:23 -0700 (PDT) (envelope-from mns@pobox.com) Received: from markspad (dynamic61.pm03.san-jose.best.com [209.24.164.189]) by proxy4.ba.best.com (8.9.0/8.9.0/best.out) with SMTP id MAA08753; Sun, 9 Aug 1998 12:40:35 -0700 (PDT) Message-Id: <199808091940.MAA08753@proxy4.ba.best.com> X-Sender: mns@ (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 09 Aug 1998 12:35:28 -0700 To: "David W. Alderman" , "Jan B. Koum " , richard@pegasus.com (Richard Foulk), Brooks Davis From: Mark Shepard Subject: ProConnect console switch [ was Re: Kbd/Mon/Mouse switch recomendations ] Cc: freebsd-hardware@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I found this thread in the freebsd mail archives and wanted to add some comments. I'm currently experimenting with console switches also, and ran into the same problems with the ProConnect -- with NT and FBSD boxes plugged into a switch, the NT box works fine but the FBSD box fails to detect a mouse on boot, yet works fine if the console switch is "inserted" after booting with a "real" mouse. FWIW, here's what's happening: the ProConnect appears to not implement the PS2 0xF5 disable command -- FreeBSD's psmprobe() routine at one point tries to enable (0xF4) and then disable the PS2 mouse, and the disable fails with an 0xFE (which indicates either a bad command or data transmission error -- but since FreeBSD seems to include code to retransmit, I assume the ProConnect just doesn't implement the disable command. Commenting out this test from psmprobe() seems to allow the mouse to be detected. I wouldn't be surprised if other OS's (NT) simply don't use the 0xF5 disable command, though it wouldn't have been that hard for ProConnect to implement it either (BTW, I haven't talked with Linksys's tech-support to verify whether or not they implement the F5 disable -- it could be the problem has some other subtler cause such as a data xmit error which is timing related.) Question: How's the video quality compare between the OmniView, Aten and ProConnect units? I'm looking for a 4-port switch which will handle 1600x1200 video with minimal degradation of video quality for ~$200 or less. Aside from this PS2 mouse quirk, the ProConnect's video seems pretty good -- perhaps a barely noticable ghosting, perhaps a very slight extra fuzzyness at 1600x1200, but really pretty good. Thanks. Mark file /usr/src/sys/i386/isa/psm.c (freebsd 2.2.7, sup'd a few days ago): /* rebuild kernel with "option PSM_DEBUG=2" to see verbose error msgs */ psmprobe() { ... #if 0 /* skip nitpicking test */ if (!enable_aux_dev(sc->kbdc) || !disable_aux_dev(sc->kbdc)) { /* MOUSE ERROR */ restore_controller(sc->kbdc, command_byte); if (verbose) printf("psm%d: failed to enable the aux device.\n", unit); endprobe(0); } #endif ... } --- Original Message --- Hi, I'm looking for recomendations for Keyboard/Monitor/Mouse switches for use with my FreeBSD and NT systems. I just returned a LinkSys ProConnect 4 CPU switch yesterday because it seems to squash any attempts at serial or ps/2 PnP probing. FreeBSD 2.2.6 also seemed unable to detect the PS/2 mouse through it at boot. After that disaster I figured I'd see what people have had good luck with. I'm looking for a 4 port solution with PS/2 and AT keyboard support and at least PS/2 mouse (good serial support if possiable) support that works with PnP. Suggestions would be greatly appreciated. Thanks for your time, Brooks Davis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message