linux-kernel - Re: Multiple Codec Problem With Intel HD Audio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hwrspwfog.wl%tiwai@suse.de>
Date:	Wed, 21 Jul 2010 07:46:07 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	davidjonx@...il.com
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Multiple Codec Problem With Intel HD Audio

At Wed, 21 Jul 2010 09:38:52 +0530,
David John wrote:
> 
> > Yes, this looks like the issue.
> > 
> > A possible fix without much hustle would be to define mode quirks for
> > both codecs by checking the PCI SSID so that they won't conflict.
> 
> How would I go about doing this as the dmesg dump had the following:
> 
> > ALSA sound/pci/hda/patch_realtek.c:1287: realtek: *No valid SSID*,
> > checking pincfg 0x40000001 for NID 0x1d
> > ALSA sound/pci/hda/patch_realtek.c:1303: realtek: Enabling init
> > ASM_ID=0x0001 CODEC_ID=10ec0888

The SSID in the above is the codec SSID.  That can be different from
PCI SSID although they are identical in many cases.

Realtek codecs suppose that the codec SSID is set to represent the
hardware implementation status so that the driver can initialize
based on it.  The message above shows that your machine doesn't
provide such SSID (as many vendors don't follow that policy,
obviously).


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/