Simon, All:

At 15:30 01/06/2004. Simon Barner had this to say:
>I just had a look at that older post of yours, and I saw that you are
>still running FreeBSD 4.8. Could you consider upgrading to 4.10-RELEASE or
>IMO there's a really good chance that upgrading will make your onboard
>NICs work properly.

Sadly, no joy.

To refresh, I'm using an adlink ebc-2000 (supplied by Ecrin
Systems in France).  It has 3 on-board NICs that are identified
as <Intel 82559 Pro/100 Ethernet> by the kernel during boot
(which agrees with adlink's datasheet for this device).

The devices do not come up under the miibus device, however,
and run in 'cripple-mode'.  They work, but at 10Mb.  If I try
to change that by using ifconfig fxp0 media commands, I get:

ifconfig: SIOCSIFMEDIA: Device not configured

ifconfig fxp0 reports:
        inet x.y.z.188 netmask 0xffff0000 broadcast x.y.z.255
        ether 00:30:64:gh:ij:kl
        media: Ethernet manual

Additionally, there are two other fxp devices on a PCI plug-in
card, and they come up happy.

Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 4.10-RELEASE #1: Fri Jun 25 13:06:22 GMT 2004
    [EMAIL PROTECTED]:/usr/src/sys/compile/MINI
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1266716809 Hz
CPU: Intel(R) Pentium(R) III CPU family      1266MHz (1266.72-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
fxp0: <Intel 82559 Pro/100 Ethernet> port 0xd400-0xd43f mem 
0xe7200000-0xe72fffff,0xe7302000-0xe7302fff irq 11 at device 8.0 on pci0
fxp0: Ethernet address 00:30:64:gh:ij:kl, 10Mbps
fxp1: <Intel 82559 Pro/100 Ethernet> port 0xd800-0xd83f mem 
0xe7000000-0xe70fffff,0xe7301000-0xe7301fff irq 5 at device 9.0 on pci0
fxp1: Ethernet address 00:30:64:gh:ij:kl, 10Mbps
fxp2: <Intel 82559 Pro/100 Ethernet> port 0xdc00-0xdc3f mem 
0xe7100000-0xe71fffff,0xe7300000-0xe7300fff irq 12 at device 10.0 on pci0
fxp2: Ethernet address 00:30:64:gh:ij:kl, 10Mbps
pcib2: <DEC 21152 PCI-PCI bridge> at device 13.0 on pci0
pci2: <PCI bus> on pcib2
pcib3: <PCI to PCI bridge (vendor=8086 device=b154)> at device 15.0 on pci2
pci3: <PCI bus> on pcib3
fxp3: <Intel 82559 Pro/100 Ethernet> port 0xc000-0xc03f mem 
0xe6000000-0xe60fffff,0xe6201000-0xe6201fff irq 10 at device 12.0 on pci3
fxp3: Ethernet address 00:30:64:gh:ij:kl
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp4: <Intel 82559 Pro/100 Ethernet> port 0xc400-0xc43f mem 
0xe6100000-0xe61fffff,0xe6200000-0xe6200fff irq 11 at device 13.0 on pci3
fxp4: Ethernet address 00:30:64:gh:ij:kl
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

pciconf -l reports:
[EMAIL PROTECTED]:8:0:  class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 
[EMAIL PROTECTED]:9:0:  class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 
[EMAIL PROTECTED]:10:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 

(note the card=0x00000000.  Hm.)

So, if you've read this far,

1) It says 'Ethernet manual'.  Does that mean that there will be 
a method (ioctl or similar) in the driver that allows me to make
explicit calls to the devices to configure 100Mb full duplex, for
example, or even Auto if it is supported.  Before you say 'look 
at the code yourself', assume that I'm doing so as you read this :>

2) Am I SOL, short of doing it myself in the fxp driver?

Richard Williamson

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to