[eepro100] Compiling source for RH 6.2

Brian Ugie bugie@pzs.com
Mon Dec 17 16:23:01 2001


This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_C09DEFEB.58395731
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi,
=20
I have installed  RH 6.2 onto an Intel R44LX server board with the eepro =
82559 chipset built in. Linux detect the card just fine and loads the =
modules and everything just fine. An 'ifconfig' shows that the card is up =
with an IP address. When I try to ping it though, I get no response. It is =
very weird. =20
I get a few of these in the /var/log/messages:
=20
Dec 17 11:01:52 NS3 ifup: SIOCADDRT: Network is unreachable
=20
I have since added in a 3c905B  (eth1) which works fine so long as the =
eepro100 adapter is down ( the module can be loaded). The 3com card will =
ping just fine but once I ifup eth0 (the eepro), then neither will ping. I =
ifdown eth0 and then the 3com will ping again. This is also all over =
telnet connected to the 3com card. Telnet works fine when eth0 is up and =
neither interface can ping.=20
=20
Any help or advice or direction would be greatly appreciated. I have tried =
new drivers and the e100 drivers from intel.
=20
Thanks
=20
--Brian



--=_C09DEFEB.58395731
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt Tahoma; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV><FONT size=3D1>Hi,</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>I have installed&nbsp; RH 6.2 onto an Intel R44LX =
server board=20
with the eepro 82559 chipset built in. Linux detect the card just fine and =
loads=20
the modules and everything just fine. An 'ifconfig' shows that the card is =
up=20
with an IP address. When I try to ping it though, I get no response. It is =
very=20
weird.&nbsp; <BR>I get a few of these in the /var/log/messages:<BR>&nbsp;<B=
R>Dec=20
17 11:01:52 NS3 ifup: SIOCADDRT: Network is unreachable<BR>&nbsp;<BR>I =
have=20
since added in a 3c905B&nbsp; (eth1) which works fine so long as the =
eepro100=20
adapter is down ( the module can be loaded). The 3com card will ping just =
fine=20
but once I ifup eth0 (the eepro), then neither will ping. I ifdown eth0 =
and then=20
the 3com will ping again. This is also all over telnet connected to the =
3com=20
card. Telnet works fine when eth0 is up and neither interface can ping.=20
<BR>&nbsp;<BR>Any help or advice or direction would be greatly appreciated.=
 I=20
have tried new drivers and the e100 drivers from=20
intel.<BR>&nbsp;<BR>Thanks<BR>&nbsp;<BR>--Brian<BR></DIV></FONT></BODY></HT=
ML>

--=_C09DEFEB.58395731--