Created attachment 343080 [details] output of alsa-info.sh Description of problem: The default audio levels on this laptop are barely audible. The hardware volume scrollwheel (which causes the OSD volume control to appear), volume control applet, and pavucontrol are all incapable of setting the volume to a sufficiently high level -- it's necessary to use alsamixer to set the 'front' control to 100%. Version-Release number of selected component (if applicable): alsa-utils-1.0.19-4.fc11.x86_64 alsa-lib-1.0.19-3.fc11.x86_64 alsa-plugins-pulseaudio-1.0.18-3.fc11.x86_64 kernel-2.6.29.2-126.fc11.x86_64 pulseaudio-utils-0.9.15-11.fc11.x86_64 pulseaudio-libs-0.9.15-11.fc11.x86_64 pulseaudio-0.9.15-11.fc11.x86_64 Steps to Reproduce: 1. Install F11 preview, update to rawhide, observe that sound is too quiet. 2. Use alsamixer to set 'front' control to 100%. 3. Observe that sound is audible. Additional info: The 'amixer_before.txt' file may not have the exact default setting for 'front'. However, I am certain that 'front' is the only control that I adjusted in alsamixer.
Created attachment 343081 [details] mixer values before fix
Created attachment 343082 [details] settings after adjusting 'front' to 100%
Created attachment 343083 [details] output of lshw Since there are several different laptop configurations with similar designations, I've also attached the 'lshw' output.
Jaroslav, was this one done in 1.0.20? Chris, once you adjust front to 100%, do Pulse volume controls then give a reasonable range of adjustment - i.e., when you set the Pulse slider to 0, does it still go quiet?
(In reply to comment #4) > Chris, once you adjust front to 100%, do Pulse volume controls then give a > reasonable range of adjustment - i.e., when you set the Pulse slider to 0, does > it still go quiet? Yes, with front at 100% it operates as expected. I think the headphone setting should also be put all the way up, but haven't confirmed that. (Unclear on whether to set the NEEDINFO flag to '+' or ' ', trying '+').
Thanks.
The alsa-utils-1.0.20-3 package should fix this issue. Reopen this bug if the problem persist.