Re: [Alsa-user] alsamixer issues?

[<ad...@yg...>]

pri...@bi... wrote:
> Can anyone give me a hand with the following problem?
> 
> I installed a new 2.4.18 kernel image today, upgrading from my 2.4.17 
> image. After I installed this, alsa broke, refusing to load at 
> boot-time, claiming that the alsa driver could not be found. This 
> required a full re-compile and install of alsa.

The modules for each new kernel are stored in /lib/modules/x.y.zz (where x.y.zz == 2.4.17, 2.4.18, etc), so when you install a new kernel you have to also install all the modules it needs.  If you're using add-on modules (not part of the main kernel tree) like ALSA in 2.4 then you have to rebuild them.

(You *might* be able to copy the ALSA module .o files from /lib/modules/2.4.17 to /lib/modules/2.4.18, but it's safest to rebuild.)

> #alsamixer: function_snd_ctl_open failed for default: No such file or
> 	directory

> This isn't a permissions problem, as the same happens when I am logged 
> in as root. The alsa drivers for my sound card (snd-card-es1968 - 
> Terratec SoundSystem DMX) are loaded on bootup

In ALSA 0.9.12 the card modules are now called snd-* instead of snd-card-* - hence the card driver is probably not being loaded, and hence the device node (in /proc/asound/dev) is not being created - thus the error above.

Hope this helps...

-- A.