Bug 521997 - kernel update to 2.6.30.5-43.fc11.x86_64 makes sound unacceptable
Summary: kernel update to 2.6.30.5-43.fc11.x86_64 makes sound unacceptable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-09 02:28 UTC by Michal Jaegermann
Modified: 2010-06-28 14:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 14:33:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
alsa-info output for 2.6.30.5-43.fc11.x86_64 (22.11 KB, text/plain)
2009-09-09 02:28 UTC, Michal Jaegermann
no flags Details
alsa-info output for the last working kernel (22.13 KB, text/plain)
2009-09-09 02:29 UTC, Michal Jaegermann
no flags Details

Description Michal Jaegermann 2009-09-09 02:28:30 UTC
Created attachment 360155 [details]
alsa-info output for 2.6.30.5-43.fc11.x86_64

Description of problem:

After booting 2.6.30.5-43.fc11.x86_64 kernel a sound is still there but sounds levels are reduced to whispers.  I happen to have powered speakers with their own amplifier, so these can be driven high enough to get some sound (but there is no headroom anymore and this causes distortions) but there is no such options for headphones and microphone and these became really unusable.  All of that despite of this small details that pavucontrol, gst-mixer and alsamixer indicate that settings did not change and are generally "high".  Rebooting to 2.6.29.6-217.2.16.fc11.x86_64 immediately restores a normal sound.

alsa-info indeed shows up that with 2.6.30.5-43.fc11.x86_64 kernel various controls are at 0% level even after 'alsactl restore' while they were pushed
up to maximum with 2.6.29.6-217.2.16.fc11.x86_64.  Does this version alsa driver requires different user-space tools?  What is present clearly is ineffective.

Version-Release number of selected component (if applicable):
kernel-2.6.30.5-43.fc11.x86_64 with 1.0.20 alsa driver

How reproducible:
always

Additional info:
Maybe the same as bug #521970 but there apparently sound was killed totally

Comment 1 Michal Jaegermann 2009-09-09 02:29:48 UTC
Created attachment 360156 [details]
alsa-info output for the last working kernel

Comment 2 Tom Sightler 2009-09-09 03:34:27 UTC
I'm having the same problem with snd_hda_intel.  I always thought the sound was too quiet to being with (much louder in Windows) and now it basically just a whisper.  Interestingly my headphones seem to work about the same as normal, only the speaker output is suppressed on this system.  This is a Dell D830 laptop.

Let me know if alsa-info is of any real value and I can post it.

Comment 3 Tom Sightler 2009-09-09 03:44:40 UTC
OK, I feel silly.  I was able to correct the speaker output level by using "alsamixer -c 0" and increasing the "Speaker" control to 100.  I could find nowhere in the GUI to control this particular setting, either in the Sound Preferences applet or the Pulse Audio Control application, but setting it from the command line is trivial.  I'm not sure why this works with the old kernel without doing this but at least I have audible sound now.

Comment 4 Michal Jaegermann 2009-09-09 18:41:51 UTC
> OK, I feel silly.

Ahem! Why?  In my case "Speaker" control is totally ineffective but playing with
various controls I found that in my case bumping up 'VIA DXS Playback Volume' makes a difference between a "whisper" sound and what looks like normal.  This is the whole difference in an output of a 'store' command for alsactl:

@@ -443,8 +443,8 @@
                comment.dbmax 0
                iface MIXER
                name 'VIA DXS Playback Volume'
-               value.0 0
-               value.1 0
+               value.0 29
+               value.1 29
        }
        control.47 {

What is more with 2.6.29.6-217.2.16.fc11 and earlier kernels these settings were by default at maximum and went down to 0 for 2.6.30.5-43.fc11 killing sound. amixer shows now zeros also on the remaining three 'VIA DXS' channels, whatever that may be, but those settings do not seem to matter in my particular setup.

> I could find nowhere in the GUI to control this particular setting,

You should be able to do that via gst-mixer (a.k.a. "Advanced Volume Control" on "Preferences" menu) but you have to turn that on using "Preferences" button of that application; most of controls by default are not displayed.  With pulseaudio tools you are SOL.

Probably unrelated but anything associated with sound generates reams of
shm_open() failed: Permission denied
shm_open() failed: Permission denied
shm_open() failed: Permission denied
shm_open() failed: Permission denied
errors.  Not that surprising as /dev/shm/ is "drwxr-xr-x 2 root root"
but Fedora 11 was always doing that.

Comment 5 Michal Jaegermann 2009-09-09 22:29:14 UTC
It appears that problems with a sound killed by "VIA DXS" settings are pretty old. Searching through Google brings, for example, that one
http://forums.gentoo.org/viewtopic.php?t=230823
from 2004. What this "DXS" stands for nobody seems to know. :-)

What changed for snd_hda_intel (see comment #2 and comment #3) I cannot tell.

Comment 6 Bug Zapper 2010-04-28 10:14:59 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-06-28 14:33:05 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.