LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Module troubles with recompiled kernel (https://www.linuxquestions.org/questions/linux-newbie-8/module-troubles-with-recompiled-kernel-455724/)

kpworrell 06-17-2006 02:21 PM

Module troubles with recompiled kernel
 
Slackware 10.2, 2.4.31 kernel recompile.

I'm following the typical procedure from slackbook.org for recompiling a 2.4.x kernel, which is to say specifically:


Code:

% su -
# cd /usr/src/linux

# make mrproper
# make menuconfig   

# make dep
# make clean

# make bzImage
# make modules

# mv /boot/vmlinuz /boot/vmlinuz.old
# cat arch/i386/boot/bzImage > /vmlinuz
# mv /boot/System.map /boot/System.map.old
# cp System.map /boot/System.map

# make modules_install

...and then I reconfigure lilo.

After this, I reboot and get "FATAL: Module ... not found." messages telling me whatever process (insmod/modprobe I assume) can't locate the modules I compiled.

I didn't think they were there at all for a bit, since I'm gullible, but it looks like they actually showed up under

/lib/modules/2.6.15/kernel/drivers/

But when I go there and launch modprobe es1371.o (for example) it says:

FATAL: Module es1371.o not found.

...just like the message I got at startup. Even though the driver was *right there* .

Is that not the right format or something? I recall the precompiled drivers that 10.2 shipped with were gzipped. My modutils is up to date, and I double-checked all the minimum software version requirements in /usr/src/linux/Documentation/Changes and my system fit the bill, so what gives?

Thanks in advance...

bigrigdriver 06-17-2006 03:15 PM

If I read your post correctly, when you try to modprobe 1371.o, you include the .o in the command. Unless Slackware is quite different from SuSE, I'd suggest 'modprobe 1371' without the .o. That's how it's done in SuSE. If you 'modprobe 1371.o', modprobe is looking for 1371.o.o, which it won't find.

Hope this helps.

kpworrell 06-17-2006 03:56 PM

You know, I should have known better than that, but I somehow forgot. I've done this before.

Anyhow, modprobe recognizes it, but it's not loading it. I get a screen full of "unresolved symbol" warnings, and then a notice from modprobe that the insmod operation failed.

What's the best way to clear that up?


All times are GMT -5. The time now is 10:33 AM.