Red Hat Bugzilla – Bug 473229
Incorrect PCM Volume in default config
Last modified: 2009-03-02 11:57:02 EST
Created attachment 324844 [details] Zero PCM Volume Description of problem: Default PCM Volume is zero, causing in some ("old") intel chips not playing of sound. The solution can't be performed with pulseaudio default controls. (see attached screenshot). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Open a music player and play a sound 2. no sound. Actual results: Default sound configuration not play sound. Expected results: Play sound with default configuration. Additional info: High PCM Volumes cause sound distortion: https://launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/42043
My default PCM volume was very low, so that I had to crank my speakers and all volumes all the way for it to be audible. When I fired up 'alsamixer -c 0', the PCM volume was at around -21dB. I brought it all the way up to +12 to make it usable. My card from lspci: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) This is from a recent model Dell Optiplex 745.
In F10 PA doesn't init the audio volume unless it has some previously saved volume to restore. It's ALSA's job to come up with sane defaults. REassigning to alsa.
Please, attach output from 'alsa-info.sh --no-upload'.
Created attachment 330885 [details] alsa-info.txt generated from "alsa-info.sh --no-upload"
Could you copy the latest /lib/alsa/init/default file from this localiton http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsactl/init/default and test if 'alsaunmute' script sets the default volumes correctly for your hw? Thank you.
Yeap, Shows this message: Unknown hardware: "ICH4" "Realtek ALC202 rev 0" "AC97a:414c4740" "" "" Hardware is initialized using a guess method but,yes, sets the correct PCM and Volume Value. Bye and Tks by your fix.
alsa-utils-1.0.19-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.