Bug 746951 - biosdevname-0.3.11 Changed named of onboard NIC to p2p1
Summary: biosdevname-0.3.11 Changed named of onboard NIC to p2p1
Keywords:
Status: CLOSED DUPLICATE of bug 746422
Alias: None
Product: Fedora
Classification: Fedora
Component: biosdevname
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Praveen K Paladugu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-18 11:34 UTC by nico
Modified: 2011-11-09 14:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-09 14:34:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description nico 2011-10-18 11:34:51 UTC
Description of problem:
The recent update of biosdevname to biosdevname-0.3.11-1.fc15.i686 changed my onboard nic in my Thinkpad T60 from em1 to p2p1.

With the latest version (biosdevname-0.3.11-1.fc15.i686) installed, biosdevname -d reports:

BIOS device: p2p1
Kernel name: p2p1
Permanent MAC: xxx
Assigned MAC : xxx
Driver: e1000e
Driver version: 1.3.10-k2
Firmware version: 0.5-1
Bus Info: 0000:02:00.0
PCI name      : 0000:02:00.0
PCI Slot      : 2
Index in slot: 1

Downgrading to the version before (biosdevname-0.3.8-1.fc15.i686) reports:

BIOS device: em1
Kernel name: p2p1
Permanent MAC: 00:1A:6B:35:F8:2B
Assigned MAC : 00:1A:6B:35:F8:2B
Driver: e1000e
Driver version: 1.3.10-k2
Firmware version: 0.5-1
Bus Info: 0000:02:00.0
PCI name      : 0000:02:00.0
PCI Slot      : embedded
Embedded Index: 1

The Kernel name is changed to em1 after reboot.


Version-Release number of selected component (if applicable):
Good version: biosdevname-0.3.8-1.fc15.i686
faulty version: biosdevname-0.3.11-1.fc15.i686

How reproducible:
With the corresponding hardware: just up/downgrade biosdevname


Actual results:
Onboard NIC will be renamed from em1 to p2p1 (on my Laptop)

Expected results:
NIC should not get renamed ;-)

Comment 1 Praveen K Paladugu 2011-11-09 14:34:03 UTC

*** This bug has been marked as a duplicate of bug 746422 ***


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