mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Hamish Whittal <hamish@QEDux.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple CDR's on an IDE based system
Date: Wed, 2 Jun 2004 14:03:59 +0200	[thread overview]
Message-ID: <20040602120359.GB22648@harddisk-recovery.com> (raw)
In-Reply-To: <1086083663.925.114.camel@defender.QEDux.co.za>

On Tue, Jun 01, 2004 at 09:54:23AM +0000, Hamish Whittal wrote:
> I have a machine that has 3 CDRW's in it. I have tried many different
> configurations of these drives on various IDE controllers, but am still
> having some problems.
> 
> I will try to sketch the scenario:
> CDRW1 slave on controller with HDD
> CDRW2 as master on second on-board IDE controller
> CDRW3 as master on additional PCI IDE controller
> 
> (I have also tried adding 2 PCI IDE controllers, and putting each CDRW
> as master on each of these controllers, but I get the FIFO buffer
> dropping to 0% very soon after starting a write).

What kind of PCI controller was that? I've seen that kind of behaviour
with Promise IDE cards.

> My machine is a Debian linux IDE based machine. The specs of the machine
> are as follows:
> CPU      : Intel(R) Pentium(R) 4 CPU 2.80GHz
> 2 IDE controllers, single 120GB HDD.
> Additional PCI IDE controller

What are the *exact* specs: what kind of IDE controller, chipsets
revisions, etc. See the file REPORTING-BUGS in your kernel source tree.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2004-06-02 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01  9:54 Hamish Whittal
2004-06-02 12:03 ` Erik Mouw [this message]
2004-06-02 11:43 Piszcz, Justin Michael

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=20040602120359.GB22648@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=hamish@QEDux.co.za \
    --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

all inboxes | Powered by JetHome®