From: Oliver Freyermuth <o.freyermuth@googlemail.com>
To: Raymond Yau <superquad.vortex2@gmail.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Digital Input on ALC3661 (from laptop HDMI IN) not working under Linux
Date: Sat, 17 Jan 2015 17:04:17 +0100 [thread overview]
Message-ID: <54BA8801.6080508@googlemail.com> (raw)
In-Reply-To: <CAN8cciZV2Z=6yck7RHpgLUK-o7rXY+i51usMgss+xH4wkZHDDA@mail.gmail.com>
>> I have an Alienware 17 laptop (sometimes called M17RX5) which has a
> Realtek ALC3661.
>>The problem I describe here should also be valid for the Alienware 18
> (all the late 2013 models, which are still the most current). At least
> some scattered forum reports suggest so.
>
>>The card works almost perfect in Linux, but one functionality is
> missing: The laptop features an HDMI input, and the Realtek card is
> supposed to take care of the incoming digital audio.
> This works fine in Windows, but in Linux, I only get the video and the
> audio stays missing.
>
>> Here you can find my alsa-info:
> http://www.alsa-project.org/db/?f=0a0502e49212a0436a30fde9d4ee56163bbc2ebc
>
> The only digial input is node 0x0a
>
> Try hda-jack-retask to change node 0x1f with pin default [Jack] digital In
Thanks a lot for your suggestion!
I tried, 0x0a stays as "not present" but I can select it in alsa-mixer
as expected. Sadly, I can only record silence.
Also setting Jack Detection to "Present" in the advanced overrides of
hdajackretask did not help.
Do you have further ideas / is there more information I can provide /
collect?
Cheers,
Oliver
>
> Node 0x0a [Audio Input] wcaps 0x100791: Stereo Digital
> Converter: stream=0, channel=0
> SDI-Select: 0
> Digital:
> Digital category: 0x0
> IEC Coding Type: 0x0
> PCM:
> rates [0x570]: 32000 44100 48000 96000 192000
> bits [0xe]: 16 20 24
> formats [0x1]: PCM
> Unsolicited: tag=00, enabled=0
> Power states: D0 D1 D2 D3 EPSS
> Power: setting=D0, actual=D0
> Connection: 1
> 0x1f
>
> Node 0x1f [Pin Complex] wcaps 0x400681: Stereo Digital
> Pincap 0x00000020: IN
> Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> Conn = 1/8, Color = Black
> DefAssociation = 0xf, Sequence = 0x0
> Misc = NO_PRESENCE
> Pin-ctls: 0x20: IN
> Unsolicited: tag=00, enabled=0
> Power states: D0 D1 D2 D3 EPSS
>
>>In Windows, I observe the HDMI-IN audio routing to the speakers is only
> done if the Realtek Audio Service is running. In Linux, I observe
> keypress-events when I either switch manually to the HDMI-in signal and also
> if a new signal is detected (something (the UEFI?) injects a keypress
> then).
> I assume the service in Windows catches these events and changes
> "something" in the Realtek Audio Settings. I see no special recording
> device in Windows, nor any explicit HDMI-input setting, nor any related
> setting in the driver. Dell links a standard Realtek driver in their
> support section.
>
>>Note the laptop has a single HDMI connector which can be used both for
> input and output (so the nvidia-card
> also shows one HDMI-out). The second NVIDIA audio out is very likely
> from the mini-display-port of the
> laptop.
>
--
Oliver Freyermuth
Physikalisches Institut der Universität Bonn
Nußallee 12
53115 Bonn
--
Raum W 0.018 (W152), Tel.: 0228 73 3697
--
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next parent reply other threads:[~2015-01-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN8ccia2tYdtR1-ECkC74UoiROAvf3faWSZ_Da09p2C24_9YnQ@mail.gmail.com>
[not found] ` <CAN8ccibptPwFidyNM9TAHjqQg_-xiXEcw3oaaqZDetn-GPVZrg@mail.gmail.com>
[not found] ` <CAN8cciZWU6-CfKKK21L39nkOqMJtNJL3k06iHWpF_J7oq=DzCg@mail.gmail.com>
[not found] ` <CAN8cciZV2Z=6yck7RHpgLUK-o7rXY+i51usMgss+xH4wkZHDDA@mail.gmail.com>
2015-01-17 16:04 ` Oliver Freyermuth [this message]
[not found] ` <CAN8cciZi-b-tSKZ0OkhKQtGPdfMTkGyKfrMxcnrDip1jSZPQUg@mail.gmail.com>
2015-02-02 19:26 ` Digital Input on ALC3661 (from laptop HDMI IN) not working under Linux Oliver Freyermuth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BA8801.6080508@googlemail.com \
--to=o.freyermuth@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).