From owner-freebsd-hardware Mon Jul 29 07:57:58 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA01904 for hardware-outgoing; Mon, 29 Jul 1996 07:57:58 -0700 (PDT) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA01897 for ; Mon, 29 Jul 1996 07:57:52 -0700 (PDT) Received: from emu.fsl.noaa.gov (kelly@emu.fsl.noaa.gov [137.75.60.32]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id OAA22888; Mon, 29 Jul 1996 14:57:51 GMT Message-Id: <199607291457.OAA22888@gatekeeper.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.4/16.2) id AA271592286; Mon, 29 Jul 1996 08:58:06 -0600 Date: Mon, 29 Jul 1996 08:58:06 -0600 From: Sean Kelly To: Lars_Koeller@odie.physik2.uni-rostock.de Cc: freebsd-hardware@freefall.freebsd.org, Lars_Koeller@odie.physik2.uni-rostock.de In-Reply-To: <199607290858.KAA06839@odie.physik2.uni-rostock.de> (message from Lars Koeller on Mon, 29 Jul 1996 10:58:37 +0200) Subject: Re: Problems connection a terminal!! Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> Lars Koeller writes: > Yes, sure, cause I can see all the configuration settings on > the screen. :-)) But I will do some changes on the cable perhaps a > version with only 1,2,3 and 7 connected will give some better > results. It might also be time to do some other software test. Try using tip on your FreeBSD host to which the terminal is connected: 1. Make an entry in /etc/remote for the serial port: wyse:dv=/dev/ttyd6:br#9600:pa=none 2. Fire up tip: tip wyse 3. Press keys on the wyse ... they should appear on your FreeBSD host. 4. Press keys on your FreeBSD running tip ... they should appear on your wyse. That really ought to work! If it doesn't, let me know! --k