Re: cdrecord bug?
On Thu, 17 Jul 2003 12:40:37 +0200
David Fokkema <dfokkema@ileos.nl> wrote:
>
> Hi group,
>
> with the cdrecord versions from testing and unstable (2.0) I am unable
> to work with an ATAPI CDROM. With the woody version (1.10) I can do:
>
> cdrecord dev=0,0 -toc
>
> and get a table of contents of an inserted audio cd. On two different
> systems, I get an error using the 2.0 version: 'cannot init drive'. It's
> picking the same drivers, using scsi (ide-scsi) so no problem there,
> except that it keeps complaining it can't do anything with the drive. I
> haven't tried on other systems (due to the lack of other systems) but I
> suspect generic-mmc scsi cdrom support is broken. Any clues? Should I
> file a bug report?
With an audio CD in my Lite-ON 48125W CD-RW drive . . .
stax:~-1077> dpkg -l cdrecord
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii cdrecord 2.0+a15-1 A command line CD writing tool
stax:~-1078> cdrecord dev=0,0 -toc
Cdrecord 2.01a15 (i686-pc-linux-gnu) Copyright (C) 1995-2003 J?rg Schilling
scsidev: '0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'LITE-ON '
Identifikation : 'LTR-48125W '
Revision : 'VS06'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
first: 1 last 17
track: 1 lba: 0 ( 0) 00:02:00 adr: 1 control: 0 mode: -1
track: 2 lba: 11518 ( 46072) 02:35:43 adr: 1 control: 0 mode: -1
track: 3 lba: 25838 ( 103352) 05:46:38 adr: 1 control: 0 mode: -1
track: 4 lba: 38244 ( 152976) 08:31:69 adr: 1 control: 0 mode: -1
track: 5 lba: 56342 ( 225368) 12:33:17 adr: 1 control: 0 mode: -1
track: 6 lba: 68261 ( 273044) 15:12:11 adr: 1 control: 0 mode: -1
track: 7 lba: 79601 ( 318404) 17:43:26 adr: 1 control: 0 mode: -1
track: 8 lba: 91056 ( 364224) 20:16:06 adr: 1 control: 0 mode: -1
track: 9 lba: 104629 ( 418516) 23:17:04 adr: 1 control: 0 mode: -1
track: 10 lba: 113510 ( 454040) 25:15:35 adr: 1 control: 0 mode: -1
track: 11 lba: 126262 ( 505048) 28:05:37 adr: 1 control: 0 mode: -1
track: 12 lba: 138691 ( 554764) 30:51:16 adr: 1 control: 0 mode: -1
track: 13 lba: 148617 ( 594468) 33:03:42 adr: 1 control: 0 mode: -1
track: 14 lba: 161951 ( 647804) 36:01:26 adr: 1 control: 0 mode: -1
track: 15 lba: 170645 ( 682580) 37:57:20 adr: 1 control: 0 mode: -1
track: 16 lba: 182946 ( 731784) 40:41:21 adr: 1 control: 0 mode: -1
track: 17 lba: 197319 ( 789276) 43:52:69 adr: 1 control: 0 mode: -1
track:lout lba: 209801 ( 839204) 46:39:26 adr: 1 control: 0 mode: -1
.. . .and 17 is a correct track count. So I don't think the problem
you're experiencing is generic to cdrecord v2 . . .
-c
--
Chris Metzler cmetzler@speakeasy.snip-me.net
(remove "snip-me." to email)
"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear
Reply to: