Hide Forgot
Created attachment 571880 [details] output from dmesg when using kernel-3.2.10-1 Description of problem: The wifi interface is available and works fine under 3.2.7 on my Dell latitude E6420, but not in the updates that I have run since: kernel-3.2.9-2.fc16.x86_64 kernel-3.2.10-1.fc16.x86_64 kernel-3.2.10-3.fc16.x86_64 Under these kernels, the wireless interface is not available in network manager Version-Release number of selected component (if applicable): kernel-3.2.10-3 How reproducible: Steps to Reproduce: 1. Update to kernel-3.2.9-2.fc16.x86_64 or 3.2.10-1 or 3.2.10-3 2. Reboot 3. No wireless interface available Actual results: Working wireless interface Expected results: No wireless interface available Additional info:
Created attachment 571881 [details] output from dmesg when using kernel-3.2.7-1 (wifi working)
You were using the wl kmod with 3.2.7-1. That's something Fedora doesn't provide, so we have no idea why it would or wouldn't load/work on a newer kernel. There's nothing we can do to help you on that particular issue. However, some of the chipsets wl supports are now supported by the brcm drivers. You might try loading those. John, do you know which?
My guess would be that brcmsmac should be loaded. Of course, it probably should have loaded automatically... Can we see the output of running 'lspci -n'?
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Unfortunately 3.3.0-4 was no better. This was the output of lspci -n under that kernel, but it is the same under 3.2.7-1: 00:00.0 0600: 8086:0104 (rev 09) 00:01.0 0604: 8086:0101 (rev 09) 00:02.0 0300: 8086:0126 (rev 09) 00:16.0 0780: 8086:1c3a (rev 04) 00:19.0 0200: 8086:1502 (rev 04) 00:1a.0 0c03: 8086:1c2d (rev 04) 00:1b.0 0403: 8086:1c20 (rev 04) 00:1c.0 0604: 8086:1c10 (rev b4) 00:1c.1 0604: 8086:1c12 (rev b4) 00:1c.2 0604: 8086:1c14 (rev b4) 00:1c.3 0604: 8086:1c16 (rev b4) 00:1c.5 0604: 8086:1c1a (rev b4) 00:1d.0 0c03: 8086:1c26 (rev 04) 00:1f.0 0601: 8086:1c4f (rev 04) 00:1f.2 0104: 8086:282a (rev 04) 00:1f.3 0c05: 8086:1c22 (rev 04) 01:00.0 0300: 10de:1056 (rev a1) 01:00.1 0403: 10de:0e08 (rev a1) 03:00.0 0280: 14e4:4359 0b:00.0 0805: 1217:8221 (rev 05) 0b:00.1 0180: 1217:8231 (rev 03)
(In reply to comment #7) > Unfortunately 3.3.0-4 was no better. > This was the output of lspci -n under that kernel, but it is the same under > 3.2.7-1: > > 03:00.0 0280: 14e4:4359 You system has a bcm43228. That is supported by the proprietary wl.ko driver. The brcmsmac driver does not yet support this device.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
ASUS P8Z77-I Deluxe has this onboard (mini PCI-E slot). The bcma module loads, but brcmsmac is not auto-loaded and no wireless device is created even if I load it manually. BCM43228 $ lspci -n [snip] 03:00.0 0280: 14e4:4359 kernel-3.6.5-1.fc17.x86_64
Still no upstream support for this in brcmsmac driver, this date.. When it comes out.. Cond NAK upstream till then..
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still no upstream driver as of 3.11.
FWIW: Support was added in 3.17, but it requires proprietary firmware. We're halfway there.