Description of problem: I have been running every version of Fedora since Fedora Core 6 and the WiFi never had a problem until Fedora 17. I never had to do anything for WiFi until Fedora 15 or earlier when I was forced to installed broadcom-wl, akmod-wl and kmod-wl from the Fusion repository for the WiFi to work. I installed Fedora 17 one month after its released. The WiFi did not work. Was it because the kmod-wl did not sync with the later Fedora 17 kernel? To ensure the quality of Fedora 17, I would refrain from hacking it to work by compiling an external source. Updating only form the Fedora and Fusion repositories will ensure the integrity of Fedora 17. Also, hacking it may not work and render it inoperable with kernel panic. After two or more normal updates, the WiFi was finally working. My Fedora 17 WiFi was broken again since the update to kernel-3.6.1-1.fc17.x86_64. In fact, that kernel does not boot up. The WiFi was still not working on my next update to to kernel-3.6.2-4.fc17.x86_64. It is not known whether the upcoming update to kernel-3.6.2-5.fc17.x86_64 would work at all. On booting up earlier versions like kernel-3.5.6-1.fc17.x86_64 and kernel-3.5.4-2.fc17.x86_64, the WiFi also did not work. Was the WiFi operating data that was used in earlier version corrupted? There is a danger that future updates, including Fedora 18, with Broadcom chipset will never work anymore as Broadcom cut the support resources or give up updating kmod-wl to sync with the regular release of Linux kernel. Then, Broadcom is truly liable to all its customers in time and resources wasted. Why is Broadcom selling a product that does not work suddenly? I am guessing that Broadcom is holding on to dear life by keeping its WiFi firmware at any cost to its customers. That is gross irresponsibilities since there are many Broadcom chipset devices running Linux. Why did Broadcom WiFi works on Windows and may have problem with Linux? As it is, Fedora has at least one monthly kernel update and Broadcom will always have great difficulty keeping up. Why don't Broadcom pass over all the essential codes to Linux like it did for Windows to relief of its pains and resources? Now, it appears that Fedora 18 beta may also have similar problem! Perhaps, the Fedora team can look into how to resolve this problem with Broadcom once and for all. Perhaps, the Fedora team can look into a fallback procedure to the last version of Fedora like Fedora 10 for Broadcom chipset where users does not have to install broadcom-wl, akmod-wl and kmod-wl from the Fusion repository and reset the kernel to that point. Fedora 17 and onwards is broken regurally because of being held hostage by Broadcom is not the way as users will give up using Fedora and move away from Fedora. At the least, the Fedora team can look into including a universal base WiFi module into the kernel such that WiFi is operational immediately after installing any Fedora version without connecting to Wired LAN to install any modules to make WiFi work on First Boot. This base WiFi will also guarantee WiFi connectivity whenever Broadcom has a problem or someone at Fedora broke the WiFi with impunity. Version-Release number of selected component (if applicable): kernel-3.6.1-1.fc17.x86_64 kernel-3.6.2-4.fc17.x86_64 How reproducible: May occur at any new kernel update. Steps to Reproduce: sudo yum -y update Actual results: kernel-3.6.1-1.fc17.x86_64 does not boot up kernel-3.6.2-4.fc17.x86_64 WiFi still not working. kernel-3.5.6-1.fc17.x86_64 WiFi that used to work does not work anymore. kernel-3.5.4-2.fc17.x86_64 WiFi that used to work does not work anymore. Expected results: Keep updating using 'sudo yum -y update' until the WiFi works again. Expect Fedora 17 WiFi will work again before the release Fedora 18 in December. Otherwise, Fedora is broken as I do not have Fedora 17 to run. Additional info: I noticed that in Fedora 17 and one or two versions earlier, there was no SSID list in the NetworkManager when the Wired LAN is connected. One of the improvement in Fedora 17 is that the NetworkManager icon changes to VPN icon when the VPN is connected.
abrt is a ghost since it cannot report to Fedora as there is no internet connection. Attempting to connect via Wireless using the NetworkManager will invoke abrt ,but as the WiFi is broken the bug cannot be transmitted to Fedora. Even if abrt stored the bugs, Wired LAN will not be used unless it is need for the next kernel update. It is not known whether the WiFi bug will be transmitted to Fedora when there was Wired LAN connections later.
Fedora does not provide or support kmod-wl, nor any kmods at all. This bugzilla component is for the userland 'module-init-utils' replacment called kmod. If you are having issues with kmod-wl, you should take them up with the people providing that module.
1. WiFi still not working after updating to kernel-3.6.3-1.fc17.x86_6 2. sudo yum remove kmod-wl akmod-wl broadcom-wl 3. sudo yum install kmod 4. reboot My WiFi for Fedora 17 is now working well. The Fedora team should now focus on the kmod package and push it into Fedora 18 by default. When all is well, there is no need to do a Wired LAN connection to install from the external Fusion repository to get WiFi to work. ================================================== I also did an update to kernel-3.6.2-1.fc16.x86_64 for Fedora 16. Like Fedora 17, the WiFi is also broken. Unlike Fedora 17, Fedora 16 does not have the kmod package. I did sudo yum remove kmod-wl-3.6.2-1.fc16.x86_64 The last two kernels: kernel-3.4.11-1.fc16.x86_64 and kernel-3.4.9-2.fc16.x86_64 failed on WiFi also. This truly highlight the danger on relying on Broadcom on kmod-wl. No I cannot use Fedora 16 on WiFi. Is there a way to get my Fedora 16 to work? Can the Fedora team push the kmod package into the Fedora 16 repository for the next update?
Sorry, no. As I've already said, Fedora doesn't support external kernel modules, and this bugzilla component is for userspace module loading utilities.
*** Bug 871219 has been marked as a duplicate of this bug. ***