Beep not working in 10.10

[Mannex]

Binary package hint: beep

Beep worked in 10.04 on same machine, but now no sound. Running 'beep --verbose' returns "[DEBUG] 1 times 200 ms beeps (100 delay between, 0 delay after) @ 440.00 Hz" so it apparently thinks it's working fine. Alsa mixer has beep set to full volume and enabled.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: beep 1.2.2-24
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Nov 20 08:10:45 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: beep

[Diaa Sami (diaa.sami)]

I have the same problem here so I did some research and found the following:
It seems the pc speaker was intentionally disabled in Maverick(see bug #77010)
To get it back edit /etc/modprobe.d/blacklist.conf and comment the line
blacklist pcspkr

I tried it and now beep works again

[Mannex (russ-mannex)]

Already commented. No beep. Other sound seems to work. Thanks, though.

[Mannex (russ-mannex)]

By the way, modprobe reports the following package as installed in the kernel:

mannex@Leviathan:~$ modprobe -l | grep pcspkr
kernel/drivers/input/misc/pcspkr.ko

So, it appears to be loaded.

[Thomas Hood (jdthood)]

Merge with bug #486154?

[Mannex (russ-mannex)]

#486154 seems to imply that it is working in Lucid (or at least should
no longer be an issue). However, I am currently running 10.10 and it is
not working there. Did something in 10.10 undo a change that was made in
10.04?
--
Mannex

On Fri, 2011-04-08 at 12:38 +0000, Thomas Hood wrote:

> Merge with bug #486154?
>

[Mannex (russ-mannex)]

Broken in 11.04 as well, after a fresh install (not an upgrade).

[Rhonda D'Vine (rhonda)]

It's not beep that is not working here, it's the general environment that disabled pc speaker support completely - or claims that it should work through the soundcard now.

Please bring this up with the sound drivers you are using that they don't offer the pcspeaker through the sound system but on the other hand blacklisting the module. There is nothing that can be done from the beep package's point of view. People decided to disable the pcspeaker, and that is the facility that beep is using, so we are unfortunately at a dead end here.

Feel free to use this bugreport for attaching it to the corresponding packages that blacklist the pcspeaker and discuss it with the responsible people there, or bring it up as new bugreport there.

 Thanks,
Rhonda

[Mannex (russ-mannex)]

Thanks, Rhonda! You are right. I hadn't really thought about it like that. Which package should I file it under? How do I determine the sound drivers I'm using? I think I'm using ALSA, but I also have PulseAudio running, I think.