From owner-freebsd-questions Fri Feb 20 16:07:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04194 for freebsd-questions-outgoing; Fri, 20 Feb 1998 16:07:31 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04107 for ; Fri, 20 Feb 1998 16:06:42 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.8/8.6.12) with SMTP id PAA05223; Fri, 20 Feb 1998 15:42:51 -0800 (PST) Date: Fri, 20 Feb 1998 15:42:51 -0800 (PST) From: Shawn Ramsey To: Doug White cc: questions@FreeBSD.ORG Subject: Re: EtherExpress PRO/100 problem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Two PCI ones? Odd, PCI is supposed to arbitrate that. Sounds like a > firmware bug. Yup. The EtherExpress setup program told me the Windows drivers could handle shared IRQ's. Apparantly, the FreeBSD drivers don't. Not that I blame FreeBSD, there is no need for shared IRQ's(usually) for network cards. > set the IRQs for the PCI bus. Took a bit to figure out which slot was > which but you knew where everything was. I looked in the BIOS and saw nothing. On my relatively new workstation, but Award BIOS, you can manually set the IRQ's, or do it automatically. I think the motherboard is just crap, I think it may have a bad cache. It has a bad something, because I cannot compile a world. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message