From owner-freebsd-questions Sat Sep 1 7:14:40 2001 Delivered-To: freebsd-questions@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 64C4837B407; Sat, 1 Sep 2001 07:14:34 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f81EDjX99800; Sat, 1 Sep 2001 16:13:45 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200109011413.f81EDjX99800@freebsd.dk> Subject: Re: BurnCD problem / bug ?? In-Reply-To: <200109011158.f81BwsS03626@web.sitecontent.com> "from fallous at Sep 1, 2001 04:58:53 am" To: fallous Date: Sat, 1 Sep 2001 16:13:44 +0200 (CEST) Cc: Simon Phillips , freebsd-questions@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems fallous wrote: > > I hope this is the right place to send this type of stuff to. > > > > I am using a Diamond Data 32x12x8 IDE CD burner. I have no problems > > actually writing a Data or Audio session to CD - the session is written > > correctly, but when burncd attempts to close the CD using the 'fixate' > > command, it receives an "Input/output error" (IOCCDRWCLOSECD or some such). > > Subsequent attempts to close the CD result in the same error. > > ... > > On an unrelated note, when I attempt to burn a CD without specifying the > > -s parameter (say, -s 12) I get a similar error message ("Input/output > > error") and no data is written to the CD - it works fine to write the > > session when I specify the -s parameter on a supported speed though (e.g. > > -s 12). > > > Is there something I am doing wrong here, or is this a bug? > > it sure seems like a bug, since I've run into the same problems with my > yamaha 8824, which is listed as supported and was working last I tried it (in > ye olde 4.2 days). drive still works fine in the winbox, so it's definitely > burncd-specific. If we are talking -stable or soon to be 4.4, you should upgrade to the latest sources, this problem should be solved now. The problem is in the kernel, not burncd (burncd actually does very little, the major part of the work is done in the ATA driver in the kernel. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message