Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Daniel Brahneborg <daniel.com@wtnord.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Daniel Brahneborg <daniel.com@wtnord.net>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Status of Promise drivers?
Date: Tue, 3 Feb 2004 19:23:36 +0100	[thread overview]
Message-ID: <20040203192336.A5570@nettis.grimsta> (raw)
In-Reply-To: <3FF1CCC1.3050304@pobox.com>; from jgarzik@pobox.com on Tue, Dec 30, 2003 at 02:06:41PM -0500

(Continued from an earlier discussion on the linux-raid list.)

I made the mistake of getting a Highpoint Rocket 1540 instead
of a Promise SATA card, and I simply can't get it to work
with the hpt366 driver in the kernel.  The driver from Highpoint
works better, but only works for the RedHat 2.4.20-8 kernel,
so I won't bother anybody with the problems with that one.

A major factor seems to be the KT600 chipset on the Abit KV7
motherboard. Is this a known issue?

On Tue, Dec 30, 2003 at 02:06:41PM -0500, Jeff Garzik wrote:
> Daniel Brahneborg wrote:
> > I'm having serious problems with my Silicon Image SATA card,
> > and am considering replacing with a (more expensive) Promise
> > SATA TX2 Plus card.
> > 
> > First I have some questions, to avoid getting into the same
> > mess as I'm in now.
> > 
> >  1. What is the status of the Promise driver?  Stable for
> >     everybody? (The SI3112 has problems for some people when
> >     using the IDE driver, and for some with the SCSI driver.)
> >     A binary module is ok, a binary bzImage definately is not.
> 
> It's beta, and stable.

Since I'm paranoid: What motherboards has it been tested and
verified with?

> >  3. Has anybody used it with *2* network cards?  Bonus
> >     points for the builtin Via Rhine and an 8139 card.
> >     (The SCSI driver for the SI3112 kills the machine when a
> >     second card is activated.)

Interestingly enough, the Highpoint card has the same effect
when activating the first network card (it doesn't matter which
one), but only with the 2.4 kernel. The 2.6 kernel works fine.
Again, could this be a motherboard issue?

/Basic


  parent reply	other threads:[~2004-02-03 18:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 19:00 Status of Promise drivers? Daniel Brahneborg
2003-12-30 19:06 ` Jeff Garzik
2003-12-30 19:24   ` Daniel Brahneborg
2003-12-30 19:57     ` Jeff Garzik
2003-12-30 20:18       ` Daniel Brahneborg
2003-12-30 20:25         ` Jeff Garzik
2003-12-30 20:38           ` Daniel Brahneborg
2003-12-30 23:38             ` Jeff Garzik
2004-01-10 15:14           ` Daniel Brahneborg
2003-12-30 20:21       ` Hendrik Visage
2003-12-30 20:27         ` Jeff Garzik
2004-02-03 18:23   ` Daniel Brahneborg [this message]
2004-02-04 15:02     ` Gunnlaugur Thor Briem
2004-02-06 21:13       ` Gunnlaugur Thor Briem
2003-12-30 23:21 ` Status of HighPoint / " Daniel Brahneborg
2003-12-30 23:37   ` Jeff Garzik
2003-12-30 23:55     ` jlewis

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=20040203192336.A5570@nettis.grimsta \
    --to=daniel.com@wtnord.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --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