User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc12 Firefox/3.5.5 Run as root /usr/bin/beep -f 1000 -n -f 2000 -n -f 1500 must beep. It was in FC10. However it is not beeping in FC12. Please help. Thanks Reproducible: Always Steps to Reproduce: 1.su - 2.password 3.cd /usr/bin 4. beep -f 1000 -n -f 2000 -n -f 1500 Actual Results: No sound Expected Results: Few beeps. It was beeping in Fedora 10 on the same computer. Just updated to FC12 - no beeping any more. Please help.
Off my head (and without running F-12 yet), I can imagine two potential spots of problems: 1. The sound mixer being set up to mute the system beep. 2. The pcspkr.ko kernel module not being loaded. Could you check those, please?
Dear Hans, Thank you very much for for your reply. Running as root: modprobe -v pcspkr fixed the problem. How to make sure pcspkr.ko kernel module is loaded each time at reboot? Thanks again, Andrew
I do not know the preferred way to always load pcspkr.ko on F-12. As a quick and dirty hack, you could add that modprobe command to rc.local. However, if you turn up the preferred way to do that on F-12, let me know. I'd like to add a README.fedora file to the beep package which contains the proper instructions.
This is exactly what i did too. Just added line modprobe -v pcspkr to /etc/rc.d/rc.local. What is confusing why kernel is not loading it automatically. If I do cd /lib/modules/2.6.31.6-134.fc12.x86_64 grep pcspkr * I see the output: modules.alias:alias platform:pcspkr snd_pcsp modules.dep:kernel/drivers/input/misc/pcspkr.ko: Binary file modules.dep.bin matches modules.order:kernel/drivers/input/misc/pcspkr.ko Can it be that the alias snd_pcsp preventing it to load. Since cat /etc/modprobe.d/blacklist.conf shows the line # sound drivers blacklist snd-pcsp I am not sure ..... Thanks again, Andrew
snd-pcsp aka snd_pcsp is an ALSA driver emulating a real PCM wave sound device on a PC speaker. You really very rarely want to actually do that, so blacklisting snd-pcsp by default makes sense. On my F11 system, /lib/modules/`uname -r`/modules.alias yields alias platform:pcspkr pcspkr alias platform:pcspkr snd_pcsp while your grep only shows an alias to snd_pcsp. That might be the relevant change. Possibly doing a echo "alias platform:pcspkr pcspkr" > /etc/modprobe.d/pcspkr.conf will make pcspkr.ko load on system startup by default without needing modprobe invocations in /etc/rc.d/rc.local. I will be checking this on an actual F12 system shortly.
I want to try your suggestion but before doing that I need to understand how this aliasing works. alias platform:pcspkr pcspkr alias platform:pcspkr snd_pcsp It seems to me that the second line overrides the first one anyway. Therefore effectively in your file only second alias is relevant. Is this true?
Looks like on F11, with the two lines in /lib/modules/`uname -r`/modules.alias alias platform:pcspkr pcspkr alias platform:pcspkr snd_pcsp and one line in /etc/modprobe.d/blacklist.conf blacklist snd-pcsp the only module effectively being in charge of platform:pcspkr is pcspkr on this F11 system. If on F12, there is one line in /lib/modules/`uname -r`/modules.alias alias platform:pcspkr snd_pcsp and one line in /etc/modprobe.d/blacklist.conf blacklist snd-pcsp then I would assume that adding a /etc/modprobe.d/pcspkr.conf with this single line alias platform:pcspkr pcspkr would lead to the same effective settings.
I just tried /etc/modprobe.d/pcspkr.conf proposal. Unfortunately beep does not work. Please let me know if it will work for you on FC12. I will stick with rc.local solution for now.
I have just tried booting F12 with a new file /etc/modprobe.d/beep.conf containing alias platform:pcspkr pcspkr This leads to the pcspkr kernel module being loaded by default on boot - just as intended. However, apparently there is something else getting in the way. My current guess is ConsoleKit, as beep works via opening /dev/console, and it started working after switching back and forth from/to X11 and the KMS console. Long story short: Even with the module loading sorted out without any ugly hacks, this still needs even more research. :-/
Hans, Thanks for the posting. In my comment #8 I did not check if module is loaded or not - apologies. I checked the beep instead, running it from (Application->System Tools->)Terminal. It did not work from the Terminal. I am not sure I understood about ConsoleKit .... . However, absolutely, I do agree that something else is going on. I know that because even with the modules loaded on my Toshiba Laptop - beep is not working. I am not sure if it is related or not - however equally annoying. Beep is a integral basic functionality of any computer and in my opinion should 'just work' out of the box. Hopefully enough people would agree with this to fix it back as it was pre FC12. Please keep posting any other observation wich can help to fix it. Thanks. Andrew
beep-1.2.2-6.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/beep-1.2.2-6.fc12
Andrew, FYI: beep-1.2.2-6.fc12 just adds a /etc/modprobe.d/beep.conf file which is commented out by default and a README.fedora file which explains the issue. No actual functionality has changed. BTW, thank you for reporting this and for faithfully helping test.
Thanks.
beep-1.2.2-6.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update beep'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0973
beep-1.3-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/beep-1.3-1.fc12
beep-1.3-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/beep-1.3-1.fc13
beep-1.3-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update beep'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/beep-1.3-1.fc13
beep-1.3-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update beep'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/beep-1.3-1.fc12
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
beep-1.3-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.