From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide cd-recording not working in 2.4.18-rc2-ac1
Date: 20 Feb 2002 22:42:30 -0500 [thread overview]
Message-ID: <1014262955.799.27.camel@psuedomode> (raw)
In-Reply-To: <E16diR7-0005RF-00@the-village.bc.nu>
In-Reply-To: <E16diR7-0005RF-00@the-village.bc.nu>
On Wed, 2002-02-20 at 20:54, Alan Cox wrote:
> > I get this on every cd I try and I've tried more than I'd have liked to.
> >
> > Performing OPC...
> >
> /usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error
> > CDB: 2A 00 00 00 00 1F 00 00 1F 00
> > status: 0x2 (CHECK CONDITION)
> > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 21 00 00 00
> > Sense Key: 0x5 Illegal Request, Segment 0
> > Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0
>
> Thats saying that cdrecord sent the drive a bogus command.
>
> > Now I know every cd isn't bad because they used to work in older
> > 2.4.17ish kernels. I have scsi-generic support compiled as a module as
>
> Does it still work with them ?
>
> > SCSI subsystem driver Revision: 1.00
> > scsi0 : SCSI host adapter emulation for IDE ATAPI devices
>
> Right same as I am using
>
> > not sure what else I can get informationwize about what the drive is
> > doing.
>
> What type of IDE controller ?
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
If i retry over and over sometimes it will eventually work. (same cd)
next prev parent reply other threads:[~2002-02-21 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 20:44 ide cd-recording not working in 2.4.18-rc2-ac1 Ed Sweetman
2002-02-21 1:54 ` Alan Cox
2002-02-21 3:42 ` Ed Sweetman [this message]
2002-02-21 8:08 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 20:23 Tony.P.Lee
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=1014262955.799.27.camel@psuedomode \
--to=ed.sweetman@wmich.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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