From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Cuenta de la lista de linux <user_linux@citma.cu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Help with promise sx6000 card
Date: 04 Feb 2003 22:52:48 +0000 [thread overview]
Message-ID: <1044399167.29825.12.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030204213903.A21554@ucw.cz>
On Tue, 2003-02-04 at 20:39, Vojtech Pavlik wrote:
> 1) Make sure the card BIOS is enabled.
> 2) In the BIOS of the card, set it to "Other OS', not Linux
Both should work. "Other OS" changes how the promise cards I have map
the IDE controllers and whether the I2O asks the OS for space or not.
Does your BIOS also change the PCI class or pci idents ?
> 3) Disable support for Promise cards in Linux
Shouldnt be needed now days
> 4) Enable I2O and I2O block devices
Use 2.4.19 or later. The promise stuff freaks if you do clever cache
hints and older kernels don't know about that
> 6) With luck, it'll work. Anyway, SX6000's are DAMN SLOW.
7) Sell the promise card to someone who doesnt know better and buy
a 3ware. Certainly under Linux the 3ware is way faster
> Now to get a SX4000 working, that's a much more interesting task ...
SX4000 is i2o or something stranger ?
next prev parent reply other threads:[~2003-02-04 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 22:19 Cuenta de la lista de linux
2003-02-03 22:26 ` John Bradford
2003-02-04 10:21 ` Juergen "George" Sawinski
2003-02-04 12:15 ` Alan Cox
[not found] ` <5E3AE650.2010208@citma.cu>
2003-02-05 16:07 ` Alan Cox
[not found] ` <5E3B06A0.40802@citma.cu>
2020-02-05 18:25 ` Linux Lists
2003-02-05 19:05 ` Alan Cox
2020-02-06 16:28 ` Linux Kernel Architectural Diagram Linux Lists
2003-02-06 15:43 ` Alex Bennee
2003-02-07 23:04 ` Piet Delaney
2003-02-04 20:39 ` Help with promise sx6000 card Vojtech Pavlik
2003-02-04 22:52 ` Alan Cox [this message]
2003-02-04 22:16 ` Vojtech Pavlik
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=1044399167.29825.12.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=user_linux@citma.cu \
--cc=vojtech@suse.cz \
/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®