Bug 750830 - RFE: disable pcspeaker
Summary: RFE: disable pcspeaker
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 13:26 UTC by Kamil Páral
Modified: 2011-11-02 13:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-02 13:44:01 UTC
Type: ---


Attachments (Terms of Use)

Description Kamil Páral 2011-11-02 13:26:08 UTC
Description of problem:
In the third millennium the PC speaker sounds are nothing but loud annoying unwanted beeps. PC speaker is disabled by default in Fedora. But when I boot Anaconda installer and work in the console, I'm struck by loud beeps any time I hit TAB key, which is really really often. And all the time I have to unload its module just to be able to work. It drives me crazy. If you want to save my soul and spare me from running across the office with a hatchet and looking for blood, *please disable the pc speaker module*.

The module is called 'pcspkr' on my machine.

Thank you.

Version-Release number of selected component (if applicable):
Anaconda 16.24

How reproducible:
always

Steps to Reproduce:
1. switch to tty2
2. hit TAB a few times for command or path completion

Comment 1 Chris Lumens 2011-11-02 13:28:39 UTC
We're going to follow whatever the kernel does for stuff like this, as it's silly to make the anaconda environment even more different.  Reassigning.

Comment 2 Josh Boyer 2011-11-02 13:39:18 UTC
The kernel has a patch to remove the modalias for pcspkr so it isn't autoloaded.  Talked to Chris and it seems anaconda is explicitly loading it.  Reassigning again.

Comment 3 Chris Lumens 2011-11-02 13:44:01 UTC
Yes, why wouldn't we be always loading the pc speaker module?  Pushed.


Note You need to log in before you can comment on or make changes to this bug.