Re: Problem using a TEAC DV-W22E with dvd+rw-tools/cdrecord-prodvd/dvdrtools.
>>> If you ever did format it, you _need_ to run cdrecord blank=full
>>> to make it usable again.
>>I get the following error trying to blank the DVD-RW media:
> You areusing a defektive kernel!
> Your kernel does not implement ATAPI CAP auto sense which is required.
> Upgrade to a fixed kernel
Ouch! If you really mean "emulate ATAPI devices as SCSI ditto via CAM",
i.e. the 'device atapicam' in kernel config file: it IS present. I think
I already use this _facility_ through cdrecord. As I say, I already write
CD-R (cdrecord) / write/rewrite CD-RW (cdrecord) / write DVD-R (growisofs)
which all use the device /dev/cd0: CDROM driver for the CAM SCSI subsystem.
I use a GENERIC kernel provided with the 5.2.1 release, with just the
following support added:
### Added by email@example.com:
### For PnP/PCI sound cards.
### USB com devices.
### Allows ATAPI devices to be accessed through the SCSI subsystem.
#device scbus # Already present, just here to remember.
#device cda # Already present, just here to remember.
#device pass # Already present, just here to remember.
#device ata # Already present, just here to remember.
#device atapicd # Already present, just here to remember.
#device da # Direct Access (disks)
### Disk encryption.
I can't see any problem here... Are you?
>># ./cdrecord-wrapper.sh -v -blank=all dev=3,0,0
>>Cdrecord-ProDVD-Clone 2.01a24 (i386-unknown-freebsd5.2) Copyright (C)
>>1995-2004 Jörg Schilling
>>Unlocked features: ProDVD Clone
>>This copy of cdrecord is licensed for:
>>cdrecord-ProDVD: Input/output error. read track info: scsi sendcmd:
>>CDB: 52 00 00 00 00 00 00 00 24 00
>>status: 0x2 (CHECK CONDITION)
>>Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>00 00 00 00 00 00 00 00 00 00 00 00
>>Sense Key: 0xFFFFFFFF , Segment 0
>>Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
>>Sense flags: Blk 0 (not valid)
The binary obtained from ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
contains the string "i386-unknown-freebsd5.2". Is there a difference
between FreeBSD-5.2 and FreeBSD-5.2.1 which can explain my error?