copying modules from one system to another?

syvy · 01-06-2007, 01:24 PM

I compiled a new kernel on my test system which is identical to my working system.
So everything is working fine, I want to use the kernel on both systems.

Is it safe to copy the whole /lib/modules/2.6.17.13-NEW tree or do I have to build the modules again?

Brian1 · 01-06-2007, 01:29 PM

As long as both systems are running the exact same kernel version then this will be fine. You will need to run the depmod command to recreate a new system map of modules so that they can be found to load.

Brian

syvy · 01-06-2007, 01:34 PM

That's what I wanted to know. Many thanks!

dugan · 01-06-2007, 09:24 PM

Quote:

Originally Posted by Brian1

As long as both systems are running the exact same kernel version

And the kernels are compiled with the same version of gcc.

syvy · 01-07-2007, 05:26 AM

Quote:

And the kernels are compiled with the same version of gcc.

The testing system ist a clone of the working system. I have a free partition to where I copy the whole system
in cases I want to make deeper changes or experiments. Even if something went wrong I can compare both
to find out what failed.

onebuck · 01-07-2007, 08:29 AM

Quote:

Originally Posted by syvy

The testing system ist a clone of the working system. I have a free partition to where I copy the whole system
in cases I want to make deeper changes or experiments. Even if something went wrong I can compare both
to find out what failed.

Hi,

When I compile a kernel for a test system, I copy the kernel and the modules for the test system from the development system. You would not have to worry anything but the depmod on the target/test system. Of course the libs/gcc should be the same.

My build/development system is the fastest system with a better monitor. I do have more than one. One is just an old AMD athlon 1600. Just allowed to chug along. I use the extraversion in the Makefile to identify the target and level.

syvy · 01-07-2007, 09:14 AM

Everything worked fine. I copied kernel and modules, did a depmod, no errors occoured. Thanks to Brian.

Quote:

I use the extraversion in the Makefile to identify the target and level.

That's what i did, too. I think otherwise it would overwrite the existing modules of the same version.

Gvsandvik, you gave me a good advice. I never compiled a kernel for another machine, but I'll keep that in mind.
Many thanks!

Brian1 · 01-07-2007, 11:19 AM

Here is another thing one can do to kernel building. If using an rpm based distro like Redhat and Redhat clones like fedora, one can build and rpm right from the kernel build directory. Issuing the command ' make rpm ' builds the kernel into an rpm format that be transferred from machine to machine as long as it is built containing the correct hardware specs of the other systems. You can build any kerenl you want for different platforms on a single machine. Do this with my slow machine that is a router. I can build the kernel for it on my dual AMD using the -j4 option for make in about the 1/12 of the time it would take on the router itself.

Brian