Created attachment 341495 [details] alsa-info.txt Description of problem: I'm filing this bug report per the "Volume not correctly controlled by new gnome-volume-control bugs: please report" email from Adam Williamson. On my Lenovo ThinkPad T61, using the internal speakers, the volume is very low until I run alsamixer -c0 and raise the PCM slider. I tested with F11-Preview LiveCD i686. Version-Release number of selected component (if applicable): kernel-2.6.29.1-102.fc11.i586 alsa-lib-1.0.19-3.fc11.i586 pulseaudio-0.9.15-11.fc11.i586 gnome-media-2.26.0-2.fc11.i586 How reproducible: always Steps to Reproduce: 1. alsa-info.sh --no-upload 2. alsactl init 3. amixer -c0 > amixer_before.txt 4. play music, note low volume even with gnome-volume-control at maximum 5. alsamixer -c0, raise PCM slider to 100% 6. now music is loud enough and can be adequately lowered using gnome-volume-control. multimedia keys volume up/down/mute all work correctly. 7. amixer -c0 > amixer_after.txt 8. diff -u amixer_before.txt amixer_after.txt > amixer_diff.txt Actual results: [root@localhost ~]# alsa-info.sh --no-upload WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. ALSA Information Script v 0.4.54 -------------------------------- This script will collect information about your ALSA installation and sound related hardware, to help diagnose your problem. Do you want to run this script? [y/n] : y Could not automatically upload output to http://www.alsa-project.org Possible reasons are: 1. Couldnt find 'wget' in your PATH 2. Your version of wget is less than 1.8.2 Please manually upload /tmp/alsa-info.txt to http://www.alsa-project.org/cardinfo-db/ and submit your post. [root@localhost tmp]# alsactl init Unknown hardware: "HDA-Intel" "Analog Devices AD1984" "HDA:11d41984,17aa20bb,00100400" "" "" Hardware is initialized using a guess method [root@localhost tmp]# amixer -c0 > amixer_before.txt [root@localhost tmp]# alsamixer -c0 [root@localhost tmp]# amixer -c0 > amixer_after.txt [root@localhost tmp]# diff -ub amixer_before.txt amixer_after.txt Expected results: PCM volume should be initialized properly by default so that the alsamixer -c0 step is unnecessary. Additional info:
Created attachment 341496 [details] amixer_diff.txt
I repeated the test with speakers attached, and the result is the same. When using powered speakers, the problem is less pronounced, because the volume happens to be "loud enough" with the default PCM volume of 64% and the powered speaker volume turned all the way up.
Thanks for the full report: triaged. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I just realized the diff may not have enough context: please also provide the amixer_before.txt and amixer_after.txt files themselves. sorry, my fault! thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 341507 [details] amixer_before.txt
Created attachment 341508 [details] amixer_after.txt
I guess this should be added to the ALSA db. Reassigning.
Please, retest witl alsa-utils-1.0.20.
I'm not the original reporter however alsa-utils-1.0.20 does appear to resolve the issue on my T61. I should note that I had to run 'alsactl init' manually in order to hear any difference.
dave: does it then survive subsequent reboots? If so, that's normal - changes to the defaults don't get automatically applied on alsa-utils updates, because the system just stores the current levels at each shut down and restores them at each boot. So it's normal that you have to run 'alsactl init' to force a reset to defaults one time.
Adam - yes it survives reboots just fine. I just wanted to note the alsactl piece for the benefit of anybody else testing to validate the fix.
OK, so we can mark this as fixed, thanks for the feedback...but, Jaroslav, as I said by email, it'd really be nice for us to try and get this overridden into GA, so people will benefit from the fixes without having to do anything manually.