Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-17-2006, 02:21 PM   #1
LQ Newbie
Registered: Jun 2006
Location: San Diego, CA
Distribution: Slackware 12.2
Posts: 10

Rep: Reputation: 0
Module troubles with recompiled kernel

Slackware 10.2, 2.4.31 kernel recompile.

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

% 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/ /boot/
# cp /boot/

# 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


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...
Old 06-17-2006, 03:15 PM   #2
LQ Addict
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
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.
Old 06-17-2006, 03:56 PM   #3
LQ Newbie
Registered: Jun 2006
Location: San Diego, CA
Distribution: Slackware 12.2
Posts: 10

Original Poster
Rep: Reputation: 0
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?


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Recompiled kernel failing thelonewolf Debian 10 08-02-2005 11:10 PM
recompiled kernel 2.6.3-13 what does this mean? rbonafied Mandriva 8 06-07-2004 01:00 PM
Can't get recompiled kernel to load!!!!! dick220369 Linux - General 4 01-21-2004 09:59 AM
recompiled kernel not in use taoweijia Linux - Newbie 1 01-09-2004 09:33 AM
recompiled kernel and no vmlinuz.old or kernel module for Nvidia Bruce Hill Slackware 13 12-11-2003 02:36 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:13 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration