<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Alienware14 lower range sound output until pin 0x1a is set for a full deeper stereo sound output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101931#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Alienware14 lower range sound output until pin 0x1a is set for a full deeper stereo sound output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101931">bug 101931</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>I'm very confused by <a href="show_bug.cgi?id=101931#c14">comment #14</a>. You seem to be contradicting yourself, but
that's probably just me misinterpreting what you say.
Please be careful with the terms. A "headphone" means a device with no mic, a
"headset" means a device with headphones and a microphone. If you mix these up,
it's impossible for me to understand what is really happening.
>From the discussion so far, I understand that you have at least a headset, do
you also have plain headphones available for testing? What about a separate
microphone, do you have that?
I'd like you to run a little script four times before and after setting the pin
in hdajackretask:
- without anything plugged in
- headphones plugged in to the headphone jack (if you don't have headphones,
use the headset instead, and note that in a comment)
- headset plugged in to the headset jack
- microphone plugged in to the microphone jack (if you don't have a
microphone, use the headset instead, and note that in a comment)
Here's the script:
pactl list cards
while read -r line; do
amixer -c1 cget "$line"
done <<< $(amixer -c1 controls | grep Jack)
That will first run "pactl list cards", which will show what pulseaudio thinks
the port state is in each case. Then there's a loop that will print the status
of each alsa mixer jack control.
If you want, you can also report where you hear sound in each case, but if you
do that, please note in each case what this command prints:
pactl list | grep 'Active Port'
I'm sorry I'm asking you to do so many tests, but there are multiple problems
and many different states that the system can be in, so it takes some effort to
get a clear picture about what happens when you do this or that.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>