Need an update-manager hook for bcmwl
Bug #381684 reported by
Mario Limonciello
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcmwl (Ubuntu) |
Invalid
|
Undecided
|
Tim Gardner | ||
update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
For users upgrading from Jaunty, there needs to be a query whether the 'wl' kernel module was in use. If it was, update-manager should mark bcmwl-kernel-source to be installed.
More ideally, it would be best if the whole Jockey hook was ran in case the blacklist file wasn't used in Jaunty but is now necessary with karmic. (Some adapters now load b43/ssb in karmic even though b43 doesn't support them yet)
Changed in bcmwl (Ubuntu): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
summary: |
- Need to produce a transitional binary package for LRM + Need an update-manager hook for bcmwl |
Changed in bcmwl (Ubuntu): | |
status: | New → Invalid |
description: | updated |
To post a comment you must log in.
Not everyone has a broadcom wireless card though. I feel that this transition should be handled by jockey instead. It should detect when restricted hardware is in use and let the user know their option of installing a restricted module. Right now that doesn't happen, and I had to install bcmwl-kernel-source manually.