From owner-freebsd-questions@FreeBSD.ORG Thu Jun 8 00:03:25 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29E9516E482 for ; Wed, 7 Jun 2006 21:32:23 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFFFB43D45 for ; Wed, 7 Jun 2006 21:32:22 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (rwcrmhc12) with ESMTP id <20060607213221m1200o5an8e>; Wed, 7 Jun 2006 21:32:21 +0000 From: Josh Paetzel To: John Nielsen , questions@freebsd.org Date: Wed, 7 Jun 2006 16:32:20 -0500 User-Agent: KMail/1.9.1 References: <200606071004.51622.josh@tcbug.org> <200606071546.08761.lists@jnielsen.net> In-Reply-To: <200606071546.08761.lists@jnielsen.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606071632.20893.josh@tcbug.org> Cc: Subject: Re: burncd error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2006 00:03:31 -0000 On Wednesday 07 June 2006 14:46, you wrote: > On Wednesday 07 June 2006 11:04, Josh Paetzel wrote: > > I'm running 6.1-RELEASE > > > > Trying to burn iso's using burncd gives me an error. > > > > gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate > > > > next writeable LBA 0 > > writing from file i386pkg-3.0.iso size 710566 KB > > written this track 710566 KB (100%) total 710566 KB > > fixating CD, please wait.. > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > > > The 'funny' thing about this is that the CDs I burn work fine. > > (I've tried several different ISOs and have checked the md5's on > > all of them.) > > > > Anyone have an idea of what is going on? I never tried to burn > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > I've seen the same thing for the past several weeks (worked fine at > some point prior to 6.1). I'm running 6-STABLE, updated every > couple weeks. As near as I've been able to determine, the fixate > step doesn't actually do anything, so your CD's will still be > "open" but should work fine under any modern OS. As a workaround > you can repeat the fixate step at a lower speed: burncd -f > /dev/acd0 -s 4 fixate > > I haven't experimented enough to know at what speed the fixate step > breaks, but that does seem to be what's going on. I also haven't > tried turning off ATAPICAM, which would be another interesting data > point. If you or someone else has the time to figure out exactly > which (set of) commits started producing this behavior, that would > be excellent material for a PR. I may get around to it myself but > it's not a high priority. > > > dmesg is attached. > > Looks like you forgot it. In my case (using ATAPICAM): > > acd1: CDRW at ata1-slave UDMA33 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not > present > > JN My client says it included a dmesg...wonder what's going on with that. I've tried using different burn speeds all the way down to 32x. I am using ATAPICAM, I wonder if it is somehow related to that? I think I'll unload that and give it a shot. -- Thanks, Josh Paetzel