[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#697709: linux-image-3.2.0-4-amd64: pcspkr and snd-pcsp fighting

On Tue, 2013-01-08 at 13:23 -0600, Nathan Schulte wrote:
> Package: src:linux
> Version: 3.2.35-2
> Severity: minor
> Upon boot, with no ALSA present (package: alsa-base), the kernel outputs this harmless message:
> Error: Driver 'pcspkr' is already registered, aborting...
> This was detailed in bug 495674, and was addressed by a blacklisting of the snd-pcsp module in alsa-base.  That's all fine and suitable, but the following reply nailed the real issue:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495674&trim=no#55
> To quote: --
> There seems to be an assumption here that this issue should be
> resolved by a blacklist in alsa-base... but what about systems w/o
> alsa-base? Servers that have no use for sound are also reporting this
> potentially frightening (albeit benign) error message, but are
> unlikely to have the alsa-base package installed.
> It seems to me that snd-pcsp should be blacklisted on all systems by
> default.

I agree, and I think we have two options:

1. Blacklist in udev rather than alsa-base.  This is already done for
the framebuffer drivers in /etc/modprobe.d/fbdev-blacklist.conf, which
conflict with KMS and X drivers.

2. Remove the module alias from snd-pcsp.  This is already done for
certain obscure network protocols which would otherwise be loaded on
demand by any local user.

I prefer option 2, since option 1 would make it difficult to switch the
preferred driver in the linux package later.  Anyone have any other
opinions on this?


Ben Hutchings
All the simple programs have been written, and all the good names taken.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: