Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Nov 2002 09:46:08 -0600 (CST)
From:      Felipe Gasper <fgasper@uiuc.edu>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/45483: Invalid MAC reported by new Linksys LNE-100TX (dc)
Message-ID:  <200211191546.gAJFk8tU000240@nh-mealworm.csh.uiuc.edu>

next in thread | raw e-mail | index | archive | help

>Number:         45483
>Category:       kern
>Synopsis:       Invalid MAC reported by new Linksys LNE-100TX (dc)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 19 07:50:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Felipe
>Release:        FreeBSD 4.7-RELEASE i386
>Organization:
>Environment:
System: FreeBSD nh-mealworm.csh.uiuc.edu 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Fri Oct 11 08:07:02 CDT 2002 root@nh-mealworm.csh.uiuc.edu:/usr/obj/usr/src/sys/CUSTOM-11-10-2002 i386


	
>Description:
	
	I have a Linksys LNE-100TX rev 5.1 that is reporting
	08:00:08:00:08:00 as its MAC address, judging from dmesg:

dc0: <ADMtek AN985 10/100BaseTX> port 0x6100-0x61ff mem 0xe4000000-0xe40003ff ir
q 10 at device 18.0 on pci0
dc0: Ethernet address: 08:00:08:00:08:00
miibus0: <MII bus> on dc0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto 

	I moved the card to a newer Windows box, and it reports a valid MAC.
	This problem, perhaps, is a result of this newer card expecting
	PCI 2.2? The hardware that I have is pretty old- about 5 years.
	I know that this issue has been discussed on some mailing lists,
	but I was unable to find an actual bug report dealing with it.

>How-To-Repeat:
	Put in a recent model of Linksys's LNE-100TX NIC (rev. 5.1 is what
	I have). This problem may be hardware-dependent, but I am getting
	an invalid MAC at boot.

>Fix:
	Not sure....could be hardware-related; if so, perhaps there is a
	workaround possible from within the kernel?
	


>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211191546.gAJFk8tU000240>