From: Takashi Iwai <tiwai@suse.de>
To: "David Gómez" <dabisu@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel8x0 still broken in 2.6.9-ac16
Date: Tue, 21 Dec 2004 11:20:01 +0100 [thread overview]
Message-ID: <s5h8y7suf5a.wl@alsa2.suse.de> (raw)
In-Reply-To: <ae4c71570412201519597d596a@mail.gmail.com>
At Tue, 21 Dec 2004 00:19:30 +0100,
David Gómez wrote:
>
> Hi Takashi ;),
>
> > The GLOB_STA register shows a weird value.
> > That's why codecs can't get probed.
> >
> > Could you try the attached patch and check the kernel messages?
>
> Here's the extract from the kernel logs after loading the modules:
>
> ...
> XXX GLOB_STA reads 0x00000100
> XXX GLOB_STA reads end: 0x00000100
> XXX codec probing: codecs = 1, glob_sta = 0x00700500
> intel8x0_measure_ac97_clock: measured 49474 usecs
> intel8x0: clocking to 48000
So, until this stage, the driver is working fine.
> ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 10 (level, low) -> IRQ 10
> PCI: Setting latency timer of device 0000:00:1f.6 to 64
> Unable to initialize codec #0
> Intel ICH Modem: probe of 0000:00:1f.6 failed with error -13
The modem initialization could conflict with the audio part.
Could you disable snd-intel8x0m driver?
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-21 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 22:54 Intel8x0 still broken in 2.6.9-ac16 David Gómez
2004-12-17 15:39 ` Takashi Iwai
2004-12-17 17:38 ` David Gómez
2004-12-20 18:14 ` Takashi Iwai
[not found] ` <ae4c71570412201519597d596a@mail.gmail.com>
2004-12-21 10:20 ` Takashi Iwai [this message]
[not found] ` <ae4c715704122111563be9a075@mail.gmail.com>
2004-12-22 14:53 ` Takashi Iwai
2004-12-22 19:22 ` David Gómez
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=s5h8y7suf5a.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dabisu@gmail.com \
/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