mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Justin Piszcz <war@starband.net>
Cc: linux-kernel@vger.kernel.org, Andre Hedrick <andre@linux-ide.org>
Subject: Re: sg in 2.4.18
Date: Thu, 16 May 2002 21:46:50 -0700	[thread overview]
Message-ID: <20020517044650.GC627@matchmail.com> (raw)
In-Reply-To: <20020513101050.A3879@coredump.electro-mechanical.com> <3CDFDEAA.A55E2A8F@starband.net>

On Mon, May 13, 2002 at 11:41:30AM -0400, Justin Piszcz wrote:
> I have two Plextor 12/10/32A CDRW's.
> 
> IDE 0 - MASTER: HDD
>              SLAVE: Plextor
> IDE 1 - MASTER: Plextor
> 
> I burn two cds at the same time at 12X.
>

I have a yamaha 16x and a nec 24x, both are IDE.

[snip]
> Believe it or not, any combination with the promise controller only yields
> results worse than the setup I've mentioned above.
> 
> I'm not sure why, but any combination you can think of (between the card, and
> 
> two IDE busses on the motherboard) I have tried.
> 
> Any combination involving the promise makes each drive resort to burnproof
> every 5-10 seconds, when I was doing tests, it took about 30-40 minutes to
> burn @ 12X (two cds parellel) due to falling back to burnproof every 5
> seconds or so.
>

Strange, can you read through the thread "A CD with errors (scratches etc.)
blocks the whole system while reading" and see if you are having a similar
problem?

> Also, putting both burners on the same chain currently does not work.
> Because when cdrecord sends the command to FIX the cd after it is done
> burning the data, the command gets sent to both IDE drives causing cdrecord
> to blow up (the burn fails) on the other burner.

Hmm, I wonder in Andre can say anyting about this.

What kernel version are you running?

Can you post the output of lspci?

With both drives running at the same time, each on a seperate cable and
controller, I was able to write without trouble.

00:00.0 Host bridge: Intel Corp. 440FX - 82441FX PMC [Natoma] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]
00:07.2 USB Controller: Intel Corp. 82371SB PIIX3 USB [Natoma/Triton II]
(rev 01)
00:08.0 VGA compatible controller: Trident Microsystems TGUI 9660/968x/968x
(rev d3)
00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20262 (rev
01)
00:0a.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 02)
00:0b.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)

  reply	other threads:[~2002-05-17  4:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 14:10 William Thompson
2002-05-13 14:53 ` Alan Cox
2002-05-13 14:36   ` William Thompson
2002-05-13 15:08 ` Richard B. Johnson
2002-05-13 15:41 ` Justin Piszcz
2002-05-17  4:46   ` Mike Fedyk [this message]
2002-05-17  5:43     ` Andre Hedrick

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=20020517044650.GC627@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=war@starband.net \
    /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®