Thanks Santiago,
I'll check this on a new debian 7 installation with all updates
installed and let you know the result.
This will be in a few weeks.
BR
Mario Pereyra
SecureTech A&M
+598 2900-6836 Tel
+598 2900-7526 Tel/Fax
b...@securetech.com.uy
Wilson F. Aldunate 1294 Of. 302
Montevideo CP 11100 - Uruguay
www.securetech.com.uy
On 15/09/16 09:59, Santiago Vila wrote:
On Thu, Sep 15, 2016 at 09:05:52AM -0300, Mario Pereyra wrote:
The file "/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko"
is present (exist) in the file system and is a module file (as
you can see in insmod command).
If the file does not exist, the response from insmod command
is other (Error: could not load module ...: No such file or directory).
But in this case this message is not present, otherwise the message
is from libkmod and is stating it is failing to inset the module.
As you say, the message is stating (and I understand it correctly)
that the file is not in the file system, but that is not true.
I can't reproduce what you reported in a newly installed Debian 7
system.
# modprobe -vv ext2
insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context
0x7f713d6d51d0 released
Can you reproduce it in a newly installed Debian 7 system?
My guess is that the file is there but it's corrupted for whatever
reason, and that's why insmod can't load the module (I can agree that
the error message may be a little bit misleading).
You can check this easily:
# apt-get install debsums
# debsums linux-image-3.2.0-4-amd64 | grep ext2
and it should say this:
/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko OK
If it says this instead:
/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko FAILED
then you should definitely reinstall the package containing ext2.ko:
# dpkg -S /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
linux-image-3.2.0-4-amd64:
/lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
# apt-get --reinstall install linux-image-3.2.0-4-amd64
If reinstalling linux-image-3.2.0-4-amd64 does not solve the problem,
please try asking in debian-user, I'm just a random Debian maintainer
who happened to take a look at bugs reported against "base".
Thanks.
