I guess you could rename the 2.4.20 directory to 2.4.22, but you'd still probably have to force load the modules. Of course the best way out of this mess is to build your own custom kernel. Greg On Tue, Feb 03, 2004 at 06:37:27PM -0700, Steve Holmes wrote: > What you probably have now is a kernel and related modules mixed > across versions. This doesn't work. A 2.4.20 kernel expects to find > all its modules under /lib/modules/2.4.20 and a 2.4.22 kernel would > likewise look for its modules in /lib/2.4.22. I really don't know how > to cause modprobe and insmod to look in a different place other than > what is specified in the kernel. > -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org
