On Mon, Oct 18, 2004 at 08:11:40PM +0100, Alan Chandler wrote: > On Monday 18 October 2004 01:51, Uwe Dippel wrote: > > Sitting on Sarge as-it-comes, daily updated. > > Suddenly xcdroast stops working today; last week it was okay. > > > > This is what I get: > > > > Calling: /usr/lib/xcdroast/bin/xcdrwrap CDRECORD dev= "ATAPI:0,1,0" > > gracetime=2 fs=4096k driveropts=burnfree -v -useinfo speed=24 -dao -eject > > -pad -data "/toast/track-01.iso" ... > > > > scsidev: 'ATAPI:0,1,0' > > devname: 'ATAPI' > > Not sure with xcdroast where the device name is held, but you should get > better results with dev=ATA > > That gives you dma write access. > > 2.6.8 requires you to run as root (as others have noted). I have been unable I use:
kernel-image-2.6.8-1-386 ( Version 2.6.8-4 ) cdrecord ( Version 2.0+a38-1 ) mkisofs ( Version 2.0+a38-1 ) and when I have read : /usr/share/doc/cdrecord/README.ATAPI.setup and apply the part "kernel 2.6.*" cdrecord worked fine. ( (except for the multisession :-) ... ;-) ) (with kernel 2.4.20 ) I guess that it's xcdroast which has a problem with kernel 2.6.8 hth -- Gerard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]