You are not logged in.
Hello everyone,
I've installed Archlinux on my Dell XPS M1530 which previously ran only Ubuntu. I am still exploring the configuration files to tweak my system to my exact needs, but I can't seem to fully remove the system beep which is seriously getting on my nerves.
The beep occurs when I try to go too far on the sides of a line in Vi, when there are no more characters, or whenever I get any error. I also get a beep everytime the system halts.
I have blacklisted the modules pcspkr and snd_pcsp by editing rc.conf and changing the Modules line so that it looks like this:
MODULES(!pcspkr !snd_pcsp)
lsmod | grep pcsp returns nothing, so I know the modules are disabled, but I still get the beeps.
Would anyone have a clue about what could be causing this beep so that I can remove it?
Thanks in advance
Note: I do not have X installed yet
Offline
No real clue, but you could try to quiet vim by
:noerrorbells
either fom the command line or in your .vimrc
It should be off by default, however.
The system halt beep might be caused by the bios.
Last edited by bernarcher (2009-03-25 17:21:23)
To know or not to know ...
... the questions remain forever.
Offline
Mmm, yes, I suppose that could do the trick with vim, but the whole system is beeping. My shell beeps when I try the left arrow on an empty line, for example. What else than pcspkr and snd_pcsp could emit a system beep?
Edit: The halt beep is before the SIGTERM signal is sent, so it probably isn't the BIOS. Ubuntu doesn't make it beep either, so I think we can forget the BIOS beep possibility...
Last edited by Vincent91 (2009-03-25 17:23:14)
Offline
Does this discussion help?
http://bbs.archlinux.org/viewtopic.php?id=64290
To know or not to know ...
... the questions remain forever.
Offline
Well as I said, lsmod shows no pcspkr and/or snd_pcsp, so I take it they are not loaded. That is why I was asking what else than those two modules could cause a system beep. Also, I am not using the MOD_BLACKLIST, which is apparently deprecated, I am using the MODULES() line with ! to disable the modules, and it seems to work fine. Work fine disabling the modules, I mean, not disabling the beep.
Offline
@vincent91. run alsamixer and see if you have Pc Beep level. if you do hit m and then alsactl store
Give what you have. To someone, it may be better than you dare to think.
Offline
Rebooting to try, I will edit in a few minutes.
Edit: Should've known that I don't have alsamixer yet... I'll have to wait until I get home to install it because I haven't yet configured Arch to connect to my University's wifi network.
Is PC Beep really an option in alsamixer? I had never noticed it.
Last edited by Vincent91 (2009-03-25 17:50:57)
Offline
Another idea.
Put "set bell-style none" in your /etc/inputrc.
To know or not to know ...
... the questions remain forever.
Offline
Is PC Beep really an option in alsamixer? I had never noticed it.
i notice that have appeared after i switch to kernel 2.6.28
Give what you have. To someone, it may be better than you dare to think.
Offline
@bernarcher
Now that could probably fix the beep for vim and the shell, but for when I halt? The reason I want that beep off so bad is that it's really loud and I wouldn't want it to beep during class...
@wonder
Interesting. My Ubuntu installation runs 2.6.27-9, that might be why it doesn't beep. I suppose alsamixer will do the trick then, once I get the chance to install it.
Last edited by Vincent91 (2009-03-25 17:56:56)
Offline
Vincent91 wrote:Is PC Beep really an option in alsamixer? I had never noticed it.
i notice that have appeared after i switch to kernel 2.6.28
There is no such option here (asamixer v1.0.19). Could it depend on the pcskr module be present?
To know or not to know ...
... the questions remain forever.
Offline
Maybe it has something to do with the soundcard you use...
I haven't seen any posts describing my problem, it could be something limited to the soundcard provided with my Dell XPS.
Offline
Maybe it has something to do with the soundcard you use...
I haven't seen any posts describing my problem, it could be something limited to the soundcard provided with my Dell XPS.
i have dell inspiron 1525, hda intel card with chipset SigmaTel STAC9205. no pcspkr module or other module that might cause beeps
Last edited by wonder (2009-03-25 18:48:25)
Give what you have. To someone, it may be better than you dare to think.
Offline
I had exactly the same problem - Dell Precision M90
My solution was to put the following in /etc/rc.local
<code>
lsmod | grep -q '^pcspkr' && rmmod pcspkr
</code>
Offline
Is PC Beep really an option in alsamixer? I had never noticed it.
Depends on your sound card, I think. I don't have one called "PC Beep", but my PC speaker does come through the Aux channel.
Offline
there is built-in PC-Speaker in kernel (not a module) so you would have to hmm re-built kernel.
Enable PC-Speaker support (PCSPKR_PLATFORM)
# CONFIG_PCSPKR_PLATFORM is not set
which is enabled by default
This option allows to disable the internal PC-Speaker
sometimes there is an "mono" options in alsamixer available which allows killing system bell
and then you have also shell option
Last edited by broch (2009-03-26 01:47:42)
Offline
Another way to kill the beep is to use 'setterm -blength 0' somewhere to stop it in the console, and 'xset -b off' in your .xinitrc or whatnot to stop it in X.
Offline
I can disable it through alsamixer, but it is only temporary. Alsamixer is reset upon system restart, so I have to turn it off again.
How can I make the changes to alsamixer permanent?
Offline
@vincent91 i already told you
alsactl store
or add alsa to daemon list
Give what you have. To someone, it may be better than you dare to think.
Offline
I can disable it through alsamixer, but it is only temporary. Alsamixer is reset upon system restart, so I have to turn it off again.
How can I make the changes to alsamixer permanent?
Best add alsa to the DAEMONS list. This will cause the mixer settings be stored on shutdown and reloaded on (re)start.
Last edited by bernarcher (2009-03-26 22:40:52)
To know or not to know ...
... the questions remain forever.
Offline