From owner-freebsd-questions Tue Jul 9 06:34:25 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07349 for questions-outgoing; Tue, 9 Jul 1996 06:34:25 -0700 (PDT) Received: from rk.ios.com (rk.ios.com [198.4.75.55]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07343 for ; Tue, 9 Jul 1996 06:34:22 -0700 (PDT) Received: (from rashid@localhost) by rk.ios.com (8.7.5/8.7.3) id JAA03426; Tue, 9 Jul 1996 09:34:10 -0400 (EDT) From: Rashid Karimov Message-Id: <199607091334.JAA03426@rk.ios.com> Subject: Re: de0 when bt0 is present == much sadness To: kelly@fsl.noaa.gov (Sean Kelly) Date: Tue, 9 Jul 1996 09:34:10 -0400 (EDT) Cc: questions@freebsd.org In-Reply-To: <199607090422.EAA17050@gatekeeper.fsl.noaa.gov> from "Sean Kelly" at Jul 8, 96 10:22:20 pm Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Gurus: > > I'm adding a DEC-21041 based PCI Ethernet card (Kingston EtheRx, if > you're curious) to a FreeBSD system that has a BusLogic BT-946C PCI > SCSI controller. I thought it'd be as simple as adding > > device de0 > > to my kernel config and jumping through the usual hoops. Upon reboot, > I'm greeted with this new message: > > de0 rev 17 int a irq 15 on pci0:11 > @@@ pcibus_ihandler_attach: result=16 > irq 15 already in use. > de0: couldn't map interrupt > > Yay, it found the card! :-) > Boo, it can't use it! :-( > > So, I looked through the pci code and it looks like it's trying to > register an interrupt handler for IRQ 15. Problem is, someone already > assigned one: the bt0 controller: > > bt0 at 0x334 irq 15 on isa This is weird ... one shouldn't assign specific IRQ to the driver IMO . Take a look at /sys/i386/conf/GENERIC at your PC. I've had enough of these combos - de0 + bt0, they all wroked fine. Check your BIOS setup for IRQs given to PCI subsystem ( slots). Rashid