@Manikandan: Yes, I made a few adjustments with HDAjackretask as described in
post #7
The original alsa-info probably looked like yours.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
AFAIK the pin for the subwoofer output is 0x17:
see this section of my alsa-info.txt attachment:
Node 0x17 [Pin Complex] wcaps 0x40050c: Mono Amp-Out
Control: name="Bass Speaker Playback Switch", index=0, device=0
ControlAmp: chs=1, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x00,
@Raymond, I'm really thankful for all the time you spend to help us on
this issue. However, you have to understand that we are no experts on
this topic and I don't know what to do with this information. I'm happy
to help by testing suggestions and gathering logfiles. Please let me
know if you need
This is the output of the command you provided:
$ aplay -D hw:0 --dump-hw-params /tmp/test_stereo_48000Hz_8bit_PCM.wav
See attached my alsa-info output...
** Attachment added: "alsa-info.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+attachment/4598160/+files/alsa-info.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for your assistance. However, I'm not sure what to do with this
information exactly... I'm no expert. As to your question:
"The other output capable pin is node 0x1b, do the driver connected this
node to node 0x02 or 0x03?"
I checked with HDAAnalyzer, it seems like 0x1b is connected with
Connecting 0x17 with hdajackretask doesn't seem to work either. It adds
a third channel which is called "subwoofer" in the sound settings, but
when testing the subwoofer there is still no sound...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
7 matches
Mail list logo
