From mboxrd@z Thu Jan 1 00:00:00 1970 From: giggz Subject: Re: [Regression] With the new 2.6.33 when I plug in headphones, the speakers don't turn off anymore Date: Sat, 27 Feb 2010 14:35:23 +0100 Message-ID: References: <1267176828.3751.12.camel@mattotaupa> <1267184543.3802.13.camel@mattotaupa> <4B87D414.5050409@gmail.com> <1267223682.3648.16.camel@mattotaupa> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by alsa0.perex.cz (Postfix) with ESMTP id 9A9291037F7 for ; Sat, 27 Feb 2010 14:33:05 +0100 (CET) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NlMn3-0003Yn-5W for alsa-devel@alsa-project.org; Sat, 27 Feb 2010 14:33:05 +0100 Received: from c165127.adsl.hansenet.de ([213.39.165.127]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Feb 2010 14:33:05 +0100 Received: from giggzounet by c165127.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Feb 2010 14:33:05 +0100 In-Reply-To: <1267223682.3648.16.camel@mattotaupa> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Paul Menzel a =E9crit : > Am Freitag, den 26.02.2010, 15:00 +0100 schrieb giggzounet: >> Paul Menzel a =E9crit : >>> Am Freitag, den 26.02.2010, 12:15 +0100 schrieb giggzounet: >>>> [snip] >>>> >>>>>> I do not know why enable_msi is set to =BB-1=AB 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 >>>>>> [=85] >>>>>> parm: enable_msi:Enable Message Signaled Interrupt= (MSI) (int) >>>>>> [=85] >>>>>> >>>>> I have modified /etc/modprobe.d/sound with : >>>>> snd-hda-intel index=3D0 enable_msi=3D0 >>>>> >>>>> I attach the log of alsa-info. >>>>> >>>> I have forgotten to say that the problem is always here with >>>> enable_msi=3D0 >>>> >>>> [snip] >>> That=92s unfortunate. It would have been nice if this had fixed it. >> I have take a look to the history of changes of hda_intel.f and found th= at : >> http://git.kernel.org/?p=3Dlinux/kernel/git/torvalds/linux-2.6.git;a=3Dc= ommit;h=3D0a27fcfaaf61108d94f0377f91bed81b2dd35f52 >> >> in the source I'm seeing a blacklist : >> /* >> * white/black-list for enable_msi >> */ >> static struct snd_pci_quirk msi_black_list[] __devinitdata =3D { >> SND_PCI_QUIRK(0x1043, 0x81f2, "ASUS", 0), /* Athlon64 X2 + nvidia */ >> SND_PCI_QUIRK(0x1043, 0x81f6, "ASUS", 0), /* nvidia */ >> {} >> }; >> >> And on my eeepc 1201n there is lot's of nvidia things...How can I know >> if I'm on this blacklist or not ? ...sorry, I don't have a lot of >> knowledge in C. But this could be explain why msi is not enabled by >> default... > = > Just to make it clear. I am also stabbing in the dark here and do not > know what those options actually do. I just saw the difference in the > outputs of `alsa-info.sh`. Maybe you can try to load `snd-hda-intel` > with `enable_msi=3D1` to enable it explicitly and try it? But I emphasize > again that this MSI issue might not be related to your problem at all. > = > Anyway, looking at the output of `alsa-info.sh` which executes I think > `lspci -vnn` we find your IDs. (I just looked through the file and > =93grepped=94 it just to include it here. > = > $ grep "PCI Vendor" -A4 alsa-info_2.6.33.log = > !!Advanced information - PCI Vendor/Device/Susbsystem ID's > !!-------------------------------------------------------- > = > 00:08.0 0403: 10de:0ac0 (rev b1) > Subsystem: 1043:83ce > = > So those quirks you listed do not apply to your system. Searching for > your device ID=92s in the tree reveals the following. > = > sound-2.6/sound/pci/hda$ grep -Ri 83ce * > patch_realtek.c: SND_PCI_QUIRK(0x1043, 0x83ce, "ASUS P1005HA", AL= C269_DMIC), > = > `ALC269_DMIC` turns up in `patch_realtek.c` in the following places. > = > sound-2.6/sound/pci/hda$ more patch_realtek.c = > /* > * configuration and preset > */ > static const char *alc269_models[ALC269_MODEL_LAST] =3D { > [ALC269_BASIC] =3D "basic", > [ALC269_QUANTA_FL1] =3D "quanta", > [ALC269_AMIC] =3D "laptop-amic", > [ALC269_DMIC] =3D "laptop-dmic", > [ALC269_FUJITSU] =3D "fujitsu", > [ALC269_LIFEBOOK] =3D "lifebook", > [ALC269_AUTO] =3D "auto", > }; > [=85] > [ALC269_DMIC] =3D { > .mixers =3D { alc269_laptop_mixer }, > .cap_mixer =3D > alc269_laptop_digital_capture_mixer, > .init_verbs =3D { alc269_init_verbs, > alc269_laptop_dmic_init_verbs }, > .num_dacs =3D ARRAY_SIZE(alc269_dac_nids), > .dac_nids =3D alc269_dac_nids, > .hp_nid =3D 0x03, > .num_channel_mode =3D ARRAY_SIZE(alc269_modes), > .channel_mode =3D alc269_modes, > .unsol_event =3D alc269_laptop_unsol_event, > .setup =3D alc269_laptop_dmic_setup, > .init_hook =3D alc269_laptop_inithook, > }, > = > But I have not clue what that all does. I do not know if and when > Takashi or some other dev will have time to answer, but until then you > could ask on IRC or try to figure out if something changed there or in > the function it calls. I think `git annotate` comes to your rescue here. > = THx for all these infos. that helps me to start! > = > Sorry, that I cannot help you further. Thanks, > = no problem! You already have helped me a lot! I will wait for the developper. And take a look to the source. Bye bye Guillaume