From owner-freebsd-questions@FreeBSD.ORG Sat Aug 15 20:01:31 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7086106568C for ; Sat, 15 Aug 2009 20:01:31 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by mx1.freebsd.org (Postfix) with ESMTP id 654A28FC4B for ; Sat, 15 Aug 2009 20:01:31 +0000 (UTC) Received: by ewy2 with SMTP id 2so200515ewy.43 for ; Sat, 15 Aug 2009 13:01:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NiDWbS6V3Pg3gQZovOQwVcryXiPjF3usAFckiKFk4+Y=; b=lKEOOVfKlA7Ac41aMMDFA/6uF9WKxaQXjj19aMnuUnNx8VJ5X+zTTTAgRNz1Bof4rU jSgYw7TQ9FMTVfmgSYL8drjLgFRj3pZVCLYnO8wsWdeyeaIU2WCG5qxmLQNZE4AAx4S6 No0vY2xIbEUguv05+9cY97/twX+WomzhJNOG4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=kC22mJYx/XB4lQZnp0VViS5tKBCfx96xkb+yZQTzlaWSQBIr2q1RzILL6E8Lgw73ZN a3G/stSx0tlhmo3rng36v5035TzKX147itq3rFIJdqJuiMaLuQcH4JlXC+ecDBvhCKKX jwdbKxTx2Ohibm51CnRSmBtwUhaQl+Te6lyWc= MIME-Version: 1.0 Received: by 10.210.82.2 with SMTP id f2mr1188581ebb.34.1250366490234; Sat, 15 Aug 2009 13:01:30 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Aug 2009 22:01:30 +0200 Message-ID: <1bd550a00908151301r4f1e814bj88eb09a39bb04685@mail.gmail.com> From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: "b. f." Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: 7.2 burncd and cdrecord problem 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: Sat, 15 Aug 2009 20:01:31 -0000 On Sat, Aug 15, 2009 at 8:02 PM, b. f. wrote: >> I'm trying to get my CD drive to work without so much success. >> Reading is fine, but when I try to burn a CD I get errors in dmesg. > >>Using cdrecord -blank=3Dfast dev=3D3,0,0 I get: > > First, I hope that you are using sysutils/cdrtools-devel rather than > sysutils/cdrtools. =A0The latter is several years out of date, and the > upstream maintainer of the software has said that no one should be > using it, but the maintainer of the FreeBSD port has so far been > unwilling to update it. > > ... > >>And dmesg shows: >>acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=3D0x24 ascq=3D0x00 >>acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=3D0x26 ascq=3D0x00 > > It is not unusual for some errors to appear, even during normal > operation, so these don't necessarily indicate a problem, although it > was good that you posted them. =A0You should run the cdrecord command > with -vv (yes, two v's) to get verbose error messages from cdrecord. > This should give you a better idea of why cdrecord is failing. =A0If the > error messages from -vv are not enough, you can also add -VV, although > this affects the timing of the operations, and should be used with > care when recording. > > I have had problems like this in the past, when a disk was corrupted, > and cdrecord balked at blanking it. =A0I used blank=3Dall with either the > -immed flag, or the -force flag, or both, to solve the problems. Honestly I didn't think this was the problem, but it seems I've had a bad virgin CD set. Two of them (of a set of 5) seem to work fine. I can write, rewrite and blank them. Aaarrghh! sorry for the noise. Nevertheless, I will try to update to cdrtools-devel since I have cdrtools installed Thanks to all of you. > > If you are using cdrtools, you should probably use the cd(4) driver > together with atapicam(4), rather than the acd(4) driver. =A0To prevent > possible problems, it is safer to prevent both drivers from attaching > to the same device. =A0I usually remove: > > device atapicd > > from my kernel, and just use: > > device ata > device atapicam > device scbus > device cd > device pass > > I don't know whether it is possible to disable the acd(4) driver using > just loader.conf(5), device.hints(5), or some other means at boot- or > run-time, but you could look into that if you don't want to go to the > trouble of removing it from your kernel. > > b. >