ASUS DRW-1608P, doesn't write anything

[Scott Long]

David Cross wrote:
> On Sat, 2005-04-16 at 02:16 -0400, David E. Cross wrote:
> 
>>I have problem with an ASUS DRW-1609P with both 5.3 and 5.4.  It won't
>>write any media.  Even "burncd" fails with the following error:
>>
>>(Yes, I know I have "test" mode on, I got tired of making coasters)
>>
>>>burncd -f /dev/acd0 -s max -v -t data file.iso  fixate
>>>adding type 0x08 file mp3.iso.aa size 720000 KB 360000 blocks
>>>next writeable LBA 2136
>>>addr = 2136 size = 737280000 blocks = 360000
>>>writing from file mp3.iso.aa size 720000 KB
>>>written this track 1120 KB (0%) total 1120 KB
>>>only wrote -1 of 32768 bytes: Device busy
>>
>>Relevent line from dmesg:
>>
>>acd0: DVDR <ASUS DRW-1608P/1.17> at ata1-master PIO4
>>
>>atapicam doesn't fix it.  UDMA doesn't fix it.  GENERIC kernel.
>>
>>Reading works fine.
>>
>>Suggestions?
>>
> 
> 
> Ok, let me ammend this a bit... cdrecord _does_ work.  I had tried
> burncd and growisofs (using CAM) for the ATAPI and ATAPICAM methods.  So
> apparently I can burn cds using atapicam and dvds using dvdrecord (from
> savanah, this should really be brought into ports).  I would like burncd
> to work, as I don't like opening my entire bus to just write optical
> media.  Any clues on where I should look for this?
> 

Whether you are using cdrecord or burncd or whatnot, you're sending
MMC-class SCSI commands to the burner to do the work.  cdrecord is much 
more sophisticated in how it does this than burncd (hence why ATAPICAM
is needed and not the canned ioctls that stock ATA provides to burncd),
so it's likely that your drive has some sort of quirk that burncd can't
cope with.  Probably the best way to get this fixed is provide access to
the hardware to Soeren.  Barring that, atapicam + burncd is a fine
replacement.  I'm not sure what you mean by 'opening the entire bus',
though.

Scott