prism2_usb both in staging and misc/wireless
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Jaunty |
Fix Released
|
Medium
|
Stefan Bader | ||
Bug Description
SRU justification:
Impact: Due to a build race there was a chance to get the prism2_usb driver from ubuntu or staging being built. Looking at some released packages the staging driver won the race most of the time.
Fix: Make sure only the staging driver will be built in future by removing the unwanted driver completely.
Testcase: check prism2_usb driver in the package.
---
We now have the staging tree in Jaunty kernels. (I was a little bit surprised, so any pointers to the plans, policies or discussion about this would be awesome). I discovered that my prism2_usb device now was picked up by the staging driver.
I guess it was not planned that we now are shipping two prism2_usb.ko modules, one in staging and another in misc/wireless. But the good news is that the staging module seems to perform better than the old:
- my wlan always come up at boot. Previously I often had USB problems if it was plugged in, and I would have to unplug and replug it once or many times.
- after heavy usage (dist-upgrades etc) it would previously often get stuck (like if it was overheated) but now it seems stable, from my testing so far. YMMV.
So maybe we can delete the old misc/wireless version, which was also a nightmare to have synced and maintained, at least from my experience dealing with the kernel team.
I don't know if you have tools to detect other driver conflicts with staging.
| Changed in linux: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in linux: | |
| assignee: | nobody → apw |
| status: | Triaged → In Progress |
| Andy Whitcroft (apw) wrote | #1 |
| Andy Whitcroft (apw) wrote | #2 |
| Changed in linux: | |
| status: | In Progress → Incomplete |
| Tormod Volden (tormodvolden) wrote | #3 |
| Andy Whitcroft (apw) wrote | #4 |
| Changed in linux: | |
| status: | Incomplete → Fix Released |
| Tormod Volden (tormodvolden) wrote | #5 |
| Stefan Bader (smb) wrote | #6 |
| Changed in linux (Ubuntu): | |
| assignee: | apw → stefan-bader-canonical |
| status: | Fix Released → In Progress |
| Changed in linux (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Tim Gardner (timg-tpi) wrote | #7 |
| Changed in linux (Ubuntu): | |
| assignee: | Stefan Bader (stefan-bader-canonical) → nobody |
| status: | Fix Committed → Fix Released |
| Changed in linux (Ubuntu Jaunty): | |
| assignee: | nobody → Stefan Bader (stefan-bader-canonical) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #9 |
| Changed in linux (Ubuntu Jaunty): | |
| status: | Fix Committed → Fix Released |
@Tormod -- we are not supposed to be enabling the Staging drivers wholesale:
debian/
debian/
And we are expecting to only be including these two drivers from staging at this time:
source "drivers/
source "drivers/
Cirtainly on my systems here I am only seeing one installed:
/lib/modules$ find 2.6.28-7-generic -name prism2_usb.ko
2.6.
/lib/modules$
Staging was picked up as a natural concequence of moving to 2.6.28, no particular policy decision was made to pick it up. As the staging area was seeded using the ubuntu drivers directory much of what we need is in there and is now being maintained so it makes sense for us to switch to the versions therein where possible. A fuller review is planned shortly.