From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mxsf15.cluster1.charter.net ([209.225.28.215]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1CNxu7-0005vY-00 for ; Sat, 30 Oct 2004 14:24:43 -0400 Received: from mxip07.cluster1.charter.net (mxip07a.cluster1.charter.net [209.225.28.137]) by mxsf15.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id i9UIO2dO028014 for ; Sat, 30 Oct 2004 14:24:02 -0400 Received: from c66.168.24.96.mad.wi.charter.com (HELO maranatha.cah) (66.168.24.96) by mxip07.cluster1.charter.net with ESMTP; 30 Oct 2004 14:24:03 -0400 X-Ironport-AV: i="3.86,111,1096862400"; d="scan'208"; a="385708448:sNHT12903200" Received: from localhost (chomiak@localhost) by maranatha.cah (8.12.11/8.12.11/Submit) with ESMTP id i9UIOdU8005862 for ; Sat, 30 Oct 2004 13:24:45 -0500 X-Authentication-Warning: maranatha.cah: chomiak owned process doing -bs Date: Sat, 30 Oct 2004 13:24:39 -0500 (CDT) From: Cheryl Homiak To: "Speakup is a screen review system for Linux." In-Reply-To: <20041030173159.GA19544@rednote.net> Message-ID: References: <20041030153915.GB14493@tomass.dyndns.org> <20041030173159.GA19544@rednote.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: problems with burning audio cds with cdrecord X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 18:24:48 -0000 Hi Janina. I have tried the following lines in my script which have worked in the past with 2.6 kernels: #!/bin/sh cdrecord -eject speed=2 dev=/dev/hdc -audio 01.cdr 02.cdr I have also tried substituting ATAPI:1,0,0 for the /dev/hdc part. both seem to start up but then I get the trackno=0 and after a while a bunch of out-of-memory errors. I'm not sure why a memory leak would affect my computer and not yours, but that's no great surprise since I don't know that much about memory leaks in the first please. There was a mention in linuxtoday of such a memory leak and that it should generate a linux-2.6.8.2 but it didn't. I think my best next diagnostic move would be to try another 2.6 kernel and see if the problem goes away. -- Cheryl "Where your treasure is, there will your heart be also."