<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: loading the correct cipcb.o file
From: David Morgan <dmorgan,AT,telocity,DOT,com>
Date: Wed, 27 Feb 2002 21:30:28 +0100

Is loading "imposter" cipecb.o files a general cipe problem or specific
to something I'm doing? After booting a freshly compiled kernel, then
compiling and 'make install'ing cipe, my problem was:

> > kernel: cipcb0: ciped version mismatch c10adff6 -> 25bed682

It turns out I have two cipcb.o files:
33772 Feb 26 17:21 /lib/modules/2.4.8-26mdk/misc/cipcb.o
34962 Feb 26 16:28

When loaded, the former works and the latter fails. But the latter, when
modprobe'd, is the one that loads. Unfortunately.

modprobe chooses which file to load according to the list of
module-files (.o's) in  /lib/modules/2.4.8-26mdk/modules.dep. That file
comes from running
"depmod -a" which apparently takes an exhaustive inventory of all ".o"
files in the filesystem(?). My modules.dep file references BOTH cipcb.o
files, but the bad one
appears first and modprobe uses it. If I comment or remove that
reference, modprobe instead finds the good one later in the file and
everything works.

Does the same thing happen to other cipe users?

<< | Thread Index | >> ]    [ << | Date Index | >> ]