Independently pcspkr works fine for the PC speaker, and snd_hda_intel for the internal speakers, however the two modules don't work together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
It's a problem in FC13; not sure about older releases or FC14.
How to best approach resolving this?
Perhaps some insight into where HDA might be hijacking the PC speaker would be helpful.
Thanks!
Perhaps some insight into where HDA might be hijacking the PC speaker would be helpful.
Thanks!
Independently pcspkr works fine for the PC speaker, and snd_hda_intel for the internal speakers, however the two modules don't work together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
It's a problem in FC13; not sure about older releases or FC14.
How to best approach resolving this?
On Fri, 2011-04-15 at 05:32 -0700, updog wrote:
Independently pcspkr works fine for the PC speaker, and snd_hda_intel for the internal speakers, however the two modules don't work together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
Is it one of those cases where the motherboard beeper is, now, emulated? Putting a beep sound effect through the sound card, and you need to have an appropriate volume control turned up on the mixer?
I prefer terminals using the actual beeper, because that can always beep, but I mayn't have speakers running all the time.
updog wrote:
Independently pcspkr works fine for the PC speaker, and snd_hda_intel for the internal speakers, however the two modules don't work together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
It's a problem in FC13; not sure about older releases or FC14.
What happens if you switch to a text-mode terminal (Ctrl-Alt-F2, or reboot in init level 3) and get the terminal to beep?
Are you sure that the terminal you usually use isn’t trying to use modern sound hardware if it’s available (so we can have MP3 ringtone beeps instead of 1970s beeps)?
*Which* terminal, anyway? There are at least seven I can think of.
Hope this helps,
James (who turns all the beeps off).
On 04/15/2011 10:31 AM, James Wilkinson wrote:
updog wrote:
Independently pcspkr works fine for the PC speaker, and snd_hda_intel for the internal speakers, however the two modules don't work together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
It's a problem in FC13; not sure about older releases or FC14.
What happens if you switch to a text-mode terminal (Ctrl-Alt-F2, or reboot in init level 3) and get the terminal to beep?
Are you sure that the terminal you usually use isn’t trying to use modern sound hardware if it’s available (so we can have MP3 ringtone beeps instead of 1970s beeps)?
*Which* terminal, anyway? There are at least seven I can think of.
Hope this helps,
James (who turns all the beeps off).
Hmm... I'm curious: How many terminals does fedora release provide besides emacs terminal and gnome terminal (on my F14 installation).
James Wilkinson wrote:
together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
"Terminal beep" also includes audible notifications from programs such as nedit and mozilla, e.g. search term not found. Affected terminals are xterm and the console; I haven't experimented with others. What I'm looking for is the sound issued by that piezoelectric thing half the population hates- I don't want it from HDA (which doesn't seem to work either, but I'm ok with that part).
Are you sure that the terminal you usually use isn’t trying to use modern sound hardware if it’s available (so we can have MP3 ringtone beeps instead of 1970s beeps)?
*Which* terminal, anyway? There are at least seven I can think of.
It's not exclusively a terminal thing (noted above), although that's what it's historically associated with. Sorry for the ambiguity.
James (who turns all the beeps off).
Anyway, the trouble is this: the beeps work as expected until snd-hda-intel is loaded. Then they're irrevocably gone, recoverable only by a reboot. I've tried mixers and beep_mode adjustments to no avail.
Milhaus (who turns all beeps on).
On 04/15/2011 03:53 PM, updog wrote:
James Wilkinson wrote:
together. Loading snd_hda_intel after pcspkr is in and working causes loss of the terminal beep.
"Terminal beep" also includes audible notifications from programs such as nedit and mozilla, e.g. search term not found. Affected terminals are xterm and the console; I haven't experimented with others. What I'm looking for is the sound issued by that piezoelectric thing half the population hates- I don't want it from HDA (which doesn't seem to work either, but I'm ok with that part).
Are you sure that the terminal you usually use isn’t trying to use modern sound hardware if it’s available (so we can have MP3 ringtone beeps instead of 1970s beeps)?
*Which* terminal, anyway? There are at least seven I can think of.
It's not exclusively a terminal thing (noted above), although that's what it's historically associated with. Sorry for the ambiguity.
James (who turns all the beeps off).
Anyway, the trouble is this: the beeps work as expected until snd-hda-intel is loaded. Then they're irrevocably gone, recoverable only by a reboot. I've tried mixers and beep_mode adjustments to no avail.
Milhaus (who turns all beeps on).
Is there a possibility that you have Two sound drivers trying to load ?
It happens in Linux, then you have to Blacklist one.
--- On Fri, 4/15/11, james tate binarynut@comcast.net wrote:
Is there a possibility that you have Two sound drivers trying to load ?
What's actually loaded doesn't look too bad:
snd_hda_codec_si3054 3908 1 snd_hda_codec_analog 74362 1 snd_hda_intel 23960 4 snd_hda_codec 85624 3 snd_hda_codec_si3054,snd_hda_codec_analog,snd_hda_intel snd_hwdep 6454 1 snd_hda_codec snd_seq 53005 0 snd_seq_device 6159 1 snd_seq snd_pcm 80324 4 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec snd_timer 19882 3 snd_seq,snd_pcm snd 62913 15 snd_hda_codec_si3054,snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer soundcore 6390 1 snd snd_page_alloc 7437 2 snd_hda_intel,snd_pcm
I didn't see anything in syslog suggesting there were failures along the way.
It happens in Linux, then you have to Blacklist one.
snd-pcsp is blacklisted. (It's a sound driver but doesn't drive the bell.)
Milhaus
updog wrote:
"Terminal beep" also includes audible notifications from programs such as nedit and mozilla, e.g. search term not found.
OK – that’s a desktop environment thing. (Which desktop environment, anyway?)
It will almost certainly consider the beeper a fallback to use if there is no other sound hardware available. As soon as you make HDA available, it will use that.
So one option might simply be to find a recording of a suitable beep, and choose that as the standard alert sound. In Gnome (at least on F14, but I don’t think F13 was any different), this was configured through System → Preferences → Sound.
Unfortunately, at least on Gnome, https://bugzilla.gnome.org/show_bug.cgi?id=607906 suggests that metacity won’t route system alerts to the PC speaker. Compiz might – what happens if you turn on Desktop Effects?
You might also want to check you have pulseaudio-module-x11 installed.
Hope this helps,
James (who is somewhat handicapped – in this case! – by not having any hardware with a PC speaker any more).
-
James Wilkinson -
JD -
Mickey -
Tim -
updog