|
Bugzilla – Full Text Bug Listing |
| Summary: | Headphones automute don't function properly on Dell Studio 15 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Lee Matheson <lee_matheson> |
| Component: | Sound | Assignee: | Takashi Iwai <tiwai> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | lee_matheson, meissner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | maint:released:11.1:23622 maint:released:sle11:23621 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
alsa-info.txt output after running alsa-info.sh with the problem
dmesg after a pc boot - speakers do not mute when headphone pluged in. alsa-info.txt with automute working - but low volume and yast-hardware-sound-other-volume crashes |
||
|
Description
Lee Matheson
2009-03-04 19:18:47 UTC
Created attachment 277144 [details]
dmesg after a pc boot - speakers do not mute when headphone pluged in.
dmesg after a pc boot.
Changed component to sound Thanks for the report. I found the culprit. It's due to the recent rewrite of the codec parser. I'll work on it. I fixed the issue now on the upstream. Please try the latest alsa-driver-kmp later (which is being built now). BTW, with the very latest version, you'll have two "Headphone" mixer controls corresponding to two HP jacks while "Front" and "Surround" were assigned to them in the earlier version. So, you might need to adjust the mixer again after the update of the driver. Created attachment 277742 [details]
alsa-info.txt with automute working - but low volume and yast-hardware-sound-other-volume crashes
Thankyou, I installed alsa-driver-kmp-pae-1.0.19.20090306_2.6.27.19_3.2-3.1. I rebooted, and sound could not be heard even with kmix master and PCM volume up 100%. I then went to Yast > Hardware > Sound > Other > Volume in an effort to move up master and PCM volume there ... ... but instead the sound function under YaST crashed, giving the xmessage dialog box: "YaST got signal 11 at YCP file Wizard.ycp:743 /sbin/yast2: line 437: 4542 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS " Basic (top level) YaST was still running, so I went to Hardware > Sound > Other > test sound and had the test sound functioning I then ran the speaker test: speaker-test -c2 -l10 -twav and the automute worked on speakers. FIXED !! Thankyou. But volume is much lower than before the kernel update, despite kmix master and PCM up full. I could "fix" this low volume level with the old kernel, by going to Yast > Hardware > Sound > Other > Volume and raising the Master and PCM volumes there higher ... but that still crashes the YaST sound module when I attempt that (with same error as above). above in previous post is alsa-info.txt file with successful automute Apologies. Speaker volume is fine, and just as loud as before. The changed mixer setup (that you warned me about) confused me a bit. The YaST sound module is still there (possibly associated with the mixer change you introduced) but that is really irrelevant to my sound functionality. Many thanks again for your fix. I meant to say the YaST sound module crash (with xmessage dialog box): "YaST got signal 11 at YCP file Wizard.ycp:743 /sbin/yast2: line 437: 4542 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS " still is reproduceable. Thanks for checking. YaST crash is a known issue. It should have been fixed for SLE11-base but seems like the fix is pending for 11.1. Ladislav, is it correct? The crash has been reported in bug #407060, it has been fixed in FACTORY (since yast2-sound-2.18.0). (I do not want to fix it in SLE11 or in 11.1 right now because the fix slightly changes the internal mixer API so it could potentially break something in autoyast or other yast modules. It needs more testing, I can release it later when it turns out that it's OK.) OK, the patches are now merged to kernel source tree so that the next update kernel will include the fix. Update released for: kernel-debug, kernel-debug-base, kernel-debug-debuginfo, kernel-debug-debugsource, kernel-debug-extra, kernel-default, kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-extra, kernel-docs, kernel-kdump, kernel-kdump-debuginfo, kernel-kdump-debugsource, kernel-pae, kernel-pae-base, kernel-pae-extra, kernel-ppc64, kernel-ppc64-base, kernel-ppc64-debuginfo, kernel-ppc64-debugsource, kernel-ppc64-extra, kernel-ps3, kernel-ps3-debuginfo, kernel-ps3-debugsource, kernel-source, kernel-source-debuginfo, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-extra, kernel-vanilla, kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-xen, kernel-xen-base, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-extra Products: openSUSE 11.1 (debug, i586, ppc, x86_64) A kernel update for SUSE Linux Enterprise 11 was just released that references / fixses this bug, with RPM version "2.6.27.21-0.1.2". Update released for: cluster-network-kmp-default, cluster-network-kmp-xen, ext4dev-kmp-default, ext4dev-kmp-xen, kernel-default, kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-extra, kernel-source, kernel-source-debuginfo, kernel-syms, kernel-xen, kernel-xen-base, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-extra, ocfs2-kmp-default, ocfs2-kmp-xen Products: SLE-DEBUGINFO 11 (x86_64) SLE-DESKTOP 11 (x86_64) SLE-HAE 11 (x86_64) SLE-SERVER 11 (x86_64) |