From owner-freebsd-stable@FreeBSD.ORG Thu Jun 14 20:36:51 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 BE21A16A46C for ; Thu, 14 Jun 2007 20:36:51 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8B013C465 for ; Thu, 14 Jun 2007 20:36:51 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l5EKalMI090111; Thu, 14 Jun 2007 14:36:47 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4671A6D7.3000202@samsco.org> Date: Thu, 14 Jun 2007 14:36:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Joe Altman , freebsd-stable@freebsd.org, idiotbg@gmail.com References: <20070614120022.D219416A4E1@hub.freebsd.org> <20070614201134.GA22000@panix.com> In-Reply-To: <20070614201134.GA22000@panix.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 14 Jun 2007 14:36:48 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: 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 20:36:51 -0000 Joe Altman wrote: > On Thu, Jun 14, 2007 at 12:00:22PM +0000, freebsd-stable-request@freebsd.org wrote: > >> 13. atapicam and cd-rw problem, no cd0 but acd0 some error >> (Momchil Ivanov) >> 22. Re: atapicam and cd-rw problem, no cd0 but acd0 some error >> (Tom Evans) >> ------------------------------ >> >> Message: 13 >> Date: Wed, 13 Jun 2007 20:34:19 +0200 >> From: Momchil Ivanov >> Subject: atapicam and cd-rw problem, no cd0 but acd0 some error >> >> 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="YES" in loader.conf or compile it in the >> kernel I see the following error >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 >> and no /dev/cd0 is created. I don`t see the above error without atapicam >> 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-STABLE. >> Any help would be appreciated :) I would be happy ot be able to burn CDs. >> >> I have acd0: CDRW at ata1-master UDMA33 >> and camcontrol shows: >> at scbus2 target 0 lun 0 (pass1) >> >> Thanks >> >> ------------------------------ >> >> Message: 22 >> Date: Thu, 14 Jun 2007 11:42:20 +0100 >> From: Tom Evans >> Subject: Re: atapicam and cd-rw problem, no cd0 but acd0 some error >> >> The error message is benign - the controller tries to send a command to > > If it's benign, then why does this occur with the error message > (quoting the OP): > > "...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-STABLE. Any help would be > appreciated :) I would be happy ot be able to burn CDs." > > Which says to me that his drive doesn't work with atapicam in his > kernel, and has not worked for at least one month. This was my > experience, until I removed atapicam from my kernel. > > To the OP: I recommend removing atapicam as a device from your kernel > config; this remedied the issue for me. I could not use my Plextor, > at all, with atapicam as a device in my kernel config. > The atapicam problems were extensively discussed on this list last month. Other than the one person on this thread whose problem was traced to not having the right drivers in the kernel, most problems are simply design limitations of the current system. The design problems are being remedied. No, I do not need people to volunteer to test the code. When I do, it will not be a secret. No, it's not ready yet, and it won't be ready for several months. Scott