| Author |
Message |
keekdown
|
|
Post subject: beep
Posted: 11.12.2011, 12:50
|
|

Joined: 2011-07-28
Posts: 17
Location: Russia
Status: Offline
|
|
| How off beep?After every reboot it appears again? |
|
|
| |
|
|
|
 |
dibl
|
|
Post subject: RE: beep
Posted: 11.12.2011, 12:56
|
|

Joined: 2010-09-12
Posts: 302
Location: Dayton, Ohio, USA
Status: Offline
|
|
| Probably that is a setting in your BIOS. In KDE, you have systemsettings > applications and system notifications > system bell, but that is after you log in. |
|
|
| |
|
|
|
 |
keekdown
|
|
Post subject: RE: beep
Posted: 11.12.2011, 13:08
|
|

Joined: 2011-07-28
Posts: 17
Location: Russia
Status: Offline
|
|
|
|
|
 |
michaaa62
|
|
Post subject: RE: beep
Posted: 11.12.2011, 13:28
|
|

Joined: 2010-09-11
Posts: 51
Location: Berlin, Germany
Status: Offline
|
|
| Blacklist the pcspkr module by adding this line
Quote:
blacklist pcspkr
to a file /etc/modprobe.d/blacklist_pcspkr.conf, which you have to create yourself. |
|
|
| |
|
|
|
 |
DonKult
|
|
Post subject: RE: beep
Posted: 11.12.2011, 13:38
|
|
Team Member

Joined: 2010-09-02
Posts: 416
Status: Offline
|
|
In alsamixer, i have a "beep" volume control, maybe you, too. Switching it to mute really "mutes" it - and it keeps this way also after a reboot. The only problem i have found with this a suspend to ram. For some strange reason this little fellow is activated again, but a disable/enable-sound-cycle fixes that (I hadn't the energy to search for a fix/bugreport for it so far…)
Alternatively, 'pcspkr' is the responsible module. Try 'modprobe -r pcspkr'. If it works you can e.g. blacklist it… |
_________________ MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
 |
keekdown
|
|
Post subject: RE: beep
Posted: 11.12.2011, 14:13
|
|

Joined: 2011-07-28
Posts: 17
Location: Russia
Status: Offline
|
|
|
|
|
 |
|
|