Lucky you. I did not even get so far to spoil the CD. K3b permanently fails to burn any data CD for me with 2.6 kernel. It keeps reporting something about failing mkisofs or cdrecord, operation not permitted or so.
The same setup did work fine in the past with 2.6 kernels. Now, with fully up-to-date SID K3b is unusable. I tried ETCH with 2.6.12 with similar result. I think cdrecord and/or mkisofs are terribly broken now. I am slowly getting fed up with the current quality of the SID/2.6 thing. As far as I remember it has never been so bad as it is now. > -----Original Message----- > From: Arthur H. Johnson II [mailto:[EMAIL PROTECTED] > Sent: Monday, September 26, 2005 4:25 PM > To: debian-user@lists.debian.org > Subject: Cdrecord and linux 2.6.12 > > > I thought I would give you guys the heads up about a problem > I just experienced, before anyone else wastes CDRs, or worse, > looses data. I upgraded to the 2.6.12 kernel last week, and > every CD burned since then has been a coaster. Everything > appeared to burn and fixate like normal, without any errors > whatsoever, however neither Linux or Windows is able to read > the CDs. Essentially I lost a week's worth of backups due to > this error. I'm not upset, I'm just glad I caught it before > I assumed the drive was bad. > > Just a heads up. No errors, except when the disk is read > after burn, something about reading past the end of the disk? > That was under linux. > Windows just flat refuses to recognize a CD in the drive. > Sorry, I lost the error exact read error under linux. > > CDs are burning fine since switching back to 2.6.6. > > -- > .''`. Arthur H. Johnson II > : :' : Debian GNU/Linux Advocate > `. `' AYSO Region 721 U6-G3 Coach > `- adidas: All Day I Dream About Soccer > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > >
