Red Hat Bugzilla – Bug 186601
internal airport and ethernet are swapped
Last modified: 2014-03-16 22:59:02 EDT
Description of problem:
During the network install, eth0 is listed as Airport, while eth1 is listed as
SunGem (ethernet). They are swapped. Interestingly, selecting eth1 prompts for
an SSID and password, so it does know eth1 is actually the airport.
This is on an older (667mhz) G4 Ti PowerBook.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Select network install
eth1: sungem ethernet
eth0: sungem ethernet
If you run 'kudzu -p -c NETWORK' post-install, does it show the right thing?
Yes. See below.
[root@indurain aldyh]# kudzu -p -c NETWORK
desc: "Apple Computer Inc. UniNorth GMAC (Sun GEM)"
desc: "Apple Computer Inc.|Airport"
Just adding confirmation.. I see the same problem on my TiBook...
Ditto on my G4 Quicksilver.
Is this still happening in Fedora 7 test 2?
I don't know about FC7t2, but on FC6 it still happens.
Why does it matter which is eth0 in the installer?
Fedora Core 6 is no longer maintained. Is this bug still present in Fedora 7 or
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.