Bug 187640 - Support aliases in /etc/modprobe.d/
Support aliases in /etc/modprobe.d/
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
: 186597 186664 (view as bug list)
Depends On:
Blocks: 87718
  Show dependency treegraph
Reported: 2006-04-01 22:54 EST by Robert Locke
Modified: 2008-05-06 11:44 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 11:44:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Locke 2006-04-01 22:54:46 EST
Description of problem:
If a network alias is defined in a file in /etc/modprobe.d/filename, it is not
picked up by system-config-network and offered to be configured.

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

How reproducible:

Steps to Reproduce:
1. Create file /etc/modprobe.d/madwifi containing "alias ath0 ath_pci"
2. Try running system-config-network to configure card - not accessible
3. Move alias to /etc/modprobe.conf
4. system-config-network now able to configure wireless adapter

Additional info:
This is the case when the madwifi package is initially installed from livna.org
which "correctly" creates a file /etc/modprobe.d/madwifi to support the modules.
 The modules are loaded by the kernel and the card can be configured by hand,
but not through the system-config-network tool.  Move the lines that were in
/etc/modprobe.d/madwifi into /etc/modprobe.conf and system-config-network now
can configure the card.
Comment 1 Gerry Tool 2006-04-02 10:36:11 EDT
Concur with this bug post.  Following work-around, ath0 works correctly. 
However, NetworkManager seems not to be compatible with it.  That should perhaps
be a separate bug report?
Comment 2 Christopher J. Bottaro 2006-05-02 11:37:50 EDT
I experience this bug as well.
Comment 3 Harald Hoyer 2006-05-19 05:53:43 EDT
*** Bug 186664 has been marked as a duplicate of this bug. ***
Comment 4 Harald Hoyer 2006-05-19 05:54:20 EDT
*** Bug 186597 has been marked as a duplicate of this bug. ***
Comment 5 Gianluca Sforna 2006-10-28 17:04:24 EDT
Still relevant in FC6.

see http://bugzilla.livna.org/show_bug.cgi?id=1225
Comment 6 Bug Zapper 2008-04-03 22:31:06 EDT
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
the change.

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
Comment 7 Bug Zapper 2008-05-06 11:44:29 EDT
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.

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