Revised output from pciconf -v -l
[EMAIL PROTECTED]:8:0: class=0x02 card=0x34278086 chip=0x10508086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = '82562EZ Pro 10/100 Mb/s VE Fast Ethernet MAC & PHY'
class= network
subclass = ethernet
-Derek
At 10:4
pciconf -v -l output is:
# pciconf -v -l
[EMAIL PROTECTED]:0:0: class=0x06 card=0x25788086 chip=0x25788086 rev=0x02
hdr=0x00
vendor = 'Intel Corporation'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x25798086 rev=0x02
hdr=0x
On Sat, Sep 27, 2003 at 12:12:40AM -0400, Mike Tancsa wrote:
> At 11:32 PM 26/09/2003, Glenn Johnson wrote:
>
> >On Fri, Sep 26, 2003 at 08:07:38PM -0400, Mike Tancsa wrote:
> >
> >> Are they Tyan motherboards by chance ? There was a thread in stable
> >> about this a few weeks ago. The problems
At 11:32 PM 26/09/2003, Glenn Johnson wrote:
On Fri, Sep 26, 2003 at 08:07:38PM -0400, Mike Tancsa wrote:
> Are they Tyan motherboards by chance ? There was a thread in stable
> about this a few weeks ago. The problems seem specific to those
> motherboards. Someone posted a potential workaround
On Fri, Sep 26, 2003 at 08:07:38PM -0400, Mike Tancsa wrote:
> Are they Tyan motherboards by chance ? There was a thread in stable
> about this a few weeks ago. The problems seem specific to those
> motherboards. Someone posted a potential workaround as well.
No, five of them are MSI dual Athlo
This worked until I went beyond p4 on 5.1 release
I found a PR that suggested adding:
{ 0x1050, "Intel 82801EB (ICH5) Pro/100 Ethernet" },
line to the if_fxp.c file, in the struct:
/*
* Claim various Intel PCI device identifiers for this driver. The
* sub-vendor and sub-device fie
Mine is an Intel® Server Board S875WP1-E, I was using a patch but it quite
working on the fxp0 interface.
-Derek
At 08:07 PM 9/26/2003 -0400, Mike Tancsa wrote:
Are they Tyan motherboards by chance ? There was a thread in stable
about this a few weeks ago. The problems seem specific to
Are they Tyan motherboards by chance ? There was a thread in stable
about this a few weeks ago. The problems seem specific to those
motherboards. Someone posted a potential workaround as well.
---Mike
On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
you wrote:
>I am
Hi Glenn,
We have several FreeBSD boxes here. Some run -current and some run -5.1-P4
and all have fxp* and em*
You must have something else going wrong that is causing you the grief.
fxp0: flags=8843 mtu 1500
options=3
inet6 fe80::202:b3ff:fe96:c64b%fxp0 prefixlen 64 scopeid 0x1
