I was unable to burn any CD-R/RW or DVD-+R/-+RW media with two new Pioneer DVW-109 writers I puchased. I'm attaching a gz of three sample k3b results. In my research, I ran across cdrtools-2.01.01_a09 at the cdrtools web site and also to this posting: http://www.redhat.com/archives/rhl-list/2006-May/msg01392.html From the above posting: .oOo. IMPORTANT NOTE for 6.0 users! Newer Linux kernels have ridiculously low default memorylocked resource limit, which prevents privileged users from starting growisofs 6.0 with "unable to anonymously mmap 33554432: Resource temporarily unavailable" error message. Next version will naturally have workaround coded in, but meanwhile you have to issue following command at command prompt prior starting growisofs: * if you run C-like shell, issue 'limit memorylocked unlimited'; * if you run Bourne-like shell, issue 'ulimit -l unlimited'; .oOo. I added ">=app-cdr/cdrtools-2.01.01_alpha09" to /etc/portage/package.unmask and compiled it in. The 'ulimit' command combined with the _alpha09 version of cdrtools now permits me to successfully write on all the media I've been able to test. Tested on two AMD64 {Opteron} based PCs. You may want to unmask _alpha09 for ~x86 and ~amd64 architectures. For anyone reading this with a Pioneer DVW-109 or DVW-509, you probably want to upgrade your firmware to version 1.58. I have not done so yet {at 1.50 as shipped}, but some of the indicated fixes has to do with successfully writing to some media. Finally, FWIW, instead of leaving k3b's selection of burning driver at 'auto', I've forced it to be 'generic-mmc'. This may prove helpful for others.
Created attachment 87604 [details] archive of several burn error messages
Bad idea to unmask this, burning only works as root - a.k.a. sucks big time.
(In reply to comment #2) > Bad idea to unmask this, burning only works as root - a.k.a. sucks big time. > Oops, sorry about that. I'm still configuring these PCs as root and didn't even think to check as a normal user. You're right - it does suck big time. {sigh} Whomever will look at this is free to close it as "invalid" if desired. However, you may want to be congizant of the apparent 'ulimit' issue during your testing and the seconday issues of updating the firmware of writers. i.e. When an ebuild is finally releasable, perhaps some verbiage regarding updating firmware may be appropriate during the ebuild. Then again, perhaps not. :-)
As cdrtools-2.01.01_alpha10 is out, which gives back capability of writing as user, we can close this bug. alpha10 isn't package-masked, but in ~arch for the next 30 days.
