From: Takashi Iwai <tiwai@suse.de>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: "Linux-Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: Question on ALSA intel8x0
Date: Mon, 08 Jan 2007 13:03:53 +0100 [thread overview]
Message-ID: <s5hk5zxwwra.wl%tiwai@suse.de> (raw)
In-Reply-To: <20070107012927.1fdcf8f3@werewolf-wl>
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
prev parent reply other threads:[~2007-01-08 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 0:29 Question on ALSA intel8x0 J.A. Magallón
2007-01-08 12:03 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hk5zxwwra.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).