From: Vojtech Pavlik <vojtech@suse.cz>
To: Baldur Norddahl <bbn-linux-kernel@clansoft.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: more than 2 promise ultradma133 TX2 controllers
Date: Sat, 13 Apr 2002 12:03:49 +0200 [thread overview]
Message-ID: <20020413120349.A23974@ucw.cz> (raw)
In-Reply-To: <20020412131831.GA3185@dark.x.dtu.dk>
On Fri, Apr 12, 2002 at 03:18:31PM +0200, Baldur Norddahl wrote:
> Hi,
>
> I noticed if I put in more than 2 promise controllers, the onboard BIOS will
> only detect disks on the first 2 controllers.
>
> I got a system with 4 controllers. Linux detects disks on them all, but when
> it comes to the detect partitions phase it hangs with DMA timeout errors on
> those controllers that didn't get initialized or listed during BIOS boot.
>
> The "Special UDMA Feature" option is supposed to initialize cards that the
> BIOS forgot. The help seems to indicate that this option was made for OLD
> cards, the ultradma133 TX2 is hardly old :-) Besides, it doesn't work.
>
> I changed the configuration to be two ultradma133 and two ultradma100 cards.
> Now the BIOS screen is shown twice, one with the two newer cards and one
> with the two older cards. And linux is happy too.
>
> I have one concern, this setup forces me to put some 160 GB disks on the
> ultradma100 card. Promise never said that card would support this, and the
> BIOS can't detect the disk correctly. Linux however seems to be fine, it
> shows the disks with their correct size and everything seems good. But is it
> safe?
Yes, it is safe. However the fact that 4 133 cards don't work should be
fixed.
UDMA133 isn't rellated to >128GB support in any way.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-04-13 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 13:18 Baldur Norddahl
2002-04-13 10:03 ` Vojtech Pavlik [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=20020413120349.A23974@ucw.cz \
--to=vojtech@suse.cz \
--cc=bbn-linux-kernel@clansoft.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®