Bug 134000 - 3c59x failure: MAC 00:00:00:00:00:00
Summary: 3c59x failure: MAC 00:00:00:00:00:00
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-28 21:37 UTC by Alan Cox
Modified: 2015-01-04 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-07 07:54:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alan Cox 2004-09-28 21:37:46 UTC
The 3c59x driver finds the 3c59x in the mobility PCI dock but reports
no MII and decides it has a Mac address of 00:00:00:00:00:00. The
latter breaks all sorts of user space tools. At the very least we
ought to spot 00:00 MAC and skip that device given that there are
devices it isn't handling correctly.

Comment 2 Dave Jones 2005-07-15 18:02:55 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 3 Dave Jones 2005-12-07 07:54:30 UTC
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug with current FC3 updates, please
reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

If you are not the reporter, but can reproduce this problem against
FC4, please open a new bug.

Thank you.



Note You need to log in before you can comment on or make changes to this bug.