Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Aug 2002 16:05:34 +0200
From:      Bernd Walter <ticso@cicely5.cicely.de>
To:        Marcin Gryszkalis <mgryszkalis@cerint.pl>
Cc:        ticso@cicely.de, freebsd-scsi@FreeBSD.ORG, freebsd-alpha <freebsd-alpha@FreeBSD.ORG>
Subject:   Re: da driver problem?
Message-ID:  <20020812140533.GG55760@cicely5.cicely.de>
In-Reply-To: <3D57BD52.1@cerint.pl>
References:  <3D5280F4.8030706@cerint.pl> <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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 12, 2002 at 03:51:14PM +0200, Marcin Gryszkalis wrote:
> Bernd Walter wrote:
> >You should fix the isp nvram table.
> >IIRC srm has support to edit these values.
> 
> >Another option would be to give disk id 0 a new id and leave
> >the controller on 0.
> 
> But as I mentioned I booted 4.5 kernel without
> ANY changes in configuration and it worked ok.
> So - obviously - changes made since April
> are deadly for my little box.

Working without propper NVRAM values can produce undefined results.
The driver tells you that the current values are dissagreeing.

> Matthew Jacob is the one who touched isp driver lately
> so maybe he can think about other solution.

I almost shure he can do.
But why should the driver work around a missconfigured device?
Why not just fix the device configuration?

-- 
B.Walter              COSMO-Project         http://www.cosmo-project.de
ticso@cicely.de         Usergroup           info@cosmo-project.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020812140533.GG55760>