From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 15 05:45: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 5B41A16A4CE for ; Thu, 15 Jan 2004 05:45:46 -0800 (PST) Received: from dexter.starfire.mn.org (starfire.skypoint.net [199.199.159.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A1B543D2F for ; Thu, 15 Jan 2004 05:45:40 -0800 (PST) (envelope-from john@dexter.starfire.mn.org) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id i0FDjdu57647 for freebsd-hardware@freebsd.org; Thu, 15 Jan 2004 07:45:39 -0600 (CST) (envelope-from john) Date: Thu, 15 Jan 2004 07:45:39 -0600 From: John To: freebsd-hardware@freebsd.org Message-ID: <20040115074539.A57621@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: Failure to probe atapi CDROM unless booting from it 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: Thu, 15 Jan 2004 13:45:46 -0000 When it is identified, the device is identified as follows: Jan 11 17:56:56 pearl /kernel: acd0: CDROM at ata0-slave PIO4 That only happens, however, when I boot from said device (this is on a Compaq Armada M700, P650, 320Mb RAM, BIOS 686H 3/15/2002(latest)). Otherwise, I get Jan 11 18:09:55 pearl /kernel: ata0-slave: ATA identify retries exceeded I am running 4.8R, but I've looked at ata-all.c from 4S, and it doesn't look significantly different with respect to this section of code. Well, it doesn't look at all different with respect to the section of code that produces the error messages above. So - is the BIOS doing something to kick-start that drive that should be added to our code? Anyone else got a similar drive which is working correctly? I've heard from other M700 owners, but they haven't identified their drives. If other drives are working, and no-one else has one of these, maybe I can arrange to trade with the company I bought this from for a different drive, or just buy a DVD-capable drive from them and be done with it. Based on this experience, however, I'd like to be able to specify exactly which drive they should send me, since, apparently, not all drives are quite interchangeable. Other suggestions? -- John Lind john@starfire.MN.ORG