On Mon, 13 Dec 1999, Steve Ames wrote:
> Hrm... no question that the ATA driver is better today, but its still
> not reporting DMA on my Quantum bigfoot drive (which should support DMA:
> http://www.quantum.com/products/archive/bigfoot_cy/bigfoot_cy_features.htm)
>
> The Maxtor is pretty old (But its been current since 3.0 :) but may
> still have some DMA support? (ftp://ftp.maxtor.com/pub/ide/71626ap.txt)
I have this drive lying in the general few-foot radius of my computer.
It's... well, problematic, to say the least, if trying to use it as a
slave on ata1 where
ata-pci0 (ALi) ---- ata0 --- ad0: <ST36422A/3.04> ATA-4 (16 s/i, 1 dq, UDMA33)
\ `-- acd0: <NEC CD-ROM DRIVE:285/3.04> (PIO)
`-- ata1 --- ad1: <WDC AC310100B/32.02S32> ATA-4 (ditto ad0)
`-- ad2: <Maxtor 71626 AP/QA3C1D20> ATA-0 (16, 1, PIO)
I get these messages and very goofy access to ad1:
Dec 15 19:08:06 green /kernel: Mounting root from ufs:/dev/ad0s1a
Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting
Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done
Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting
Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done
Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting
Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done
Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting
Dec 15 19:08:06 green /kernel: ad1: ad_timeout: trying fallback to PIO mode
Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done
(rc continues here)
So ad1 runs in PIO, and mount may or may not have successfully gotten
ad1 mount entries up.
>
> What am I missing?
>
Something possibly close to what I am :/ That 71626 seems strange.
> -Steve
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED] `------------------------------'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
