On Thu, Sep 15, 2016 at 02:17:08PM -0300, Mario Pereyra wrote:
> 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.
Well, if you can't afford reinstalling linux-image-* and perform a
reboot because it's a supe
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
Hi.
Make sure you have all the security updates installed and that you
have the latest version of linux-image-3.2.0-4-amd64, otherwise the
problem might be already fixed and we are running in circles.
At this moment it should be 3.2.81-2, you can check this here:
https://packages.qa.debian.org/l
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 ot
Package: base
Severity: critical
Justification: breaks unrelated software
# LANG=C mount -o ro /dev/sdc1 /mnt/disk/
mount: unknown filesystem type 'ext2'
# modprobe -vv ext2
insmod /lib/modules/3.2.0-4-amd64/kernel/fs/ext2/ext2.ko
libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_m
5 matches
Mail list logo