From owner-freebsd-scsi Tue Apr 8 15:00:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA04628 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 15:00:39 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-15.ix.netcom.com [199.35.213.207]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04600; Tue, 8 Apr 1997 15:00:16 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id OAA27677; Tue, 8 Apr 1997 14:58:31 -0700 (PDT) Date: Tue, 8 Apr 1997 14:58:31 -0700 (PDT) Message-Id: <199704082158.OAA27677@silvia.HIP.Berkeley.EDU> To: stesin@gu.net CC: se@freebsd.org, hackers@freebsd.org, scsi@freebsd.org, davidg@freebsd.org In-reply-to: (message from Andrew Stesin on Mon, 7 Apr 1997 22:25:27 +0300 (EEST)) Subject: Re: Intel XXpress again (was: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Hi again, * * sorry for "replying" to my own message, but now the possibility * of FreeBSD-2.2.1 to occupy this Big Box forever has grown to almost * 100%... if only I knew the way to get FreeBSD recognize 2 PCI busses. :(( * * HEEEELP!!!! :) I wonder if DavidG on the lists. * Now I can tell you what are the major (just biggest ones :) * chips on the backplane, all have "INTEL" on them: * * 1. PCIset S82374SB (I suspice that this chip is a clue..) * 2. PCIset S82375SB (gets recognized as 82375EB? EISA works anyway) I think the "823*B" chips are PCI- bridges. The one I have says: chip1 rev 1 on pci0:1:0 chip2 rev 0 on pci0:1:1 (It is only one chip.) * 3. A|M|I 9637LZR (chip is (c)1994 Intel, no idea what's it) * 4. XPC 637909-001 (no idea) * 5. XPD 637910-001 2 parts (no idea) Justin suggested the motherboard may have two host-PCI bridges, so maybe these are those. * Just now I'm trying to boot a GENERIC with the increased size * of vty' history buffer -- otherwise no way to catch * all the messages esp. with "-v", PCI ones fly away, * too many of them. Unfortunately, building a "true" * FreeBSD boot floppy isn't so trivial. :( So no success yet... Can you get it to a point that it can run "dmesg"? * I'm considering this, but I don't trust my own skills of * hacking pretty unfamiliar kernel code to get production * system running in 2-3 days... I still hope that there already is * a solution... Well, let's see if David can help you. Satoshi