From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755559Ab0GUFqO (ORCPT ); Wed, 21 Jul 2010 01:46:14 -0400 Received: from cantor.suse.de ([195.135.220.2]:33464 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751200Ab0GUFqI (ORCPT ); Wed, 21 Jul 2010 01:46:08 -0400 Date: Wed, 21 Jul 2010 07:46:07 +0200 Message-ID: From: Takashi Iwai To: davidjonx@gmail.com Cc: "linux-kernel@vger.kernel.org" Subject: Re: Multiple Codec Problem With Intel HD Audio In-Reply-To: <4C4672D4.9030400@gmx.com> References: <4C432E1D.3000703@gmx.com> <4C4672D4.9030400@gmx.com> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.1 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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