From: Takashi Iwai <tiwai@suse.de>
To: Dan Aloni <da-x@monatomic.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, alsa-user@lists.sourceforge.net
Subject: Re: Kernel 2.6.22 + ALSA + Intel HDA = hda_codec: Unknown model
Date: Mon, 16 Jul 2007 12:05:37 +0200 [thread overview]
Message-ID: <s5h644ky87i.wl%tiwai@suse.de> (raw)
In-Reply-To: <20070714143615.GA20527@localdomain>
At Sat, 14 Jul 2007 17:36:15 +0300,
Dan Aloni wrote:
>
> On Sat, Jul 14, 2007 at 06:18:40AM -0400, Justin Piszcz wrote:
> > Hi all,
> >
> > I use an A-BIT AW9D-MAX motherboard and while the audio works fine using
> > the Intel HDA driver; however, I see this in dmesg:
> >
> > [ 29.188561] Advanced Linux Sound Architecture Driver Version 1.0.14
> > (Thu May 31 09:03:25 2007 UTC).
> > [ 29.188728] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low)
> > -> IRQ 17
> > [ 29.188822] PCI: Setting latency timer of device 0000:00:1b.0 to 64
> > [ 29.240729] hda_codec: Unknown model for ALC882, trying auto-probe from
> > BIOS...
> > ^^^^^^^^^^^^^
> > [ 29.280743] ALSA device list:
> > [ 29.280781] #0: HDA Intel at 0xfdff8000 irq 17
> >
> > 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
> > Definition Audio Controller (rev 01)
> >
> > Two lspci (-vx) listings attached.
> >
> > Can we get the PCI ID added to the kernel source so it does not say
> > unknown model?
>
> Actually, it is reported as unknown in a deeper probing level than
> PCI. I once made a patch that among other thing identified that
> A-BIT board exactly.
>
> http://mailman.alsa-project.org/pipermail/alsa-devel/2007-April/000441.html
>
> It is possible to take this patch, drop the other bits and just
> leave out the nice print that just tells it's A-BIT AW9D-MAX.
Your fixes are implemented in another way, so it should work as it is
on 2.6.23 once after alsa.git is merged -- except for (obviously
annoying-for-some-people) "unknown model" message. I'd say, simply
ignore it ;) It's no bug.
> Though AFAIK, ALSA maintainers have plans to move most of the
> probing code to userspace somehow so I'm not sure if it is
> quite relevant.
Yeah, we'd like to go in that way, but it gets stucked right now,
mainly due to lack of development time. A proto-type is availabe at
ftp://ftp.suse.com/pub/people/tiwai/hda-tools/
but not sure whether this development will be continued to the final
form or choose another method.
thanks,
Takashi
prev parent reply other threads:[~2007-07-16 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 10:18 Justin Piszcz
2007-07-14 14:36 ` Dan Aloni
2007-07-16 10:05 ` 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=s5h644ky87i.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-user@lists.sourceforge.net \
--cc=da-x@monatomic.org \
--cc=jpiszcz@lucidpixels.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
all inboxes | Powered by JetHome®