nvidia MCP61 chipset variant + alsa-base.conf

mrmnemo · 07-24-2010, 08:11 AM

hi,

Just wondering if anyone could tell me how the models in alsa-base.conf ( see model list here )are configured.
My issue is: My volume is extremely low. I have tried telling alsa to load profile for 3stack and 6stack configurations. However, most of the models listed for acer seem to be laptops. In my case I am running a ACER aspire ASE380 I have tried a few of the acer model listings with moderate success. My system is running ALC888 ( is it possible that its being identified incorrectly by the system? ) with 6 analog stack + 1 optic + 1 coax + 1 front mic + 1 front head-phone.

I am wondering how the models differ from each other in the conf files. Can any one tell me where to look?

Thanks

Shadow_7 · 07-24-2010, 08:42 AM

Should they vary? I have an MCP61 on my old desktop. I had to do some trickery on OLDer versions of alsa, but no current issues that I'm aware of beyond 1.0.16 or newer. Some mixer stuff changed in 1.0.14 and 1.0.15. And I had to adjust the default periods when recording from it back then. But I would assume it's alright now. Given 1.0.23 is the most recent version. Not that I've used it since getting a Delta 44. AFAIK, the configuration (outside of your .asoundrc) is the same as any card.

something like this:

alias char-major-116 snd
alias char-major-14 soundcore
options snd major=116 cards_limit=3
options snd-hda-intel index=0
alias snd-card-0 snd-hda-intel

alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

mrmnemo · 07-24-2010, 12:17 PM

Quote:

Originally Posted by Shadow_7

Should they vary?

In my case it appears to. I had to add the below text to /etc/modprob.d/alsa-base.conf to get sound to an audible level.

Code:

options snd-hda-intel=acer

I would have thought that adding 6stack-dig would have addressed my issue. As it is, alsamixer is maxed out and un-muted with alsa 1.0.22 ( current ubuntu repo version. However, I have ran alsa 1.0.23 with no change to volume levels. Forcing the above model DID increase the volume; so, maybe I can tweak it a little more? I just dont know much about configuring drivers.

The user file you mentioned is for session based volume levels correct? Does it address per-session mod's for sound cards?

Thanks again for the help.

Shadow_7 · 07-24-2010, 12:45 PM

.asoundrc is for user based sound configuration. Mainly so apps can tell what you want for your default device and other 5.1 or more fancy configurations.

# modinfo snd-hda-intel

Code:

...
depends:        snd-pcm,snd-page-alloc,snd
vermagic:       2.6.26-2-686 SMP mod_unload modversions 686 
parm:           power_save:Automatic power-saving timeout (in second, 0 = disable). (int)
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, 3 = FIFO size). (array of int)
parm:           probe_mask:Bitmask to probe codecs (default = -1). (array of int)
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_controller:Reset controller in power save mode. (bool)

Perhaps that might help. That syntax of yours looks fishy. Perhaps

Code:

options snd-hda-intel id=acer

would work better. Although it might be assumed. Or you might have fat fingered your post.

$ lspci -n
and google on the vender:device number for that card might help. There are a few quirky snd-hda-intel cards out there. It is kind of the new kid on the block in terms of drivers. And it covers many versions of the same chipset.

mrmnemo · 07-24-2010, 01:46 PM

yeah, fat fingered. heheh
at work, will try the vendor lookup when i get home. THANKS!!

mrmnemo · 07-27-2010, 10:35 PM

so i have to check for each of these? or cant i get the info by the device ( and its role)?

Code:

@media-test:~$ lspci -n
00:00.0 0500: 10de:03ea (rev a1)
00:01.0 0601: 10de:03e0 (rev a2)
00:01.1 0c05: 10de:03eb (rev a2)
00:01.2 0500: 10de:03f5 (rev a2)
00:02.0 0c03: 10de:03f1 (rev a3)
00:02.1 0c03: 10de:03f2 (rev a3)
00:04.0 0604: 10de:03f3 (rev a1)
00:05.0 0403: 10de:03f0 (rev a2)
00:06.0 0101: 10de:03ec (rev a2)
00:08.0 0101: 10de:03f6 (rev a2)
00:09.0 0604: 10de:03e8 (rev a2)
00:0b.0 0604: 10de:03e9 (rev a2)
00:0c.0 0604: 10de:03e9 (rev a2)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:05.0 0400: 14f1:5b7a
01:06.0 0280: 1814:0301
01:09.0 0c00: 104c:8024
02:00.0 0300: 10de:0295 (rev a1)
03:00.0 0200: 11ab:4364 (rev 12)

thanks again man.

Shadow_7 · 07-29-2010, 02:11 PM

cross reference that list with the results of vanilla $ lspci -v
The first ##:##.# stays the same between the two lists.

If you google on the ####:####, you generally find results quicker specific to your card. Technically ffff:ffff since it's a hex number identifier.

$ lspci -v | grep -i "audio"

$ lspci -n

Shadow_7 · 07-29-2010, 02:14 PM

Technically the lspci -v name is pulled from this list.

http://pciids.sourceforge.net/

Although probably a snapshot in time of it on your installation. Not to be confused with lsusb, which is a different list and different identifier.