No System Beep on Dell inspiron 1420
I dual boot slackware 12.2 and Ubuntu 8.10 on my laptop. I don't have a default system beep on
my computer, which can be annoying at times. Sometimes, after doing a pm-suspend in Ubuntu, the system beep will work for a little while when I am on the console. Any help would be great! |
There is a package in ubuntu you can install called
Code:
beep Code:
sudo apt-get install beep Code:
.TH BEEP 1 "November 2006" |
look in
/etc/modprobe.d/blacklist to see if the pc speaker isn't blacklisted depending on the terminal, look in the conf for xset b off or set bell-style none make sure if you use gnome: Applications > Accessories > Terminal beep is enabled. |
First off, thanks for the replys!
I installed the "beep" program in Ubuntu, but that still did not produce any sound. I also checked the blacklist file, and the pc speaker isn't listed anywhere. Also, system bell is checked on in the gnome-terminal in Ubuntu. I also didn't see any of those other things that turn of the pc speaker in the conf files... Can alsamixer control the pc speaker? Could I have it muted/turned off somewhere else? Thanks for your help, Glen |
is the speaker connected ?
|
I think it has to be, as it does work sometimes after a pm-suspend. I've only noticed that
on Ubuntu. Is there any other way that the internal speaker gets turned on, that possibly pm-suspend is doing? |
It looks like this is the exact same problem I am having:
http://fixunix.com/debian/536822-bug...kr-loaded.html From what I can tell, Slackware 12.2 is not using alsa-driver-1.0.18, so does anybody know if there is a fix? I'll check to see if there is a way to upgrade to the newest version. If anybody has any tips that would be great too. |
hello,
after going through my logs after doing a pm-suspend on Ubuntu, I noticed that the beep stops working when I change the sound levels in alsamixer. The message sent at this time is: Code:
May 4 18:24:28 gordan-the-pig kernel: [ 650.692145] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x00cf1c00 |
polling mode means it won't sit waiting for ever, but will poll the device periodically to see if it has 'recovered'. I'd say your speaker is fried, but that is not an expert opinion by any means. YMMV.
|
hi
me thinks its the pcspkr module he wants...to use the case speaker? Code:
su eg /sbin/modprobe pcspkr |
Thank you all for the help, but I seemed to find a hack sufficient enough for my means. I found a solution which is mentioned in this thread: http://www.linuxquestions.org/questi...d-card-723900/
None of the scripts that came with it worked, but after searching around, I finally found one that worked well enough. The script was called "playbeepd", but as I do not recall the website or the author, I will not post the code. If anybody is interested, send me a message and I can send it to you. Thanks once again for the help. I have learned quite a bit about how the modules work from it. |
Looks like a hardware issue to me my friend ... Contacting your Vendor/Nearest Service Center should be first on your priority list !
Debian |
glad you got sorted, if you've anyway of explaining what you did to solve the problem, make and model of computer, speaker etc., please do post it, you may help someone else down the line!
|
So here is a summary of what I did:
1. Realized that there was no kernel module setting that was getting in my way. That is, the pcspkr module was loaded and not blacklisted. You can find this stuff in /etc/modules.d or similar. 2. Confirmed that the internal speaker did work, that is, it was plugged in, and was in fact able to make noise, although only loudly, and under very special circumstances. 3. Having given up on getting my internal pc speaker to work (it still would be nice if I could get it to), I looked into diverting the beep signals that get sent to pcspkr to go play a sound through my sound card/normal speakers/whatever the proper terminology is, instead. 4. There are a few packages out there, although not all seemed to work for me. There is softbeep found here: http://0pointer.de/lennart/projects/softbeep/ , which did not cut it for me on Slackware 12.2 or Ubuntu 8.10. Also those links to the package don't work, and you might need to do some more searching. They are in the Ubuntu repositories at least, and no compiling is necessary. 5. Since softbeep didn't work, I looked furter and eventually found the Fancy Beeper Daemon which created a new device at /dev/beep that can capture the beep signals and execute a command to play a .wav via a number of ways. You can find the package here: http://www.carcosa.net/jason/software/beep/ . 6. This program compiled fine in Ubuntu 8.10, but I needed to download the kernel source to get it to compile in Slackware 12.2. I found that rather confusing, as the error I got seemed to mean that I didn't have the kernel header files, which I did. I guess there was a terminology problem somewhere. Anyway, that should indeed compile with the provided install script. 7. For me, none of the provided daemons worked. I searched around and found the following one from http://www.shallowsky.com/blog/linux/custom-beep.html . I don't want to reproduce the code here, solong as the link still works. 8. To finish it all up, I added a file to /etc/rc.d to get everything to run at boot. I called it rc.beep and it contains: Code:
#!/bin/bash can alternatively give the correct sound file as an argument. I sadly do not know enough about programming to figure out how to make a real daemon, but this seemed to work well enough. 9. After a pm-suspend, the script got killed for some reason, so, making the daemon still needs to be perfected. 10. Does anybody know how to make slackware handle more than one sound being sent to the audio device? Can it pause the one playing to play a new sound? That is about the last thing on my list of issues. I hope this helps! |
All times are GMT -5. The time now is 06:58 PM. |