From owner-freebsd-questions@FreeBSD.ORG Sat May 19 17:25:17 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E414616A400 for ; Sat, 19 May 2007 17:25:17 +0000 (UTC) (envelope-from fj@panix.com) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.freebsd.org (Postfix) with ESMTP id C098913C48C for ; Sat, 19 May 2007 17:25:17 +0000 (UTC) (envelope-from fj@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id AB4B058ABB for ; Sat, 19 May 2007 13:25:08 -0400 (EDT) Received: (from fj@localhost) by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id l4JHP8m23272 for freebsd-questions@freebsd.org; Sat, 19 May 2007 13:25:08 -0400 (EDT) Date: Sat, 19 May 2007 13:25:08 -0400 From: Joe Altman To: freebsd-questions@freebsd.org Message-ID: <20070519172508.GA20300@panix.com> References: <20070518032457.GA22768@panix.com> <464D607A.2080805@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <464D607A.2080805@gmail.com> User-Agent: Mutt/1.5.10i Subject: Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 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, 19 May 2007 17:25:18 -0000 On Fri, May 18, 2007 at 11:14:50AM +0300, Simon Phoenix wrote: > > I have the same error message since version 1.42.2.3 of the atapi-cam.c. > Hangs while writing media was fixed in 1.42.2.4, but this error message > not disappear. > > acd0: DMA limited to UDMA33, controller found non-ATA66 cable > acd0: DVDR at ata1-master UDMA33 > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 > 0x01 Yes; and from what little I know about this, it is a necessary thing to have atapicam as a kernel device because USB flash drives require it: camcontrol devlist at scbus1 target 0 lun 0 (cd0,pass0) at scbus2 target 0 lun 0 (da0,pass1) Without this: device atapicam there is no use for this: device da # Direct Access (disks) What I cannot figure out is why only two people are reporting the existence of this problem.