From owner-freebsd-questions@FreeBSD.ORG Thu Sep 2 11:34:50 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5CE516A4CE for ; Thu, 2 Sep 2004 11:34:50 +0000 (GMT) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F082B43D48 for ; Thu, 2 Sep 2004 11:34:49 +0000 (GMT) (envelope-from richard.williamson@u4eatech.com) Received: by mail.u4eatech.com (Postfix, from userid 503) id 60E1536002B; Thu, 2 Sep 2004 12:34:48 +0100 (BST) Received: from apus.u4eatech.com (apus.degree2.com [172.30.40.129]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.u4eatech.com (Postfix) with ESMTP id E02A8360026; Thu, 2 Sep 2004 12:34:44 +0100 (BST) Message-Id: <6.1.2.0.2.20040902123500.0272ab98@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 02 Sep 2004 12:39:00 +0100 To: putnam@speakeasy.net From: "Richard P. Williamson" In-Reply-To: <20040902104332.GA88731@happy-idiot-talk.infracaninophile.c o.uk> References: <20040902104332.GA88731@happy-idiot-talk.infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 cc: Unix Help Subject: Re: I have no idea X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2004 11:34:50 -0000 >On Thu, Sep 02, 2004 at 07:58:05AM +0000, putnam@speakeasy.net wrote: >> I am experiencing strange things. When my system boots the screen is >>overrun with " " " marks everywhere and as it loads the words on the screen >>are all misspells as do the command's when I type them in, they still give >>the expected response thought. I cannot figure this out do you have any >>Ideas for me.? Further to Matthew Seaman's response, if you are doing this over a serial terminal, you might check the speed/bits/stop/parity of the serial connections (9600, 8N1), and the serial cable itself. I've seen this when the cable was nulled/not nulled when it should not/ should have been, or the baud rate was enough off and one side wasn't auto-sensing the speed correctly. HTH, rip