From owner-freebsd-stable Sat Aug 25 13:16: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B44A737B407; Sat, 25 Aug 2001 13:15:58 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA08918; Sat, 25 Aug 2001 14:15:49 -0600 (MDT) (envelope-from ken) Date: Sat, 25 Aug 2001 14:15:49 -0600 From: "Kenneth D. Merry" To: Thomas Quinot Cc: stable@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Failure to attach SCSI CD burner Message-ID: <20010825141549.A8851@panzer.kdm.org> References: <20010825185223.A24294@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010825185223.A24294@melusine.cuivre.fr.eu.org>; from thomas@cuivre.fr.eu.org on Sat, Aug 25, 2001 at 06:52:23PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Aug 25, 2001 at 18:52:23 +0200, Thomas Quinot wrote: > Him > > I have an HP4020 CD burner, and for a few weeks it has stopped > being attached at boot, except when there is a CD-ROM in the > drive at boot time. Otherwise I get the following message: > > (cd0:sym0:0:2:0): got CAM status 0x4c > (cd0:sym0:0:2:0): fatal error, failed to attach to device > (cd0:sym0:0:2:0): lost device > (cd0:sym0:0:2:0): removing device entry > > (and subsequently, any attempts at accessing /dev/cd0* result > in 'Device not configured', which makes sense). > Is this a known problem? > > Last 'make world' on that machine is: > 4.4-PRERELEASE #9: Thu Aug 9 17:33:53 CEST 2001 This is pretty odd. It looks like your drive is returning an error when there is no CD in the drive, which is normal. What is not normal is that it isn't providing sense information to tell us what that error is. So this didn't happen before? Have you done anything to the drive? (like upgrade the firmware?) When did you last build a new kernel before this happened? I suppose this started happening when you last built a kernel/world? Do you have any other controllers you could put the drive on to see if it is a controller/driver issue? Try this, without a CD in the drive: camcontrol cmd cd0 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" Then try it with a CD in the drive. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message