I would like to work with KINO. KINO needs the module raw1394. In make gconfig I have checked Device Drivers --> IEEE1394 (FireWire) Support --> IEEE1394 (FireWire) Support with a M.

I compiled and installed the module:
make modules SUBDIRS=drivers/ieee1394
make modules_install SUBDIRS=drivers/ieee1394

The files ieee1394.ko and raw1394.ko are installed in the directory /lib/modules/2.6.5-1.358custom/kernel/drivers/ieee1394

When I want to load the module (insmod ./raw1394.ko) I get the next error:
insmod: error inserting './raw1394.ko': -1 Invalid module format

I work with Fedora Core 2 (kernel 2.6.5)

Can anyone help me?

Does Fedora Core 2 come with the firewire modules already compiled? Run
If you see the raw1394 and ieee1394 modules there, run (as root)
That should install the modules. If you want them installed everytime you boot up, add them to /etc/modules.preload (I think FC2 uses that file)

--mascdman

The modules are not already compiled. When I compiled them they come in the directory
/lib/modules/2.6.5-1.358custom/kernel/drivers/ieee1394

instead of

/lib/modules/2.6.5-1.358smp/kernel/drivers/ieee1394

insmod or modprobe doesn't work in the custom-directory, it does work in smp-directory. I think I compiled them not correctly. Do you know what the difference is between:
"make gconfig" and "make oldconfig"? I have made the knew config file with "make gconfig" and then compiled the modules.

You compiled them correctly, but I think the problem is that you're mixing modules from different kernels (that extra "custom" on the end of the kernel version (yeah, even though they're the same release number))

Unless someone else can suggest a faster way, I'd suggest just recompiling a kernel. You can get the configuration for the current running kernel by running
This will overwrite any changes you've make in make gconfig. Then do
and add in ieee1394/raw1394 support. Recompile and install the kernel and modules and setup your bootloader to use the new kernel.

--mascdman

Thanks! I will try it tonight.

I just tried it and it worked. I can now load the .ko modules from the 2.6.5-1.358custom directory with insmod and modprobe!

Excellent

--mascdman