It seems Hans Ottevanger wrote:
> Hi folks,
>
> I am currently having problems with my new Dual Celeron testsystem,
> when trying to use UDMA66.
> ABIT BP6
> 2x Celeron 466 (NOT overclocked)
> 128 Mbyte RAM
> Matrox G400 16 MByte
> 3Com 905B
> 2x Maxtor 92041U4 20 GByte
> Aopen CDROM 48x
> When I use the UDMA33 disk, no problem occurs at all, I can even run
> "make buildworld" without any problems. When accessing the disk on the
> UDMA66 channel however, the system regularly hangs, followed by a
First of, you have to use a very current -current, I've committed some
fixes to the HPT/Promise code resently that are vital to making
this work.
If you are using the newest code, then the problem might be that
your disks doesn't work proberly with UDMA66. I've seen several
newer disks that has problems here, and frankly Maxtor is not
known for their quality in this respect.
You could try to disable the UDMA66 code on the HPT chips by
ifdef'ing out the code that deals with it like below, if this
helps you are most like dealing with disks that has problems
with UDMA66. Dont be alarmed though, there is next to no
performance difference for you...
Trying another disk is also an option, I know that the IBM's
work just fine, and that some of the Quantums and WDC's are broken.
Index: ata-dma.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v
retrieving revision 1.31
diff -u -r1.31 ata-dma.c
--- ata-dma.c 2000/02/04 10:20:21 1.31
+++ ata-dma.c 2000/02/12 18:43:47
@@ -435,7 +435,7 @@
if ((device == ATA_MASTER && scp->devices & ATA_ATAPI_MASTER) ||
(device == ATA_SLAVE && scp->devices & ATA_ATAPI_SLAVE))
break;
-
+#if 0
if (udmamode >=4 && !(pci_read_config(scp->dev, 0x5a, 1) & 0x2)) {
error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0,
ATA_UDMA4, ATA_C_F_SETXFER, ATA_WAIT_READY);
@@ -449,6 +449,7 @@
return;
}
}
+#endif
if (udmamode >= 2) {
error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0,
ATA_UDMA2, ATA_C_F_SETXFER, ATA_WAIT_READY);
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
