lost snd-mix after kernel update

I have Opensuse 10.3 and after update of kernel on 2.6.22 I lost my snd-mix. I can hear sound but without volume control. It si by default on middle volume.
snd-mix is not listed in output of lsmod command.



Do you mean snd-mixer-oss? When I search for all snd occurences on my openSUSE-10.3:
rpm -qa --filesbypkg | grep snd
I noted only the snd-mixer-oss.ko and snd-mixart.ko sound modules:


I find no such “snd-mix” module.

Did you perhaps change your alsa modules after a kernel update? To investigate that possibility, how about checking if any recent updates to your kernel resulted in a downgrade of your alsa? I think < not sure > that if a replacement alsa was installed, it will show up if you type:
rpm -qa --last | grep alsa

… also, for completeness, on my openSUSE-10.3 PC, when I type “lsmod |grep snd” I get:

oldcpu@stonehenge:~> lsmod | grep snd
snd_pcm_oss            50432  0
snd_mixer_oss          20096  1 snd_pcm_oss
snd_seq_midi           13440  0
snd_seq_midi_event     10880  1 snd_seq_midi
snd_seq                54452  2 snd_seq_midi,snd_seq_midi_event
snd_intel8x0           36636  1
snd_ac97_codec         97060  1 snd_intel8x0
ac97_bus                6272  1 snd_ac97_codec
snd_pcm                82564  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              26756  2 snd_seq,snd_pcm
snd_mpu401             12684  0
snd_mpu401_uart        12416  1 snd_mpu401
snd_rawmidi            28416  2 snd_seq_midi,snd_mpu401_uart
snd_seq_device         12172  3 snd_seq_midi,snd_seq,snd_rawmidi
snd                    58164  14 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore              11460  1 snd
snd_page_alloc         14472  2 snd_intel8x0,snd_pcm

I put “snd-mix” module because I was reported by alsamixergui that snd-mix cannot be loaded.
Actually, when I do : lsmod
there is no snd-mix-oss module and loudspeaker icon does not appear on the right side of taskbar on my desktop. I hear sound but with default values.
I cannot sart alsamixer in terminal too.

I did not configure anything on alsa, update of kernel was done automatically and I di dnot interfere in anything; just noticed that mixer is missing and that sound volume is not possible to increase.

When I type lsmod |grep snd I get:
snd_seq 66740 0
snd_seq_device 24460 1 snd_seq
snd_hda_intel 285596 1
snd_pcm 94852 1 snd_hda_intel
snd_timer 39044 2 snd_seq,snd_pcm
snd 70452 7 snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
soundcore 23748 1 snd
snd_page_alloc 26760 2 snd_hda_intel,snd_pcm

please advise.

Best wishes,


You do not have to “configure anything”. It CAN “just happen” dependent on what version of alsa you had in place before the kernel update, and dependent on what dependencies that alsa version had with the existing kernel.

Seeing what kernel modules you have loaded is helpful, but I need more. I need the alsa application/driver information I asked. ie specifically:

No worries (from my point of view) if you can’t do that. Without that data, maybe someone else will chime in and help you.

Good luck in your efforts.

After issuing command
rpm -qa --last | grep alsa
I got the following output:
java-1_5_0-sun-alsa-1.5.0_update15-0.1 Wed Jul 2 11:34:58 2008
alsa-plugins-jack-1.0.15-2.1 Wed Jul 2 02:54:33 2008
alsa-firmware-1.0.15-4.1 Wed Jul 2 02:52:05 2008
alsa-plugins-1.0.15-2.1 Wed Jul 2 02:48:35 2008
alsa-utils-1.0.15-2.1 Wed Jul 2 02:46:48 2008
alsa-1.0.15-16.1 Wed Jul 2 02:44:42 2008
java-1_6_0-sun-alsa-1.6.0.u6-3.1 Wed Jul 2 02:27:45 2008
alsamixergui-0.9.0rc1-644 Wed Jul 2 02:27:21 2008
alsa-tools-gui-1.0.14-38 Wed Jul 2 02:27:19 2008
alsa-oss-1.0.14-23 Wed Jul 2 02:27:18 2008
alsa-plugins-samplerate-1.0.14-41 Wed Jul 2 02:27:16 2008
alsaplayer-0.99.80-1 Wed Jul 2 02:26:50 2008
alsa-plugins-pulse-1.0.14-41 Wed Jul 2 02:25:06 2008
alsa-driver-unstable-kmp-default- Thu Jun 19 23:16:53 2008
kalsatools-1.5.0-468 Thu Mar 13 14:31:43 2008
alsa-driver-kmp-default-1.0.16.hg20080301_2.6.22.17_0.1-1.1 Sun Mar 2 00:20:14 2008

I hope this helps.



I think
(1) you have the wrong versions of many of your apps, and
(2) you may have too many applications … or your update to the latest alsa was not done properly.
You have updated to alsa-driver-kmp-default to a 1.0.16 version, … but have not updated the remainder, but left them at 1.0.14 or 1.0.15. Why? Don’t you think that is opening your self up to possible version incompatibility problems.

Also, why so many alsa apps? for example, on my 11.0 pc my mixer (kmix) works well …

oldcpu@stonehenge2:~> rpm -qa | grep alsa

and on my 10.3 PC my alsa works well:

oldcpu@stonehenge1:~> rpm -qa | grep alsa

You can see I only have a fraction of the apps you have.

OK, what si your suggestion, what I have to do.
Is there any script to clean this up?



No. You added them manually. You will have to clean them up manually.

I replaced all alsa packages and install again. When I run alsaconf it is setup correctly and I was prompted that alsa is ready and volumes adjusted…
but I do not have sound again.

I gues that something else is probelm and that obviously system integration may be issue with big smp kernel for opensuse 10.3.

Best wishes,


I thought you could hear sound, but “without volume/mixer control”? Now you have no sound at all?

Please can you type the following in an xterm/konsole and post here the output, so I can see what you installed:
rpm -qa | grep alsa
rpm -qa | libasound2
cat /etc/modprobe.d/sound

and also run these two scripts, and post here the output URL that they will provide you:

wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && bash alsa-info.sh 

and for the following script enter your root password when prompted and type “NO” if you do not understand the question.

su -c 'wget -O tsalsa wget http://home.cfl.rr.com/infofiles/tsalsa && bash tsalsa' 

Don’t forget to post the URLs they provide here.

here is oputput of rpm -qa | grep alsa


here is output of
rpm -qa | grep libasound2

ANother output as you requested:
cat /etc/modprobe.d/sound

options snd-hda-intel enable=1 index=0

uniq.unknown_key:HDA Intel

alias snd-card-0 snd-hda-intel

result of first script:
general pastebin - vedran - post number 1061805

result of teh second script:
tsalsa.txt - nopaste.com (beta)

Yes, I do not hear any sound now :frowning:



Ok, thanks, its clear to see your problem is likely with the ALC268 hardware codec.

I note you are using a bigsmp. Do you really have a lot of RAM in your PC?

Anyway that aside, there have been a LOT of updates done to alsa to address the ALC268. A search on the alsa site reveals: Search results for alc268 - AlsaProject

So I recommend you update you version of alsa. To do that, open a konsole/xterm and with root permissions copy and paste in the following. Note these commands MUST be sent in the exact sequence shown.

zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_10.3/ multimedia
zypper install alsa alsa-utils alsa-tools alsa-firmware alsa-oss alsa-plugins alsa-plugins-jack libasound2
zypper rr multimedia
zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_10.3_Update/ multimedia
zypper install alsa-driver-kmp-bigsmp
zypper rr multimedia

Then reboot your PC, and test your sound (and check your mixer). If that does not work after installing and rebooting, then with that update in place, change your /etc/modprobe.d/sound file to be the following:

options snd-hda-intel enable=1 index=0
# uniq.unknown_key:HDA Intel
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=auto

and restart your alsa with rcalsasound restart and test your audio (and check your mixer).

and if that doesn’t work, replace “auto” with “toshiba” in the /etc/modprobe.d/sound file, … ie …change your /etc/modprobe.d/sound file to be the following:

options snd-hda-intel enable=1 index=0
# uniq.unknown_key:HDA Intel
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=toshiba

and restart your alsa with rcalsasound restart and test your audio (and check your mixer).


My sound is working now without changes to/etc/modprobe.d/sound.
Yes, I use bigsmp kernel. I have 1G of RAm and soon I will have another 1G of RAM. I guess that is enough.
When I Boot in normal kernel I do not have sound. I guess something else should be done, i.e. install driver for normal kernel.
It seems to me that update of kernel that I have had previously did not respect order that you practised and I firstly did not have mixer and after changing alsa I have had everything except sound.
Is it possibel to have sound in theboth kernels, if possible.

SHould I install alsa-driver for normal kernel and is there any special order to do that so nothing will be confused and mixed up?

Thanks, you are great :slight_smile:


I have 2G of RAM on my home PC, and I do not use bigsmp.

I had thought bigsmp was for much larger amounts of RAM, … ie > 3GB. Perhaps someone who knows more than I can correct me on this (please)! :smiley:

The alsa driver you install has to match your kernel! The commands I gave are for a bigsmp. If you change to a different kernel, then the commands will be different.

Please try the /etc/modprobe.d/sound change:

options snd-hda-intel enable=1 index=0
# uniq.unknown_key:HDA Intel
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=auto 

and restart alsa afterward. Please see my above post for more details. Note, if you run alsaconf, or go into yast > hardware > sound after doing the /etc/modprobe.d/sound edits, you will lose the edits (and possibly lose sound again).

Huh, I di dnot know that bigsmop requires so much RAM :frowning:
I am willing to return to my normal default kernel.

WHat are the commands to get sound working in normal kernel?

I Have edited /etc/modprobe.d/sound and sound is working
in bigsmp kernel as it woked before that change.



I recommend you start a new thread on this.

I believe you just need to install the default kernel, and it will replace the bigsmp kernel, but there could be many side affects such as:

  • breaking wireless;
  • breaking graphics;
  • breaking sound;
  • breaking webcam
  • break any virtual box/vmware setups
    Of course all of the above are fixable, but its best one is prepared.

I’m not even convinced it is necessary to move back to a “default” kernel. Maybe the “bigsmp” is fine.

Hence I recommend a new thread, so you get attention from users by virtue of a succinct and appropriate thread title, such that any recommendations I provide, will have a quality check by other users.

You noted your sound is back. How about your volume control? Is that working ok now?


So far my bigsmp works fine and I do not notice in my everyday work that machine is slower.
Thus, I will stick with it.
Now, I have in my normal kernel everything except sound which si not big issue.

yes, my volume control is back :slight_smile:
Thanks a million.

Best wishes,