So, I got a new graphics card, mainboard and ram and could finally build a pc that WORKS with linux. The old workstation for somewhat reasons randomly locked up in X without any errors in the logs or anything. My best guess is faulty memory or faulty memory on the graphics card. ANYWAY, new pc, fresh good Lenny-installation.
Most stuff went smooth, but I can't seem to kill the pc-speaker at start. I can without problems do a modprobe -r pcspkr, and the pc-speaker shuts up untill I reboot. So I figured the best way to kill it for "good" inside linux is to blacklist it. But, that don't work. If I do, the pc-speaker will still make friggin annoying sounds in terminals and when gdm loads, but I won't be able to modprobe -r it. Untill I remove the blacklist and reboots and modprobes it.
Any good suggestions before I physically rip it out of my box?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Problems killing pcspkr for good.
- Telemachus
- Posts: 4574
- Joined: 2006-12-25 15:53
- Been thanked: 2 times
Try blacklist snd_pcsp and see this thread.
Remember to search the forum. That thread was the second hit searching pcspkr; your thread was first.
Remember to search the forum. That thread was the second hit searching pcspkr; your thread was first.
"We have not been faced with the need to satisfy someone else's requirements, and for this freedom we are grateful."
Dennis Ritchie and Ken Thompson, The UNIX Time-Sharing System
Dennis Ritchie and Ken Thompson, The UNIX Time-Sharing System
Create a file;
and as root save it as /etc/modprobe.d/00local
You will never hear the pc speaker again, even after dist-upgrades.
00local is never overwritten by upgrades or package installs and while adding a module to the blacklist might work, it often doesn't do what people expect because it's not supposed to be used to blacklist kernel modules. If you read /etc/modprobe.d/blacklist:
Code: Select all
#disable pcspkr
install pcspkr /bin/true
You will never hear the pc speaker again, even after dist-upgrades.
00local is never overwritten by upgrades or package installs and while adding a module to the blacklist might work, it often doesn't do what people expect because it's not supposed to be used to blacklist kernel modules. If you read /etc/modprobe.d/blacklist:
So create 00local and use that instead, it never fails and never changes.# This file lists modules which will not be loaded as the result of
# alias expansion, with the purpose of preventing the hotplug subsystem
# to load them. It does not affect autoloading of modules by the kernel.