Red Hat Bugzilla – Bug 172673
Patch to add basic ethtool interface to Prism54 Wireless Network Devices
Last modified: 2007-11-30 17:11:16 EST
Description of problem:
As I have mentioned in
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169492), there can be some
difficulties when using a Prism54-based card in Fedora Core with its
system-config-network packages. Furthermore, reflecting the concerns explicated
in (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135954), the
system-config-network utilities do not automatically list the Prism54 hardware
as an item to add to the list. If it lists the module as an option, it has been
after much black-magic has occurred.
To make using Prism54 cards more intuitive with Fedora Core, I wrote a patch to
/usr/share/system-config-network/module-info that includes the Prism54 device.
After adding the entry to the list, system-config-network-* now properly handles
This is a known problem, as I have mentioned with #135954, so there is no reason
that the module-info should not be patched to reflect a fix.
Version-Release number of selected component (if applicable):
The majority of the time.
Steps to Reproduce:
1. Insert a Prism54 card on boot.
2. Attempt to add the Prism54 hardware using system-config-network
Despite the kernel's recognition of the device and everything else that would
suggest a functioning device, a Prism54 device cannot be added. The driver does
not show up in the list.
The Prism54 driver should appear in the list.
It does not matter whether the Prism54 device was added before booting the
machine or after it was running. This situation is generally hopeless. I have a
Created attachment 120803 [details]
Patch to add Prism54 device to system-config-network driver list.
Harald, I second the report and was about to report the same.
This patch makes it work for me, too.
The code is not yet in rawhide. I propose we should add it.
I talked to Harald. He proposed, this patch is a workaround, but we should
prefer a real fix, which is to add "ethtool -i" interface support to the prism
I hacked a patch, and indeed it seems to make things work.
Attaching, FYI, but will also send it to the netdev mailing list.
Created attachment 127681 [details]
What needs to be done to get this small patch in?
So, did you send it to netdev like you promised on 4/12?
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
I finally posted the patch to the netdev list today.
Do you intend to follow-up to Jeff Garzik's reply?
I finally did:
I have pushed Kai's patch upstream destined for 2.6.21. It should be in
Fedora (rawhide) shortly thereafter.