LinuxQuestions.org - MODPOST 0 modules while compiling kernel

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - MODPOST 0 modules while compiling kernel (https://www.linuxquestions.org/questions/slackware-14/modpost-0-modules-while-compiling-kernel-799692/)

MODPOST 0 modules while compiling kernel

First of all, hello world and everybody.

Since the polish Slackware forum couldn't help me with this issue i've had for pretty long time, i decided to take chances here. It may, or may not be Slackware-related (didn't try another distro for serious usage since hell of time), so sorry if it turns out more general problem and i'm posting it here.

It may sound a little noob-like at first glance, but believe me I'm not doing it for the first time :) Straight to the point. After successful compilation of bare kernel (bzImage), modules are just not being made. When

Code:

make modules

all i got is

Code:

  Building modules, stage 2.

  MODPOST 0 modules

Enable loadable module support=y, and variety of features are checked as =m. A lot of messages at bzImage compilation are

Code:

CC [M] sth

so i presume, that "something" is happening to code, from which .ko files would be compiled, but... after all the process, there are just no .ko files. :| So then

Code:

# make modules_install

installs only /lib/firmware part, leaving /lib/modules/{kernel name}/kernel empty.

Here's what i've tried:

compilation as ordinary user or root, at /usr/src, /home, /root
on ext3 or reiserfs filesystems
compilation of a couple of kernel versions between, and including, 2.6.24.2 (yes, that problem is that old :/ ) - 2.6.33
downloaded from kernel.org and that from slackware packages
with default slackware .config files, and with simply make menuconfig and save (without making any changes)
using some slackBuild from slackbuilds.net
different slackware versions (12.2, 13.0, and -current now)
windows-style "format c:", i mean, dd if=/dev/zero of=/dev/sdaX, and reinstall of Slackware
what's more, it was happening on my old pc, and now on new notebook

Nothing of that helped. But if it will help, i will repeat whatever is needed from that list above.

All I have googled about that is this https://forums.gentoo.org/viewtopic-...0-start-0.html.

I see two options, either i'm ommiting something that obvious that i can't see it, or it is some strange vortex of black energy that forms above me during kernel compilation process, inducing some mystical bug that affects only few doomed ones, including me, and causes "no you will not have your modules hahaha".

Second last thing i want to do is not using modules at all (compiling everyting into kernel) (cause the last thing is abandon Slackware for other distro), so... if you have any, and i mean "any", idea, how to track this down, i would be very grateful.

Not sure what the problem is but here are some things to try.

Back up your .config file and then change into the kernel source directory then run the following commands

Code:

make mrproper

cp /path/to/config-backup .config 

make prepare

make scripts

make && make modules_install

Are any modules actually enabled in your config?
Try using simply 'make' instead of 'make bzImage' + 'make modules'.

Quote:

Originally Posted by gnashley (Post 3922617)

Are any modules actually enabled in your config?

Yes, a lot of.

Quote:

Originally Posted by gnashley (Post 3922617)

Try using simply 'make' instead of 'make bzImage' + 'make modules'.

That's what i'm doing, 'make' + 'make modules' too, despite it's redundant.

Quote:

Originally Posted by mRgOBLIN (Post 3922442)

Not sure what the problem is but here are some things to try.

Back up your .config file and then change into the kernel source directory then run the following commands

Code:

make mrproper

cp /path/to/config-backup .config 

make prepare

make scripts

make && make modules_install

I've tried 'mrproper', i didn't use 'prepare' and 'scripts' (cause they are run as a part of 'make', am i right?) but i'll try that one more time.

[edit]

Haven't helped... :(

Code:

  CHK    include/linux/version.h

  CHK    include/generated/utsrelease.h

  CALL    scripts/checksyscalls.sh

  Building modules, stage 2.

  MODPOST 0 modules

Once again, .o files are being compiled ("CC [M] foo/bar/baz.o" messages), but no .ko files in /lib/modules after modules_install :( Although, firmware are built and installed just fine.