On Mon, Feb 14, 2005 at 04:47:46AM +0000, Pigeon wrote:
> On Sun, Feb 13, 2005 at 12:33:51PM -0800, James Vahn wrote:
> > Pigeon wrote:
> > > James Vahn wrote:
> > > > I'm using a vanilla kernel-2.6.10 and have CDR_DEVICE=ATAPI:0,0,0 
> > > > defined
> > > > in /etc/default/cdrecord. The K3B icon has been modified to use "sudo 
> > > > k3b"
> > > > under the icon properties>application>command.
> > >
> > > I thought this was only the case with kernels from 2.6.[78] on? I've
> > > deliberately stayed with 2.6.6 in order to avoid it. I'll give it a
> > > shot next time I have a CD to burn, but AFAICT it's a solution to a
> > > different problem.
> > 
> > Could be, but the problem to me sounds like the early 2.6 kernels.
> > Upgrade to .10, drop the use of ide-scsi, and drop the suid bit.
> > Try sudo and the ATAPI: device instead. It worked a treat for me,
> > the lockups and bad burns of 2.6.x are no longer a problem.
> 
> OK, it's certainly worth a shot... though I notice that Sigve
> Indregard, in the thread "CD recording", is having the same kind of
> problems as me, with an identical CD writer to mine, and 2.6.8. My
> suspicion is it's something funny about that model of drive
> (CyberDrive CW088D). Standardisation doesn't seem to be all it could
> be where CD writers are concerned.

OK, a belated follow-up to this...

I upgraded to 2.6.10, and tried many combinations of dropping the suid
bit and using dev=ATAPI:x,y,z, dev=ATA:x,y,z and dev=/dev/hdx. Nothing
worked. I still got the same flood of errors and lockups. Though for
some odd reason, cdrdao carried on working all through.

Extensive googling revealed about three people who also had a
CyberDrive CW-088D and they couldn't get it to work either (though
apparently the CW-058D does work).

A couple of days ago, the drive ceased to make good recordings - the
burn process (using cdrdao) would complete normally, but reading the
disk back produced input/output errors after an undefined but large
number of sectors had been read. Reading the disk with a different
drive produced the same result.

I replaced it with a Philips PBDV1640B CD/DVD writer, and without any
software upgrades cdrecord started working again (using dev=/dev/hdx
and not suid). (Result for CDs; I haven't tried burning DVDs yet.)

I have written http://pigeon.dyndns.org/stuff/cw088d.html in the hope
that it will help others avoid finding out the hard way that the
CW-088D is buggy.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: 
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F

Attachment: signature.asc
Description: Digital signature

Reply via email to