From owner-freebsd-questions@FreeBSD.ORG Mon Oct 23 03:03:33 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 D3E9516A407 for ; Mon, 23 Oct 2006 03:03:33 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp6.server.rpi.edu (smtp6.server.rpi.edu [128.113.2.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B4F843D4C for ; Mon, 23 Oct 2006 03:03:32 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp6.server.rpi.edu (8.13.1/8.13.1) with ESMTP id k9N33Vll006956; Sun, 22 Oct 2006 23:03:31 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <726CFBB1-2BB1-42A5-8A8F-96B880D316A3@HiWAAY.net> References: <726CFBB1-2BB1-42A5-8A8F-96B880D316A3@HiWAAY.net> Date: Sun, 22 Oct 2006 23:03:30 -0400 To: David Kelly , FreeBSD Questions From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Cc: 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:03:33 -0000 At 9:15 PM -0500 10/21/06, David Kelly wrote: >Dell PowerEdge 400SC, 6.2-PRERELEASE (altho this is an old issue) > >dmesg says: > >acd0: DMA limited to UDMA33, controller found non-ATA66 cable >acd0: DVDR at ata1-master UDMA33 >cd0: 33.000MB/s transfers > >The controller is properly probed as, > "atapci0: " > >This DVD isn't writing discs as fast as other brands on other machines >and OS's (such as MacOS X). Lite-On has a newer firmware that I have >not tried. Well, first the obvious question: What kind of cable do you have it hooked up with? 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! -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu