wl vs. b43 are not properly configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
Hardy |
Fix Released
|
Undecided
|
Martin Pitt | ||
Intrepid |
Fix Released
|
Undecided
|
Martin Pitt | ||
linux-restricted-modules (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Medium
|
Unassigned |
Bug Description
Fresh install of kubuntu Intrepid alpha 5, then full update. Attempt detection of wlan hardware with Hardware Drivers Manager, which finds and activates "wl", and also proposes fwcutter usage to get "Broadcom B43 wireless driver". This downloads the firmware without complaint, and finally requests reboot. After reboot the B43 driver is still not checked. This procedure repeats, but no check of the B43 results, and wlan does not see any networks.
On same computer using kubuntu 8.04 all works fine
SRU justification: The current hardy-proposed kernel (2.6.24-21) now contains the wl driver as well, and we need a GUI friendly way to configure it (relative to b43). "wl" was not shipped yet with hardy final (it didn't even exist at that time), thus we need to supply the corresponding handler in a jockey SRU as well.
Test case: On a system with a Broadcom wireless card, open jockey. You should see the "B43" or the "Broadcom STA" driver, or both if your card is supported by both. Only one should be displayed as active/in use at a time. Try to enable the other one, reboot, and make sure your wifi works.
Changed in jockey: | |
status: | New → Confirmed |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in jockey: | |
milestone: | none → ubuntu-8.10 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. I have classified this bug as a bug in linux.