From owner-freebsd-hardware Fri Jun 27 00:57:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09999 for hardware-outgoing; Fri, 27 Jun 1997 00:57:57 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09992 for ; Fri, 27 Jun 1997 00:57:54 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA07479 (5.67b/IDA-1.5 for ); Fri, 27 Jun 1997 09:57:49 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id JAA10693; Fri, 27 Jun 1997 09:57:52 +0200 (CEST) X-Face: " Date: Fri, 27 Jun 1997 09:57:50 +0200 From: Stefan Esser To: Jon Inouye Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Jon Inouye on Thu, Jun 26, 1997 at 12:16:02PM -0700 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 26, Jon Inouye wrote: > We just received two machines using Pentium II motherboards > (Intel PD440FX) with AMI BIOS 1.00.04.DT0. The problem is the > BIOS configures the PCI SCSI and Ethernet devices to share the > same IRQ. While WindowsNT device drivers appear to have no problem > with this (IRQ sharing is part of the PCI spec), some Linux and FreeBSD > drivers do. There are some free IRQs, but the BIOS assignment appears > to be non-user-configurable. I've looked for a SCU (System Configuration > Utility) program for this motherboard on the Intel developers web > site without success. Moving boards around and disabling the COM, USB, > and LPT devices didn't help either. Hi Jon! I'm the maintainer of the FreeBSD PCI code, and that PCI interrupt sharing doesn't work for all cards is (bad) news to me ... Could you please be more specific, and send a VERBOSE boot log (i.e. enter "-v" at the "Boot: " prompt) ? You didn't even give information on the FreeBSD version you are trying to install ... I'll either give further directions (or fix any bug in the code, if there really is one) in order to get you going ... > The current solution is removing the SCSI controller and going with > an IDE disk. I'd appreciate any other suggestions or pointers to > a SCU program I can use! This is obviously inacceptable ... But we will do better than that :) Regards, STefan