[Intel-gfx] HD audio not working

[Takashi Iwai]

[Cc re-added, please don't drop Cc]

At Thu, 09 Aug 2012 04:00:07 +0200,
Øyvind Kvålsvoll wrote:
> 
> Patch tested now on alsa-1.0.25, compiled for 3.2.xx kernel.
> 
> Unfortunately this patch does not fix the problem, still only noise on 
> TrueHD and DTS-HD (on HDMI).

So it didn't change anything?

> It can play TrueHD and DTS-HD if decoded and output (on HDMI) to 
> multichannel PCM.
> The patch did not destroy anything, as far as I could verify during this 
> short test playing different format audio and video files.
> 
> I did not verify that the patch was actually embedded correctly.
> Alsa-version was verified by version and build date.

Don't trust anything from this 1.0.25 number.  It's just confusing.
It sticks for so long time although the code has been rewritten
largely.  That is, 1.0.25 isn't only 1.0.25.  Not like Highlander.
(I suggested Jaroslav to drop this numbering, but he didn't agree...)

For testing, try alsa-driver-snapshot tarball below.
  ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz

there you need to apply the patch in alsa-kernel directory with -p2.


thanks,

Takashi

> 
> 
> Øyvind Kvålsvoll
> (+47) 41306243
> N-6008 Ålesund, Norway
> 
> 
> On 08.08.2012 09:31, Takashi Iwai wrote:
> > At Wed, 08 Aug 2012 00:33:56 +0200,
> > Øyvind Kvålsvoll wrote:
> >> Ref. to filed bug https://bugs.freedesktop.org/show_bug.cgi?id=49055:
> >>
> >> DTS-HD and Dolby TrueHD audio is not working in Intel Sandy Bridge.
> >> This must have been well known for quite some time now, and I consider
> >> this to be a serious error in the Intel driver.
> >> Due to this error it is not possible to play DTS-HD or Dolby-TrueHD on
> >> Linux.
> >>
> >> I have waited patiently several months for a fix, as I was confident
> >> that Intel knew about the problem and surely would fix this in the next
> >> driver release.
> >> I also have the understanding that quite many people are waiting for
> >> this fix.
> >>
> >> Seeing as the bug is filed, and someone has actually looked at it and
> >> identified the problem, is there a plan for further progress on this?
> > Could you check whether the test patch Xingchao posted in the last
> > week fixes your problem?
> > 	https://patchwork.kernel.org/patch/1256981/
> >
> > If this really cures, we can cook up it in a bit better form and merge
> > to the upstream.
> >
> >
> > thanks,
> >
> > Takashi
> >
>