Re: today's burn failure
Jonathan Ryshpan <[email protected]> Tue, 22 Dec 2009 13:16:53 -0800
| Newsgroups | gmane.comp.kde.k3b |
|---|---|
| Organization | Berkeley Linux Team |
| Message-ID | <1261516613.2079.62.camel@localhost> |
On Tue, 2009-12-22 at 10:47 -0800, Stanley Zappa wrote: > Today's burn failure (see log below) came with the message "probably a > buffer underrun--please choose a slower burn speed" A couple of possible problems: Your computer is too slow. Exactly what brand, how many CPUs, how much memory, bus speed, etc.? The error log indicates that memory can't be locked. This means that program or data may be swapped out to your hard drive. The CD you are burning is waiting relentlessly for data. If the data is swapped out, it can't be available in time and the write will fail. On my system (Fedora-11), there are instructions on how to make yourself eligible to have a program you execute lock data (including programs) into memory. To get started finding out about locking memory, etc. try $ man cderecord especially the section "PROCESS SCHEDULING PRIORITY". You'll have to check with an expert on Helena Mint Linux, or at least on Ubuntu to see exactly what you should do. These fine details are different on different distros. I hope this doesn't tell you lots about what you already know. Good Luck - jon > What makes this odd is that yesterday I changed permissions to > CDRTOOLS to '777' and managed to burn *one* CD. (Now, once again, I > can't burn any) This doesn't exactly make sense. If you mean that you executed: $ sudo chmod 777 /usr/bin/cdrtools or similar, it shouldn't make any difference. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev