On 29-11-07 10:15, ashok.shanmugam@xxxxxxxxx wrote:
Is there anything to do with the kernel .config file and kernel modules?
Because the same kernel modules which were running properly gives me
"invalid module format" on the same kernel with few changes made in the
.config file.
Well, yes, generally the kernel and modules are (and should be) compiled at
the same time and they do things like enforcing that they're compiled for
the kernel you're trying to load them into and with compatible options.
Actually the earlier kernel wasn't compiled with debug options. Now i
wanted to build the kernel with all hacking options enabled. So i
changed the .config file, but the earlier modules are not loading with
this debug kernel. As i don't have the src code of kernel modules, i've
become panic.
Yes, well, you've run into the main problem with binary modules. When you
use any you cannot just replace your kernel whenever you feel like it
yourself but have made yourself dependent on the range of kernels the module
supplier provides you modules for.
The more widespread binary modules (say, nvidia) provide the module as a
binary library with source surroundings so that you can at least recompile
for small differences but even then something like rmap (when it was
introduced in 2.4) or 4K kernel stacks can mean you're out of luck.
The fortunate side-effect of this is that you can ignore all the principled
and/or legal objections to closed source modules since using any is simply
totally unacceptable from a practical standpoint already. Hurrah!
Good luck...
Rene.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
