Description of problem: The console beep that you hear if in a virtual terminal and tab complete can't complete, or when gdm lets you know you can log in, sounds absolutely terrible on Dell Precision M6300. The sound during the firstboot sound check is fine, however. And beep in BIOS sounds fine, as well. May be related to bug #503787? Version-Release number of selected component (if applicable): 2.6.18-151.el5 How reproducible: Always, at least on this machine with 5.4 tree. Steps to Reproduce: 1. Install 20090528.4 tree on Dell Precision M6300 2. get to GDM prompt or tab complete in virtual terminal. Actual results: Beep sounds sick. Expected results: Normal sounding beep. Additional info: Regression. Has been suggested that because of the way that this beep works, it may be a bug in acpi causing the timing of the signal sent to the device to be off (may be a poor rephrase of what was said; I didn't totally follow).
I suspect this is CONFIG_HDA_INPUT_BEEP, which is new in the ALSA backport for 5.4 and appears to have been turned on. This causes the console beep to be generated by the sound hardware rather than using the traditional PC speaker interface, so it may well sound different. Maybe this should be turned off if we want to avoid perceived regressions?
The HDA beep might be turned off using mixer - 'alsamixer -c 0'. Look for Speaker word. It look like two beep generators (HDA and old one) are running simultaneously on this machine. Also, please, attach output from 'alsa-info.sh --no-upload' script (can be downloaded from http://www.alsa-project.org/alsa-info.sh').
Created attachment 354694 [details] alsa-info output
turning down, and muting "Speaker" had no effect on the nasty beep sound.
Sorry, try "PC Beep"..
That definitely makes it be quiet, although I could have sworn that I'd previously tried that!
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
It appears like a similar problem to bug#526751 which is resolved.