From owner-freebsd-stable@FreeBSD.ORG Thu Jun 14 13:20:17 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4639616A46B for ; Thu, 14 Jun 2007 13:20:17 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id A926F13C469 for ; Thu, 14 Jun 2007 13:20:16 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by ug-out-1314.google.com with SMTP id u2so709163uge for ; Thu, 14 Jun 2007 06:20:15 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=pZLLuGE13bK63EzTJHTM++pTiAPF3NxhYkb1Zrlukr3pHje3GP1cMm5BUpmH21wBAvOqHG0G+ktDpoEJ2QP5FzO55rAIwwNSE8QQvi4761/i/YJQ0yUugDSjrpJ6Cn3QrnDsY5hShnZi3ErIyQxrt5FrmZNYVhvfIFKXSQRSP3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=pR+chEbyxIgyvgJBwr+oe6ujSoW1WmsWd0q4g1rJgNKnppEoBolaACkuJz7Y6lnAlHSpp2QHOSR7gpm1Vwy3mFR3ozgS7lGGDjli5W/9ofcE7FPGfOQhZpUCHFMT3J/B6CDlmBp9PqkVq/QfWhKg7T0cdDUkJUyr2Y+M2y0WwgQ= Received: by 10.78.56.19 with SMTP id e19mr659966hua.1181827215354; Thu, 14 Jun 2007 06:20:15 -0700 (PDT) Received: from ?IPv6:::ffff:127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTP id d26sm4027667nfh.2007.06.14.06.20.13 (version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 06:20:14 -0700 (PDT) From: Tom Evans To: "eculp@argosteve.com" In-Reply-To: <20070614073519.fhyyh35ztw8swssk@correo.argosteve.com> References: <200706132034.22794.idiotbg@gmail.com> <1181817741.1212.3.camel@localhost> <20070614073519.fhyyh35ztw8swssk@correo.argosteve.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-canLSypoi+STR9YbfGQO" Date: Thu, 14 Jun 2007 14:20:12 +0100 Message-Id: <1181827212.1212.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-stable@freebsd.org Subject: Re: atapicam and cd-rw problem, no cd0 but acd0 some error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2007 13:20:17 -0000 --=-canLSypoi+STR9YbfGQO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2007-06-14 at 07:35 -0500, eculp@argosteve.com wrote: > Quoting Tom Evans : >=20 > > On Wed, 2007-06-13 at 20:34 +0200, Momchil Ivanov wrote: > >> Hi guys, > >> > >> I am running 6-STABLE as of today and I cannot use the CD-RW on my > >> IBM T40 to > >> burn CDs. When I put atapicam_load=3D"YES" in loader.conf or compile i= t in the > >> kernel I see the following error > >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=3D0x24 ascq=3D0x00 sks=3D0= x40 > >> 0x00 0x01 > >> and no /dev/cd0 is created. I don`t see the above error without atapic= am > >> loaded or in kernel. This is not something new, I haven`t been able to > >> get /dev/cd0 since more than a month following 6-STABLE, don`t know if= it > >> ever worked on 6 or 6.x, but I certainly cannot get it to work on 6-ST= ABLE. > >> Any help would be appreciated :) I would be happy ot be able to burn C= Ds. > >> > >> I have acd0: CDRW at ata1-master UDMA3= 3 > >> and camcontrol shows: > >> at scbus2 target 0 lun 0 (pass1) > >> > >> Thanks > >> > > > > The error message is benign - the controller tries to send a command to > > the device, the device doesn't support it, so you get the error message= . > > That's all, everything else should work. > > > > Do you load or compile into your kernel > > device scbus > > device cd > > device atapicam > > > > atapicam allows you to access ATAPI devices through the SCSI subsystem, > > so you must ensure that you have a SCSI subsystem to access them > > through. > > > > Cheers > > > > Tom >=20 > Hi Tom, >=20 > I am getting a very similar error with my sony cdrom: >=20 > Jun 14 07:12:36 HOME kernel: acd0: FAILURE - INQUIRY ILLEGAL REQUEST =20 > asc=3D0x24 ascq=3D0x00 > Jun 14 07:12:36 HOME kernel: (probe0:ata1:0:1:0): error 22 > Jun 14 07:12:36 HOME kernel: (probe0:ata1:0:1:0): Unretryable Error > Jun 14 07:12:36 HOME kernel: pass0 at ata1 bus 0 target 1 lun 0 > Jun 14 07:12:36 HOME kernel: pass0: =20 > Removable CD-ROM SCSI-0 device > Jun 14 07:12:36 HOME kernel: pass0: 33.000MB/s transfers > Jun 14 07:12:36 HOME kernel: GEOM: new disk cd0 > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6 > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error > Jun 14 07:12:36 HOME kernel: cd0 at ata1 bus 0 target 1 lun 0 > Jun 14 07:12:36 HOME kernel: cd0: =20 > Removable CD-ROM SCSI-0 device > Jun 14 07:12:36 HOME kernel: cd0: 33.000MB/s transfers > Jun 14 07:12:36 HOME kernel: cd0: Attempt to query device size failed: =20 > NOT READY, Medium not present > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6 > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6 > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): error 6 > Jun 14 07:12:36 HOME kernel: (cd0:ata1:0:1:0): Unretryable Error >=20 > There was a good cd in the burner when booting. >=20 > the unfortunate part is that in this case, it doesn't seem to be =20 > benign because I can't mount any cd nor can I use burncd or k3b. >=20 > Any suggestions appreciated. IIRC, I can use burncd if I remove scsi sup= port. >=20 > Thanks, >=20 > ed >=20 Hey ed Those errors look different to what was described (I only get one such error in my dmesg), and different to what the OP reported (he didnt get a cd0). I don't run STABLE, just CURRENT, so I don't know what to suggest. There was a lot of talk about problems burning in k3b on freebsd-stable@ a few months ago, I suggest searching the archives for k3b and see what the resolution was to that. If you haven't already (and don't have a good reason to not), I'd ensure your kernel + userland are up to date, perhaps track RELENG_6 rather than RELENG_6_[12] and see if that helps. Tom --=-canLSypoi+STR9YbfGQO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGcUCMlcRvFfyds/cRAllDAKCVgOFz/895QIHRYRuDx71OTDfEJACglXCh rFhqyeFYjPvt3LxF/RgKcz8= =Xdld -----END PGP SIGNATURE----- --=-canLSypoi+STR9YbfGQO--