and cdrecord [WAS: burncd error on blade 1500]

[Anton Shterenlikht]

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. For example this is what I get on ia64 9.0-current:

# cdrecord -scanbus
Cdrecord-Clone 2.01 (ia64-unknown-freebsd9.0) Copyright (C) 1995-2004 Jörg Schilling
Using libscg version 'schily-0.8'.
scsibus0:
        0,0,0     0) 'HP 73.4G' 'ST373454LC      ' 'HPC2' Disk
        0,1,0     1) 'HP 73.4G' 'ST373454LC      ' 'HPC2' Disk
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
scsibus1:
        1,0,0   100) *
        1,1,0   101) *
        1,2,0   102) 'SEAGATE ' 'ST318452LC      ' '2213' Disk
        1,3,0   103) 'HP      ' 'C7438A          ' 'V303' Removable Tape
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
#

So I think this Cannot open SCSI driver error might be
caused by some other problem on my system, and not by
the cdw device. But where??

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423