Bug 517769 - snd-intel8x0: audio level is incorrectly initialized
Summary: snd-intel8x0: audio level is incorrectly initialized
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: AlsaVolume
TreeView+ depends on / blocked
Reported: 2009-08-17 02:01 UTC by Eric Moret
Modified: 2010-12-05 06:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-05 06:36:00 UTC
Type: ---

Attachments (Terms of Use)
amixer -c0 when sound does not work (5.54 KB, text/plain)
2009-08-17 02:01 UTC, Eric Moret
no flags Details
amixer -c0 when sound works (5.55 KB, text/plain)
2009-08-17 02:02 UTC, Eric Moret
no flags Details
Screenshot (446.44 KB, image/png)
2009-09-19 23:19 UTC, Eric Moret
no flags Details
non working /proc/asound/card0/codec97#0/ac97#0-0+regs (768 bytes, text/plain)
2009-09-22 15:04 UTC, Eric Moret
no flags Details
working /proc/asound/card0/codec97#0/ac97#0-0+regs (768 bytes, application/octet-stream)
2009-09-22 15:05 UTC, Eric Moret
no flags Details
Kerneloops 1 (878 bytes, text/plain)
2009-09-23 15:40 UTC, Eric Moret
no flags Details
Kerneloops 2 (890 bytes, text/plain)
2009-09-23 15:41 UTC, Eric Moret
no flags Details
/var/log/messages (134.02 KB, text/plain)
2009-09-23 15:41 UTC, Eric Moret
no flags Details

Description Eric Moret 2009-08-17 02:01:48 UTC
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

Comment 1 Eric Moret 2009-08-17 02:02:32 UTC
Created attachment 357593 [details]
amixer -c0 when sound works

Comment 2 Eric Moret 2009-08-17 02:03:49 UTC
This issue happens on the internal laptop speaker

Comment 3 Lennart Poettering 2009-08-17 19:15:40 UTC
Uh? Your second snapshot shows the PCM volume as *lower* as the first one. Have you mixed them up?

Comment 4 Eric Moret 2009-08-18 02:37:35 UTC
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.

Comment 5 Lennart Poettering 2009-08-19 14:47:52 UTC
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?)

Comment 6 Eric Moret 2009-09-01 21:54:50 UTC
Ping, anything I can do to help debug this issue? And no Lennart this is not the mute button toggled.

Comment 7 Eric Moret 2009-09-19 23:19:27 UTC
Created attachment 361794 [details]

Comment 8 Eric Moret 2009-09-19 23:39:04 UTC
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.

Comment 9 Eric Moret 2009-09-20 00:23:07 UTC
BTW, here are relevant component versions:


Comment 10 Jaroslav Kysela 2009-09-22 08:11:49 UTC
Please, attach also contents of /proc/asound/card0/codec* files for working and non-working case. Thanks.

Comment 11 Eric Moret 2009-09-22 15:04:29 UTC
Created attachment 362099 [details]
non working /proc/asound/card0/codec97#0/ac97#0-0+regs

Comment 12 Eric Moret 2009-09-22 15:05:10 UTC
Created attachment 362100 [details]
working /proc/asound/card0/codec97#0/ac97#0-0+regs

Comment 13 Eric Moret 2009-09-22 15:06:18 UTC
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

Comment 14 Jaroslav Kysela 2009-09-23 07:48:37 UTC
Commented diff:

-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 ?

Comment 15 Eric Moret 2009-09-23 15:40:18 UTC
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.

Comment 16 Eric Moret 2009-09-23 15:40:55 UTC
Created attachment 362319 [details]
Kerneloops 1

Comment 17 Eric Moret 2009-09-23 15:41:18 UTC
Created attachment 362320 [details]
Kerneloops 2

Comment 18 Eric Moret 2009-09-23 15:41:55 UTC
Created attachment 362321 [details]

Comment 19 Jaroslav Kysela 2009-09-24 07:17:41 UTC
/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

Comment 20 Eric Moret 2009-09-24 14:14:44 UTC
Could you please suggest a way of doing this when using the testday livecd?

Comment 21 Eric Moret 2009-09-29 04:08:26 UTC
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.

Comment 22 Bug Zapper 2009-11-16 11:30:04 UTC
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:

Comment 23 Bug Zapper 2010-11-04 10:29:03 UTC
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: 

Comment 24 Bug Zapper 2010-12-05 06:36:00 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.