Please see this bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123927
Essentially, the PC speaker has been disabled long time ago and it does not work by default on Fedora. Some applications actually require the PC speaker in order to provide full functionality - like X-Chat beeping on certain messages. There is a fairly simple workaround, just run this command once: "/sbin/modprobe pcspkr" then add the same command to the end of /etc/rc.d/rc.local to make the change permanent across reboots.
However, it needs to get a real solution, not just a workaround. If you feel the same, please add your comments to the bug report mentioned above.
On Wed, 2005-03-09 at 11:49 -0800, Florin Andrei wrote:
There is a fairly simple workaround, just run this command once: "/sbin/modprobe pcspkr" then add the same command to the end of /etc/rc.d/rc.local to make the change permanent across reboots.
Actually, if you know for a fact that you don't have an /etc/rc.modules and nothing ever will create that file on your system, it's probably better to do this:
echo #!/bin/sh > /etc/rc.modules echo "/sbin/modprobe pcspkr" >> /etc/rc.modules chmod +x /etc/rc.modules
rc.modules, if exists, is called by rc.sysinit It seems like a better idea to load up the module early in the boot chain.
On Wed, 9 Mar 2005, Florin Andrei wrote:
On Wed, 2005-03-09 at 11:49 -0800, Florin Andrei wrote:
There is a fairly simple workaround, just run this command once: "/sbin/modprobe pcspkr" then add the same command to the end of /etc/rc.d/rc.local to make the change permanent across reboots.
Actually, if you know for a fact that you don't have an /etc/rc.modules and nothing ever will create that file on your system, it's probably better to do this:
echo #!/bin/sh > /etc/rc.modules echo "/sbin/modprobe pcspkr" >> /etc/rc.modules chmod +x /etc/rc.modules
rc.modules, if exists, is called by rc.sysinit It seems like a better idea to load up the module early in the boot chain.
Actually, if /etc/rc.modules does exist, just add the modprobe command to it. Also, if any package replaces an existing /etc/rc.modules instead of appending lines to it, that package is broken.
On Wed, 2005-03-09 at 15:48 -0500, Matthew Saltzman wrote:
Actually, if /etc/rc.modules does exist, just add the modprobe command to it. Also, if any package replaces an existing /etc/rc.modules instead of appending lines to it, that package is broken.
If that's the case, then probably it would be better if Fedora would deploy an empty rc.modules, containing only "#!/bin/sh" and let the packages echo "" >> to it. Or create a directory instead, allow packages to put files in it, and let rc.sysinit source'em up. This is probably the cleanest way.
On Wed, 9 Mar 2005, Florin Andrei wrote:
On Wed, 2005-03-09 at 15:48 -0500, Matthew Saltzman wrote:
Actually, if /etc/rc.modules does exist, just add the modprobe command to it. Also, if any package replaces an existing /etc/rc.modules instead of appending lines to it, that package is broken.
If that's the case, then probably it would be better if Fedora would deploy an empty rc.modules, containing only "#!/bin/sh" and let the packages echo "" >> to it. Or create a directory instead, allow packages to put files in it, and let rc.sysinit source'em up. This is probably the cleanest way.
That seems reasonable to me. But I don't think there are any FC packages that use it. The ipw2200 and slmodem modules would be candidates, but they aren't in FC.
On Wed, 09 Mar 2005 11:49:24 -0800, Florin Andrei florin@andrei.myip.org wrote:
Please see this bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123927
Essentially, the PC speaker has been disabled long time ago and it does not work by default on Fedora. Some applications actually require the PC speaker in order to provide full functionality - like X-Chat beeping on certain messages. There is a fairly simple workaround, just run this command once: "/sbin/modprobe pcspkr" then add the same command to the end of /etc/rc.d/rc.local to make the change permanent across reboots.
However, it needs to get a real solution, not just a workaround. If you feel the same, please add your comments to the bug report mentioned above.
-- Florin Andrei
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
And I'm glad that it is! I always hated those stupud beeps. But I didn't really notice it's absence in FC3, maybe because I cut the wire to the PC speaker about four operating systems ago...
Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com
On Wed, 2005-03-09 at 23:45 +0200, Dotan Cohen wrote:
On Wed, 09 Mar 2005 11:49:24 -0800, Florin Andrei florin@andrei.myip.org wrote:
And I'm glad that it is! I always hated those stupud beeps. But I didn't really notice it's absence in FC3, maybe because I cut the wire to the PC speaker about four operating systems ago...
No need to cut any wires. Assuming the module works properly and it's loaded automatically, it's trivial to disable the speaker: either mute it with alsamixer, or do this:
echo "install pcspkr /bin/true" >> /etc/modprobe.conf
The PC speaker is a traditional feed-back mechanism, it's probably better to not disable it unless there's a good reason to.
On Wed, 09 Mar 2005 14:23:14 -0800, Florin Andrei florin@andrei.myip.org wrote:
On Wed, 2005-03-09 at 23:45 +0200, Dotan Cohen wrote:
On Wed, 09 Mar 2005 11:49:24 -0800, Florin Andrei florin@andrei.myip.org wrote:
And I'm glad that it is! I always hated those stupud beeps. But I didn't really notice it's absence in FC3, maybe because I cut the wire to the PC speaker about four operating systems ago...
No need to cut any wires. Assuming the module works properly and it's loaded automatically, it's trivial to disable the speaker: either mute it with alsamixer, or do this:
echo "install pcspkr /bin/true" >> /etc/modprobe.conf
The PC speaker is a traditional feed-back mechanism, it's probably better to not disable it unless there's a good reason to.
-- Florin Andrei
No 'good reason' other than that I hate it. It startles me. And I found that I swicth operating systems about once a year, so why even bother with it? The only time I want to hear sound on my computer is when I: 1) listen to music, 2) watch a movie, 3) talk on skype. I especially hate webpages with embedded music in them, or flash / shockwave files on websites that make noise. I haven't found a way to tell firefox DONT ever make noise, EVEN when flash tells you to do sol.
Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com