module issue?
Robert Heller
heller at deepsoft.com
Thu May 24 12:33:30 UTC 2018
At Thu, 24 May 2018 11:43:35 +0200 "Ubuntu user technical support, not for general discussions" <ubuntu-users at lists.ubuntu.com> wrote:
>
> On Thu, 24 May 2018 10:35:33 +0200, Oliver Grawert wrote:
> >this is not an ubuntu kernel, where did you get it from ?
>
> This seems to be a kernel for a Raspberry Pi, see
>
> https://raspberrypi.stackexchange.com/questions/83329/linux-modules-mismatch-version?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
>
> Those Raspberry Pi techies are seemingly missing basic Linux
> troubleshooting skills, perhaps they should consider to start with an
> averaged Linux computer first, instead of using a Raspberry Pi.
>
> Since the OP is booted to 4.9.80 and the modules are for 4.14.34, it's
> most likely the issue mentioned by Nils. A kernel was updated and
> perhaps the older running kernel was removed, but it was not rebooted.
The Raspberry Pi kernel update removes/replaces the older kernel and its
modules, unlike either the Ubuntu or RHEL/CentOS kerne updates, which
*install* the new kernel along side the old kernel. It is a "weird" thing to
do, but a reboot will likely solve the OP's problem.
>
> Instead of posting a lot of irrelevant output, it might be worth to run
>
> apt list --installed 'linux*'; lsb_release -a
>
> Regards,
> Ralf
>
>
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller at deepsoft.com -- Webhosting Services
More information about the ubuntu-users
mailing list