From: mike_rothon <mfr@supanet.com>
To: linux-raid@vger.kernel.org
Subject: Re: hostRAID, AIC-7901, disable? - FIXED
Date: Sun, 20 Mar 2005 12:29:31 +0000 [thread overview]
Message-ID: <d1jq8n$p62$1@sea.gmane.org> (raw)
In-Reply-To: <d1bh6i$vfk$1@sea.gmane.org>
I will prefix this message by stating that I am not a Linux expert in any way!
This is especially true of Kernel and module matters.
Finally, however and after many hours of trying I believe I have found a good
fix to run u320raid on a SuSE linux box!
Tucked away on the Adaptec web site is an IBM download for SLES9, which is
claims to be "released". What isn't mentioned is that this driver **seems to
be** compatible with SuSE Linux 9.1.
You can find an image of the driver update disk here:
http://www.adaptec.com/ibm/downloads/released_serveRAID7e_index.html
Instructions to make the disk are in the adaptec user guide.
If you haven't had experience of driver update disks before (as I hadn't) there
is a good article here:
http://portal.suse.com/sdb/en/2001/12/hmeyer_driver_update.html
Importantly however for SuSE to find the driver you need to rename the directory
from i386-SLES3 to i386-9.1 and the subdirectories in the update.tar.gz file to
match your kernel version. CAVEAT - this is slightly risky - as it leads to a
"tainted" kernel.
With the stock kernel on the 9.1 CD's it appears the driver is compatible
although there is a tainted message during boot.
Feedback is welcomed, particular about the advisability of this solution.
Mike Rothon.
Certisa Ltd.
www.certisa.com
prev parent reply other threads:[~2005-03-20 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 16:04 hostRAID, AIC-7901, disable? murray evans
2004-12-13 21:09 ` Colin McDonald
2004-12-13 21:15 ` murray evans
2004-12-15 17:49 ` Doug Ledford
2004-12-21 20:41 ` linuxraid
2005-03-17 9:05 ` mike_rothon
2005-03-20 12:29 ` mike_rothon [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='d1jq8n$p62$1@sea.gmane.org' \
--to=mfr@supanet.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).