snd_pcsp: To blacklist or not to blacklist?
Bug #276067 reported by
Björn Torkelsson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center |
Invalid
|
Medium
|
|||
compiz (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
gnome-control-center (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
module-init-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When snd_pcsp was introduced, there were some problems reported with it, including:
Bug 242966 (snd_pcsp getting selected as the primary sound card)
Bug 246969 (login failure in VMware)
Random bugs about people getting crackling through their speaker unexpectedly
The module was first forced to a non-default index in alsa-base, then blacklisted entirely in module-init-tools.
Now, it's been pointed out that this breaks the system bell functionality in compiz.
Should the module be blacklisted or not?
Changed in gnome-control-center: | |
status: | Unknown → New |
description: | updated |
Changed in gnome-control-center: | |
importance: | Unknown → Medium |
Changed in gnome-control-center: | |
status: | New → Invalid |
To post a comment you must log in.
This might be a trade-off against *all* audio being routed through the PC speaker. See https:/ /tango. 0pointer. de/pipermail/ pulseaudio- discuss/ 2008-September/ 002371. html - Luke, do you have any further comments here?
We do seem to build in pcspkr, judging from /boot/config- 2.6.27- 4-generic.