On Sep 26, 2005, at 3:09 AM, John P Taylor wrote:
I'm having problems generating the cpint_mod in a debian 2.6.8 system.
I'm falling at the 1st hurdle:
make -C /lib/modules/`uname -r`/build M=`pwd` SUBDIRS=`pwd` modules
make: Entering directory `/lib/modules/2.6.8-2-s390/build'
make: *** No rule to make target `modules'. Stop.
make: Leaving directory `/lib/modules/2.6.8-2-s390/build'
the above messages are returned after I added a build directory to
the "
/lib/modules/2.6.8-2-s390" path.
If I run the make against the directory where I expanded the cpint
tar.gz, then a cpint.o is generated. I tried renaming that to
"cpint_mod.ko" placing it appropriately down the /lib/modules path,
changing modules.dep and running depmod -a, but without any success:
modprobe cpint_mod
FATAL: Error inserting cpint_mod
(/lib/modules/2.6.8-2-s390/kernel/drivers/s390/char/cpint_mod.ko):
Invalid module format
What am I doing wrong here?
Neale's code expects to find kernel headers in /lib/whatsit/build
They aren't.
You need to install the kernel-headers module package appropriate to
the Linux you're running, and then point the build at /usr/src/kernel-
headers-whatsit instead.
I also found that I had to just make my own local copies of version.h
and module.h to set the UTS kernel string so that it would not whine
on insmod.
I changed the "wheel" group to the "daemon" group in cpint_load, and
made the initial modprobe something like
insmod $MODULE || insmod -f $MODULE || really_fail
So that it at least TRIES to load without tainting the kernel.
However, all this was done with cpint 1.6.x, since I was working to
2.4.27, but it's probably pretty close for 2.6.
Adam
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
