public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Santinoli <david@santinoli.com>
Subject: Re: ALSA: hda/realtek: quirk for D945GCLF2 mainboard
Date: Sun, 9 May 2010 01:24:08 +0200	[thread overview]
Message-ID: <201005090124.11811.s.L-H@gmx.de> (raw)
In-Reply-To: <s5hiq70rtlc.wl%tiwai@suse.de>

[-- Attachment #1: Type: Text/Plain, Size: 743 bytes --]

Hi

On Sunday 09 May 2010, Takashi Iwai wrote:
> At Fri, 7 May 2010 02:59:01 +0200,
> Stefan Lippers-Hollmann wrote:
> > On Friday 07 May 2010, Takashi Iwai wrote:
> > > At Thu, 29 Apr 2010 23:00:42 +0200,
> > > Stefan Lippers-Hollmann wrote:
> > > > Hi
> > > > Since kernel 2.6.33 (and including 2.6.34-rc5-git10), sound output is 
> > > > broken on my Intel D945GCLF2 mainboard, while it did work well on earlier
> > > > kernels up to and including 2.6.32.12.
[...]

> Could you try probe_mask=4 option without reverting?
> I don't find any wrong verb with the quirk, so this looks more like a
> problem in the slot probing.

Unfortunately I can't observe any improvement with probe_mask=4, logs 
attached.

Regards
	Stefan Lippers-Hollmann

[-- Attachment #2: alsa-info_plain-probe_mask-4-2.6.34-rc6-git5.log.gz --]
[-- Type: application/x-gzip, Size: 2434 bytes --]

[-- Attachment #3: dmesg_plain-probe_mask-4-2.6.34-rc6-git5.log.gz --]
[-- Type: application/x-gzip, Size: 8477 bytes --]

  reply	other threads:[~2010-05-08 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 21:00 ALSA: hda/realtek: quirk for D945GCLF2 mainboard Stefan Lippers-Hollmann
2010-05-06 10:50 ` Takashi Iwai
2010-05-07  0:59   ` Stefan Lippers-Hollmann
2010-05-07  8:42     ` Takashi Iwai
2010-05-08 23:24       ` Stefan Lippers-Hollmann [this message]
2010-05-10 15:18         ` Takashi Iwai

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=201005090124.11811.s.L-H@gmx.de \
    --to=s.l-h@gmx.de \
    --cc=david@santinoli.com \
    --cc=linux-kernel@vger.kernel.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