From: henrik@storner.dk (Henrik Størner)
To: linux-kernel@vger.kernel.org
Subject: Re: athlon+2.2+pdc20267=hang?
Date: 24 Mar 2001 10:19:02 +0100 [thread overview]
Message-ID: <99hoq6$q8$1@osiris.storner.dk> (raw)
In-Reply-To: <18520000.985334866@skittlebrau.trafford.dementia.org>
In <18520000.985334866@skittlebrau.trafford.dementia.org> Derrick J Brashear <shadow@dementia.org> writes:
>Earlier today I swapped an Athlon (tbird) 850 and an Epox 8KTA3 in for the
>dual Celeron I had, moving all the cards into the new system. One of these
>was a Promise PDC20267 with 4 40gb disks attached. The machine would not
>boot; I assumed it was the i686-smp kernel and installed a Redhat
>7.0-provided i386 kernel. Several hours and a dozen or so boots later, it
>looks like when the bios on the PDC20267 is installed, the system hangs
>while booting at the point where it would probe C/H/S from the devices
>attached to the PDC20267 (they've already been identified by that point)
I see the same thing with an ASUS A7V133 motherboard that has a
PDC20265 installed on the motherboard. If I disable the PDC BIOS, the
system boots normally - but trying to use any UDMA mode hangs.
Ordinary mdma2 mode works fine.
So I suspect that the real culprit is the UDMA mode which the BIOS
probably enables - when I boot the the BIOS disabled, the device shows
up as running in pio mode.
All in all, I haven't had much success with the PDC controllers -
both cases I have tried will hang the system when enabling UDMA
(and there is no common hardware involved).
--
Henrik Storner | "ATA100 is another testimony to the fact that
<henrik@storner.dk> | pigs can be made to fly given sufficient thrust"
|
| Linux kernel hacker Alan Cox, on IDE drives
next prev parent reply other threads:[~2001-03-24 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 8:07 athlon+2.2+pdc20267=hang? Derrick J Brashear
2001-03-24 9:19 ` Henrik Størner [this message]
2001-03-24 12:59 ` athlon+2.2+pdc20267=hang? Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='99hoq6$q8$1@osiris.storner.dk' \
--to=henrik@storner.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®