Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Apr 1999 11:39:29 -0700 (PDT)
From:      Doug White <dwhite@resnet.uoregon.edu>
To:        Jeff Hamilton <gandolf@destiny.erols.com>
Cc:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: Network problems
Message-ID:  <Pine.BSF.4.03.9904221137520.7869-100000@resnet.uoregon.edu>
In-Reply-To: <199904220004.UAA00308@gandolf.dhs.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9904221137520.7869-100000>