RE: Auto DMA vs. Manual DMA Settings... FBSD 3.51

[Jamie Hermans]

Hi Doug...

Actually, it is a proper UDMA66 cable (so agrees the Promise UDMA66
controller I was playing with a while back).

But ... I'm not looking for UDMA66 speeds, like I mentioned - the
motherboard only supports UDMA33 anyways.

With a tip from another reply, I found this on Maxtor's website: (although
my ASUS board is much newer than Oct 98, it's a start)

Overview: Some older Ultra DMA 33 motherboards with older BIOS' (revision
date 10/28/98 and older) have exhibited compatibility issues with Ultra
DMA/66/100 drives. The symptom manifests itself as a system hangs at boot,
and performance problems. On some motherboards the system does not properly
check the UDMA setting returned by the drive. The end result is that the
motherboard attempts to set itself up in an unsupported mode. These issues
arise because of a bug in the system's BIOS, NOT a problem with the Maxtor
hard drive. Some System's will also have performance problems due to the
controller chipset. To eliminate this problem, Maxtor has developed the
UDMAUPDT.EXE

... Jamie


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Doug White
Sent: Friday, August 25, 2000 10:57 pm
To: Jamie Hermans
Cc: [EMAIL PROTECTED]
Subject: Re: Auto DMA vs. Manual DMA Settings... FBSD 3.51


It may be that:

a) your cable is damaged;
b) your system is too noisy;
c) your disks proclaim UDMA capability but can't actually deliver it.

I'd suggest upgrading to a proper DMA66 cable and see if that helps.

Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED] |  www.FreeBSD.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Auto DMA vs. Manual DMA Settings... FBSD 3.51

[Doug White]

On Fri, 25 Aug 2000, Jamie Hermans wrote:

 I am having an issue with the wd driver (from FBSD 3.51).  Once a customer
 kernel (having the flags 0xa0ffa0ff for wd) is booted, I get screen-full's
 of this error message when there is any hard drive access:
 
DMA failure, DMA status 5active
 
 I can "slow down" or degrade my DMA settings in the BIOS to avoid this
 message, but I'm sure I am taking a performance penalty in doing this.

It may be that:

a) your cable is damaged;
b) your system is too noisy;
c) your disks proclaim UDMA capability but can't actually deliver it.

 http://www.freebsd.org/cgi/mid.cgi?db=mid[EMAIL PROTECTED]
 
 ... where this was covered back in December 1999 - I had hoped that this
 would have been resolved by now.
 
 System hardware - Maxtor UDMA66 drive, motherboard only supports UDMA33
 however, so that's not really an issue.

I'd suggest upgrading to a proper DMA66 cable and see if that helps.

 My question ... can I use the ad driver from 4.x with 3.51-RELEASE?  This
 problem doesn't occur under 4.0 or 4.1-RELEASE/STABLE.  If this is possible
 ... how?

No, the ata driver is not available on 3.X.

Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED] |  www.FreeBSD.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message