From: Alex Deucher <adeucher@UU.NET>
To: linux-kernel@vger.kernel.org
Subject: Re: Chipsets, DVD-RAM, and timeouts....
Date: Wed, 03 Jan 2001 10:00:08 -0500 [thread overview]
Message-ID: <3A533E78.A3F737ED@uu.net> (raw)
I've been using a maxtor udma/66 13.6GB drive on the hpt366 for over a
year now with no problems whatsoever... even in udma/66 mode (also with
several different BIOS revisions). I have not however, ever been able
to get a cdrom to work on this controller either in windows 98/NT or in
linux 2.2/2.4.
I don't think Maxtors should be blacklisted.
Alex
------------------------
On Tue, 2 Jan 2001, David Woodhouse wrote:
> It's a combination of chipset and drive that causes the problems. I've
> been using ata66 with the same controller on a different drive
> (FUJITSU MPE3136AT) for some time now, and it's been rock solid. It's only
> the IBM DTLA drive that's been a problem on this controller.
Maxtor has problems with hpt366 also.
> Highpoint made changes in their 1.26¹ BIOS to correctly support the IBM
> DTLA drives. If we can get access to information about what they had to
> change, we ought to be able to get it to work on those drives reliably.
Too bad Maxtor is still broken with hpt366...
Also, using CDROM on hpt366 is recipe for disaster...
-Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-03 15:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 15:00 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-01 8:07 Chipsets, DVD-RAM, and timeouts Andre Hedrick
2001-01-01 15:27 ` Jens Axboe
2001-01-01 16:12 ` Alan Cox
2001-01-01 16:50 ` Jens Axboe
2001-01-01 17:34 ` Alan Cox
2001-01-01 22:19 ` Stefan Traby
2001-01-01 22:44 ` Alan Cox
2001-01-02 14:31 ` Jens Axboe
2001-01-02 18:02 ` Kai Henningsen
2001-01-01 18:13 ` Linus Torvalds
2001-01-01 19:06 ` Andre Hedrick
2001-01-01 19:13 ` Alan Cox
2001-01-01 19:53 ` Andre Hedrick
2001-01-01 20:27 ` Linus Torvalds
2001-01-01 20:32 ` Andre Hedrick
2001-01-02 17:30 ` David Woodhouse
2001-01-02 18:38 ` Hakan Lennestal
2001-01-02 18:42 ` Linus Torvalds
2001-01-02 19:15 ` Hakan Lennestal
2001-01-03 0:46 ` James H. Cloos Jr.
2001-01-02 19:44 ` Andre Hedrick
2001-01-02 19:53 ` Alan Cox
2001-01-02 22:27 ` David Woodhouse
2001-01-02 22:42 ` Dan Hollis
2001-01-02 22:44 ` Linus Torvalds
2001-01-02 22:49 ` Andre Hedrick
2001-01-02 22:56 ` Dan Hollis
2001-01-02 22:50 ` Jens Axboe
2001-01-02 22:59 ` Dan Hollis
2001-01-02 22:59 ` Jens Axboe
2001-01-02 23:48 ` davej
2001-01-05 1:42 ` Hakan Lennestal
2001-01-05 3:42 ` Andre Hedrick
2001-01-03 12:40 ` Zdenek Kabelac
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=3A533E78.A3F737ED@uu.net \
--to=adeucher@uu.net \
--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