Discussion:
modprobe: Module ext4 not found. WARNING: no dependencies for kernel module 'ext4' found
Anisha Kaul
2012-01-24 04:10:28 UTC
Permalink
Greetz,

I compiled the kernel 3.1.0, and following are the warnings that I am getting:
"linux-dopx:/usr/src/linux-3.1.0-1.2 # make installsh
/usr/src/linux-3.1.0-1.2/arch/x86/boot/install.sh 3.1.0
arch/x86/boot/bzImage \ System.map "/boot"
Kernel image:   /boot/vmlinuz-3.1.0Initrd image:
/boot/initrd-3.1.0Root device:
/dev/disk/by-id/ata-ST3250310AS_6RYNQEXY-part2 (/dev/sda2) (mounted on
/ as ext4)Resume device:
/dev/disk/by-id/ata-ST3250310AS_6RYNQEXY-part1 (/dev/sda1)find:
`/lib/modules/3.1.0/kernel/drivers/ata': No such file or
directorymodprobe: Module ata_generic not found.WARNING: no
dependencies for kernel module 'ata_generic' found.modprobe: Module
ext4 not found.WARNING: no dependencies for kernel module 'ext4'
found.Features:       block usb resume.userspace
resume.kernelBootsplash:     openSUSE (1280x1024)41713 blocks
"

The steps I took are:
1. make menuconfig
2. make bzImage
3. make modules
4. make modules_install
5. make install

The platform is:
# uname -a
Linux linux-dopx 3.2.1-12-desktop #1 SMP PREEMPT Thu Jan 19 16:02:50
IST 2012 x86_64 x86_64 x86_64 GNU/Linux

Rebooting says: "Could not load /lib/modules/3.1.0/modules.dep"
What's the point that I am missing?

-Anisha
Anisha Kaul
2012-01-24 04:17:22 UTC
Permalink
Well, the "make installsh" in the previous mail is a typo. The command
I used is "make install".

-Anisha
Larry Finger
2012-01-24 04:53:52 UTC
Permalink
Post by Anisha Kaul
Well, the "make installsh" in the previous mail is a typo. The command
I used is "make install".
In a standard openSUSE configuration, ext4 is built into the kernel, which is
why the module is not found. Ignore the warning, or change the configuration.

Larry
Anisha Kaul
2012-01-24 04:56:38 UTC
Permalink
Post by Larry Finger
In a standard openSUSE configuration, ext4 is built into the kernel, which
is why the module is not found. Ignore the warning, or change the
configuration.
Thanks for responding, but I already ignored the warning rebooted the system.
I got the error "Could not find/load /lib/modules/3.1.0/modules.dep",
and the system
didn't boot with the error "ext4 filesystem not found".

-Anisha
Larry Finger
2012-01-24 05:26:27 UTC
Permalink
Post by Anisha Kaul
Post by Larry Finger
In a standard openSUSE configuration, ext4 is built into the kernel, which
is why the module is not found. Ignore the warning, or change the
configuration.
Thanks for responding, but I already ignored the warning rebooted the system.
I got the error "Could not find/load /lib/modules/3.1.0/modules.dep",
and the system
didn't boot with the error "ext4 filesystem not found".
One thing you did wrong appears to be that you built the kernel as root. That is
definitely not recommended.

When you did the 'make modules_install', was the last step 'DEPMOD <version>'?
That is the step that build the appropriate versions of modules.dep.

Larry
Anisha Kaul
2012-01-24 05:32:47 UTC
Permalink
Post by Larry Finger
One thing you did wrong appears to be that you built the kernel as root.
That is definitely not recommended.
I didn't know that. Will take care in future. But, what is so harmful
about that?
Post by Larry Finger
Post by Larry Finger
When you did the 'make modules_install', was the last step 'DEPMOD
<version>'? That is the step that build the appropriate versions of
modules.dep.
The result is:

# make modules_install
INSTALL arch/x86/kernel/test_nx.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL net/netfilter/xt_mark.ko
DEPMOD 3.1.0


Thanks for responding.
-Anisha
Larry Finger
2012-01-24 15:49:48 UTC
Permalink
Post by Anisha Kaul
Post by Larry Finger
One thing you did wrong appears to be that you built the kernel as root.
That is definitely not recommended.
I didn't know that. Will take care in future. But, what is so harmful
about that?
Maybe nothing; however, if there is a bug in the Kmake process, severe damage
may be done. At one point, such a bug destroyed /dev/null when the kernel was
built as root. Once that happened, nothing would boot. It is best to avoid any
such possibility.
Post by Anisha Kaul
Post by Larry Finger
Post by Larry Finger
When you did the 'make modules_install', was the last step 'DEPMOD
<version>'? That is the step that build the appropriate versions of
modules.dep.
# make modules_install
INSTALL arch/x86/kernel/test_nx.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL net/netfilter/xt_mark.ko
DEPMOD 3.1.0
Yes, that is the step that builds modules.dep. You can manually do it with

sudo /sbin/depmod -a 3.1.0

Larry
Greg KH
2012-01-24 16:49:49 UTC
Permalink
Post by Larry Finger
Post by Anisha Kaul
Post by Larry Finger
One thing you did wrong appears to be that you built the kernel as root.
That is definitely not recommended.
I didn't know that. Will take care in future. But, what is so harmful
about that?
Maybe nothing; however, if there is a bug in the Kmake process,
severe damage may be done. At one point, such a bug destroyed
/dev/null when the kernel was built as root. Once that happened,
nothing would boot. It is best to avoid any such possibility.
Even better, we once had a bug that would delete / entirely if you built
the kernel as root. A lot of us thought we should have just kept that
bug in there...

greg k-h
Larry Finger
2012-01-24 18:05:39 UTC
Permalink
Post by Greg KH
Even better, we once had a bug that would delete / entirely if you built
the kernel as root. A lot of us thought we should have just kept that
bug in there...
That would be a really big hammer! :)

Larry
Anisha Kaul
2012-01-25 01:00:38 UTC
Permalink
Post by Larry Finger
Yes, that is the step that builds modules.dep. You can manually do it with
sudo /sbin/depmod -a 3.1.0
So, now that it is already done, do I still have to do it manually?
The problem is still there.
Larry Finger
2012-01-25 01:36:06 UTC
Permalink
Post by Anisha Kaul
Post by Larry Finger
Yes, that is the step that builds modules.dep. You can manually do it with
sudo /sbin/depmod -a 3.1.0
So, now that it is already done, do I still have to do it manually?
The problem is still there.
Is modules.dep present? If so, what permissions? My copy shows 644.

Larry

Loading...