[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hhbjblscn.wl%tiwai@suse.de>
Date: Tue, 03 Aug 2010 15:48:40 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Leandro Lucarella <luca@...cax.com.ar>
Cc: linux-kernel@...r.kernel.org, Jaroslav Kysela <perex@...ex.cz>,
Kailang Yang <kailang@...ltek.com>,
Daniel T Chen <crimsun@...ntu.com>,
alsa-devel@...a-project.org
Subject: Re: Regression 2.6.35: Intel N10/ICH 7 Family HDA (Realtek ALC662 rev1) beep broken
At Tue, 3 Aug 2010 10:44:09 -0300,
Leandro Lucarella wrote:
>
> > Please give alsa-info.sh output.
>
> I didn't know where to find the script,
It's listed in Documentation/sound/alsa/HD-Audio.txt :)
> Google gave me this:
> http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh
> So this is what I've use. I've shared the results at:
> http://www.alsa-project.org/db/?f=6a051da2475c7246f40c493a310fecb0a1a289f5
>
> > > I've tried to naively (I'm not a kernel hacker, so I was just guessing) add a
> > > new entry with the quirks beep_white_list by copying the entry for ASUS like
> > > this:
> > >
> > > diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> > > index 596ea2f..ca3ed12 100644
> > > --- a/sound/pci/hda/patch_realtek.c
> > > +++ b/sound/pci/hda/patch_realtek.c
> > > @@ -5183,6 +5183,7 @@ static void fillup_priv_adc_nids(struct hda_codec *codec, hda_nid_t *nid
> > >
> > > static struct snd_pci_quirk beep_white_list[] = {
> > > SND_PCI_QUIRK(0x1043, 0x829f, "ASUS", 1),
> > > + SND_PCI_QUIRK(0x8086, 0xd613, "INTEL", 1),
> > > {}
> > > };
> > >
> > > But it didn't work either.
> >
> > Hm, this should work. At least, you should have beep mixer & co with
> > this.
>
> Well, my bad, I booted the wrong kernel when trying the patch. The patch
> works correctly, so I'll be very glad if it hits Linus kernel soon :)
>
> I could send you the patch but I don't know exactly what to put in the
> commit message. The problem is the same as the one with the ASUS P5-V?
I can add such a trivial patch manually, of course. But I'd need
to know which machine you have (vendor/model name, etc).
thanks,
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists