Date: Mon, 12 Aug 2002 10:16:58 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Marcin Gryszkalis <mgryszkalis@cerint.pl> Cc: ticso@cicely.de, freebsd-scsi@FreeBSD.ORG, freebsd-alpha <freebsd-alpha@FreeBSD.ORG> Subject: ISP Nvram [ was 'da driver problem?' ] Message-ID: <Pine.BSF.4.21.0208121012280.73304-100000@beppo> In-Reply-To: <3D57BD52.1@cerint.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Aug 2002, 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. Dunno what changed. > Matthew Jacob is the one who touched isp driver lately > so maybe he can think about other solution. Interrupt the boot process and at the loader prompt do set isp_debug=0x1f and boot (or fail to boot) and send us the output. Or add set isp_no_nvram=0x1 to keep NVRAM from being read. You haven't said whether you're now loading isp firmware or not. -matt 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?Pine.BSF.4.21.0208121012280.73304-100000>