All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>, linux-scsi@vger.kernel.org
Subject: Re: 2.5.56-mm1 fails to detect cd burner
Date: Sun, 30 Mar 2003 22:03:29 -0800	[thread overview]
Message-ID: <20030331060329.GY13178@holomorphy.com> (raw)
In-Reply-To: <3E87D73E.5030107@torque.net>

William Lee Irwin III wrote:
>> There are no ostensible errors. I logged the whole cdrecord session
>> (and used axboe's "special" cdrecord version) and have that, but
>> there's nothing obviously going wrong anywhere in it.

On Mon, Mar 31, 2003 at 03:50:54PM +1000, Douglas Gilbert wrote:
> William,
> Perhaps you could try an older version of cdrecord
> that uses the sg interface. That way we may be able to
> isolate the problem (and you may even get a useful
> CD-R burnt).
> Does that "special" version of cdrecord interface to the
> kernel via the CDROM_PACKET or the SG_IO ioctl?
> When I connected my Yamaha 4416S burner to an Adaptec
> 19160 on the 2.5.65 kernel it locked up in the scan
> as you reported. My Tekram 390U3W with the sym53c8xx_2
> driver didn't have this problem. I haven't had the need
> to burn a CD-R recently. I have downloaded Justin's
> latest aic7xxx driver but haven't loaded it yet.

It seems to be using some kind of ioctl.

-- wli

      reply	other threads:[~2003-03-31  6:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  6:36 2.5.56-mm1 fails to detect cd burner William Lee Irwin III
2003-03-11 16:03 ` William Lee Irwin III
2003-03-17 15:27   ` Justin T. Gibbs
2003-03-18 21:13     ` William Lee Irwin III
2003-03-29 13:49       ` William Lee Irwin III
2003-03-30 21:24         ` William Lee Irwin III
2003-03-30 22:26           ` Justin T. Gibbs
2003-03-31  5:29             ` William Lee Irwin III
2003-03-31  5:50               ` Douglas Gilbert
2003-03-31  6:03                 ` William Lee Irwin III [this message]

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=20030331060329.GY13178@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=dougg@torque.net \
    --cc=gibbs@scsiguy.com \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.