From owner-freebsd-questions Thu Apr 22 11:42:12 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id DF54215430 for ; Thu, 22 Apr 1999 11:42:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA01552; Thu, 22 Apr 1999 11:39:30 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Apr 1999 11:39:29 -0700 (PDT) From: Doug White To: Jeff Hamilton Cc: freebsd-questions Subject: Re: Network problems In-Reply-To: <199904220004.UAA00308@gandolf.dhs.org> 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 On Wed, 21 Apr 1999, Jeff Hamilton wrote: > >> IRQ 5 and 9 were both shown as unused by the system bios before I > >> installed the 2 NIC's. FreeBSD recognizes all devices in the system, > and > >> there are no conflicts with any of them listed in the dmesg output. > (at > >> least none that I see) > > > >Thats the thing, something may be there (like the onboard soundcard) > that > >FreeBSD doesn't detect. Try locking out IRQs 5 and 9 in the BIOS setup > to > >force the PCI resource assigner to something else. > > I don't think that there is any way to do this...The bios is very > limited on configuration options such as this. I can manually assign > IRQ's to devices, but cannot reserve IRQ's. Can you assign them to something to trick the PCI resource manager? > >What CPU does this thing have? > > It's a Pentium-120. The motherboard is a Compaq board, and uses a > Compaq bios. Could the older motherboard and bios be a part of the > problem? Actually, the fact Compaq touched it has more to do with it than anything. :-) > >The Pro is a *much* better card if you can help it. The xl driver > isn't > >up to the caliber of the fxp driver. > > Well...I removed the 3com xl card, and replaced it with an old ISA > 3c509. I'm still getting the device timeouts on the EtherExpress, but > the the ep driver works well with the 3c509, and since my cable modem is > only 10mbit, there's no performance problem. Oh, that'll be worse! Yuck. Sounds like a busted PCI bus, what I'd expect from Compaq. :-( > Would upgrading to FreeBSD and the newer fxp driver help this, or is > this entirely a hardware issue? It's hardware. I'll bet money on it. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message