From owner-freebsd-questions@FreeBSD.ORG Mon Oct 23 03:22:41 2006 Return-Path: X-Original-To: questions@freebsd.org 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 9188616A416 for ; Mon, 23 Oct 2006 03:22:41 +0000 (UTC) (envelope-from juhasaarinen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40D7643D60 for ; Mon, 23 Oct 2006 03:22:36 +0000 (GMT) (envelope-from juhasaarinen@gmail.com) Received: by wx-out-0506.google.com with SMTP id t4so1493208wxc for ; Sun, 22 Oct 2006 20:22:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iLF3YoMt0OeT7Qu03nmg6UIrB5AJfE7FYPtZussXbxD6f5XYL4BCouVyWmeDG1V4AB7zv/e6kof1bPv5vPBG5JsYm3DoR+19AixswEZOLF+MnV2N86V4ulOsSQYFE5A3Xztt6UmzUqMvhHx8vYjP+yZfE8makjUOOldTLYDtEQ0= Received: by 10.70.87.9 with SMTP id k9mr6049755wxb; Sun, 22 Oct 2006 20:22:35 -0700 (PDT) Received: by 10.70.24.18 with HTTP; Sun, 22 Oct 2006 20:22:35 -0700 (PDT) Message-ID: Date: Mon, 23 Oct 2006 16:22:35 +1300 From: "Juha Saarinen" To: "Garance A Drosihn" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <726CFBB1-2BB1-42A5-8A8F-96B880D316A3@HiWAAY.net> Cc: David Kelly , FreeBSD Questions Subject: Re: non-ATA66 cable? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 03:22:41 -0000 > Assuming you have the right cable, make sure you have it connected > correctly. I had a problem like this once, and it turned out that I > had put the cable on backwards. I had connected the end of the cable > meant for the motherboard to the device (a disk, iirc), and visa-versa. > > I switched the cable around, and then it worked fine. Of course, I > didn't discover this until after a few years, while I was in the > process of replacing that PC! ! That made me go and check my machines here... -- Juha