Jockey user experience nightmare for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver
Bug #578970 reported by
beej
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Jockey |
New
|
Undecided
|
Unassigned | ||
NULL Project |
Invalid
|
Undecided
|
Unassigned | ||
New User Experience Team |
Invalid
|
Wishlist
|
Unassigned | ||
jockey (Ubuntu) |
Opinion
|
Undecided
|
Unassigned |
Bug Description
The Jockey user experience is awful when Ubuntu (currently 10.04) is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
summary: |
- user experience for installation of Ubuntu on machines requiring b43 and - b43-legacy wireless driver needs work + user experience nightmare for installation of Ubuntu on machines + requiring b43 and b43-legacy wireless driver |
description: | updated |
description: | updated |
description: | updated |
summary: |
- user experience nightmare for installation of Ubuntu on machines + Jockey user experience nightmare for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver |
description: | updated |
Changed in new-user-experience-team: | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
1) The release of Ubuntu you are using: Luci Lynx, but the problem has been persistent and ongoing since at least Hardy
2) Focus of bug: User Experience with Jockey finding, loading, and activating b43, 43 legacy drivers.
To make sure this an addressable/fixable User Experience bug I'll make the assumption that the intention of the bug reporter is to limit the scope to using Jockey to get Broadcom b43 and b43 legacy drivers working on initial install or upgrade, not on any of the other issues like intermittent connections, wpa connection difficulty, etc., etc.
3) What you expected to happen: That Jockey should load and activate Broadcom b43 and 'b43 Legacy' wifi drivers.
4) What actually happens: Jockey consistently fails to correctly find, load and activate these drivers requiring all manner of research, involving b43-fwcutter, bcmwl source, ndiswrapper, command line fiddling and even sometimes requiring manual make and compile. This is completely unacceptable for Ubuntu to achieve its goals for user friendliness.
This is an appropriate meta bug to file because a comprehensive fix is needed that will ensure that Jockey consistently loads and activates the proprietary Broadcom drivers correctly in a smooth "just works" way.
This is a pervasive problem that is plaguing new the new Ubuntu user's experience. The Ubuntu forums are seeing a steady stream of new Ubuntu users who are trying out the otherwise very user-friendly Lucid Lynx.
To call it "pretty bad" as the bug reporter did is completely understating it. Try "nightmare". Manually working with b43-fwcutter is a nightmare for new users. Not to mention if that DOESN'T work and you actually need to user ndiswrapper instead (as I found I had to after days of arduous trials).
I will come back and post more details of my set up later but for now to try to get the big picture, here's just some of the related reported bugs -- the pattern is very clear. Getting Broadcom wireless to work is a complete nightmare for new Ubuntu users.
355645 Can not set up wireless network on BCM4318 linux (Ubuntu) Confirmed
511379 cannot load Broadcom STA wireless driver (BCM4311)
188975 Broadcom bcm4306 rev 3 chipset not working linux (Ubuntu) Medium In Progress
197558 ssb module breaks BCM4328 with ndiswrapper (regression from 2.6.24-10) linux (Ubuntu) Medium Confirmed
210373 Broadcom 4306 doesn't work! I cannot connect to any wireless network linux (Ubuntu) Medium Incomplete
291271 Jockey Not Detecting Broadcom Wireless Card, When It Should & Provide Use of B43 or STA Driver jockey (Ubuntu) Medium Confirmed
504639 [regression] no wlan on s10e broadcom since update to kernel 2.6.31-17 linux (Ubuntu) Medium Triaged
414751 jockey-gtk crashed with signal 5 in _XError() when loading sta wirelless broadcom driver bcmwl-kernel-source is installed jockey (Ubuntu) Medium Incomplete
552300 Improve apt update error reporting jockey (Ubuntu) Medium Triaged
117729 [ndiswrapper] [broadcom] failure to connect to wpa network after kernel update wpasupplicant (Ubuntu) Low New
191408 Hardware drivers show ...