Red Hat Bugzilla – Bug 249988
Sound output is not stereo until volume slider is moved
Last modified: 2007-11-30 17:12:11 EST
Description of problem: When I first start up and login, there is only sound
coming out of one channel. Until the volume slider is moved, it is stuck like
that. Once the slider in the mixer is moved, sound comes out of both left and
Version-Release number of selected component (if applicable): 1.0.14-0.4.rc3.fc7
How reproducible: Happens every time I start up the computer and login
Steps to Reproduce:
1. Start up and login
2. Play something and listen to sound
3. Move the volume slider and listen again, sound is now stereo
Actual results: Sound is not stereo until slider is moved.
Expected results: Sound should always be stereo since the channels are linked
and they are not muted.
Here is a link to Launchpad report, as I had this problem in Ubuntu Feisty as
well. They have linux-source-2.6.20 marked as the affected package, but since
Fedora 7 uses 2.6.22.x that needs to be changed.
Aha, okay. There's an updated kernel package for F7 with alsa-drivers 1.0.14.
Anyway, what channel do you have to move? There's a command line utility nammed
alsaunmute what should set all channels to the default values. Does it do that?
Anyway, can you please attach /root/scsconfig.log? It can be generated by
Created attachment 161716 [details]
Sound Config log
The channel I have to move is "PCM". I ran the command "alsaunmute 0", and that
made the volume louder and unmuted the left channel. However it doesn't work if
I reboot, I have to do it again just like moving the volume slider.
Aha. Is the volume of "PCM" preserved during boot? If not, that could be a dupe
of Bug 247468.
Anyway, please report it at upstream (www.alsa-project.org) and file a bug
there. This bug should be fixed there for all distros.
Hi Martin, sorry for the delayed response. The PCM level isn't preserved when I
reboot, it goes back to 50%. I believe with the updated alsa-drivers, that the
stereo problem has been taken care of, so this bug can be closed and set to
fixed. I will contribute to Bug 24746 to help with that one. Thanks for all