On 1/2/19 11:24 PM, haaber wrote:
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
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`.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1e89d919-72a7-8480-d03a-00c68337d319%40maa.bz.
For more options, visit https://groups.google.com/d/optout.
