From owner-freebsd-questions@FreeBSD.ORG Tue Aug 16 23:14:30 2005 Return-Path: X-Original-To: freebsd-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 BA8AF16A41F for ; Tue, 16 Aug 2005 23:14:30 +0000 (GMT) (envelope-from mark@mkproductions.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A69143D45 for ; Tue, 16 Aug 2005 23:14:30 +0000 (GMT) (envelope-from mark@mkproductions.org) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j7GNETcm017547 for ; Tue, 16 Aug 2005 19:14:29 -0400 X-ORBL: [66.139.109.212] Received: from [192.168.1.45] (ppp-66-139-109-212.dsl.stlsmo.swbell.net [66.139.109.212]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id j7GNEOhs005932; Tue, 16 Aug 2005 19:14:25 -0400 Message-ID: <4302811A.3010601@mkproductions.org> Date: Tue, 16 Aug 2005 19:13:14 -0500 From: Mark Kane User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050620) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jason References: <430128F1.9@mkproductions.org> <43013444.8080808@ec.rr.com> <43014383.1040400@mkproductions.org> <43026F5B.4010705@ec.rr.com> In-Reply-To: <43026F5B.4010705@ec.rr.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: How to Force UDMA100 Mode on Boot? 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: Tue, 16 Aug 2005 23:14:30 -0000 jason wrote: > I checked the links and saw no dmesg or drive models for all drives. I > can tell you UDMA 133 was not an official spec, a least at first. It > was a maxtor only thing, and not all chipsets handled it. Basically > maxtor tightened the timings on the ide cable signals to squence extra > data. If you have new and old drives, plus different brands I would not > expect to run at 133 speeds. I don't care to look it up now, but you > may want to find out if any other drive manufactures support the 133 > spec today. Also there are load and signal degregation issues with to > think about with longer cables. If you have a full tower case with the > longest cables you can buy you won't get max speeds even at the 133 > setting. If you know someone whos works in a pc rpair shop you could > ask them what cable length does to drive speeds. I am told if you want > to copy drives for customers you want to get a good cable, but only with > 1 device per cable and get it as short as possible. A 2 inch cable will > dramatically shorten the time to copy whole drives compared to a 16 inch > cable. Well now I can't even get two drives on the same channel to mount together. If one is mounted and I try to mount the other one on the same channel, the other gets immediate DMA_READ problems and then failures. This is trying two brand new drives with brand new cables. If I eliminate one of the drives and run one on each channel, they all work fine together. I'm not sure if that rc.local trick that was suggested would work now. I don't know if drives get mounted before rc.local would get executed or not. Going to have to bring back my thread on the errors. -Mark