i386/139811: FreeBSD did not recognize Intel Gigabit ET Dual
Port Srvr Adpt network adapter from intel with chipset 897654
Vogel, Jack
jack.vogel at intel.com
Wed Oct 21 18:00:14 UTC 2009
The following reply was made to PR i386/139811; it has been noted by GNATS.
From: "Vogel, Jack" <jack.vogel at intel.com>
To: "bug-followup at FreeBSD.org" <bug-followup at FreeBSD.org>,
"jluis.estgf at gmail.com" <jluis.estgf at gmail.com>
Cc:
Subject: Re: i386/139811: FreeBSD did not recognize Intel Gigabit ET Dual
Port Srvr Adpt network adapter from intel with chipset 897654
Date: Wed, 21 Oct 2009 10:23:21 -0700
--_000_1DB50624F8348F48840F2E2CF6040A9D9B9788C8orsmsx508amrcor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
This is not an adequate designation of the parts involved, I need the Intel=
part numbers, I also cannot tell from this description if this is only sup=
posed to describe the adapter board or a server motherboard.
I'm guessing that you mean its an 82576? If so, are you aware that in Free=
BSD 7.2 this should use the igb rather than the em driver? Nevertheless, bo=
th drivers are in the GENERIC kernel so your adapter should be discovered.
The only other thing I can think of, depending on the server hardware, with=
many things plugged into expansion slots I have seen some cards mysterious=
ly disappear from the PCI tree, this would be on ESB2 type systems. Making =
sure that all firmware is updated to the latest can help this. You can try =
removing everything but the new card and see if it then becomes visible. Tr=
y putting the adapter into a different system as another test.
If this fails its likely bad hardware.
Jack Vogel
Intel LAD Software
--_000_1DB50624F8348F48840F2E2CF6040A9D9B9788C8orsmsx508amrcor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>This is not an adequate designation of the parts involve=
d, I
need the Intel part numbers, I also cannot tell from this description if th=
is
is only supposed to describe the adapter board or a server motherboard.<o:p=
></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I’m guessing that you mean its an 82576? If =
so,
are you aware that in FreeBSD 7.2 this should use the igb rather than the e=
m
driver? Nevertheless, both drivers are in the GENERIC kernel so your adapte=
r
should be discovered.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>The only other thing I can think of, depending on the se=
rver
hardware, with many things plugged into expansion slots I have seen some ca=
rds
mysteriously disappear from the PCI tree, this would be on ESB2 type system=
s.
Making sure that all firmware is updated to the latest can help this. You c=
an
try removing everything but the new card and see if it then becomes visible=
.
Try putting the adapter into a different system as another test.<o:p></o:p>=
</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>If this fails its likely bad hardware.<o:p></o:p></span>=
</font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Jack Vogel<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Intel LAD Software<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
--_000_1DB50624F8348F48840F2E2CF6040A9D9B9788C8orsmsx508amrcor_--
More information about the freebsd-i386
mailing list