[Preston] Module/Kernel versions

[Guy]

If you set the CONFIG_MODVERSION to Y, surely that would make the kernel a 
bit more flexible in the modules it would load.
In Debian you can define a custom revision number for the kernel. maybe by 
applying the patch you have somehow changed the revision number? The kernel 
and modules revision numbers have to match especially if the modversion is 
not set.
Is there such a command in Mandrake as 'make modules_clean' that you could do 
before 'make menuconfig'. The 'Debian way' of kernel compilation is slightly 
different but I would have to use a similar command. This only really applies 
to modules that are not built into the kernel i.e third party or special 
modules that cannot be built in for whatever reason. (I have to put these in 
/usr/src/modules)

Just ideas :0)
-- 
Guy

On Wednesday 20 November 2002 3:01 pm, you wrote:
> I've installed Linux Mandrake9.0. All was ok.
> I downloaded the 2.4.19 kernel source tree from Mandrake site. I also
> downloaded a patch that enables packet-CD writing in 2.4.19. I then
> performed:
> make clean
> make menuconfig
> make dep
> make bzImage
> make modules
> make modules_install
>
> Now when I try to load any module, I get some message about "the module
> being compiled for linux-2.4.19-16mdk and the kernel version is
> linux-2.4.19-16.1mdk"
>
> I've tried the process several times but cant get rid of this message.
>
> I have CONFIG_MODVERSION set to N in my config.
>
> Any ideas chaps!?!
> TIA
> Daz
>