From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Ole Gjerde <gjerdelist@icebox.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Adaptec 2100S and 2.4.7-pre8(and 2.4.6-ac5) i2o driver
Date: Sat, 21 Jul 2001 15:07:19 -0600 [thread overview]
Message-ID: <20010721150718.A2638@zed.dlitz.net> (raw)
In-Reply-To: <026101c11045$455ec0b0$0b64a8c0@mimer.no>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Thu, Jul 19, 2001 at 01:23:40PM +0200, Ole Gjerde wrote:
> Hi,
> I've been trying to get this Adaptec 2100S RAID card to work. It works fine
> with the adaptec patch(the dpt_i2o driver), but I would really like to get
> it to work with the stock i2o driver. According to the messages I've seen
> so far this should work without any problems.
>
> However, when the kernel boots, it scans the bus, finds the card and starts
> the initializing and then it oopses.
>
Are you using i2o_block or i2o_scsi? i2o_scsi is broken, but some people
have gotten i2o_block to work.
Unfortunately, I'm also having problems with this card on a RAID1 array.
Basically, the install works fine, then if I run dselect update on Debian,
it'll get to Reading Package Lists...1%, then the drive freezes for several
seconds. I get the following message, and the controller starts beeping
(because the array is "degraded"), and the OS continues to work normally
(albeit the ear-pearcing beeping).
/dev/i2o/hda error: Failure communicating to device.
end_request: I/O error, dev 50:09 (i2o block), sector 4416
Alan, if you're following this, do you have any ideas?
--
Dwayne C. Litzenberger - dlitz@dlitz.net
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-07-21 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 11:23 Adaptec 2100S and 2.4.7-pre8(and 2.4.6-ac5) i2o driver Ole Gjerde
2001-07-21 21:07 ` Dwayne C. Litzenberger [this message]
2001-07-23 13:16 ` gjerdelist
2001-07-23 13:30 ` Dwayne C. Litzenberger
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=20010721150718.A2638@zed.dlitz.net \
--to=dlitz@dlitz.net \
--cc=gjerdelist@icebox.org \
--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