Detecting different Audio Chip what manual says

Joseph_sys

Two problems.

1.)
I just replaced my mother board (old Soyo motherboard went down) so I got Biostar M7VIG 400.
The manual says it has C-Media CMI9761A sound chip
When I run lspci it reports VIA Technologies audio controller:
Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)

Is it because there is no support for CMI9761A chip in Linux yet?

2.)
I've compiled INTO the kernel 2.6.11.10 support for Alsa PCI Via controller.
When I try to restart alsasound /etc/init.d/alsasound restart I get
Loading ALSA modules...
* Loading: snd-card-0...
FATAL: Module snd_cmipci not found.

cmipci chip set used to be in old Soyo motherboard. I've changed dirver in /etc/modules.d/alsa to via82xx:
alias snd-card-0 snd-via82xx
alias sound-slot-0 snd-via82xx

but it still tries to load cmipci, where is it taking this information from.

I know it will not work if I have chip CMI9761A but since it is reporting VT8233/A/8235/8237 I'm trying to test if it will work.

3.)
My LAN controller according to the manual is: PHY VIA VT6103 but the system is reporting VT6102:
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)

Just makes me wander why there are such discrepancies.

djpenguin · Guru Joined: 02 Sep 2004 Posts: 386

1) lspci is reading the BIOS and getting a response from the southbridge where the C-media chip is attached. It's supposed to look like that, don't worry about it.

2) Is it compiled as a module or into the kernel? Because that error message is the result of ALSA trying to load a module.

3) No clue about that, perhaps it's a slightly newer board revision.

Joseph_sys · Posted: Mon Jun 06, 2005 12:09 am Post subject:

djpenguin · Guru Joined: 02 Sep 2004 Posts: 386

If it's compiled into the kernel, you don't need to do anything to the /etc/modules.d/alsa file, and you also don't need to have the alsasound init script running. That mismatch is probably what's causing the trouble.

However, you'll lose mixer settings with every shutdown with ALSA compiled in-kernel, so the best thing to do woud be to compile ALSA as a kernel module and let the alsasound init script handle saving the mixer settings.