[eepro100] 82559ER

Isabelle, Francois Francois.Isabelle@ca.kontron.com
Thu Mar 7 11:13:00 2002


I don't know,
		( it might not be the place for this but Kontron SBC using
the 82559er implements this ).
	The best would be to contact the embedded PC manufacturer because it
CAN work.


-----Original Message-----
From: Bernd Stahlbock [mailto:stahlbock@basysprint.de]
Sent: 7 mars, 2002 10:05
To: Isabelle, Francois; eepro100@scyld.com
Subject: AW: [eepro100] 82559ER


Hello all,

I'm just looking for an BootOnLan solution for a embedded PC Board with a
559er on it. Does anybody has a solution already?

Can I use the normal PXE files and just patch the chip ID? Would this work?

best regards
Bernd Stahlbock

> -----Ursprüngliche Nachricht-----
> Von: eepro100-admin@scyld.com [mailto:eepro100-admin@scyld.com]Im
> Auftrag von Isabelle, Francois
> Gesendet: Montag, 5. November 2001 15:21
> An: eepro100@scyld.com
> Betreff: RE: [eepro100] 82559ER
>
>
> Hi, you might as well have some difficulties finding a PXE (Boot from lan)
> bios extension for the 82559ER, since there is no support from Intel to
> implement it.
>
> > -----Original Message-----
> > From:	Christoph Plattner [SMTP:christoph.plattner@alcatel.at]
> > Sent:	20 septembre, 2001 02:49
> > To:	ml_ravi@usa.net
> > Cc:	eepro100@scyld.com
> > Subject:	Re: [eepro100] 82559ER
> >
> > Hello,
> >
> > 	yes I think, I can help you.
> > The 82559ER is a subset of the 82559. The feature the
> > 82559ER misses in comparison to 82559
> > - No CardBus and modem support, as the 82559 has a internel
> > 	PCMCIA/CardBus controller
> > - Some restriction in WOL
> > - New Device ID 1209 for 82559ER, I think 82559 has Device ID 1229
> >
> > For a "normal" user, there is NO relevant differece between the
> > two chip derivates. The only point is, that chip ID of 1209
> > instead of the 1229, which often older drivers do not recognize.
> > For this I often patch the chip ID (for test purpose) or I add
> > the new ID to be tested from the driver.
> >
> > With friendly regards
> > 	Christoph
> >
> >
> > ravi modgekar wrote:
> > >
> > > hi,
> > >    Does anybody can help me out in finding out the
> > > main difference between 82559ER and 82559.
> > >
> > > thanks
> > > --- eepro100-admin@scyld.com wrote:
> > > >
> > > > Send eepro100 mailing list submissions to
> > > >       eepro100@scyld.com
> > > >
> > > > To subscribe or unsubscribe via the web, visit
> > > >       http://www.scyld.com/mailman/listinfo/eepro100
> > > > or, via email, send a message with subject or body
> > > > 'help' to
> > > >       eepro100-request@scyld.com
> > > > You can reach the person managing the list at
> > > >       eepro100-admin@scyld.com
> > > >
> > > > When replying, please edit your Subject line so it
> > > > is more specific than
> > > > "Re: Contents of eepro100 digest..."
> > > >
> > > >
> > > > Today's Topics:
> > > >
> > > >   1. eepro100 driver (2.4 kernel) fails with S2080
> > > > Tomcat i815t motherboard. (Ben Greear)
> > > >   2. e100 driver fails to work correctly with Tyan
> > > > S2080 Tomcat i185t
> > > >  motherboard. (Ben Greear)
> > > >   3. Re: eepro100 driver (2.4 kernel) fails with
> > > > S2080 Tomcat
> > > >  i815t motherboard. (Donald Becker)
> > > >   4. Re: eepro100 driver (2.4 kernel) fails with
> > > > S2080 Tomcati815t
> > > >  motherboard. (Ben Greear)
> > > >   5. BSD driver (Alexander Gdalevich)
> > > >
> > > > --__--__--
> > > >
> > > > Message: 1
> > > > Date: Tue, 18 Sep 2001 19:20:13 -0700
> > > > From: Ben Greear <greearb@candelatech.com>
> > > > Organization: Candela Technologies
> > > > To: eepro list <eepro100@scyld.com>,
> > > > linux-kernel <linux-kernel@vger.kernel.org>
> > > > Subject: [eepro100] eepro100 driver (2.4 kernel)
> > > > fails with S2080 Tomcat i815t motherboard.
> > > >
> > > > I have a Tyan motherboard (S2080 Tomcat i815t) with
> > > > 2 built-in NICs.
> > > >
> > > > The manual claims this:
> > > >
> > > > "One Intel 82559 LAN controller
> > > >  One ICH2 LAN controller"
> > > >
> > > > Seems that the eepro driver tries to bring up both
> > > > of
> > > > them, and fails to read the eeprom on the second one
> > > > it
> > > > scans.  One visible result is that the MAC is all
> > > > FF's.
> > > >
> > > > I have two other EEPRO NICs in the system, and they
> > > > seem to be
> > > > detected first.
> > > >
> > > > The kernel is 2.4.10-pre11:
> > > > [root@lanf2 /root]# dmesg | more
> > > > Linux version 2.4.10-pre11 (root@lanf2) (gcc version
> > > > 2.96 20000731 (Red Hat Linux 7.1 2.96-85)) #3 Tue
> > > > Sep 18
> > > >  10:07:01 MST 2001
> > > > The same problem is appearant with RH's 7.1 kernels
> > > > (the upgrade 2.4.3* too).
> > > >
> > > >
> > > > Here is a pertinent part of the dmesg.
> > > > eepro100-diag messages
> > > > follow below, along with an 'ifconfig -a'.
> > > >
> > > > The kernel is 2.4.10-pre11:
> > > > [root@lanf2 /root]# dmesg | more
> > > > Linux version 2.4.10-pre11 (root@lanf2) (gcc version
> > > > 2.96 20000731 (Red Hat Linux 7.1 2.96-85)) #3 Tue
> > > > Sep 18
> > > >  10:07:01 MST 2001
> > > >
> > > >
> > > >
> > > > eepro100.c:v1.09j-t 9/29/99 Donald Becker
> > > >
> > > http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> > > > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by
> > > > Andrey V. Savochkin <saw@saw.sw.com.sg> and others
> > > > PCI: Found IRQ 10 for device 01:0b.0
> > > > eth0: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#3), 00:E0:81:03:B9:7B, IRQ 10.
> > > >   Board assembly 567812-052, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >   General self-test: passed.
> > > >   Serial sub-system self-test: passed.
> > > >   Internal registers self-test: passed.
> > > >   ROM checksum self-test: passed (0x04f4518b).
> > > > PCI: Found IRQ 3 for device 01:09.0
> > > > eth1: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#2), 00:90:27:65:39:1B, IRQ 3.
> > > >   Board assembly 721383-006, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >   General self-test: passed.
> > > >   Serial sub-system self-test: passed.
> > > >   Internal registers self-test: passed.
> > > >   ROM checksum self-test: passed (0x04f4518b).
> > > > PCI: Found IRQ 9 for device 01:04.0
> > > > PCI: Sharing IRQ 9 with 00:1f.3
> > > > eth2: Intel Corporation 82557 [Ethernet Pro 100],
> > > > 00:90:27:65:37:8A, IRQ 9.
> > > >   Board assembly 721383-006, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >   General self-test: passed.
> > > >   Serial sub-system self-test: passed.
> > > >   Internal registers self-test: passed.
> > > >   ROM checksum self-test: passed (0x04f4518b).
> > > > PCI: Found IRQ 11 for device 01:08.0
> > > > eth3: Invalid EEPROM checksum 0xff00, check settings
> > > > before activating this device!
> > > > eth3: OEM i82557/i82558 10/100 Ethernet,
> > > > FF:FF:FF:FF:FF:FF, IRQ 11.
> > > >   Board assembly ffffff-255, Physical connectors
> > > > present: RJ45 BNC AUI MII
> > > >   Primary interface chip unknown-15 PHY #31.
> > > >     Secondary interface chip i82555.
> > > >   General self-test: passed.
> > > >   Serial sub-system self-test: passed.
> > > >   Internal registers self-test: passed.
> > > >   ROM checksum self-test: passed (0x04f4518b).
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [root@lanf2 /root]# eepro100-diag
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdf00.
> > > > A potential i82557 chip has been found, but it
> > > > appears to be active.
> > > > Either shutdown the network, or use the '-f' flag.
> > > > Index #2: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xde80.
> > > > Index #3: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdd00.
> > > > Index #4: Found a Intel i82562 EEPro100 adapter at
> > > > 0xdd80.
> > > >  Use '-a' or '-aa' to show device registers,
> > > >      '-e' to show EEPROM contents, -ee for parsed
> > > > contents,
> > > >   or '-m' or '-mm' to show MII management registers.
> > > >
> > > >
> > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth3
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdf00.
> > > > i82557 chip registers at 0xdf00:
> > > >   0c000090 0f22c000 00000000 00080002 18250021
> > > > 00000600
> > > >   No interrupt sources are pending.
> > > >    The transmit unit state is 'Active'.
> > > >    The receive unit state is 'Ready'.
> > > >   This status is unusual for an activated interface.
> > > >  The Command register has an unprocessed command
> > > > 0c00(?!).
> > > > EEPROM contents, size 64x16:
> > > >     00: e000 0381 7bb9 0403 0000 0201 4701 0000
> > > >   0x08: 5678 1234 4082 100c 8086 0000 0000 0000
> > > >       ...
> > > >   0x30: 0128 0000 0000 0000 0000 0000 0000 0000
> > > >   0x38: 0000 0000 0000 0000 0000 0000 0000 d393
> > > >  The EEPROM checksum is correct.
> > > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > >   Station address 00:E0:81:03:B9:7B.
> > > >   Board assembly 567812-052, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >  MII PHY #1 transceiver registers:
> > > >   3000 782d 02a8 0154 05e1 0021 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000
> > > >   0400 0000 0001 0000 0000 0000 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000.
> > > >   Baseline value of MII status register is 782d.
> > > >
> > > >
> > > >
> > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth2
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdf00.
> > > > i82557 chip registers at 0xdf00:
> > > >   0c000090 0f22c000 00000000 00080002 18250021
> > > > 00000600
> > > >   No interrupt sources are pending.
> > > >    The transmit unit state is 'Active'.
> > > >    The receive unit state is 'Ready'.
> > > >   This status is unusual for an activated interface.
> > > >  The Command register has an unprocessed command
> > > > 0c00(?!).
> > > > EEPROM contents, size 64x16:
> > > >     00: e000 0381 7bb9 0403 0000 0201 4701 0000
> > > >   0x08: 5678 1234 4082 100c 8086 0000 0000 0000
> > > >       ...
> > > >   0x30: 0128 0000 0000 0000 0000 0000 0000 0000
> > > >   0x38: 0000 0000 0000 0000 0000 0000 0000 d393
> > > >  The EEPROM checksum is correct.
> > > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > >   Station address 00:E0:81:03:B9:7B.
> > > >   Board assembly 567812-052, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >  MII PHY #1 transceiver registers:
> > > >   3000 782d 02a8 0154 05e1 0021 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000
> > > >   0400 0000 0001 0000 0000 0000 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000.
> > > >   Baseline value of MII status register is 782d.
> > > >
> > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth1
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdf00.
> > > > i82557 chip registers at 0xdf00:
> > > >   0c000090 0f22c000 00000000 00080002 18250021
> > > > 00000600
> > > >   No interrupt sources are pending.
> > > >    The transmit unit state is 'Active'.
> > > >    The receive unit state is 'Ready'.
> > > >   This status is unusual for an activated interface.
> > > >  The Command register has an unprocessed command
> > > > 0c00(?!).
> > > > EEPROM contents, size 64x16:
> > > >     00: e000 0381 7bb9 0403 0000 0201 4701 0000
> > > >   0x08: 5678 1234 4082 100c 8086 0000 0000 0000
> > > >       ...
> > > >   0x30: 0128 0000 0000 0000 0000 0000 0000 0000
> > > >   0x38: 0000 0000 0000 0000 0000 0000 0000 d393
> > > >  The EEPROM checksum is correct.
> > > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > >   Station address 00:E0:81:03:B9:7B.
> > > >   Board assembly 567812-052, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >  MII PHY #1 transceiver registers:
> > > >   3000 782d 02a8 0154 05e1 0021 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000
> > > >   0400 0000 0001 0000 0000 0000 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000.
> > > >   Baseline value of MII status register is 782d.
> > > >
> > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth0
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82557 (or i82558)
> > > > EtherExpressPro100B adapter at 0xdf00.
> > > > i82557 chip registers at 0xdf00:
> > > >   0c000090 0f22c000 00000000 00080002 18250021
> > > > 00000600
> > > >   No interrupt sources are pending.
> > > >    The transmit unit state is 'Active'.
> > > >    The receive unit state is 'Ready'.
> > > >   This status is unusual for an activated interface.
> > > >  The Command register has an unprocessed command
> > > > 0c00(?!).
> > > > EEPROM contents, size 64x16:
> > > >     00: e000 0381 7bb9 0403 0000 0201 4701 0000
> > > >   0x08: 5678 1234 4082 100c 8086 0000 0000 0000
> > > >       ...
> > > >   0x30: 0128 0000 0000 0000 0000 0000 0000 0000
> > > >   0x38: 0000 0000 0000 0000 0000 0000 0000 d393
> > > >  The EEPROM checksum is correct.
> > > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > >   Station address 00:E0:81:03:B9:7B.
> > > >   Board assembly 567812-052, Physical connectors
> > > > present: RJ45
> > > >   Primary interface chip i82555 PHY #1.
> > > >  MII PHY #1 transceiver registers:
> > > >   3000 782d 02a8 0154 05e1 0021 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000
> > > >   0400 0000 0001 0000 0000 0000 0000 0000
> > > >   0000 0000 0000 0000 0000 0000 0000 0000.
> > > >   Baseline value of MII status register is 782d.
> > > >
> > > > [root@lanf2 /root]# ifconfig -a
> > > > eth0      Link encap:Ethernet  HWaddr
> > > > 00:E0:81:03:B9:7B
> > > >           inet addr:192.168.1.56
> > > > Bcast:192.168.1.255  Mask:255.255.255.0
> > > >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> > > > Metric:1
> > > >           RX packets:412 errors:0 dropped:0
> > > > overruns:0 frame:0
> > > >           TX packets:278 errors:0 dropped:0
> > > > overruns:0 carrier:0
> > > >           collisions:0 txqueuelen:100
> > > >           Interrupt:10 Base address:0xe000
> > > >
> > > > eth1      Link encap:Ethernet  HWaddr
> > > > 00:90:27:65:39:1B
> > > >           BROADCAST MULTICAST  MTU:1500  Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0 txqueuelen:100
> > > >           Interrupt:3
> > > >
> > > > eth2      Link encap:Ethernet  HWaddr
> > > > 00:90:27:65:37:8A
> > > >           BROADCAST MULTICAST  MTU:1500  Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0 txqueuelen:100
> > > >           Interrupt:9 Base address:0x2000
> > > >
> > > > eth3      Link encap:Ethernet  HWaddr
> > > > FF:FF:FF:FF:FF:FF
> > > >           BROADCAST MULTICAST  MTU:1500  Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0 txqueuelen:100
> > > >           Interrupt:11 Base address:0x4000
> > > >
> > > > lo        Link encap:Local Loopback
> > > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > > >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> > > >           RX packets:18 errors:0 dropped:0
> > > > overruns:0 frame:0
> > > >           TX packets:18 errors:0 dropped:0
> > > > overruns:0 carrier:0
> > > >           collisions:0 txqueuelen:0
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Ben Greear <greearb@candelatech.com>
> > > > <Ben_Greear@excite.com>
> > > > President of Candela Technologies Inc
> > > > http://www.candelatech.com
> > > > ScryMUD:  http://scry.wanfear.com
> > > > http://scry.wanfear.com/~greear
> > > >
> > > > --__--__--
> > > >
> > > > Message: 2
> > > > Date: Tue, 18 Sep 2001 19:41:23 -0700
> > > > From: Ben Greear <greearb@candelatech.com>
> > > > Organization: Candela Technologies
> > > > To: linux.nics@intel.com
> > > > CC: eepro list <eepro100@scyld.com>
> > > > Subject: [eepro100] e100 driver fails to work
> > > > correctly with Tyan S2080 Tomcat i185t
> > > > motherboard.
> > > >
> > > > It seems to assign the second NIC's MAC to all FF's.
> > > >  The eepro100
> > > > driver for Linux also fails:  It reports a bad
> > > > checksum on the eeprom.
> > > > I already sent a bug report to the linux kernel
> > > > developers about that one,
> > > > and it has the gory details if you want to see
> > > > them...
> > > >
> > > > Note that eth3 seems to be some generic (unknown??)
> > > > 8255* chipset,
> > > > where the other one is more specifically
> > > > identified...
> > > >
> > > >
> > > > Here are the e100 driver loading messages:
> > > >
> > > > Sep 18 19:39:17 lanf2 kernel: Intel(R) PRO/100 Fast
> > > > Ethernet Adapter - Loadable driver, ver 1.6.13
> > > > Sep 18 19:39:17 lanf2 kernel: Copyright (c) 2001
> > > > Intel Corporation
> > > > Sep 18 19:39:17 lanf2 kernel: PCI: Found IRQ 10 for
> > > > device 01:0b.0
> > > > Sep 18 19:39:17 lanf2 kernel:
> > > > Sep 18 19:39:17 lanf2 kernel: eth0: Intel(R)
> > > > PRO/100+ Server Adapter (PILA8470B)
> > > > Sep 18 19:39:17 lanf2 kernel:   Mem:0xfe9ff000
> > > > IRQ:10  Speed:10 Mbps  Dx:Half
> > > > Sep 18 19:39:17 lanf2 kernel:   Hardware receive
> > > > checksums enabled
> > > > Sep 18 19:39:17 lanf2 kernel:   ucode was not loaded
> > > > Sep 18 19:39:21 lanf2 kernel: PCI: Found IRQ 3 for
> > > > device 01:09.0
> > > > Sep 18 19:39:21 lanf2 kernel:
> > > > Sep 18 19:39:21 lanf2 kernel: eth1: Intel(R)
> > > > PRO/100+ Management Adapter
> > > > Sep 18 19:39:21 lanf2 kernel:   Mem:0xfe9fe000
> > > > IRQ:3  Speed:0 Mbps  Dx:N/A
> > > > Sep 18 19:39:21 lanf2 kernel:   Failed to detect
> > > > cable link.
> > > > Sep 18 19:39:21 lanf2 kernel:   Speed and duplex
> > > > will be determined at time of connection.
> > > > Sep 18 19:39:21 lanf2 kernel:   Hardware receive
> > > > checksums enabled
> > > > Sep 18 19:39:21 lanf2 kernel:   ucode was not loaded
> > > > Sep 18 19:39:24 lanf2 kernel: PCI: Found IRQ 9 for
> > > > device 01:04.0
> > > > Sep 18 19:39:24 lanf2 kernel: PCI: Sharing IRQ 9
> > > > with 00:1f.3
> > > > Sep 18 19:39:24 lanf2 kernel:
> > > > Sep 18 19:39:24 lanf2 kernel: eth2: Intel(R)
> > > > PRO/100+ Management Adapter
> > > > Sep 18 19:39:24 lanf2 kernel:   Mem:0xfe9fc000
> > > > IRQ:9  Speed:0 Mbps  Dx:N/A
> > > > Sep 18 19:39:24 lanf2 kernel:   Failed to detect
> > > > cable link.
> > > > Sep 18 19:39:24 lanf2 kernel:   Speed and duplex
> > > > will be determined at time of connection.
> > > > Sep 18 19:39:24 lanf2 kernel:   Hardware receive
> > > > checksums enabled
> > > > Sep 18 19:39:24 lanf2 kernel:   ucode was not loaded
> > > > Sep 18 19:39:27 lanf2 kernel: PCI: Found IRQ 11 for
> > > > device 01:08.0
> > > > Sep 18 19:39:27 lanf2 kernel:
> > > > Sep 18 19:39:27 lanf2 kernel: eth3: Intel(R)
> > > > 8255x-based Ethernet Adapter
> > > > Sep 18 19:39:27 lanf2 kernel:   Mem:0xfe9fd000
> > > > IRQ:11  Speed:0 Mbps  Dx:N/A
> > > > Sep 18 19:39:27 lanf2 kernel:   Failed to detect
> > > > cable link.
> > > > Sep 18 19:39:27 lanf2 kernel:   Speed and duplex
> > > > will be determined at time of connection.
> > > > Sep 18 19:39:27 lanf2 kernel:   Hardware receive
> > > > checksums disabled
> > > > Sep 18 19:39:27 lanf2 kernel:   ucode was not loaded
> > > >
> > > >
> > > >
> > > > [root@lanf2 /root]# ifconfig -a
> > > > eth0      Link encap:Ethernet  HWaddr
> > > > 00:E0:81:03:B9:7B
> > > >           inet addr:192.168.1.56
> > > > Bcast:192.168.1.255  Mask:255.255.255.0
> > > >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> > > > Metric:1
> > > >           RX packets:17 errors:0 dropped:0
> > > > overruns:0 frame:0
> > > >           TX packets:9 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0
> > > >
> > > > eth1      Link encap:Ethernet  HWaddr
> > > > 00:90:27:65:39:1B
> > > >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> > > > Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0
> > > >
> > > > eth2      Link encap:Ethernet  HWaddr
> > > > 00:90:27:65:37:8A
> > > >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> > > > Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0
> > > >
> > > > eth3      Link encap:Ethernet  HWaddr
> > > > FF:FF:FF:FF:FF:FF
> > > >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> > > > Metric:1
> > > >           RX packets:0 errors:0 dropped:0 overruns:0
> > > > frame:0
> > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > carrier:0
> > > >           collisions:0
> > > >
> > > > lo        Link encap:Local Loopback
> > > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > > >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> > > >           RX packets:18 errors:0 dropped:0
> > > > overruns:0 frame:0
> > > >           TX packets:18 errors:0 dropped:0
> > > > overruns:0 carrier:0
> > > >           collisions:0
> > > >
> > > > [root@lanf2 /root]#
> > > >
> > > > Any ideas??
> > > >
> > > > THanks,
> > > > Ben
> > > >
> > > > --
> > > > Ben Greear <greearb@candelatech.com>
> > > > <Ben_Greear@excite.com>
> > > > President of Candela Technologies Inc
> > > > http://www.candelatech.com
> > > > ScryMUD:  http://scry.wanfear.com
> > > > http://scry.wanfear.com/~greear
> > > >
> > > > --__--__--
> > > >
> > > > Message: 3
> > > > Date: Wed, 19 Sep 2001 00:21:38 -0400 (EDT)
> > > > From: Donald Becker <becker@scyld.com>
> > > > To: Ben Greear <greearb@candelatech.com>
> > > > cc: eepro list <eepro100@scyld.com>,
> > > > linux-kernel <linux-kernel@vger.kernel.org>
> > > > Subject: Re: [eepro100] eepro100 driver (2.4 kernel)
> > > > fails with S2080 Tomcat
> > > > i815t motherboard.
> > > >
> > > > On Tue, 18 Sep 2001, Ben Greear wrote:
> > > >
> > > > > I have a Tyan motherboard (S2080 Tomcat i815t)
> > > > with 2 built-in NICs.
> > > > >
> > > > > The manual claims this:
> > > > >
> > > > > "One Intel 82559 LAN controller
> > > > >  One ICH2 LAN controller"
> > > > >
> > > > > Seems that the eepro driver tries to bring up both
> > > > of
> > > > > them, and fails to read the eeprom on the second
> > > > one it
> > > > > scans.  One visible result is that the MAC is all
> > > > FF's.
> > > >
> > > > Does the diagnostic program correctly read the
> > > > EEPROM on both cards?
> > > > If so, my driver release should work with the cards.
> > > >
> > > > > eth0: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#3), 00:E0:81:03:B9:7B, IRQ 10.
> > > > > eth1: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#2), 00:90:27:65:39:1B, IRQ 3.
> > > > > eth2: Intel Corporation 82557 [Ethernet Pro 100],
> > > > 00:90:27:65:37:8A, IRQ 9.
> > > > > eth3: Invalid EEPROM checksum 0xff00, check
> > > > settings before activating this device!
> > > > > eth3: OEM i82557/i82558 10/100 Ethernet,
> > > > FF:FF:FF:FF:FF:FF, IRQ 11.
> > > >
> > > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth3
> > > >
> > > > The diagnostic does not (and cannot) know which card
> > > > is "eth3".
> > > > (Consider the case where no driver is loaded.)
> > > >
> > > > You must specify the interface to examine with e.g.
> > > > "-#3"
> > > >
> > > > Donald Becker                         becker@scyld.com
> > > > Scyld Computing Corporation           http://www.scyld.com
> > > > 410 Severn Ave. Suite 210             Second Generation Beowulf
> > > > Clusters
> > > > Annapolis MD 21403                    410-990-9993
> > > >
> > > >
> > > > --__--__--
> > > >
> > > > Message: 4
> > > > Date: Tue, 18 Sep 2001 22:04:55 -0700
> > > > From: Ben Greear <greearb@candelatech.com>
> > > > Organization: Candela Technologies
> > > > To: Donald Becker <becker@scyld.com>
> > > > CC: eepro list <eepro100@scyld.com>,
> > > > linux-kernel <linux-kernel@vger.kernel.org>
> > > > Subject: Re: [eepro100] eepro100 driver (2.4 kernel)
> > > > fails with S2080 Tomcati815t
> > > > motherboard.
> > > >
> > > > Interestingly enough, when I manually set a MAC it
> > > > seems to pass traffic,
> > > > at least at low speeds.  I'm about to crank it up a
> > > > bit to see what
> > > > falls out :)
> > > >
> > > > (Working fine at 10Mbps (about 4200
> > > > packets-per-second..)
> > > >
> > > >
> > > > Donald Becker wrote:
> > > > >
> > > > > On Tue, 18 Sep 2001, Ben Greear wrote:
> > > > >
> > > > > > I have a Tyan motherboard (S2080 Tomcat i815t)
> > > > with 2 built-in NICs.
> > > > > >
> > > > > > The manual claims this:
> > > > > >
> > > > > > "One Intel 82559 LAN controller
> > > > > >  One ICH2 LAN controller"
> > > > > >
> > > > > > Seems that the eepro driver tries to bring up
> > > > both of
> > > > > > them, and fails to read the eeprom on the second
> > > > one it
> > > > > > scans.  One visible result is that the MAC is
> > > > all FF's.
> > > > >
> > > > > Does the diagnostic program correctly read the
> > > > EEPROM on both cards?
> > > > > If so, my driver release should work with the
> > > > cards.
> > > > >
> > > >
> > > > It doesn't seem to...
> > > >
> > > >
> > > > [root@lanf1 /root]# eepro100-diag -aaeemmf -#1
> > > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker
> > > > (becker@scyld.com)
> > > >  http://www.scyld.com/diag/index.html
> > > > Index #1: Found a Intel i82562 EEPro100 adapter at
> > > > 0xdd80.
> > > > i82557 chip registers at 0xdd80:
> > > >   0c000050 0f162000 00000000 00080002 1be7ffff
> > > > 00000600
> > > >   No interrupt sources are pending.
> > > >    The transmit unit state is 'Suspended'.
> > > >    The receive unit state is 'Ready'.
> > > >   This status is normal for an activated but idle
> > > > interface.
> > > >  The Command register has an unprocessed command
> > > > 0c00(?!).
> > > > EEPROM contents, size 256x16:
> > > >     00: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x08: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x10: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x18: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x20: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x28: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x30: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x38: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x40: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x48: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x50: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x58: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x60: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x68: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x70: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x78: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x80: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x88: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x90: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0x98: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xa0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xa8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xb0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xb8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xc0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xc8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xd0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xd8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xe0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xe8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xf0: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >   0xf8: ffff ffff ffff ffff ffff ffff ffff ffff
> > > >  *****  The EEPROM checksum is INCORRECT!  *****
> > > >   The checksum is 0xFF00, it should be 0xBABA!
> > > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > >   Station address FF:FF:FF:FF:FF:FF.
> > > >   Board assembly ffffff-255, Physical connectors
> > > > present: RJ45 BNC AUI MII
> > > >   Primary interface chip i82555 PHY #-1.
> > > >     Secondary interface chip i82555, PHY -1.
> > > >   Baseline value of MII status register is 0000.
> > > >
> > > > [root@lanf1 /root]#
> > > >
> > > > > > eth0: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#3), 00:E0:81:03:B9:7B, IRQ 10.
> > > > > > eth1: Intel Corporation 82557 [Ethernet Pro 100]
> > > > (#2), 00:90:27:65:39:1B, IRQ 3.
> > > > > > eth2: Intel Corporation 82557 [Ethernet Pro
> > > > 100], 00:90:27:65:37:8A, IRQ 9.
> > > > > > eth3: Invalid EEPROM checksum 0xff00, check
> > > > settings before activating this device!
> > > > > > eth3: OEM i82557/i82558 10/100 Ethernet,
> > > > FF:FF:FF:FF:FF:FF, IRQ 11.
> > > > >
> > > > > > [root@lanf2 /root]# eepro100-diag -aaeemmf eth3
> > > > >
> > > > > The diagnostic does not (and cannot) know which
> > > > card is "eth3".
> > > > > (Consider the case where no driver is loaded.)
> > > >
> > > > I wish it would have complained about me sending it
> > > > eth3 then, so
> > > > I would have known!
> > > >
> > > > >
> > > > > You must specify the interface to examine with
> > > > e.g. "-#3"
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> > > > >
> > > > > Donald Becker
> > > > becker@scyld.com
> > > > > Scyld Computing Corporation
> > > > http://www.scyld.com
> > > > > 410 Severn Ave. Suite 210               Second
> > > > Generation Beowulf Clusters
> > > > > Annapolis MD 21403
> > > > 410-990-9993
> > > > >
> > > > > _______________________________________________
> > > > > eepro100 mailing list
> > > > > eepro100@scyld.com
> > > > > http://www.scyld.com/mailman/listinfo/eepro100
> > > >
> > > > --
> > > > Ben Greear <greearb@candelatech.com>
> > > > <Ben_Greear@excite.com>
> > > > President of Candela Technologies Inc
> > > > http://www.candelatech.com
> > > > ScryMUD:  http://scry.wanfear.com
> > > > http://scry.wanfear.com/~greear
> > > >
> > > > --__--__--
> > > >
> > > > Message: 5
> > > > From: "Alexander Gdalevich" <gdalevich@hotmail.com>
> > > > To: eepro100@scyld.com
> > > > Date: Wed, 19 Sep 2001 11:53:02 -0400
> > > > Subject: [eepro100] BSD driver
> > > >
> > > > People, hello!
> > > >
> > > > Is there an eepro100 driver for BSD?
> > > >
> > > > Thanks.
> > > >
> > > >
> > > >
> > > >
> > > _________________________________________________________________
> > > > Get your FREE download of MSN Explorer at
> > > > http://explorer.msn.com/intl.asp
> > > >
> > > >
> > > >
> > > >
> > > > --__--__--
> > > >
> > > > _______________________________________________
> > > > eepro100 mailing list
> > > > eepro100@scyld.com
> > > > http://www.scyld.com/mailman/listinfo/eepro100
> > > >
> > > >
> > > > End of eepro100 Digest
> > >
> > > __________________________________________________
> > > Terrorist Attacks on U.S. - How can you help?
> > > Donate cash, emergency relief information
> > > http://dailynews.yahoo.com/fc/US/Emergency_Information/
> > >
> > > _______________________________________________
> > > eepro100 mailing list
> > > eepro100@scyld.com
> > > http://www.scyld.com/mailman/listinfo/eepro100
> >
> > --
> >   +--------V--------+	Christoph.Plattner@alcatel.at
> >   |  A L C A T E L  |	-----------------------------
> >   +-----------------+	Phone: +43 1 27722 3706
> >          T A S		Fax:   +43 1 27722 3955
> >
> > _______________________________________________
> > eepro100 mailing list
> > eepro100@scyld.com
> > http://www.scyld.com/mailman/listinfo/eepro100
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
>