Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 234714 - D620: FC7T3 network card becomes eth1
Summary: D620: FC7T3 network card becomes eth1
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-31 18:43 UTC by Bernd Bartmann
Modified: 2008-05-07 01:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-07 01:23:15 UTC

Attachments (Terms of Use)
output of dmesg (deleted)
2007-03-31 18:44 UTC, Bernd Bartmann
no flags Details
output of lspci -v (deleted)
2007-03-31 18:44 UTC, Bernd Bartmann
no flags Details

Description Bernd Bartmann 2007-03-31 18:43:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070219 Firefox/

Description of problem:
The broadcom network card in my DELL D620 laptop gets eth1 in FC7T3 (also with todays rawhide kernel). This was not the case in FC7T2. This is the only network card in the system besides the WLAN interface.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run FC7T3 on a DELL D620

Actual Results:

Expected Results:

Additional info:

Comment 1 Bernd Bartmann 2007-03-31 18:44:10 UTC
Created attachment 151356 [details]
output of dmesg

Comment 2 Bernd Bartmann 2007-03-31 18:44:48 UTC
Created attachment 151357 [details]
output of lspci -v

Comment 3 Pete Zaitcev 2007-03-31 21:25:03 UTC
Tools have to add HWADDR into /etc/sysconfig/network-scripts/ifcfg-XXXX,
and create all of them, not just the eth0. This way scripts assign names
correctly. The /etc/mactab does not work anymore in all cases with the
transition away from calling nameif in scripts.

Comment 4 Harald Hoyer 2007-04-05 15:13:52 UTC
HWADDR can be configured in s-c-network. (Bind to MAC Address)

Comment 5 Bernd Bartmann 2007-04-05 16:38:06 UTC
Have you actually read the bug report???

There is only ONE network card in the laptop. This has always been eth0. There
is no need whatsoever that it suddenly becomes eth1 when there then is no eth0
at all.

Comment 6 Harald Hoyer 2007-04-10 08:24:43 UTC
> This is the only network card in the system besides the WLAN interface.

so, you have a WLAN interface, which becomes eth0 ?

Comment 7 Bernd Bartmann 2007-04-10 16:36:47 UTC
No, I have ONE LAN card (Broadcom using the tg3 driver) that is detected as eth0
first but then suddenly becomes eth1. See the dmesg output posted earlier.

There is also a WLAN card (wlan0 / wmaster0 Intel 3945) in the laptop that can
be switched off. Regardless if the WLAN interface is switched off or on then LAN
card  always becomes eth1.

Comment 8 Bug Zapper 2008-04-03 23:52:15 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

Comment 9 Bug Zapper 2008-05-07 01:23:13 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

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