From nobody@FreeBSD.ORG Tue Aug  3 12:05:21 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 5859015102; Tue,  3 Aug 1999 12:05:21 -0700 (PDT)
Message-Id: <19990803190521.5859015102@hub.freebsd.org>
Date: Tue,  3 Aug 1999 12:05:21 -0700 (PDT)
From: jooji@neptune.oceancomputer.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: fxp driver not completely compatible with latest Intel PRO/100+ NICs
X-Send-Pr-Version: www-1.0

>Number:         12943
>Category:       kern
>Synopsis:       fxp driver not completely compatible with latest Intel PRO/100+ NICs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    dg
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug  3 12:10:00 PDT 1999
>Closed-Date:    Mon Oct 16 12:05:19 PDT 2000
>Last-Modified:  Mon Oct 16 12:06:20 PDT 2000
>Originator:     Jasper O'Malley
>Release:        FreeBSD 3.2-STABLE (cvsupped 7/31/1999)
>Organization:
Ocean Computer Group
>Environment:
FreeBSD edge-nj.example.com 3.2-STABLE FreeBSD 3.2-STABLE #3: Mon Aug  2 14:47
:47 EDT 1999     root@edge-nj.example.com:/usr/src/sys/compile/EDGE-NJ  i386
>Description:
The fxp driver in -STABLE incorrectly identifies the MAC address of any
and all new Intel PRO/100+ Management PCI NICs--model 734938-001, and
probably later models, as well--as 00:a4:c0:91:d2:9c. Although the
card still operates with the driver, placing two or more machines using
these NICs on the same Ethernet network results in a conflict. Unlike
older cards, ifconfig reports that the media type for the card is
"manual", with a single supported media type of "manual", and does not
report any "status" information.

Also, the following error is reported on boot:

   fxp2: warning: unsupported PHY, type = 0, addr = 0

Here's the full output of ifconfig for the card:

   fxp2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet 10.2.24.254 netmask 0xffffff00 broadcast 10.2.24.255
           ether 00:a4:c0:91:d2:9c
           media: manual
           supported media: manual

For reference, the actual MAC address of the above card, as reported
by the DOS-based Intel setup utility, is 00:90:27:89:76:81. As an aside,
the command

   ifconfig fxp2 ether 00:90:27:89:76:81

results in a segfault; this happens with the old Intel PRO cards, too.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->wpaul 
Responsible-Changed-By: des 
Responsible-Changed-When: Wed Aug 4 03:44:02 PDT 1999 
Responsible-Changed-Why:  
Ethernet drivers belong to Bill. 
Responsible-Changed-From-To: wpaul->dg 
Responsible-Changed-By: dg 
Responsible-Changed-When: Wed Aug 4 06:20:00 PDT 1999 
Responsible-Changed-Why:  
I wrote the fxp driver. 
State-Changed-From-To: open->analyzed 
State-Changed-By: dg 
State-Changed-When: Wed Aug 4 09:38:02 PDT 1999 
State-Changed-Why:  
It appears that the SEEPROM format has changed with the newest cards. I'm 
awaiting info on the new format from Intel. 

From: "Guseyn Ismaylov" <guseyn@azeri.com>
To: <freebsd-gnats-submit@freebsd.org>,
	<jooji@neptune.oceancomputer.com>
Cc:  
Subject: Re: kern/12943: fxp driver not completely compatible with latest Intel PRO/100+ NICs
Date: Thu, 24 Sep 1998 17:18:27 +0400

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_0003_01BDE7DF.584EBB80
 Content-Type: text/plain;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 Please tell me ...
 How can i fix this problem?
 
 ------=_NextPart_000_0003_01BDE7DF.584EBB80
 Content-Type: text/html;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <!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.2014.210" name=3DGENERATOR>
 <STYLE></STYLE>
 </HEAD>
 <BODY bgColor=3D#ffffff>
 <DIV><FONT face=3DArial size=3D2>Please tell me ...</FONT></DIV>
 <DIV><FONT face=3DArial size=3D2>How can i fix this=20
 problem?</FONT></DIV></BODY></HTML>
 
 ------=_NextPart_000_0003_01BDE7DF.584EBB80--
 
 

From: Alexander Latour-Henner <alex@servicefactory.com>
To: freebsd-gnats-submit@FreeBSD.org, jooji@neptune.oceancomputer.com
Cc:  
Subject: Re: kern/12943: fxp driver not completely compatible with latest Intel 
 PRO/100+ NICs
Date: Tue, 25 Jul 2000 14:02:34 +0200

 This is a multi-part message in MIME format.
 --------------5DE3AC04BA741013FC0F6F91
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Here is some info that may contribute to resolution of this problem.
 
 Intel has indeed changed the layout of the SEEPROM  for the newer
 chips (in my case 82559C).
 
 Offset 0x6 is not referenced any more in the 82559 data sheet. What
 remains in this case are the MDI-registers 2 and 3, PHY ID High and Low
 byte respectively. According to the 82559 data sheet:
 
 Register 2 = 0x02A8
 Register 3 = 0x0154
 
 For comparison, a 82555 has:
 
 Register 2 = 0x02A8
 Register 3 = 0x0150
 
 While trying to verify this I stumbled on a fundamental problem of not
 being able to get anything useful over the MDI. Another go at the 82559
 data sheet (section 9.1.7) hinted that one is supposed to reset (=0b)
 bit 28 (Ready) of the MDI Control Register when issuing an MDI command.
 Doing so did indeed solve the MDI communication problem and enabled
 succesful readback of the differentiating MDI Register 3.
 Even though I haven't found any explicit reference to it, it seems
 entirely adequate to handle the 82559 as comprising a 82555 PHY.
 
 After applying these mods, my Compaq Armada M300 with Mini-PCI NIC/Modem
 combo produces the following response to ifconfig fxp0:
 
 fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet6 fe80::2b4:c0ff:fe91:a6%fxp0 prefixlen 64 scopeid 0x1
         inet 10.2.0.12 netmask 0xffffff00 broadcast 10.2.0.255
         ether 00:b4:c0:91:00:a6
         media: autoselect (100baseTX) status: active
         supported media: autoselect 100baseTX <full-duplex> 100baseTX
 10baseT/UTP <full-duplex>
         10baseT/UTP
 
 Hope this helps.
 
 Alex
 
 
 
 
 
 --------------5DE3AC04BA741013FC0F6F91
 Content-Type: text/x-vcard; charset=us-ascii;
  name="alex.vcf"
 Content-Transfer-Encoding: 7bit
 Content-Description: Card for Alexander Latour-Henner
 Content-Disposition: attachment;
  filename="alex.vcf"
 
 begin:vcard 
 n:Latour-Henner;Alexander
 x-mozilla-html:FALSE
 org:Service Factory AB
 version:2.1
 email;internet:alex@servicefactory.com
 adr;quoted-printable:;;=C5rsta=E4ngsv=E4gen 17, 6tr;Stockholm;;S-11743;Sweden
 x-mozilla-cpt:;0
 fn:Alexander Latour-Henner
 end:vcard
 
 --------------5DE3AC04BA741013FC0F6F91--
 
 
State-Changed-From-To: analyzed->closed 
State-Changed-By: dg 
State-Changed-When: Mon Oct 16 12:05:19 PDT 2000 
State-Changed-Why:  
Fixed in later revs of the fxp driver. The bug was caused by a change 
in the size of the SEEPROM. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=12943 
>Unformatted:
