[Bug 928394] New: Headphone jack not working anymore
http://bugzilla.opensuse.org/show_bug.cgi?id=928394 Bug ID: 928394 Summary: Headphone jack not working anymore Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: floux.dp@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since the last PulseAudio patch, the headphone jack is not working anymore. As a workaround, the "principal" audio jack is working (behind the computer). I tried to delete the ~/.config/pulse directory but it does not change anything. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #2 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #3 from Foulques du Peloux
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #4 from Foulques du Peloux
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #5 from Takashi Iwai
Created attachment 632180 [details] alsa-info.sh output
You took this while you didn't plug the headphone jack, right? If so, please give alsa-info.sh snapshot at the headphone plugged, too. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #6 from Foulques du Peloux
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #7 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Takashi Iwai
Prior to 22 April 2015 pulse audio, (front headphone jack) was functioning.
If you need assistance to test, please post message to me. My email address is open to you
reach me at Leslie Satenstein lsatenstein@yahoo.com
even wit today's regression, it is still not functioning,
Do you want the same three files from my system?
Yes, these are essential to understand the problems. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #11 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #12 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #13 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #14 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #15 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Takashi Iwai
SURPRISE SURPRISE
If you do not have wget installed, alsa-info.sh will overwrite itself with a NULL
I requested to pass --no-upload option. This update is triggered only when no arguments are passed or --update option is passed. It's no bug but a feature. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Takashi Iwai
Good Morning
I am uploading two files for you. Saturday 25April
File1 alsa-info-after.txt (with headphone plugged into the jack)
File2 alsa-info-noHdPhone.txt (headphone was removed from the jack)
In both outputs, there is no change in "Headphone Jack" control value. It means that the driver didn't detect the headphone jack. Most likely it's either a hardware problem or a BIOS problem. The fact that the old PA worked was a bug. It shouldn't have worked as you expected. Now it gets fixed, and the problem is revealed. That said, it's no regression but rather a "fix" to behavior correctly to the hardware that doesn't behave as expected.
Pleasenote.
Fedora 21,22 are experiencing the same issue.
I use both SUSE13.2 and Fedora21.
This implies the same consequence. Now, what you can do is to check the real pin configuration and the hardware configuration. Try to alsa-tools package (or hdajackretask) and see which any pin gives the jack detection corresponds to your headphone jack. If yes, you need to reassign the headphone pin correctly, set up as a "patch" firmware to load to the driver. If no pin reacts to the headphone jack, it's a hardware problem. You might have connected the front panel in a wrong mode (AC97) that has a different pin assignment. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #18 from Leslie Satenstein
From non-working system (pulseaudio 6 and alsa 6) re-examine Without headphones plugged. and headphones plugged.
You have results on the same hardware. The only thing I can do is show you the *rpm files for alsa and pulseaudio. With the last 4 files you do have enough to go on. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #19 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #20 from Takashi Iwai
I reverted to a system that used version 5 of pulseaudio and alsa, and the headphone jack works.
Please look at the last 4 files.
Final two show the results when the headphone jack works.
No, it doesn't "work" if your attached alsa-info.sh outputs are correct. It's merely a bug of older PulseAudio that ignored "Front Headphone Jack" state.
Headphone out (not plugged), Headphone IN jack and working
To generate this for you, I reverted to a system that used versions 5 of pulseaudio and alsa.
From non-working system (pulseaudio 6 and alsa 6) re-examine Without headphones plugged. and headphones plugged.
What is "alsa 6"...? There is no such thing.
You have results on the same hardware.
The only thing I can do is show you the *rpm files for alsa and pulseaudio.
With the last 4 files you do have enough to go on.
If so, again, it's a hardware problem. Look at the state of "Front Headphone Jack" in both states. Both showed like: control.43 { iface CARD name 'Front Headphone Jack' value false This indicates that the headphone jack wasn't detected in the driver. When a jack detection is provided by the driver, PulseAudio does automatic switching between the outputs per jack state. And, the older PA didn't work well with this jack, so it *looked* as if it's working; namely, the headphone output wasn't touched. That is, what the result was old PA was a bug of PA, and it got "fixed" by this update. Check your hardware setup again. There can be a BIOS setup problem. Or, check alsa-info.sh outputs again. If "Front Headphone Jack" state changes, then the situation is different. The consequence here was derived just from the alsa-info.sh outputs you attached here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #21 from Takashi Iwai
Re comment 17 alsa-info.sh
If you remove or rename wget, and run this script, it will wipe itself out.
Ah, OK, I misunderstood your description. Then it's a clear bug. I'll check it and fix the upstream code, too. No need to create another bug report. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #23 from Foulques du Peloux
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #24 from Takashi Iwai
Sometimes I have to unplug and replug my headphone to have the sound working. It was never happening before.
This is also unlikely a regression of PA itself, but rather the flaky jack detection. The change in PA reveals such instability because PA tries to follow the jack state more strictly. In anyway, please get alsa-info.sh outputs at both working and non-working states. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #25 from Takashi Iwai
(In reply to Leslie Satenstein from comment #19)
Re comment 17 alsa-info.sh
If you remove or rename wget, and run this script, it will wipe itself out.
Ah, OK, I misunderstood your description. Then it's a clear bug. I'll check it and fix the upstream code, too. No need to create another bug report.
To make it clear: my comment here was only about alsa-info.sh script being overwritten by an empty file. The PA behavior and headphone problem is irrelevant from the comment above. The headphone problem is a hardware-specific issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #26 from Leslie Satenstein
(In reply to Leslie Satenstein from comment #18)
I reverted to a system that used version 5 of pulseaudio and alsa, and the headphone jack works.
Please look at the last 4 files.
Final two show the results when the headphone jack works.
No, it doesn't "work" if your attached alsa-info.sh outputs are correct. It's merely a bug of older PulseAudio that ignored "Front Headphone Jack" state.
Headphone out (not plugged), Headphone IN jack and working
To generate this for you, I reverted to a system that used versions 5 of pulseaudio and alsa.
From non-working system (pulseaudio 6 and alsa 6) re-examine Without headphones plugged. and headphones plugged.
What is "alsa 6"...? There is no such thing.
You have results on the same hardware.
The only thing I can do is show you the *rpm files for alsa and pulseaudio.
With the last 4 files you do have enough to go on.
If so, again, it's a hardware problem.
Look at the state of "Front Headphone Jack" in both states. Both showed like:
control.43 { iface CARD name 'Front Headphone Jack' value false
This indicates that the headphone jack wasn't detected in the driver. When a jack detection is provided by the driver, PulseAudio does automatic switching between the outputs per jack state. And, the older PA didn't work well with this jack, so it *looked* as if it's working; namely, the headphone output wasn't touched. That is, what the result was old PA was a bug of PA, and it got "fixed" by this update.
Check your hardware setup again. There can be a BIOS setup problem.
Or, check alsa-info.sh outputs again. If "Front Headphone Jack" state changes, then the situation is different. The consequence here was derived just from the alsa-info.sh outputs you attached here.
Good morning from Montreal Canada. My last 4 attachments show the in/out, working/nonworking runs of alsa-info.sh I have updates to the working pulseaudio headphone jack blocked from updates. Updates to most recent releases of the kernel have not affected that working alsa/pulseaudio or the others. Comment. My main system has 5 hard disks, SUSE is on it's own as is Fedora and Windows 8.1. If the headphone jack hardware is the cause of the error, it would have impacted windows8.1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #27 from Takashi Iwai
My last 4 attachments show the in/out, working/nonworking runs of alsa-info.sh I have updates to the working pulseaudio headphone jack blocked from updates.
Updates to most recent releases of the kernel have not affected that working alsa/pulseaudio or the others.
Did you test "alsactl monitor" while plugging/unplugging the headphone jack, as I suggested in the previous mail? If there is no event triggered by that, it means a hardware problem.
Comment. My main system has 5 hard disks, SUSE is on it's own as is Fedora and Windows 8.1. If the headphone jack hardware is the cause of the error, it would have impacted windows8.1.
The fact that it "works" on Windows doesn't mean that there is no hardware problem. Windows doesn't use the full feature like Linux. We sometimes hit bugs Windows doesn't hit; sometimes because we use more chip features than Windows (the vendor never tested properly), or often BIOS is broken but Windows has a static workaround in it. Also, Windows' behavior might be similar like bare ALSA driver, i.e. the headphone isn't muted while unplluged. The headphone mute while unplgged is rather specific behavior of PA. So, check whether the headhpone jack detection really works or not. If it doesn't, accept the fact that there is something wrong in hardware or its setup (e.g. BIOS). A driver bug is very unlikely in this regard. Then check your BIOS setup and hardware setup. I'll suggest another workaround once when you confirm all these. Please report further on Bugzilla. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #28 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #29 from Takashi Iwai
alsactl monitor
does not indicate headphone in or transition to/from out on my desktop system..
However, executing diff between pairs of files shows differences in some fields, which I believe may serve to indicate headphone in/out.
The question is *which* fields changed. Please give the diff output. Otherwise one cannot judge.
With desktop and headphones in, speakers remain active.
Yeah, that's already the problem. This should have been muted like laptop.
With laptop, speakers are muted with headphones in.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #32 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #34 from Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Leslie Satenstein
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
Foulques du Peloux
http://bugzilla.opensuse.org/show_bug.cgi?id=928394
--- Comment #39 from Leslie Satenstein
participants (1)
-
bugzilla_noreply@novell.com