From: Mikael Pettersson <mikpe@csd.uu.se>
To: Cajoline <cajoline@andaxin.gau.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ASUS TUSL2-C and Promise Ultra100 TX2
Date: Fri, 25 Oct 2002 16:01:12 +0200 [thread overview]
Message-ID: <15801.20136.556691.985301@kim.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0210251530530.4572-100000@andaxin.gau.hu>
Cajoline writes:
> I recently setup a box with the following components:
> Intel Celeron 1300 MHz
> ASUS TUSL2-C motherboard
> 2 x Promise Ultra100 TX2 controllers
Those have the 20268 chip, right?
> Any 2.4 kernel I have tried on this machine displays this strange
> behavior: any drives attached to the PDC controllers only work at udma
> mode 2 (UDMA33).
I've recently installed a Ultra133 TX2 (PDC 20269) in a box, and it
also only does UDMA33 in 2.4.20-pre11. 2.5.44 with the PDC driver
for "new" chips does UDMA100, however. (The disk is only UDMA100.)
The latest 2.4.20-pre-ac is supposed to have new IDE drivers, but
I haven't had time to test it myself.
> So I have come to the conclusion there must be some rather bizarre
> incompatibility between the PDCs and this motherboard.
Unlikely.
> Let me note that the PDC controllers do work just fine with other older
> motherboards. And another thing, during boot-up, the PDCs do show the
> drives attached to it, detected at the right udma mode.
Did those boards also use standard 2.4 kernels?
/Mikael
next prev parent reply other threads:[~2002-10-25 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 13:32 ASUS TUSL2-C and Promise Ultra100 TX2 Cajoline
2002-10-25 14:01 ` Mikael Pettersson [this message]
2002-10-26 4:32 ` Cajoline
[not found] <008601c27c91$17671950$020da8c0@nitemare>
2002-10-26 1:59 ` Robbert Kouprie
2002-10-26 5:12 ` Cajoline
2002-10-26 14:38 ` Robbert Kouprie
2002-10-27 2:26 ` Cajoline
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=15801.20136.556691.985301@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=cajoline@andaxin.gau.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.