dom0 bell

[haaber]

Hi, I never understood the purpose of the loudspeaker bell in linux, but
on my machine, it is particularly loud and annoying. Is there a
reasonable way to deactivate it forever? Thank you (and a happy new
year), Bernhard

[unman]

Try these:
As root rmmod pcspkr, should stop it in running machine.
Edit /etc/modprobe.d/blacklist, and insert a line:
blacklist pcspkr
If that doesnt work, put the rmmod command in a startup script.

The ultimate sanction is to unplug the leads to the internal speaker
from motherboard.

[haaber]

On 12/31/18 11:17 AM, unman wrote:
> On Sun, Dec 30, 2018 at 10:32:16PM +0100, haaber wrote:
>> Hi, I never understood the purpose of the loudspeaker bell in linux, but on
>> my machine, it is particularly loud and annoying. Is there a reasonable way
>> to deactivate it forever? Thank you (and a happy new year), Bernhard
>
> Try these:
> As root rmmod pcspkr, should stop it in running machine.
> Edit /etc/modprobe.d/blacklist, and insert a line:
> blacklist pcspkr

That helps in dom0 terminal, but neither on dom0 login screen nor dom0
xterm. Funny.

> If that doesnt work, put the rmmod command in a startup script.

I'd love to place it in /etc/rc.local -- but there is none! Can I create
it?? Can I blacklist it somewhere else on boot (grub??)

> The ultimate sanction is to unplug the leads to the internal speaker
> from motherboard.

Yes. That would be a joyful step, too. I am afraid if I have to cut the
red or the blue cable first, to avoid detonantion :)) Let us try
startup scripts first ... Bernhard

[unman]

Can you check with lsmod to see if pcspkr is being loaded?

[haaber]

>>>
>>> Try these:
>>> As root rmmod pcspkr, should stop it in running machine.
>>> Edit /etc/modprobe.d/blacklist, and insert a line:
>>> blacklist pcspkr
>> That helps in dom0 terminal, but neither on dom0 login screen nor dom0
>> xterm. Funny.
>>
>>> If that doesnt work, put the rmmod command in a startup script.
>> I'd love to place it in /etc/rc.local -- but there is none! Can I create
>> it?? Can I blacklist it somewhere else on boot (grub??)
>>
>>> The ultimate sanction is to unplug the leads to the internal speaker
>>> from motherboard.
>> Yes. That would be a joyful step, too. I am afraid if I have to cut the red
>> or the blue cable first, to avoid detonantion :)) Let us try startup
>> scripts first ... Bernhard
>
> Can you check with lsmod to see if pcspkr is being loaded?
>

Yes, despite /etc/modprobe.d/blacklist it is being loaded. I remove it
manually with rmmod in the momemt but that is odd. This is why I earch
where to put a line in some init script .. Bernhard

[unman]

Try changing that line to:
install pcspkr true

[Ivan Mitev]

Not sure if you managed to blacklist the pcspkr module ; if not you
could try to mute the beep: in dom0, run alsamixer (you may have several
cards, for instance I have to run `alsamixer -c1` because the first card
is my hdmi port). There should be a "beep" column - navigate to it and
press "M" to toggle mute.

If that works, the mixer settings should be saved automatically on
shutdown by the alsa-state systemd service but you can store the
settings manually with `sudo alsactl store`.

[haaber]

> Not sure if you managed to blacklist the pcspkr module ; if not you
> could try to mute the beep: in dom0, run alsamixer (you may have several
> cards, for instance I have to run `alsamixer -c1` because the first card
> is my hdmi port). There should be a "beep" column - navigate to it and
> press "M" to toggle mute.
>
> If that works, the mixer settings should be saved automatically on
> shutdown by the alsa-state systemd service but you can store the
> settings manually with `sudo alsactl store`.
>

That seems a great solution, thank you!! Bernhard