mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Leandro Lucarella <luca@llucax.com.ar>
Cc: linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Kailang Yang <kailang@realtek.com>,
	Daniel T Chen <crimsun@ubuntu.com>,
	alsa-devel@alsa-project.org
Subject: Re: Regression 2.6.35: Intel N10/ICH 7 Family HDA (Realtek ALC662 rev1) beep broken
Date: Tue, 03 Aug 2010 17:24:11 +0200	[thread overview]
Message-ID: <s5h7hk7lnxg.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100803144810.GD3508@llucax.com.ar>

At Tue, 3 Aug 2010 11:48:10 -0300,
Leandro Lucarella wrote:
> 
> Takashi Iwai, el  3 de agosto a las 15:48 me escribiste:
> > 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 :)
> 
> Woops!
> 
> > > 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).
> 
> Is a desktop box.
> CPU Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz
> Motherboard Intel Corporation DG41RQ

OK, it's fine, I just wanted to be sure that it's no other brand.
The fix is now applied to sound tree, and will be included in the next
pull request, then will reach to stable tree.


thanks,

Takashi

  reply	other threads:[~2010-08-03 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  4:00 Leandro Lucarella
2010-08-03  5:42 ` Takashi Iwai
2010-08-03 13:44   ` Leandro Lucarella
2010-08-03 13:48     ` Takashi Iwai
2010-08-03 14:48       ` Leandro Lucarella
2010-08-03 15:24         ` Takashi Iwai [this message]
2010-08-03 16:00           ` Leandro Lucarella

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=s5h7hk7lnxg.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=crimsun@ubuntu.com \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@llucax.com.ar \
    --cc=perex@perex.cz \
    /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®