Bug 699176 - Fedora does not detect headphones on my hardware
Summary: Fedora does not detect headphones on my hardware
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: first=2.6.38.2 tested=3.3 alsa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-23 22:42 UTC by Amir Hedayaty
Modified: 2013-03-28 13:52 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-28 13:52:29 UTC
Type: ---


Attachments (Terms of Use)

Description Amir Hedayaty 2011-04-23 22:42:16 UTC
Description of problem:
When plugging in the headphone to front cords of the case, I expect the speakers to be disabled and sound redirected to headphones.

If FC14, there was a wired behaviour but kind of work, first volume was muted, the volume was low on speakers and very high on headphones, so if I tuned the volume between 0%-20%, worked for me.

In the FC15 even this does not happen, front cords are  totally neglected, I have tried different settings in sound preferences.


Version-Release number of selected component (if applicable):

This is my sound card,
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)

Also here are kernel and pulseaudio versions
kernel-2.6.38.2-9.fc15.x86_64
pulseaudio-0.9.22-5.fc15.x86_64

How reproducible:


Steps to Reproduce:
1. make some noise
2. plug in headphones
  
Actual results:
Nothing

Expected results:
Speakers to be muted
sound redirected to headphones

Additional info:

Comment 1 Amir Hedayaty 2011-11-21 11:21:55 UTC
I found a workaround on the internet,
Run alsa-mixer
turn of "Independent HP"

Everything fine after that.

It seems there is an attempt to fix the issue on kernel,

http://kerneltrap.org/mailarchive/git-commits-head/2010/4/17/31959

Can anyone tell if the patch is landed on the latest kernel in Fedora 16?

Comment 2 Josh Boyer 2012-06-04 19:05:26 UTC
The commit mentioned in comment #1 was included in the original kernel you reported the issue on.

Are you still seeing this with the 2.6.43/3.3 F15/F16 kernel updates?

Comment 3 Amir Hedayaty 2012-06-06 17:19:00 UTC
I am using FC17 right now, and is not fixed yet.
If you have anly tried it on FC16, I can test it on FC16 as well.

Comment 4 Giovanni Tirloni 2012-06-24 02:10:08 UTC
Same happens on FC16 here as well.

1. Play some music and goes to the speakers
2. Plug headphone
3. Music still plays on the speakers and no sound on the headphones.

I'm using KDE, so if I go to Settting / Multimedia / Phonon and change the output device from "Analog Speakers" to "Analog Headphones", music starts playing on the headphones. If I select "Analog Output", music isn't played in either of them.

So it seems that F16 is able to make use of the headphones but it's not detecting when they are plugged and/or doesn't mute the speakers and redirect sound to the headphones.

KDE 4.8.3
alsa-firmware-1.0.25-1.fc16.noarch
alsa-lib-1.0.25-1.fc16.x86_64
alsa-plugins-pulseaudio-1.0.25-3.fc16.x86_64
alsa-tools-firmware-1.0.25-1.fc16.x86_64
alsa-utils-1.0.25-7.fc16.x86_64
kde-settings-pulseaudio-4.7-14.fc16.noarch
pulseaudio-0.9.23-1.fc16.x86_64
pulseaudio-libs-0.9.23-1.fc16.x86_64
pulseaudio-libs-glib2-0.9.23-1.fc16.x86_64
pulseaudio-module-bluetooth-0.9.23-1.fc16.x86_64
pulseaudio-module-x11-0.9.23-1.fc16.x86_64
pulseaudio-utils-0.9.23-1.fc16.x86_64

Comment 5 A. Folger 2012-11-13 23:59:54 UTC
I am also using FC17 and suffer from the same bug. I have been suffering from this for a while. As a matter of fact, since F13, as you can see here:
https://bugzilla.redhat.com/show_bug.cgi?id=623632

Comment 6 Josh Boyer 2013-03-14 17:35:19 UTC
Is this still a problem with 3.8.2 in updates-testing?

Comment 7 Josh Boyer 2013-03-28 13:52:29 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


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