linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Edward King <edk@cendatsys.com>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
	Mikael Pettersson <mikpe@user.it.uu.se>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: re: Linux 2.4.21pre4-ac5 status report
Date: Mon, 3 Mar 2003 20:57:50 +0100	[thread overview]
Message-ID: <20030303195750.GI6946@louise.pinerecords.com> (raw)
In-Reply-To: <3E63B227.8030101@cendatsys.com>

> [edk@cendatsys.com]
> 
> >>Maybe that's changed in 2.4.21-pre-ac new IDE code, I don't know.
> >>
> >>Your cards don't share interrupts with anything else I hope?
> >>
> I tried  two pdc20268's which failed miserably
> 
> Used an Asus motherboard and an FIC motherboard, different cables, 
> different cards, different powersupply.Hard drives are 200GB western 
> digitals, one drive per channel.  
> 
> Tried an SIIG card with the SiI680 chipset -- same problem using is and 
> the pdc20268, but is more stable than a single pdc -- so now I have 4 
> drives on that card.
> 
> My kernel is 2.4.21-pre4-ac6 -- let me know if the pre5's solve the problem.

I'd be quite interested to know whether the FreeBSD IDE driver can handle
these setups properly.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2003-03-03 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01 12:52 Linux 2.4.21pre4-ac5 status report Mikael Pettersson
2003-03-01 13:04 ` Soeren Sonnenburg
2003-03-03 19:51   ` Edward King
2003-03-03 19:57     ` Tomas Szepe [this message]
2003-03-03 20:56       ` Soeren Sonnenburg
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01  8:14 Soeren Sonnenburg
2003-03-01  8:57 ` Tomas Szepe
2003-03-01 10:29   ` Soeren Sonnenburg
2003-03-01 10:32     ` Tomas Szepe
2003-03-01 10:47       ` Soeren Sonnenburg

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=20030303195750.GI6946@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=edk@cendatsys.com \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@user.it.uu.se \
    /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).