Date: Sat, 19 Dec 2009 14:06:30 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-sparc64@freebsd.org Subject: Re: and cdrecord [WAS: burncd error on blade 1500] Message-ID: <20091219130630.GA54383@alchemy.franken.de> In-Reply-To: <20091218195514.GA64224@mech-cluster241.men.bris.ac.uk> References: <20091218184220.GA54077@mech-cluster241.men.bris.ac.uk> <20091218195514.GA64224@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091219130630.GA54383>