On Thu, 2004-01-08 at 17:55, Bill Kenworthy wrote: > was probably me, and that has been fixed (I bugziller'd it) Kernel > builds should always install modules into new directories, but there > have been a couple of instances where in the rush to get a bugfix out, > they didnt increment the version correctly. Check the version and > extraversion parameters in the kernel Makefile if you are paranoid ... > > BillK > Ah, so it's in the Makefile and not the .config file. No wonder I didn't find it.
I am a bit troubled by this idea that the modules are supposed to go into separate directories. The idea is great, but it doesn't explain why I cannot seem to keep multiple working versions of Alsa on my system. Here's what I see - why doesn't Alsa always work? 1) I build a kernel, like 2.4.20-r1, and I build Alsa, and everything works. Presumably Alsa is in a directory 2.4.20-r1. I have directories named like that in /lib/modules. 2) I build a new kernel, like 2.4.20-r5, and I build Alsa again. Alsa works and is presumably in a directory named 2.4.20-r5. 3) I decide to reboot into 2.4.20-r1 and what I find is that Alsa no longer works. Why? If the directories are both there, why doesn't Alsa still work for both? Maybe I'm doing something wrong somewhere that I need to learn about. Thanks! Mark -- [EMAIL PROTECTED] mailing list
