Skip to contentSkip to conversation

Invalid module format - how does one fix this?

DISCUSSION Ed Tomlinson 2 participants 3 messages Nov 24, 2002

lore
Share & tools
lore
#0 lore raw

Hi,

2.5.49-mm1 works ok here (shpte enabled too). I see two frustrating problems left with the modules change (user perspective). The most irratating one is messages like:

FATAL: Error inserting /lib/modules/2.5.49-mm1/kernel/ac97_codec.o: Invalid module format

I get this on about 10% of the modules I want to load. How do I fix it?

The second is that automatic loading is not working. Manually loading modules is a PITA. What plans are there to fix this?

TIA
Ed Tomlinson

#1 lore raw
Quoted 3 lines · Ed Tomlinson

FATAL: Error inserting /lib/modules/2.5.49-mm1/kernel/ac97_codec.o: Invalid module format

I get this on about 10% of the modules I want to load. How do I fix it?

readelf -r module_in_question.o

then look at arch/$ARCH/kernel/module.c and find out which relocation is not implemented. Then implement it. Enabling DEBUGP there and in kernel/module.c may also help.

-Andi

#2 lore raw
Quoted 11 lines · Andi Kleen
Quoted 4 lines · Ed Tomlinson

FATAL: Error inserting /lib/modules/2.5.49-mm1/kernel/ac97_codec.o:
Invalid module format

I get this on about 10% of the modules I want to load. How do I fix it?

readelf -r module_in_question.o

then look at arch/$ARCH/kernel/module.c and find out which relocation is not implemented. Then implement it. Enabling DEBUGP there and in kernel/module.c may also help.

Looking in i386/kernel/module.c, it should be using printk to tell me what is missing. I am not seeing these in my logs. Is there some /proc or /sys setting I need to change to see warnings?

Tia,
Ed Tomlinson