From owner-freebsd-scsi Mon Oct 19 10:37:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27275 for freebsd-scsi-outgoing; Mon, 19 Oct 1998 10:37:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27270 for ; Mon, 19 Oct 1998 10:36:59 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA23839; Mon, 19 Oct 1998 11:36:18 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810191736.LAA23839@panzer.plutotech.com> Subject: Re: Strange error In-Reply-To: from "Matthew N. Dodd" at "Oct 16, 98 02:14:28 am" To: winter@jurai.net (Matthew N. Dodd) Date: Mon, 19 Oct 1998 11:36:18 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew N. Dodd wrote... > On Fri, 16 Oct 1998, Kenneth D. Merry wrote: > Oct 14 17:56:23 eisa-test /kernel: (da2:bt0:0:2:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > Oct 14 17:56:23 eisa-test /kernel: (da2:bt0:0:2:0): NOT READY asc:4,2 > Oct 14 17:56:23 eisa-test /kernel: (da2:bt0:0:2:0): Logical unit not ready, initializing cmd. required > Oct 14 17:56:23 eisa-test /kernel: (da2:bt0:0:2:0): fatal error, failed to attach to device(da2:bt0:0:2:0): removing device entry > > When I boot with media in the drive. > > Most annoying this behavior. I'm not sure why it thinks it needs to > remove the device entry. Did the patch I sent fix that problem? > > > If it would help I have the entire SCSI reference for the drive and the > > > changer available. (2meg PDF @ 600 odd pages). My review of this document > > > has turned up nothing but maybe someone a bit more clued in to the SCSI > > > system would have better luck. > > > > Well, send it on. I'll take a look through it when I get a chance and see > > if I can figure out what's going on. (or you can just give me the URL to > > download it from somewhere) [ ... ] > > Did this work under the old SCSI code? Do you know if it works with any > > other OSes? > > I'm pretty sure they worked with VMS at one point. > > I'd test 'em with Linux but 1. linux doesn't support OPTICAL devices 2. > linux has no way to set mode pages that I can tell. 3. linux has no scsi > changer support. My NetBSD machines didn't seem to like them but I didn't > try very hard and they are all running really old software. Well, I've taken a look through the spec (yes, the whole thing), and I didn't really see anything that would indicate what the problem is. So, I've got a couple of ideas: - Hook it up to an NT box (or some other platform that HP supports) and see whether it works. I know this is distasteful, and you might have to install some HP drivers to make it work, but it would tell us whether there is a hardware problem or not. - If it works under NT, send me the changer and I'll try to get it to work. We've got SCSI analyzers here and can send bus traces to HP if necessary. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message