I have an anoying problem which probably has a simple sollution. I recently recompiled my kernel, but decided not to use the newly created kernel. However, later when trying to install the atmel wlan driver i stumbled upon this error. When trying to run modprobe I got the error that kernel-module mismatched. It said that the module was compiled for kernel version 2.4.20-30.9custom while I'm running 2.4.20-30.9. I guess this is because when recompiling the kernel linux want to make it clear that I had done some changes in the configuration. So my question is, how do I fix this without having to run the recompiled kernel? I remember having read somewhere that it is possible to set the name of the new kernel somewhere. So could one sollution be to set the name to 2.4.20-30.9 and recompile the kernel again? Is there perhaps an even simpler way?

/Andreas

yeah , a simple way is to remove the trailing custom from the Makefile in your source directory when compiling a custom but same version kernel.

Other than that someone else may have a remedy.

You must have compiled the atmel driver for the custom kernel. Why not just recompile it for the current kernel?

Another solution, is to insmod --force the atmel module. This isn't the best idea since modprobe loads dependent modules and insmod will only get the specific module. I don't know if modprobing atmel loads other drivers but those would then need to be insmoded. If the atmel driver is the load driver loaded when you modprobe it then you can do the insmod --force and just ignore the kernel mismatch error message.

Also, it is always a good idea to give your custom compiled kernel a unique name. If you keep the current name and foobar everything you won't have a good kernel to boot into. If you foobar the custom kernel and have given it a custom name you can always boot back into the good kernel.

I suggest you to reinstall the source of your kernel and recompile the atmel driver after that. Should fix the problem.