Chapter 8.3 compiling the kernel problem

engineer · 01-08-2013, 08:41 PM

Hello again everyone.

I am working in LFS 7.1, and came across the following issue after configuring the kernel and attempting to make the modules:

Code:

root:/sources/linux-3.2.6# make modules_install
  INSTALL arch/x86/kernel/test_nx.ko
  INSTALL drivers/hid/hid-logitech-dj.ko
  INSTALL drivers/scsi/scsi_wait_scan.ko
  INSTALL net/netfilter/xt_mark.ko
  DEPMOD  3.2.6
Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt

After doing a bit of research, it seems like there is an issue with where the depmod link is pointing, or the link is not being read properly. I went back and double checked the Kmod install I did previously, and all of the links seemed to be intact.

I'm not sure how to proceed...

The link to the codemonkey website above is quite old, but that is where I got the idea to check the depmod link from the install for Kmod.

Here is the output from the first command, 'make':

Code:

root:/sources/linux-3.2.6# make
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready  (#1)
  Building modules, stage 2.
  MODPOST 4 modules

druuna · 01-09-2013, 01:18 AM

Does the make modules_install step stop or do you get a warning only and does it continue?

Do check to see if the modules are created (this directory: /lib/modules/3.2.6/). If the modules are there I would continue.

McZ · 01-09-2013, 05:04 AM

Quote:

Originally Posted by engineer

Hello again everyone.

I am working in LFS 7.1, and came across the following issue after configuring the kernel and attempting to make the modules:

Code:

root:/sources/linux-3.2.6# make modules_install
  INSTALL arch/x86/kernel/test_nx.ko
  INSTALL drivers/hid/hid-logitech-dj.ko
  INSTALL drivers/scsi/scsi_wait_scan.ko
  INSTALL net/netfilter/xt_mark.ko
  DEPMOD  3.2.6
Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt

...

I had that error when I built the kernel once. And from what I found out there is no error in the build process just a warning that the kernel may not be able to load the modules due to missing module-init-tools compatibility.

if the symlinks created after kmod is built are correct, it can be some library problem. Can you run depmod -a? if not can you run ldd /sbin/depmod to see if there is any missing library?

engineer · 01-09-2013, 05:07 PM

Quote:

Originally Posted by druuna

Does the make modules_install step stop or do you get a warning only and does it continue?

Do check to see if the modules are created (this directory: /lib/modules/3.2.6/). If the modules are there I would continue.

Well, the post I made from the output was all that was displayed after running the make modules_install command, then it returned me to the command line. I'm not sure if it finished, since that is the last module that ran. I do know that I didn't change very many things (maybe it was only 4) in the kernel configuration GUI (I had no idea what most of the items meant), so I suppose it's very possible that they did install.

I'll check the directory you gave and see if the modules are in there, and if they are, I'll proceed. By the way, is there a way to see which modules should be getting installed based upon what I selected in the GUI, or should I have remembered them or written them down or something (for future information).

Thank you.

druuna · 01-10-2013, 08:40 AM

Quote:

Originally Posted by engineer

By the way, is there a way to see which modules should be getting installed based upon what I selected in the GUI, or should I have remembered them or written them down or something (for future information).

The easiest way would probably be a grepping for the module token in the created .config file:

Code:

# all the individual module entries
grep "=m" .config

# amount of module entries
grep -c "=m" .config

I'm not entirely sure if an individual module is build for every entry, but it should give you a reasonable ballpark figure.