How to disable the pc speaker (beep!) - Revision history

Aiju at 19:26, 23 January 2011

2011-01-23T19:26:46Z

Iosonofabio: /* Remove the pc speaker modules "pcspkr" and "snd_pcsp" */

2008-11-12T08:45:27Z

‎Remove the pc speaker modules "pcspkr" and "snd_pcsp"

JamMule: There are now two kernel modules, which allow the computer to shatter your eardrums.

2008-09-04T13:14:47Z

There are now two kernel modules, which allow the computer to shatter your eardrums.

RichardNeill: Liking the system beep

2008-08-05T23:39:14Z

Liking the system beep

Ændrük at 11:35, 27 April 2008

2008-04-27T11:35:53Z

Mrunge: inputrc and beeps

2007-03-03T14:08:52Z

inputrc and beeps

Helge: /* Re-enabling the pc speaker */

2007-03-02T11:46:24Z

‎Re-enabling the pc speaker

Helge: How to re-enable it

2007-03-02T11:45:49Z

How to re-enable it

Helge at 11:24, 2 March 2007

2007-03-02T11:24:04Z

New page

Get rid of the annoying beeps in Linux (Xubuntu 6.10 Edgy Eft): Remove the pc speaker module.

Open a terminal and issue this command as root:
rmmod pcspkr

To prevent the pcspkr module from loading again at startup, open /etc/modprobe.d/blacklist with your favorite text editor (as root) and add following lines to the end of the file:
# disable the **** pc speaker
blacklist pcspkr

← Older revision		Revision as of 19:26, 23 January 2011
Line 51:		Line 51:


−	== ~~Learning~~ to ~~love~~ the ~~beeps~~ ==	+	== Dr. Thinkpad; Or: How I Learned to Stop Worrying and Love the Beep ==

	Actually, these beeps are quite useful sometimes (especially with shell-scripts that want to get your attention with echo -e "\a" ).		Actually, these beeps are quite useful sometimes (especially with shell-scripts that want to get your attention with echo -e "\a" ).

← Older revision		Revision as of 08:45, 12 November 2008
Line 17:		Line 17:

	If this does not feel comfortable, you can also edit the aforementioned file with your favorite text editor and add the blacklist lines yourself.		If this does not feel comfortable, you can also edit the aforementioned file with your favorite text editor and add the blacklist lines yourself.
		+
		+
		+	== New kernels: remove via !<module> ==
		+	In the new linux kernels, the use of file {{path\|/etc/modprobe.d/blacklist}} is is deprecated. The correct solution is to put a ! in front ov every module you want to blacklist. For instance, in ArchLinux you just have to modify your {{path\|/etc/rc.conf}} according to the following:
		+
		+	MODULES=(!pcspkr !snd_pcsp <other modules>)
		+

	=== Re-enabling the pc speaker ===		=== Re-enabling the pc speaker ===

@@ Line 1: / Line 1: @@
 Get rid of the annoying beeps in Linux
-== Remove the pc speaker module "pcspkr" ==
+== Remove the pc speaker modules "pcspkr" and "snd_pcsp" ==
 Open a terminal and issue this command as root:
-To prevent the "pcspkr" module from loading again at startup, open /etc/modprobe.d/blacklist with your favorite text editor (as root) and add following lines to the end of the file:
+{{cmdroot|modprobe -r pcspkr snd_pcsp}}
- # disable the **** pc speaker
- blacklist pcspkr
+To prevent the "pcspkr" and "snd_pcsp" modules from loading again at startup add them to modprobe's blacklist in {{path|/etc/modprobe.d/blacklist}}.  You can do this with the following command:
 === Re-enabling the pc speaker ===
-Temporarily activate it by loading the module (run this from a terminal with root privileges):
+The speaker can be temporarily activated by loading either of the modules:
- modprobe pcspkr
-If you don't want to prevent the module from loading during startup, delete the lines from /etc/modprobe.d/blacklist described in the previous section.
+If you do not want to prevent the modules from loading during startup, delete the two blacklist lines mentioned in the previous section from {{path|/etc/modprobe.d/blacklist}}.
 == Disable console beeps in /etc/inputrc ==

← Older revision		Revision as of 23:39, 5 August 2008
Line 29:		Line 29:
	Or if it's just the terminal tab auto-completion that's bothering you, uncheck:		Or if it's just the terminal tab auto-completion that's bothering you, uncheck:
	: Terminal > Edit > Current Profile > Terminal bell		: Terminal > Edit > Current Profile > Terminal bell
		+
		+
		+	== Learning to love the beeps ==
		+
		+	Actually, these beeps are quite useful sometimes (especially with shell-scripts that want to get your attention with echo -e "\a" ).
		+	The reason people tend to hate them are because they get overused.
		+
		+	1. Make bash tab-completion less beepy, by editing ''/etc/inputrc'' (or ''~/.inputrc''). Add:
		+
		+	# Show all if ambigious.
		+	set show-all-if-ambiguous on
		+
		+	This makes tab-completion more useful, as well as less irritating: we now only get a beep on a true error (no possible completions); if multiple options are possible, all are printed, and it doesn't beep.
		+
		+
		+	2. Make the beep quieter, shorter, and a nicer pitch. I tend to set 440 Hz, 50ms. Configure with kcontrol (in KDE), or just use xset in your startup files:
		+	xset b 50 440 50

@@ Line 1: / Line 1: @@
-Get rid of the annoying beeps in Linux (Xubuntu 6.10 Edgy Eft): Remove the pc speaker module "pcspkr".
+Get rid of the annoying beeps in Linux
 Open a terminal and issue this command as root:
@@ Line 7: / Line 9: @@
   # disable the **** pc speaker
   blacklist pcspkr
 Another solution is to disable console beeps in /etc/inputrc (change with your favourite editor, should work on all distributions)
@@ Line 12: / Line 22: @@
   set bell-style none
-==Re-enabling the pc speaker==
+== Disable the system beep in Gnome ==
-Temporarily activate it by loading the module (run this from a terminal with root privileges):
- modprobe pcspkr
+In Ubuntu 7.10 and later, uncheck:
-If you don't want to prevent the module from loading during startup, delete the lines from /etc/modprobe.d/blacklist described in the previous section.
+Or if it's just the terminal tab auto-completion that's bothering you, uncheck:

← Older revision		Revision as of 11:46, 2 March 2007
Line 12:		Line 12:
	modprobe pcspkr		modprobe pcspkr

−	If you don't want to prevent the module from loading during startup, delete the lines ~~described in the previous section~~ from /etc/modprobe.d/blacklist.	+	If you don't want to prevent the module from loading during startup, delete the lines from /etc/modprobe.d/blacklist described in the previous section.