Re: 1.0.16->1.0.17 regression for some HDA NVidia's

["Ozan Çağlayan" <ozan@pardus.org.tr>]

Takashi Iwai wrote On 11-07-2008 20:54:
>
> To make sure: bdl_pos_adj=32 or higher doesn't work, too?
> Also, if you set bdl_pos_adj=0, do you get any warning messages?
>
> It's fine to take bdl_pos_adj=0 as default for Nvidia chips.  But,
> basically this value (when it's big enough) shouldn't disable the
> sound at all.
>   
I've tried the values (2,8,16,32,64,128,256,1024,2048,4096,8192).
When the parameter is set to 2048,4096 or 8192, here's the dmesg message 
we get:

ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
hda-intel: IRQ timing workaround is activated for card #0. Suggest a 
bigger bdl_pos_adj.
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096
ALSA ../alsa-kernel/pci/hda/hda_intel.c:1056: Too big adjustment 4096

The sound works well with those values.

The other small values avoid pulse to work correctly with ALSA.

When the parameter is set 0, the sound works well and the driver outputs 
this message:
hda-intel: IRQ timing workaround is activated for card #0. Suggest a 
bigger bdl_pos_adj.

2 MCP51 and 2 MCP61 users reported that setting the parameter to 0 
solves the incompatibility between alsa and pulse.

Thanks.


-- 
Ozan Çağlayan


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