Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161250AbXAHMDz (ORCPT ); Mon, 8 Jan 2007 07:03:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161252AbXAHMDz (ORCPT ); Mon, 8 Jan 2007 07:03:55 -0500 Received: from mx1.suse.de ([195.135.220.2]:43855 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161253AbXAHMDy (ORCPT ); Mon, 8 Jan 2007 07:03:54 -0500 Date: Mon, 08 Jan 2007 13:03:53 +0100 Message-ID: From: Takashi Iwai To: "J.A. =?UTF-8?B?TWFnYWxsw7Nu?=" Cc: "Linux-Kernel, " Subject: Re: Question on ALSA intel8x0 In-Reply-To: <20070107012927.1fdcf8f3@werewolf-wl> References: <20070107012927.1fdcf8f3@werewolf-wl> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta27) (fiddleheads) (+CVS-20060704) (i386-suse-linux) 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 X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1579 Lines: 39 At Sun, 7 Jan 2007 01:29:27 +0100, J.A. =?UTF-8?B?TWFnYWxsw7Nu?= wrote: > > Hi... > > I have a curious issue with snd_intel8x0 ALSA driver: > > Jan 7 01:14:27 werewolf-wl kernel: ACPI: PCI interrupt for device 0000:00:1f.5 disabled > Jan 7 01:14:27 werewolf-wl kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 21 > Jan 7 01:14:27 werewolf-wl kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 > Jan 7 01:14:27 werewolf-wl kernel: AC'97 0 analog subsections not ready > Jan 7 01:14:27 werewolf-wl kernel: intel8x0_measure_ac97_clock: measured 50136 usecs > Jan 7 01:14:27 werewolf-wl kernel: intel8x0: measured clock 219 rejected > Jan 7 01:14:27 werewolf-wl kernel: intel8x0: clocking to 48000 > > And this file is created: > > /dev/.udev/failed/class@sound@controlC0 > > What does this 'failed' mean ? Why is my card 'not ready' ? Judging from the kernel message, the driver looks OK except that the clocking measurement doesn't work properly (I guess it's built-in?). So, it's rather a user-space issue (e.g. missing stuff in initrd). > Sound works, anyways. > > BTW, before alsa driver loads, I hear a strange whisper through the speakers, > nothing since the sound subsystem is initialized. Bad connections ? Does it happen with a cold boot or at any boot sequence? Takashi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/