Hi all !<div><br></div><div>I already reported this problem here:</div><div><a href="https://bugs.freedesktop.org/show_bug.cgi?id=49055">https://bugs.freedesktop.org/show_bug.cgi?id=49055</a> </div><div><br></div><div>I was also in emailing on this problem with Intel developer Wu Fengguang.</div>
<div>It is probably an Intel driver problem.</div><div>His last email (back in may) was:</div><div><br></div><div><font color="#3333ff"><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">"Hi Attila,</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Sorry for the delay! During the time I consulted another Intel</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">developer but still remain clueless on this problem. I'll try to</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">reach the Windows driver developers for help..</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Thanks,</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Fengguang"</span></font><br><br>I'll try to ping him if there is any newson this.</div><div><br></div><div>Cheers,</div>
<div><br></div><div>Attila</div><div><br><br><div class="gmail_quote">2012/7/22 Frederik Vogelsang <span dir="ltr"><<a href="mailto:frederik.vogelsang@gmail.com" target="_blank">frederik.vogelsang@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Paul,<br>
<br>
thanks a lot for your reply. I am not using Pulseaudio, just plain<br>
ALSA. These are the software versions I am currently using:<br>
<br>
Linux: 3.5.0 (always on latest stable)<br>
Alsa: in-kernel driver, alsa-lib 1.0.25 (always on latest stable)<br>
xf86-video-intel: 2.20.0 (always on latest stable)<br>
<br>
I do not think these matter, but I'll include them nonetheless:<br>
xorg-server: 1.12.2<br>
libdrm: 2.4.33<br>
mesa: 8.0.3<br>
<br>
I am not using a Live-System. This is a Gentoo Linux system, booted from UEFI.<br>
<br>
This is what is already working:<br>
* 3D acceleration<br>
* Sound (except from this very issue)<br>
* DTS/Dolby Digital passthrough<br>
* 7.1 LPCM<br>
<br>
This is what does not work:<br>
* DTS HD/Dolby TrueHD pass-through/bitstreaming through HDMI 1.3<br>
<br>
The driver even recognizes the audio formats supported by my AV receiver:<br>
<br>
localhost ~ # cat /proc/asound/card0/eld#3.0<br>
monitor_present 1<br>
eld_valid 1<br>
monitor_name VSX-LX51<br>
connection_type HDMI<br>
eld_version [0x2] CEA-861D or below<br>
edid_version [0x3] CEA-861-B, C or D<br>
manufacture_id 0x2f41<br>
product_id 0x0<br>
port_id 0x0<br>
support_hdcp 0<br>
support_ai 1<br>
audio_sync_delay 4<br>
speakers [0x4f] FL/FR LFE FC RL/RR RLC/RRC<br>
sad_count 9<br>
sad0_coding_type [0x1] LPCM<br>
sad0_channels 2<br>
sad0_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000<br>
sad0_bits [0xe0000] 16 20 24<br>
sad1_coding_type [0x1] LPCM<br>
sad1_channels 8<br>
sad1_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000<br>
sad1_bits [0xe0000] 16 20 24<br>
sad2_coding_type [0x2] AC-3<br>
sad2_channels 6<br>
sad2_rates [0xe0] 32000 44100 48000<br>
sad2_max_bitrate 640000<br>
sad3_coding_type [0x7] DTS<br>
sad3_channels 7<br>
sad3_rates [0x6c0] 44100 48000 88200 96000<br>
sad3_max_bitrate 1536000<br>
sad4_coding_type [0x9] DSD (One Bit Audio)<br>
sad4_channels 6<br>
sad4_rates [0x40] 44100<br>
sad5_coding_type [0xa] E-AC-3/DD+ (Dolby Digital Plus)<br>
sad5_channels 8<br>
sad5_rates [0xc0] 44100 48000<br>
sad6_coding_type [0xb] DTS-HD<br>
sad6_channels 8<br>
sad6_rates [0x1ec0] 44100 48000 88200 96000 176400 192000<br>
sad7_coding_type [0xc] MLP (Dolby TrueHD)<br>
sad7_channels 8<br>
sad7_rates [0x1ec0] 44100 48000 88200 96000 176400 192000<br>
sad8_coding_type [0xe] WMAPro<br>
sad8_channels 8<br>
sad8_rates [0x6e0] 32000 44100 48000 88200 96000<br>
sad8_profile 3<br>
<br>
I am not sure if this is a regression. I do not have any other Intel<br>
systems I could use for testing (like Sandy Bridge or earlier), only<br>
my Ivy Bridge build with a HD4000. I can only say that DTS HD<br>
passthrough works in a similar Linux system with a NVidia GT 430 using<br>
the command above, so it can neither be the cable's nor the receiver's<br>
fault.<br>
<br>
<br>
- Frederik<br>
<br>
<br>
2012/7/22 Paul Menzel <<a href="mailto:paulepanter@users.sourceforge.net">paulepanter@users.sourceforge.net</a>>:<br>
<div class="HOEnZb"><div class="h5">> Dear Frederik,<br>
><br>
><br>
> Am Freitag, den 20.07.2012, 21:03 +0200 schrieb Frederik Vogelsang:<br>
><br>
>> I am using a Core i5-3475S on a ASUS P8H77-I. The system is connected<br>
>> to my amp through HDMI. For some reason I cannot get passthrough of<br>
>> DTS-HD MA or Dolby TrueHD to work properly. On my HTPC with an ION2<br>
>> chipset I can use<br>
>><br>
>> aplay -D hdmi:CARD=NVidia,DEV=2,AES0=6 -c8 -fs16_le -r192000 dtshd_test.spdif<br>
>><br>
>> and the receiver recognizes and plays the DTS-HD MA stream. On my<br>
>> Intel system I am trying the exact same thing (different card name,<br>
>> obviously) and the receiver only plays noise (shows 7.1 PCM instead of<br>
>> DTS-HD).<br>
>><br>
>> Am I doing anything wrong? Are there any configuration options I am<br>
>> missing or kernel module parameters? I am using the latest stable<br>
>> xf86-video-intel driver and Linux kernel.<br>
><br>
> I guess the developers might look at your problem on Monday, but please<br>
> note the specific versions. ALSA version might also be interesting. Do<br>
> you use PulseAudio? Have you tried some live systems? And lastly is this<br>
> a regression?<br>
><br>
> Anyway, please also provide some log files as documented in [1].<br>
><br>
><br>
> Thanks and good luck,<br>
><br>
> Paul<br>
><br>
><br>
> [1] <a href="http://intellinuxgraphics.org/how_to_report_bug.html" target="_blank">http://intellinuxgraphics.org/how_to_report_bug.html</a><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Intel-gfx mailing list<br>
> <a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
><br>
_______________________________________________<br>
Intel-gfx mailing list<br>
<a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
</div></div></blockquote></div><br></div>