alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: giggzounet <giggzounet@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [Regression] With the new 2.6.33 when I plug in headphones, the speakers don't turn off anymore
Date: Fri, 26 Feb 2010 13:09:05 +0100	[thread overview]
Message-ID: <4B87B9E1.4040809@gmail.com> (raw)
In-Reply-To: <1267184543.3802.13.camel@mattotaupa>

Paul Menzel a écrit :
> Am Freitag, den 26.02.2010, 12:15 +0100 schrieb giggzounet:
>> [snip]
>>
>>>> I do not know why enable_msi is set to »-1« and not one since it should
>>>> be enabled by default now [1]. Could you try to load the sound module
>>>> with `enable_msi` set to `0` and report back your findings, please.
>>>>
>>>>         $ sudo modinfo snd-hda-intel
>>>>         […]
>>>>         parm:           enable_msi:Enable Message Signaled Interrupt (MSI) (int)
>>>>         […]
>>>>
>>> I have modified /etc/modprobe.d/sound with :
>>> snd-hda-intel index=0 enable_msi=0
>>>
>>> I attach the log of alsa-info.
>>>
>> I have forgotten to say that the problem is always here with
>> enable_msi=0
>>
>> [snip]
> 
> That’s unfortunate. It would have been nice if this had fixed it.
> 
> I CC Takashi, since he is the author of [1]. Maybe he can tell us if it
> is related.
> 
> The only relevant(?) difference there is the following.
> 
>         $ diff -u alsa-info_2.6.32.9.log alsa-info_2.6.33_enable_msi.log
>         […]
>         @@ -85,11 +85,12 @@
>          
>          !!Module: snd_hda_intel
>          	bdl_pos_adj : 32,-1,-1,-1,-1,-1,-1,-1
>         +	beep_mode : 1,1,1,1,1,1,1,1
>         […]
> 
> The only other thing I can think of is, that you go trough the commit
> log yourself and try to figure out what changed regarding to your
> chipset and CODEC.
> 
> And last not least you could try DebPkg:libasound2 from unstable and see
> if this changes anything. Although I guess it will not.
> 

I'm using the libasound2 from lenny-backport version 1.0.21. Also it is
not very far from the one in unstable (1.0.22).

> 
> Thanks,
> 
> Paul
> 
> 
> [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=71623855e20c3febebb5fa60528cde2592678bd5
> 

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

  reply	other threads:[~2010-02-26 12:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  9:03 [Regression] With the new 2.6.33 when I plug headphones, the speaker doen't get off anymore giggzounet
2010-02-26  9:33 ` [Regression] With the new 2.6.33 when I plug in headphones, the speakers don't turn " Paul Menzel
2010-02-26 11:12   ` giggzounet
2010-02-26 11:15     ` giggzounet
2010-02-26 11:42       ` Paul Menzel
2010-02-26 12:09         ` giggzounet [this message]
2010-02-26 14:00         ` giggzounet
2010-02-26 22:34           ` Paul Menzel
2010-02-27 13:35             ` giggz
2010-02-27 13:29       ` giggz
2010-02-27 13:59 ` [Regression] With the new 2.6.33 when I plug headphones, the speaker doen't get " giggz
2010-02-28 14:29   ` giggz
2010-03-01 13:31     ` Takashi Iwai
2010-03-01 13:44       ` giggzounet
2010-03-01 18:06       ` giggz

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=4B87B9E1.4040809@gmail.com \
    --to=giggzounet@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;
as well as URLs for NNTP newsgroup(s).