From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 22 16:09:46 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDD8716A528 for ; Wed, 22 Dec 2004 16:09:46 +0000 (GMT) Received: from S3.cableone.net (smtp3.cableone.net [24.116.0.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E8743D54 for ; Wed, 22 Dec 2004 16:09:46 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.123.89]) by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 5150404 for multiple; Wed, 22 Dec 2004 09:21:58 -0700 Date: Wed, 22 Dec 2004 10:08:49 -0600 From: Vulpes Velox To: Matej Message-ID: <20041222100849.3cc680a9@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <41C930AC.4030301@bomango.net> References: <41C930AC.4030301@bomango.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: freebsd-hardware@freebsd.org Subject: Re: atapi burning problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 16:09:47 -0000 On Wed, 22 Dec 2004 09:30:36 +0100 Matej wrote: > Hello, > I've tried to burn a dao audio cd using burncd but the system > hanged. No combination of keys worked. Several times. Then I tried > to burn a tao audio cd. The process seemed to be without errors but > the result was very scratchy cd with some kind of distorsion in > there. I thought it was something wrong with .cdr files so I > converted one back to .wav and it was ok. Then I tried to burn a > data cd, but the result was an I/O error when trying to mount it. > So the burning doesn't work. I have the NEC 3500 dvd writer. > Is my only chance to try scsi emulation with atacom or is there > anything else to do? What commands you using for it? Also check if the sysctl hw.ata.atapi_dma is set to 1. I have had the occasional problem caused by this with one drive I have.