Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Pemberton <cjpembo@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Lenovo 3000 N100 Laptop quirk
Date: Sat, 08 Sep 2007 01:06:25 -0500	[thread overview]
Message-ID: <46E23BE1.3030708@gmail.com> (raw)
In-Reply-To: <s5hmyvyhwb5.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Thu, 06 Sep 2007 22:09:37 -0500,
> Chris Pemberton wrote:
>   
>> To enable sound on a Lenovo 3000 N100 laptop...
>>
>> In patch_realtek.c (near line # 10882):
>>
>> Change:
>>
>> SND_PCI_QUIRK(0x17aa, 0x2066, "Lenovo", ALC861VD_LENOVO),
>>
>> to:
>>
>> SND_PCI_QUIRK(0x17aa, 0x2066, "Lenovo 3000 N100", ALC861VD_3ST),
>>     
>
> Hm, that's bad.  ALC861VD_LENOVO is exactly for your laptop model, so
> it has to be fixed.
>
> What is exactly a problem?  Could you figure out which codec setting
> may trigger the problem by comparing codec#* file between these
> models?
>
> And, above all, which ALSA version are you using and how did you test
> it?  The latest version, and the output from both HP and spekaer?
>
>
> thanks,
>
> Takashi
>
>   
I used the most resent alsa-driver snapshot, but I did the modification 
I detailed above.  This has been my method of getting alsa to work for a 
few months now.

My ALSA information, based on yesterday's snapshot and my modification, 
is located at http://pastebin.ca/686568

I will get those codecs that you are asking for this weekend:  one with 
my modification and the other with whatever the latest snapshot has by 
default.

Let me know what else you need.

Thanks,

Chris

  reply	other threads:[~2007-09-08  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  3:09 Lenovo 3000 N100 Laptop quirk Chris Pemberton
2007-09-07 23:47 ` Takashi Iwai
2007-09-08  6:06   ` Chris Pemberton [this message]
2007-09-11  7:31   ` Chris Pemberton

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=46E23BE1.3030708@gmail.com \
    --to=cjpembo@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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