From owner-freebsd-hardware Sun Jul 28 08:49:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA27461 for hardware-outgoing; Sun, 28 Jul 1996 08:49:34 -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 IAA27435; Sun, 28 Jul 1996 08:49:23 -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 PAA19957; Sun, 28 Jul 1996 15:49:15 GMT Message-Id: <199607281549.PAA19957@gatekeeper.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.4/16.2) id AA230148967; Sun, 28 Jul 1996 09:49:27 -0600 Date: Sun, 28 Jul 1996 09:49:27 -0600 From: Sean Kelly To: Lars_Koeller@odie.physik2.uni-rostock.de Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org In-Reply-To: <199607281333.PAA29567@odie.physik2.uni-rostock.de> (message from Lars Koeller on Sun, 28 Jul 1996 15:33:33 +0200) Subject: Re: Problems connection a terminal!! Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Lars" == Lars Koeller writes: Lars> so everything seems to be o.k. but I never get a Lars> character on the terminal only if I switch on local echo. Are you sure the cable is working ... have you tried some continuity tests on the pins? Are the brightness and contrast controls on the terminal turned all the way up? You might want to check /etc/rc.serial as well too and be certain no strange lock-state or initial-state flags are set for ttyd2. I'd also recommend you see my chapter on Hardwired Terminals in the FreeBSD handbook, but it still hasn't been checked in! :-( -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/