Re: version mismatch in modules
Alex Nicolaou (anicolao@mud.cgl.uwaterloo.ca)
Fri, 10 Sep 1999 13:47:30 +0000
ngroups wrote:
> it starts the old kernel, so we checked the lilo.conf and found it was
> uncorrectly referring to the old kernel, we fix this and boot again
> The boot sequence works fine untill it meets "checking module dependecies",
> then the system seem to wait forever.
> we break with a ctrl_c and step forward.
> The eth0 doesn't work (we have an addictional module for 3c59x)
>
> we investigate about modules :
> - depmod -a (a lot of unresolved symbol)
> - modprobe 3c59x (kernel-module version mismatch ...)
>
> Qestions :
> - is the stale during checking module dependecies connected to 3c59x module
> version mismatch?
> - does the "make modules" recompile the modules including 3c59x (not sure we
> have all the sources, where can we get them?)?
> - how can we come out from this? (we can still boot our system with 2.2.5-15
> and works fine)
It sounds to me like you had old modules lying around in the
/lib/modules/xxx directory that your new 2.2.12 build put its modules
into. Start by making a backup of whatever is in /lib/modules, then rm
the subdirectory tree that you're building, then redo make
modules_install, then boot with the new kernel. If you don't already
have a boot floppy you might want to make one first.
alex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/