Created attachment 357592 [details]
amixer -c0 when sound does not work
PulseAudio-based volume control cannot adjust volume satisfactorily with my audio chip. I am running on a Dell Latitude C640 equipped with an Intel Corporation 82801CA/CAM AC'97 Audio Controller.
1. Start an Video file with Totem -> no sound
2. Start gst-mixer and play with PCM volume slider -> sound starts working
3. From now on pulseaudio can be used to adjust sound volume
Created attachment 357593 [details]
amixer -c0 when sound works
This issue happens on the internal laptop speaker
Uh? Your second snapshot shows the PCM volume as *lower* as the first one. Have you mixed them up?
Indeed this is not a mistake, I did reproduce the issue today. What happens is when I use gst-mixer to play with the PCM volume slider, I hear a pop noise then sound starts working. It seems to me like something gets initialized that triggers the sound card. Is there anything else as far as output that might help fixing the issue. I can easily collect before/after.
If PCM indeed gets louder when the slider goes down this is a driver bug. Reassigning to ALSA/kernel.
(Or maybe it's just the mut toggle that was reset?)
Ping, anything I can do to help debug this issue? And no Lennart this is not the mute button toggled.
Created attachment 361794 [details]
I have one more test case to add to this bug. I moved to using testday-20090915-i686.iso live cd and although I do not experience the above mentionned problem, I now seeing the following issue:
1. Start live cd and g-v-c
Default window is as seen in attached screenshot from comment #7
Alert volume: set to minimum but Mute checkbox unchecked
Sound theme: Default
Enable window and button sounds: unchecked
2. I now check the Enable window and button sounds checkbox, then without changing the Alert volume still set to minimum, I click various entries listed under Choose an alert sound (Bark, Drip, Glass). For each of those I hear sound fine.
3. I now adjust the alert volume slider and have to set it to 75% to match the sound level experienced in step 2 above.
BTW, here are relevant component versions:
Please, attach also contents of /proc/asound/card0/codec* files for working and non-working case. Thanks.
Created attachment 362099 [details]
non working /proc/asound/card0/codec97#0/ac97#0-0+regs
Created attachment 362100 [details]
There was also a file called non working /proc/asound/card0/codec97#0/ac97#0-0 but its content did not change between workind and non working
-0:26 = 000f # working
+0:26 = 020d # not-working - analog sections NOT ready, DAC powerdown set
Are any suspicious messages related to sound in /var/log/messages ?
What's in /sys/modules/ac97_codec/parameters/power_save file ? Zero ?
I see a couple of kernel oops. see attached traces below but I do not think they are related to the sound subsystem, I am also attaching the /var/log/messages file. I could not find a file under /sys/modules/ac97_codec/parameters/power_save but I found one with the same name under /sys/module/snd_ac97_codec/parameters/power_save This later file had a 5 in it, not a zero.
Created attachment 362319 [details]
Created attachment 362320 [details]
Created attachment 362321 [details]
/sys/module/snd_ac97_codec/parameters/power_save is correct. Please, set it to zero in a boot script and report if your problem goes away:
echo 0 > /sys/module/snd_ac97_codec/parameters/power_save
Could you please suggest a way of doing this when using the testday livecd?
I managed to repartition my drive and install rawhide on its own partition. As you suggested, I tried putting 0 in power_save and the problem indeed goes away.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.