View Single Post
Old 05-29-03, 12:31 AM   #4
stuartlevy
Registered User
 
Join Date: May 2003
Location: flat, steamy Champaign, IL
Posts: 36
Default

Another way to prevent an install-under-kernel-B
from trashing the module already installed-under-kernel-A
is to move the installed kernel-A module first
to a place where modprobe can find it but
nvidia-installer can't, then run the nvidia-installer normally.

E.g. I have kernels "2.4.18-bigmem" and
"2.4.20-xfs". I've already run nvidia-installer
under 2.4.18-bigmem; it created a file
/lib/modules/2.4.18-bigmem/kernel/drivers/video/nvidia.o
which I want to keep.

Now I boot to 2.4.20-xfs, but before running
nvidia-installer, I say
Code:
  cd /lib/modules/2.4.18-bigmem
  mkdir misc
  mv  kernel/drivers/video/nvidia.o  misc/
Neat huh?

Moving nvidia.o out of the kernel/... subtree
also means (for better or worse) that if I
"make modules_install" on that kernel's
source tree, it won't erase nvidia.o.
That's good if I make only small changes,
but bad if I make a kernel .config change that breaks compatibility.
Find out by running "depmod -ae".
If nvidia.o has undefined symbols,
then rm /lib/modules/whatnot/misc/nvidia.o,
re-run nvidia-installer and then mv... as above.
stuartlevy is offline   Reply With Quote