From owner-freebsd-scsi Sun Dec 5 13:53:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E8A5915428; Sun, 5 Dec 1999 13:53:14 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA24738; Sun, 5 Dec 1999 22:31:23 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA72235; Sun, 5 Dec 1999 19:59:20 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912051859.TAA72235@yedi.iaf.nl> Subject: Re: ISP firmware compiled in as a default.... In-Reply-To: from Matthew Jacob at "Dec 5, 1999 10:36:13 am" To: mjacob@feral.com Date: Sun, 5 Dec 1999 19:59:20 +0100 (CET) Cc: gallatin@cs.duke.edu, freebsd-scsi@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (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 As Matthew Jacob wrote ... > > Did you have both internal AND external devices on the same KZPBA card? > > FYI: we (== Compaq) don't support this. Obviously this decision is based > > on the f/w that is in the SRM code. Tests have shown it really does not > > work well when both internal and external devices are present on the same > > card. YMMV of course and I obviously don't know what was biting you. > > Wasn't a standard KZPBA, but that's not the high order bit. If the f/w > figures out there's something on both internal and external connectors, > it's supposed to drop the pullups. That's why the 7.65 f/w is a lot better > than the 5.XXX f/w- in this case. Hm. Well the reasons I heared within Compaq was that they did not like the signal quality on the SCSI bus when both internal and external devices are present. Ultra SCSI speeds obviously make this worse, as do marginal cables etc. > > > So, I'm in a bit of a quandary now as to what the right thing to do is. > > > > Don't shoot me: the right thing to do is to make it possible to boot > > ... I won't shoot you, but it doesn't help me answer the question of > 'should f/w be compiled in by default'. I suppose Mike answered it best > about checking sizes. Clearer answer: my vote is to include the 1040 f/w > > Hm. The DEC-sanctioned cards (as far as SRM booting goes, so for > > system disks) only use 1040's if I'm not mistaken. So this might be the > > most practical short-term solution. How much would 1040-only f/w > > add to the installation kernel ? > > Actually, the latest 4100 f/w (at least the one I installed at NASA/Ames) > recognizes the 2100, but won't boot from it. Nyah, Nyah! PTI PCI-470 Probably SRM is picky somehow. -- | / o / / _ Arnhem, The Netherlands - The FreeBSD Project |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message