Description of problem: Updating to kernel-3.6.2-1.fc16.x86_64 broke the WiFi function. Wireless failed in the latest and the last three kernels. Even removing kmod-wl-3.6.2-1.fc16.x86_64 dependancies, wireless does not work for previous kernels. Version-Release number of selected component (if applicable): kernel-3.6.2-1.fc16.x86_64 kmod-wl--3.6.2-1.fc16.x86_64 How reproducible: May occur at any new kernel update. Steps to Reproduce: sudo yum -y update Actual results: kernel-3.6.2-1.fc16.x86_64 wireless failed kernel-3.4.11-1.fc16.x86_64 wireless failed also kernel-3.4.9-2.fc16.x86_64 wireless failed also kernel-3.4.9-1.fc16.x86_64 wireless failed also Expected results: Expect the Fedora team to put the kmod package into the Fedora 16 repository promptly. Additional info: Fedora 17 has the same problem, but it has the kmod-7-2.fc17.x86_64.rpm package. After removing kmod-wl akmod-wl broadcom-wl the wireless for Fedora works well will all existing kernels.
Putting the kmod package similar to kmod-7-2.fc17.x86_64.rpm into the Fedora 16 repository is the cleanest, safest and most natural way to ensure the quality and integrity of the Fedora 16 system. No need to wait or beg the Broadcom team and the is no guarantee that kmod-wl will not be broken again. If the Fedora team is not going to put kmod into Fedora 16, can you give me instructions as to how to make wireless working? Can I install kmod-7-2.fc17.x86_64.rpm into Fedora 16? Is it compatible with Fedora 16?
(In reply to comment #2) > > Putting the kmod package similar to kmod-7-2.fc17.x86_64.rpm into > the Fedora 16 repository is the cleanest, safest and most natural way to > ensure the quality and integrity of the Fedora 16 system. No it isn't. That has nothing to do with wireless. F16 uses module-init-tools. > If the Fedora team is not going to put kmod into Fedora 16, can you give me > instructions as to how to make wireless working? Can I install > kmod-7-2.fc17.x86_64.rpm into Fedora 16? No, but it doesn't matter anyway. > Is it compatible with Fedora 16? No. *** This bug has been marked as a duplicate of bug 870704 ***