[arch-general] howto properly disable sound device pulse/alsa?
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded. I've found that I have the following device: $ dmesg | grep Beep [ 10.594164] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input7 And that the following command will disable the beep: $ amixer -c0 set Beep 0% mute How should I go about making this persistent? I think avoiding that device would be best, can it be done by adding (or disabling) some udev config? Or, can I somehow make the 0% mute persistant in asound.conf? Thanks
Just enable the alsa daemon in rc.conf so that sound levels get reloaded on boot according to what they were at shutdown time. ^^
On 07/10/2011 08:50 PM, jesse jaara wrote:
Just enable the alsa daemon in rc.conf so that sound levels get reloaded on boot according to what they were at shutdown time. ^^
Yeah, I know about this, but is there a way to just put it in a config file without the alsa-utils package?
On 07/10/2011 07:44 PM, Matthew Monaco wrote:
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded.
Are you blacklisting this module through the old syntax in rc.conf? The configuration for blacklisting modules changed not too long ago (although not terribly recently, either, so sorry if you were already aware of this). http://www.archlinux.org/news/changes-to-module-blacklisting/
On 07/11/2011 12:30 AM, dmbuce@gmail.com wrote:
On 07/10/2011 07:44 PM, Matthew Monaco wrote:
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded.
Are you blacklisting this module through the old syntax in rc.conf? The configuration for blacklisting modules changed not too long ago (although not terribly recently, either, so sorry if you were already aware of this).
http://www.archlinux.org/news/changes-to-module-blacklisting/
I've been blacklisting it via "install pcspkr /bin/false" all along.
2011/7/11 Matthew Monaco <dgbaley27@verizon.net>
On 07/11/2011 12:30 AM, dmbuce@gmail.com wrote:
On 07/10/2011 07:44 PM, Matthew Monaco wrote:
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded.
Are you blacklisting this module through the old syntax in rc.conf? The configuration for blacklisting modules changed not too long ago (although not terribly recently, either, so sorry if you were already aware of this).
I've been blacklisting it via "install pcspkr /bin/false" all along.
Blacklisting won't work I think as this isint the classical/physical beeper speaker embended in the motherborad but instead a "virtual" one implemented in the sound card to produce the beep sound from the real speakers. So only way is to just mute it. -- (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.)
On 07/11/2011 07:50 AM, jesse jaara wrote:
2011/7/11 Matthew Monaco<dgbaley27@verizon.net>
On 07/11/2011 12:30 AM, dmbuce@gmail.com wrote:
On 07/10/2011 07:44 PM, Matthew Monaco wrote:
I think since Gnome 3 / pulseaudio, I've had an annoying system beep when shutting down. The pcspkr module is not loaded.
Are you blacklisting this module through the old syntax in rc.conf? The configuration for blacklisting modules changed not too long ago (although not terribly recently, either, so sorry if you were already aware of this).
I've been blacklisting it via "install pcspkr /bin/false" all along.
Blacklisting won't work I think as this isint the classical/physical beeper speaker embended in the motherborad but instead a "virtual" one implemented in the sound card to produce the beep sound from the real speakers. So only way is to just mute it.
So, like I was originally asking... I guess "amixer -c0 set Beep 0% mute" is ok in rc.local, but I'd prefer to not even have the device. $ udevadm info --query=all --path=/sys/devices/pci0000\:00/0000\:00\:1b.0/input/input7/ P: /devices/pci0000:00/0000:00:1b.0/input/input7 E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:00/0000:00:1b.0/input/input7 E: PRODUCT=1/111d/7605/1 E: NAME="HDA Digital PCBeep" E: PHYS="card0/codec#0/beep0" E: PROP=0 E: EV=40001 E: SND=6 E: MODALIAS=input:b0001v111Dp7605e0001-e0,12,kramls1,2,fw E: SUBSYSTEM=input I tried creating 00-custom.rules and 99-custom.rules in /etc/udev/rules.d SUBSYSTEM=="input" NAME=="HDA Digital PCBeep" OPTIONS+="ignore_device" I also tried = and == for OPTIONS. But the device is still showing up. Is there some Arch specific rule overriding this?
I tried creating 00-custom.rules and 99-custom.rules in /etc/udev/rules.d
SUBSYSTEM=="input" NAME=="HDA Digital PCBeep" OPTIONS+="ignore_device"
I also tried = and == for OPTIONS. But the device is still showing up. Is there some Arch specific rule overriding this?
You need to unset CONFIG_SND_HDA_INPUT_BEEP, in your kernel config and recompile the driver. Here's how it is in my kernel config file: # CONFIG_SND_HDA_INPUT_BEEP is not set -- дамјан
participants (4)
-
Damjan
-
dmbuce＠gmail.com
-
jesse jaara
-
Matthew Monaco