* Chris Howells (chrish@gmx.co.uk) [011110 11:01]: ->On Saturday 10 November 2001 17:51, Konstantin (Kastus) Shchuka wrote: -> ->> > I assume that the module is from ALSA. However, shouldn't the ALSA ->> > patches be in Hubert's kernel? ->> ->> alsa is not a patch, so it can't be there. SuSE keeps it in a separate ->> rpm. -> ->OK, so what I don't understand is why I should need to fiddle with this if I ->re-compile a new kernel? -> ->With my own 2.4.10 kernel, everything (including ALSA) was set up nicely. -> ->I compiled 2.4.13, and alsa no longer works. Do I need to reinstall SuSE's ->ALSA RPMs? -> ->Or must they be compiled against the current kernel version (and since SuSE's ->RPMS were against 2.4.10, it won't work?) I find this strange. I never recompiled the ALSA modules while going from 2.4.2 --> 2.4.7 .. I would delete the references to sound in modules.conf and then rerun alsaconf and it worked. I can't imagine that that .10 is so much different then .13 that you should have to do this. I would delete all references to sound...it looks something like this... -- options snd snd_cards_limit=1 snd_major=116 alias snd-card-0 snd-card-emu10k1 options snd-card-emu10k1 snd_id=card1 snd_index=0 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-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss -- It was at the end of the modules.conf file. After this rerun either YaST2 or alsaconf so the entries are remade. This should work. I then run depmod -a just to make sure everything is correct. I could be TOTALLY off base here, but it's worked for me. -----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "Technological progress is like an axe in the hands of a pathological criminal" -AE