From owner-freebsd-questions  Wed Jul 17 13:56:37 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA19508
          for questions-outgoing; Wed, 17 Jul 1996 13:56:37 -0700 (PDT)
Received: from hammurabi.nh.ultra.net (hammurabi.nh.ultra.net [205.162.79.24])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA19503
          for <questions@freebsd.org>; Wed, 17 Jul 1996 13:56:34 -0700 (PDT)
Received: from larry ([192.32.36.129]) by hammurabi.nh.ultra.net (8.7.4/dae0.6) with SMTP id QAA09914; Wed, 17 Jul 1996 16:56:30 -0400 (EDT)
Message-ID: <31ED1C97.41C67EA6@qosnet.com>
Date: Wed, 17 Jul 1996 17:02:15 +0000
From: Greg Burch <gregb@qosnet.com>
X-Mailer: Mozilla 3.0b5a (X11; I; FreeBSD 2.1.0-RELEASE i386)
MIME-Version: 1.0
To: questions@freebsd.org
CC: png@qosnet.com
Subject: Triton II workaround?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

I was wondering if anyone could help on this one or point us to someone
who can?

We get the following messages when we boot Triton-II's using FreeBSD
2.1.0:
pci0:0: Intel Corporation, device=0x1250, class=bridge (host) [no driver
assigned]
pci0:7: Intel Corporation, device=0x7000, class=bridge (isa) [no driver
assigned]

For comparison, we get these messages on our Tritons:
chip0 <Intel 82437 (Triton)> rev 2 on pci0:0
chip1 <Intel 82371 (Triton)> rev 2 on pci0:7

We are using identical kernels on all machines. On the Triton-IIs, we do
not get interrupts passed through to our interrupt handlers and we
assume this has something to do with "no driver assigned".

We have used a real simple DOS-based tickler on the Triton-IIs and the
interrupts are detected.

We'd appreciate thoughts regarding possible solutions.

Thanks,

Greg Burch
Qosnetics