From owner-freebsd-alpha Mon Aug 12 10:47:13 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BE5337B401; Mon, 12 Aug 2002 10:47:08 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CCD743E65; Mon, 12 Aug 2002 10:47:07 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.5/8.12.2) with ESMTP id g7CHjlH4001873; Mon, 12 Aug 2002 19:47:02 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.5/8.12.5/Submit) id g7CHjlYm001872; Mon, 12 Aug 2002 19:45:47 +0200 (CEST) Date: Mon, 12 Aug 2002 19:45:47 +0200 From: Wilko Bulte To: Marcin Gryszkalis Cc: ticso@cicely.de, freebsd-scsi@FreeBSD.ORG, freebsd-alpha Subject: Re: da driver problem? Message-ID: <20020812194547.A1841@freebie.xs4all.nl> References: <20020808152922.A18763@panzer.kdm.org> <3D53BD58.1060600@cerint.pl> <20020809130749.GJ52932@cicely5.cicely.de> <3D53C01A.1050702@cerint.pl> <20020809151159.GV52932@cicely5.cicely.de> <3D57A4BA.9060104@cerint.pl> <20020812122428.GF55760@cicely5.cicely.de> <3D57BD52.1@cerint.pl> <20020812140533.GG55760@cicely5.cicely.de> <3D57C88C.5010003@cerint.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D57C88C.5010003@cerint.pl>; from mgryszkalis@cerint.pl on Mon, Aug 12, 2002 at 04:39:08PM +0200 X-OS: FreeBSD 4.6-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Aug 12, 2002 at 04:39:08PM +0200, Marcin Gryszkalis wrote: > Bernd Walter wrote: > > Working without propper NVRAM values can produce undefined results. > > The driver tells you that the current values are dissagreeing. > > > But why should the driver work around a missconfigured device? > > Why not just fix the device configuration? > > I agree but I don't know proper NVRAM values (I assume that > when I get to srm the help will tell me how to change them). > Where to search for info? ("invalid nvram header" doesn't > give many hits in google - mainly A.Gallatin's dmesgs ;-) ) Stick the Qlogic card into a PC, and fix the nvram settings from the builtin Qlogic BIOS. I had to do that once, worked fine. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message