[eepro100] eepro100 crashing with D815EEA motherboard

[Alvin Oga]

hi ya brian...

i have dozens of servers with the Intel D815EEAAL motherboard
( onboard lan... 

I am using the "patched" eepro100.c driver...
	http://www.linux-1U.net/MotherBoard/ee*

i moved the old eepro100.c driver aside and than used the patched one
	cd /usr/src/linux-2.2.16/drivers/net
	cp -p eepro100.c eepro100.2.2.16.c
	patch -m0 < eepro100.patch.txt  
	( but i manually edited the files instead )
	- than recompile that modules or into the kernel

-- sometimes i need to re-run lilo or remake the kernel if at bootup
   the systems gets the silly erroneous(?) "eth0: resources not available"etc

have fun
alvin
http://www.linux-1U.net.....1U firwalss...1U raid5....
 

On Sun, 1 Oct 2000, Brian Hirt wrote:

> Hello,
> 
> I recently purchased an Intel D815EEA motherboard that has an 
> integrated LAN apaptor.   I'm using RedHat 6.2, which doesn't
> know about this card, so I installed the most recent netdriver
> code, ftp://ftp.scyld.com/pub/network/netdriver-2.0-3.src.rpm
> 
> After installing the new drivers, the driver is recognized, but 
> my machine locks up whenever I try to bring the interface up, 
> forcing me to cycle the power.  The lock up appears to happen 
> 100% of the time.  If I initialize the driver with 
> "options=0x40" the driver seems to always initialize, but at 
> 10Mbps half duplex.  I was willing to live with this drawback, 
> but now I'm running into more problems.
> 
> The driver will periodically fail with a transmit time out:
> 
> 	kernel: eth0: Transmit timed out: status 0050  0080 at 2500/2512 commands 000c0000 000c0000 000c0000. 
> 
> sometimes the machine will continue to work, sometimes is locks
> up so badly that I have to cycle the power.  Sometimes it locks
> up without an error message.  I can reproduce the crash by doing 
> an ftp of a large file (600mb).  I have three identical boxes
> that all exhibit the same problems.  I'm at a totaly loss about
> what to do.  If there is more information that might help, let 
> me know.
> 
> Any suggestions?  Is this driver known not to work with the D815EEA?
> 
> My linux kernel is 2.2.14
> 
> The driver recognizes the card as such:
> 
> Intel i82562 EEPro100 at 0xc8036000, 00:D0:B7:A6:87:5D, IRQ 11. 
> 
> 
> eepro100-diag -f -aa, produces:
> 	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 0xdf00.
> 	i82557 chip registers at 0xdf00:
> 	  00000050 074900e4 00000000 00080002 18250000 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.
> 
> eepro100-diag -f -e, produces:
> 	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 0xdf00.
> 	Intel EtherExpress Pro 10/100 EEPROM contents:
> 	  Station address 00:D0:B7:A6:87:5D.
> 	  Board assembly 000000-000, Physical connectors present: RJ45
> 	  Primary interface chip i82555 PHY #1.
> 
> mii-diag eth0
> 	Basic registers of MII PHY #1:  0000 7809 02a8 0330 05e1 0000 0000 0000.
> 	 Basic mode control register 0x0000: Auto-negotiation disabled, with
> 	 Speed fixed at 10 mbps, half-duplex.
> 	 Basic mode status register 0x7809 ... 780d.
> 	   Link status: previously broken, but now reestablished.
> 	 Link partner information information is not exchanged when in fixed speed mode.
> 
> 
> 
> -- 
> The world's most ambitious and comprehensive PC game database project.
> 
>                       http://www.mobygames.com
> 
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
>