Hi

I have just completed a fresh install of Slack 11.00 and chose the 2.6 kernel.

I did the "installpkg modules" bit and everything has booted ok BUT

When I try and modprobe some modules I get this errot :-

modprobe ieee1394
FATAL: Error inserting ieee1394 (/lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format
bash-3.1#

the modules appear to be present thus :-

pwd
/lib/modules/2.6.17.13/kernel/drivers/ieee1394
bash-3.1#

ls
dv1394.ko ieee1394.ko pcilynx.ko sbp2.ko
eth1394.ko ohci1394.ko raw1394.ko video1394.ko
bash-3.1#

But they seem to be of the wrong format???

AQny ideas anyone?

Cheers


Stewart

are you sure its not compiled into the kernel as opposed to modular?

# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=y


tobyl

Make sure you are running the same version of kernel as installed modules. Check if they exactly match by and f.E.

Thanks for the reply.

The 1394 stuff is compiled as modules :-

cat .config |grep 1394
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
CONFIG_IEEE1394=m
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set


also the kernel is :-

uname -r
2.6.17.13


And the 2.6.17.13 modules appear to be there :-

ls /lib/modules/2.6.17.13/kernel/drivers/ieee1394/
dv1394.ko ieee1394.ko pcilynx.ko sbp2.ko
eth1394.ko ohci1394.ko raw1394.ko video1394.ko
bash-3.1#

but not the correct format???

Stewart

that should be

Curious ...

Some modules load ok but not the 1394 ones it would seem :-

modinfo ieee1394
filename: /lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko
license: GPL
vermagic: 2.6.17.13 mod_unload 486 gcc-3.4
depends:
parm: ignore_driversisable automatic probing for drivers. (int)
parm: fcp:Map FCP registers (default = 1, disable = 0). (int)
parm: disable_irmisable Isochronous Resource Manager functionality. (bool)
parm: disable_nodemgrisable nodemgr functionality. (int)

But when modprobed :-

modprobe ieee1394
FATAL: Error inserting ieee1394 (/lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format


Stewart

maybe try modprobe -v ieee1394 (verbose), check dmesg also

I compile my own kernels so I may not be the best person to comment, but as I see it, you have kernel 2.6.17.13.

According to slackware-11.0/kernels/VERSIONS.TXT

All of these kernels are version 2.4.33.3,
except huge26.s which is version 2.6.17.13,
and test26.s which is version 2.6.18

so you are using huge26.s?

Well according to slackware-11.0/kernels/huge26.s/config


# Automatically generated make config: don't edit
# Linux kernel version: 2.6.17.13
# Wed Sep 27 22:25:37 2006
......
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=y


from slackware/slackware-11.0/README.TXT

-- huge26.s/ ....
...
If you use this kernel, MAKE SURE that when you
| | reach the installer's kernel installation menu that
| | you install this kernel again, or you may find that
| | the machine will not reboot properly. Also, this
| | kernel will require the kernel-modules package from
| | /extra/linux-2.6.17.13/.

so could you just confirm that you did that, and that your modules package is from /extra/linux-2.6.17.13/

if you did, well then there is definitely something strange going on...

tobyl

Hi

Yes I did indeed :-

Boot using the huge26.s kernel
choose the huge26.s kenel when prompted for a kernel to install
used installpkg kernel-modules from the 2.6.17.13 folder


Not sure what the best fix is ... Re install from scratch using 2.4 or try and re compile either a 2.4 or 2.6 kernel and modules.

Regards

Stewart

Well I am puzzled as well. Maybe someone else knows what is wrong...

My choice would be to recompile a 2.6 kernel & modules, or try the 2.6.18 kernel from /testing

tobyl

It is strange indeed.

What I think may be the problem is :-

The .config is in fact the 2.4 .config which shows that all the 1394 drivers have been configured as modules but the 2.6.17 kernel actually has some of the drivers compiled into the kernel? What then makes it confusing is that the 2.6.17 modules include modules for all the 1394 drivers.

Having said that look what happens with a clean rebooted system :

lsmod | grep 1394

nothing found

modprobe ieee1394
FATAL: Error inserting ieee1394 (/lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format

lsmod | grep 1394

nothing found

modprobe dv1394
WARNING: Error inserting ieee1394 (/lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format

But it seems to have loaded

lsmod | grep 1394
dv1394 16980 0

Also

modprobe raw1394
WARNING: Error inserting ieee1394 (/lib/modules/2.6.17.13/kernel/drivers/ieee1394/ieee1394.ko): Invalid module format

And then

lsmod | grep 1394
raw1394 24308 0
dv1394 16980 0


Something is messed up.

I guess I need to try dvgrab or kino to see whether the srivers are in fact available?

Stewart

Could you post the output with :
ls -al /boot

ls -al /boot
total 6580
drwxr-xr-x 2 root root 4096 2006-10-28 09:52 ./
drwxr-xr-x 21 root root 4096 2006-10-30 13:29 ../
lrwxrwxrwx 1 root root 37 2006-10-28 09:29 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r-- 1 root root 1101492 2006-10-28 09:43 System.map
-rw-r--r-- 1 root root 629105 2006-09-01 07:51 System.map-ide-2.4.33.3
-rw-r--r-- 1 root root 512 2006-10-28 09:52 boot.0300
-rw-r--r-- 1 root root 168 2006-10-28 09:52 boot_message.txt
-rw-r--r-- 1 root root 62900 2006-10-28 09:43 config
-rw-r--r-- 1 root root 41810 2006-09-01 07:51 config-ide-2.4.33.3
-rw-r--r-- 1 root root 5032 2006-08-08 06:34 diag1.img
-rw------- 1 root root 49664 2006-10-28 09:52 map
-r-------- 1 root root 3476293 2006-10-28 09:43 vmlinuz
-rw-r--r-- 1 root root 1313255 2006-09-01 07:51 vmlinuz-ide-2.4.33.3


Regards

Stewart

Your /boot dir doesn't look very good.

What is this 'map' file ?
Why are the permissions set to 0400 for vmlinuz ? should be 0644 (-rw-r--r--)

Usually the stock vmlinuz and System.map files are named accordingly
to the kernel version (like vmlinuz-ide-2.4.33.3 and System.map-ide-2.4.33.3)
Maybe you could upgradepkg your kernel-ide and kernel-modules packages
from your CD ?

I pretty much followed the installation as suggested in the notes :=

Booted from CD using huge26.i

When requested to choose a kernel I opted from Kernel from CD and selected the huge26.i

Finally I did a installpkg of the 2.6 kernel-modules.

Apart from all that I haven't made any changes to /usr/src or /boot.

However, I have installed DropLine gnome

Maybe its safer to stick with the standard 2.4 installation?

Stewart