From owner-freebsd-questions Tue Jan 26 23:08:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08321 for freebsd-questions-outgoing; Tue, 26 Jan 1999 23:08:53 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from elemental.alchemy.com (elemental.alchemy.com [206.58.126.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08314 for ; Tue, 26 Jan 1999 23:08:48 -0800 (PST) (envelope-from steve@alchemy.com) Received: from elemental.alchemy.com (elemental.alchemy.com [206.58.126.23]) by elemental.alchemy.com (8.9.1/8.9.1) with SMTP id XAA22016 for ; Tue, 26 Jan 1999 23:08:01 -0800 (PST) Date: Tue, 26 Jan 1999 23:08:01 -0800 (PST) From: Steve Willoughby To: questions@FreeBSD.ORG Subject: Cascading OmniView console switches: the answer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted a couple of weeks ago about trouble cascading my OmniView console switches with my FreeBSD servers. I finally found the clue on the OmniView web site FAQ (I just wish it were in the manual). It turns out that the model of switch I have (4-port PS/2) requires that the switches be cascaded using a 5-pin DIN (AT-style) keyboard cable, even though everything else uses PS/2 connectors. They work like a charm now. Nice switches too. FYI, in case anyone else was stuck with the same problem. Regards, Steve Willoughby steve@alchemy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message