Red Hat Bugzilla – Bug 131080
Network Config Utility drops all wireless hardware after reboot.
Last modified: 2014-03-16 22:47:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.4 (KHTML, like Gecko) Safari/125.9
Description of problem:
Building the box with a Netgear MA 311 PCI wireless adapter works fine. The adapter is correctly detected as a Prism 2.5 chipset wireless adapter. The wireless device is added with no problem. It is bound to the correct hardware, mode, channel and WEP key are correctly set, and despite an error message during activation (SET failed), the device comes up and works fine.
When the box is rebooted, however, the following anomalies occur:
- During boot sequence, kudzu detects a change in hardware (it wants to remove and add a Prism 2.5 chipset controller). I ignore both.
- The wireless controller doesn't work.
- After login, the network config-tool reveals the following
- The device created (eth1) remains unchanged
- The hardware (eth1) has been changed from a wireless Prism/Intersil adapter to the onboard ethernet adapter (showing the same hardware as both eth0 and eth1). The status of eth1 is system, not ok.
- Any attempt to manually add a wireless device, shows a list of ethernet adapters, not wireless adapters.
- The ifcfg files for both the ethernet adapter and the wireless adapter are correct.
- The hardware browser shows, under network devices, the correct onboard ethernet adapter as /dev/eth0 as well as the Prism/Intersil device as /dev/eth2. There are no references to /dev/eth1
This behavior was repeated during a rebuild.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Build FC2 using special kernel boot disk for Via C3 chipset. (see bugzilla ID 120685). At end, load kernel 184.108.40.206-525
2. Get configure wireless ethernet adapter
Its a mini-com mini-ITX board, running a Via C3 chip. 128 MB RAM. The wireless card is a Netgear MA 311.
Have you upgraded to the errata kudzu packages?
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Closing, no response to query.