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=commitdif...