All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: 1.0.16->1.0.17 regression for some HDA NVidia's
Date: Thu, 10 Jul 2008 19:41:45 +0300	[thread overview]
Message-ID: <48763BC9.40005@pardus.org.tr> (raw)
In-Reply-To: <s5h4p70vgae.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Tue, 08 Jul 2008 00:31:43 +0300,
> Ozan Çağlayan wrote:
>   
>> Takashi Iwai wrote:
>>     
>>> At Sun, 06 Jul 2008 19:18:01 +0300,
>>> Ozan Çağlayan wrote:
>>>   
>>>       
>>>> Everything seems OK with those onboard audio chipsets but there's 
>>>> absolutely no sound.
>>>> We have 2 bug reports on our bug tracking system indicating this 
>>>> regression for MCP51, MCP61 and MCP73.
>>>>
>>>> Here are the URL's for alsa-info.sh output's:
>>>>
>>>> MCP51: http://pastebin.ca/1062418
>>>> MCP61: http://pastebin.ca/1058482
>>>> MCP73: http://pastebin.ca/1058319
>>>>
>>>> Those users have recently reported that downgrading to 1.0.16 series 
>>>> solves the problem.
>>>>     
>>>>         
>>> Could you run alsa-info.sh on 1.0.16, too?  Then we can compare
>>> between working and non-working states.
>>>
>>>
>>> thanks,
>>>
>>> Takashi
>>>   
>>>       
>> Hi,
>>
>> I've also entered a bug report for this problem which includes the two 
>> outputs:
>>
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4038
>>     
>
> The first thing to check is that you are using pulse plugin.
> Is it intended, and confirmed to work?
>
> The next thing to check is whether 1.0.16 driver works with the same 
> environment (1.0.17 lib, utils, etc) -- that is, your 1.0.16 alsa-info
> output.  If yes, get alsa-info.sh output again, then install 1.0.17
> driver again and re-test.  Get alsa-info.sh output on 1.0.17 again
> (for non-working) to compare exactly.
>   
First the problem is not present when pulseaudio is stopped. And also, 
we can get sound with 1.0.17rc1 too. So briefly:

1.0.16 + pulse -> works well
1.0.17rc1 + pulse -> works well
1.0.17rc1,rc2 + pulse -> No sound.

It seems that something is broken for these chipsets in either alsa or 
pulse tree. Any ideas for your alsa-{driver,lib,plugins} part?

Thanks a lot.

-- 

Ozan Çağlayan
<ozan_at_pardus.org.tr>

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-07-10 16:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 16:18 1.0.16->1.0.17 regression for some HDA NVidia's Ozan Çağlayan
2008-07-07 16:00 ` Takashi Iwai
2008-07-07 21:31   ` Ozan Çağlayan
2008-07-08 10:09     ` Takashi Iwai
2008-07-10 16:41       ` Ozan Çağlayan [this message]
2008-07-11  4:47         ` Takashi Iwai
2008-07-10 21:26           ` Ozan Çağlayan
2008-07-11 17:54             ` Takashi Iwai
2008-07-11  6:31               ` Ozan Çağlayan
2008-07-11 21:25                 ` Takashi Iwai
2008-07-11 11:31                   ` Ozan Çağlayan
2008-07-13  6:45                     ` Hans-Frieder Vogt
2008-07-14  6:47                       ` Takashi Iwai
2008-07-15 20:54                         ` Hans-Frieder Vogt
2008-07-16 10:49                           ` 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=48763BC9.40005@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.