and cdrecord [WAS: burncd error on blade 1500]

[Marius Strobl]

On Sat, Dec 19, 2009 at 08:11:49PM +0000, Anton Shterenlikht wrote:
> On Sat, Dec 19, 2009 at 02:06:30PM +0100, Marius Strobl wrote:
> > On Fri, Dec 18, 2009 at 07:55:14PM +0000, Anton Shterenlikht wrote:
> > > On Fri, Dec 18, 2009 at 06:42:20PM +0000, Anton Shterenlikht wrote:
> > > > on 9.0 current
> > > > 
> > > > # burncd -t -f /dev/acd0 data ./trydata fixate
> > > > burncd: ioctl(CDRIOCINITTRACK): Input/output error
> > > > #
> > > > 
> > > > I've hw.ata.atapi_dma=0 in /boot/loader.conf
> > > 
> > > I also tried cdrecord:
> > > 
> > > # cdrecord -v -dummy dev=1,0,0 ./z.iso
> > > cdrecord: No write mode specified.
> > > cdrecord: Asuming -tao mode.
> > > cdrecord: Future versions of cdrecord may have different drive dependent default
> > > s.
> > > cdrecord: Continuing in 5 seconds...
> > > Cdrecord-Clone 2.01 (sparc64-unknown-freebsd9.0) Copyright (C) 1995-2004 Jörg Sc
> > > hilling
> > > TOC Type: 1 = CD-ROM
> > > scsidev: '1,0,0'
> > > scsibus: 1 target: 0 lun: 0
> > > cdrecord: Error 0. Cannot open SCSI driver.
> > > cdrecord: For possible targets try 'cdrecord -scanbus'.
> > > cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
> > > 
> > > # camcontrol devlist -v
> > > scbus0 on ata0 bus 0:
> > > <>                                 at scbus0 target -1 lun -1 ()
> > > scbus1 on ata1 bus 0:
> > > <TSSTcorp CDW/DVD TS-H492C SI00>   at scbus1 target 0 lun 0 ()
> > > <>                                 at scbus1 target -1 lun -1 ()
> > > scbus-1 on xpt0 bus 0:
> > > <>                                 at scbus-1 target -1 lun -1 (xpt0)
> > > #
> > > 
> > 
> > At least for reading atapicam(4) works on sparc64 and cdrecord
> > is also known to work for writing CDs with SCSI writers on
> > sparc64, I currently don't have hardware to test whether it's
> > also possible to write CDs with ATAPI writers using cdrecord
> > on sparc64 though. Given that atapicam(4) works for reading
> > it's unlikely that there are bugs preventing writing, I think
> > it's way more likely that your drive is one of those incapable
> > of simulating writes or it denies writing in PIO mode.
> 
> It seems atapicam detects this cdw device ok (from dmesg):
> 
> cd0 at ata1 bus 0 scbus1 target 0 lun 0
> cd0: <TSSTcorp CDW/DVD TS-H492C SI00> Removable CD-ROM SCSI-0 device
> cd0: 16.000MB/s transfers
> cd0: cd present [1 x 2048 byte records]
> 
> but scanbus fails:
> 
> # cdrecord -scanbus
> Cdrecord-Clone 2.01 (sparc64-unknown-freebsd9.0) Copyright (C) 1995-2004 Jörg Sc
> hilling
> cdrecord: Error 0. Cannot open SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'.
> cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
> #
> 
> I think cdrecord -scanbus should work even if there is no cdw device
> present.

There's a bug in cdrtools (fixed in cdrtools-devel since some time)
which prevents `cdrecord -scanbus` from working when there's no
scbus0. This bug is limited to bus scanning though and the cdrtools
otherwise should work when specifiy the target via dev=. I'm not
sure whether you're hitting this as accroding to your camcontrol
output there's a scsibus0 on your machine. In any case this works
just fine with cdrtools-devel here:
b1k5# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a62 (sparc64-unknown-freebsd9.0) Copyright (C) 1995-2009 Jrg Schilling
Using libscg version 'schily-0.9'.
scsibus2:
        2,0,0   200) 'JLMS    ' 'XJ-HD166S       ' 'D3S4' Removable CD-ROM
        2,1,0   201) *
        2,2,0   202) *
        2,3,0   203) *
        2,4,0   204) *
        2,5,0   205) *
        2,6,0   206) *
        2,7,0   207) *

Marius