[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#815853: marked as done (Cannot modprobe due to wrong kernel version string)



Your message dated Thu, 25 Feb 2016 18:40:18 +0900
with message-id <CAEQ9gEnnjH+GCot6be8m-SLOgi277-hVcK-XJJ=y0X49Ak0vEQ@mail.gmail.com>
and subject line Re: Bug#815853: Cannot modprobe due to wrong kernel version string
has caused the Debian Bug report #815853,
regarding Cannot modprobe due to wrong kernel version string
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
815853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815853
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-armmp-lpae
Version: 3.16.7-ckt20-1+deb8u2
Severity: grave

The package installs modules in /lib/modules/3.16.0-4-armmp-lpae
but uname -r returns
3.16.0-4-armmp

This means that modules cannot be loaded, e.g.

$ sudo modprobe nls_cp437
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not
open moddep file '/lib/modules/3.16.0-4-armmp/modules.dep.bin'

For lpae kernels append -lpae to the kernel version string.

Best regards

Heinrich Schuchardt

--- End Message ---
--- Begin Message ---
On Thu, Feb 25, 2016 at 3:57 PM, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> The error was caused by the system not using the kernel installed in
> /boot but reading it from /dev/mmcblk0p1.
>
> Please, close the message.

Thanks for your report and clarification!

--- End Message ---

Reply to: