Matt,

This doesn't show anything obvious to me. Is there anything here that's helpful?

# lsmod | grep snd
snd_hda_codec_nvhdmi     3720  1
snd_hda_intel          28648  2
snd_hda_codec          64872  2 snd_hda_codec_nvhdmi,snd_hda_intel

# lsmod | grep snd | cut -d ' ' -f 1 | xargs modinfo | grep parm
parm:           index:Index value for Intel HD audio interface. (array of int)
parm:           id:ID string for Intel HD audio interface. (array of charp)
parm:           enable:Enable Intel HD audio interface. (array of bool)
parm:           model:Use the given board model. (array of charp)
parm:           position_fix:Fix DMA pointer (0 = auto, 1 = none, 2 =
POSBUF). (array of int)
parm:           bdl_pos_adj:BDL position adjustment offset. (array of int)
parm:           probe_mask:Bitmask to probe codecs (default = -1).
(array of int)
parm:           probe_only:Only probing and no codec initialization.
(array of bool)
parm:           single_cmd:Use single command to communicate with
codecs (for debugging only). (bool)
parm:           enable_msi:Enable Message Signaled Interrupt (MSI) (int)
parm:           power_save:Automatic power-saving timeout (in second,
0 = disable). (int)
parm:           power_save_controller:Reset controller in power save
mode. (bool)

from
# lsmod | grep snd | cut -d ' ' -f 1 | xargs modinfo
all the parm values belong to the snd-hda-intel module.

Alistair

On Wed, Aug 12, 2009 at 10:57 AM, Matt Zagrabelny<mzagr...@d.umn.edu> wrote:
> On Mon, 2009-08-10 at 15:21 -0400, Alistair Boyle wrote:
>> Matt,
>>
>> Thanks for the reply.
>>
>> Please have a look at the alsa-info output I sent (attached to the
>> previous email). It includes the amixer output which shows no simple
>> mixer control that provides a "cenum" capability. The only input
>> control thats available is the "Digital" control which has a
>> "cvolume". This would indicate (I'd think) that there's probably an
>> alsa mismatch with the chipset since its not recognizing all the
>> capabilities of the board. Perhaps not surprising since the Studio 14
>> has only been around for a few months.
>>
>> Any further suggestions?
>
> Perhaps something like:
>
> lsmod | grep snd | cut -d ' ' -f 1 | xargs modinfo | grep parm
>
> to see what parameters there are out there for your modules. Perhaps
> they mention something about your hardware.
>
> --
> Matt Zagrabelny - mzagr...@d.umn.edu - (218) 726 8844
> University of Minnesota Duluth
> Information Technology Systems & Services
> PGP key 1024D/84E22DA2 2005-11-07
> Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2
>
> He is not a fool who gives up what he cannot keep to gain what he cannot
> lose.
> -Jim Elliot
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to