From owner-freebsd-scsi Mon Aug 14 20:45: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 782A037B63E for ; Mon, 14 Aug 2000 20:45:03 -0700 (PDT) (envelope-from chuckr@picnic.chuckr.org) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id XAA00691 for ; Mon, 14 Aug 2000 23:45:32 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Mon, 14 Aug 2000 23:45:32 -0400 (EDT) From: Chuck Robey To: FreeBSD-scsi@FreeBSD.org Subject: multiple scsi busses Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just had quite a fright, and I'd appreciate a bit of advice before I stick my neck out again. I have an Intel DK440LX board, which has a dual bussed 7895 on it. I added an adaptec 29160, so the 29160 came up as ahc2 (the dual bussed 7895 being ahc0 and ahc1). Fright was when I accidentally set the 29160 up to use it's bios (like the 7895 was). Suddenly, no scsi drive would boot. An hour later (after testing every cable connection and losing some hair I couldn't really afford to lose) I set the bios setting on the 29160 off, and I could boot again. Can anyone explain in a bit of detail just what I did wrong, or why it was so wrong? I want, ultimately, to have a drive hung off the 29160 to boot (and there will be 2 drives on the 29160) so I have to understand what I'm doing a bit better, in getting ahc0-2 to compatibly coexist. Thanks! ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message