From: Oliver Feiler <kiza@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: What does "hdX: CHECK for good STATUS" mean?
Date: Mon, 28 Oct 2002 23:15:59 +0100 [thread overview]
Message-ID: <200210282315.59281.kiza@gmx.net> (raw)
In-Reply-To: <1035843617.3552.67.camel@irongate.swansea.linux.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 28 October 2002 23:20, you wrote:
> On Mon, 2002-10-28 at 21:47, Oliver Feiler wrote:
> > Btw, why is the drive not set to UDMA(33) on boot (like the other 80 GB
> > Samsung drive)? I haven't found the drive in the ida-dma.c UDMA
> > blacklists. Could this be some braindead BIOS thing? I had to flash a
> > beta BIOS (Asus P5A-B) to get the board to boot with the 80 GB disks at
> > all.
>
> Because there are known problems with some combinations of WD drives and
> Ali controllers.
So this is just a "better be safe than sorry" thing? Obviously my data
survived since I copied ~60 GB onto the drive running in UDMA33 mode. :)
What kind of problems would that be? A long time ago I had a 1.2 GB WD drive
where forcing any DMA mode would result in massive data shredding.
Meaning: once it works in UDMA there is nothing to worry about?
Thanks for the quick answer.
Oliver
- --
Oliver Feiler <kiza@(gmx(pro).net|lionking.org|claws-and-paws.com)>
http://www.lionking.org/~kiza/ <-- homepage
PGP-key ID 0x561D4FD2 --> /pgpkey.shtml
http://www.lionking.org/~kiza/journal/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9vbcfOpifZVYdT9IRAqT+AJ94LWLZwPTSh8huEx6PA0XeBLguGwCfRzgF
t23o4RL/gzqx8/g/UuVzjSc=
=SML7
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-10-28 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 21:47 What does "hdX: CHECK for good STATUS" mean? Oliver Feiler
2002-10-28 22:20 ` Alan Cox
2002-10-28 22:15 ` Oliver Feiler [this message]
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=200210282315.59281.kiza@gmx.net \
--to=kiza@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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