Starting with kernel 2.6, kernel modules have some versions infos attached to them. Thats the '*.ko' files. That's the one you should insmod. On my side, I have a different problem, specific to SuSE 9.1. It works on other distros with kernel 2.6. When linking, I have the following warning: "xxx is COMMON symbol". And then when I try to load the module: "invalid module format" I know SuSE uses a special branch of gcc 3.3 which includes some features of gcc 3.4. But what could cause that ? The common symbols are static members attributes of classes which are no different than many other similar static members.... Any clue ? On Fri, 2004-07-30 at 14:43, Lei Yang wrote: > Hello, > > I've got a problem here on installing cloop. I was trying to get > cloop-2.0.1 built and installed on a SuSe 9.1 box with kernel version > 2.6.5 . I followed all the instructions in > http://www.knopper.net/download/knoppix/cloop.README > and sucessfully went through compilation, depmod -a and mknod. > > I don't know how to create a compressed filesystem with cloop yet. But > when I tried to load the module into kernel, 'insmod /path/to/cloop.o", > there is an error: > insmod: error inserting 'cloop.o': -1 Invalid module format > > What should I do with it? Could anyone help me? > > I am no expert in kernel modules and really appreciate any hints! > > Thanks! > > Lei > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ -- Michel Hubert <mhubert@xxxxxxxxxx> Matrox Graphics Inc. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
