Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #190758 > unrolled thread

kernel nvidia dkms rebuild after upgrade?

Back to article view | Back to linux.debian.user

Contents

  kernel nvidia dkms rebuild after upgrade? Boyan Penkov <boyan.penkov@gmail.com> - 2018-01-07 19:50 +0100
    Re: kernel nvidia dkms rebuild after upgrade? Yao Wei <mwei@lxde.org> - 2018-01-08 00:40 +0100
      Re: kernel nvidia dkms rebuild after upgrade? Boyan Penkov <boyan.penkov@gmail.com> - 2018-01-08 01:10 +0100
      Re: kernel nvidia dkms rebuild after upgrade? Mark Fletcher <mark27q1@gmail.com> - 2018-01-08 01:30 +0100
    Re: kernel nvidia dkms rebuild after upgrade? Boyan Penkov <boyan.penkov@gmail.com> - 2018-01-08 01:10 +0100
    Re: kernel nvidia dkms rebuild after upgrade? Daniel Reichelt <debian@nachtgeist.net> - 2018-01-08 01:10 +0100

#190758 — kernel nvidia dkms rebuild after upgrade?

Hello,

After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
light of meltdown -- my nvidia drivers failed to load.

Rebulding the modules manually --
https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
-- did fix it.

Did I miss something?

Cheers!

-- 
Boyan Penkov

[toc] | [next] | [standalone]

#190772

[Multipart message — attachments visible in raw view] — view raw

It is caused by a missing dependency libelf-dev.
It is already reported against linux-headers-4.14.0-3-amd64:
https://bugs.debian.org/886474

I have the same symptom of broadcom-sta-dkms

On Mon, 8 Jan 2018 at 02:47 Boyan Penkov <boyan.penkov@gmail.com> wrote:

> Hello,
>
> After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
> light of meltdown -- my nvidia drivers failed to load.
>
> Rebulding the modules manually --
>
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
> -- did fix it.
>
> Did I miss something?
>
> Cheers!
>
> --
> Boyan Penkov
>
>

[toc] | [prev] | [next] | [standalone]

#190773

[Multipart message — attachments visible in raw view] — view raw

Thanks, Yao —  in messing around with this, I did end up finding a thread that suggested installing libelf-dev — I did so, but I guess the order in which I did it make me recompile my dkms modules manually.

Thanks for the note!
--
Boyan Penkov
www.boyanpenkov.com

> On Jan 7, 2018, at 18:31, Yao Wei <mwei@lxde.org> wrote:
> 
> It is caused by a missing dependency libelf-dev.
> It is already reported against linux-headers-4.14.0-3-amd64:
> https://bugs.debian.org/886474 <https://bugs.debian.org/886474>
> 
> I have the same symptom of broadcom-sta-dkms
> 
> On Mon, 8 Jan 2018 at 02:47 Boyan Penkov <boyan.penkov@gmail.com <mailto:boyan.penkov@gmail.com>> wrote:
> Hello,
> 
> After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
> light of meltdown -- my nvidia drivers failed to load.
> 
> Rebulding the modules manually --
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017 <https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017>
> -- did fix it.
> 
> Did I miss something?
> 
> Cheers!
> 
> --
> Boyan Penkov
> 

[toc] | [prev] | [next] | [standalone]

#190777

On Sun, Jan 07, 2018 at 11:31:58PM +0000, Yao Wei wrote:
> It is caused by a missing dependency libelf-dev.
> It is already reported against linux-headers-4.14.0-3-amd64:
> https://bugs.debian.org/886474
> 
> I have the same symptom of broadcom-sta-dkms
> 
Interesting. I noticed the libelf dependency when building 4.15-rc6 on 
an LFS machine the other day, also driven by Meltdown, and had to 
install elfutils to get the kernel to build without errors. Looks like 
the new kernel has a dependency on that -- one reason is to use the ORC 
kernel unwinder which is the default in that version I believe. Using 
the alternative, the Frame Pointer unwinder, allows the build to happen 
but then you get complaints at modules_install time for something else 
that wants libelf too, I forget what. Installing elfutils solved all 
issues.

I hadn't seen the problem in Debian but where I run Debian I run stretch 
so just installed the stable update from stretch to fix Meltdown. Since 
my stretch machines are behind my firewall anyway my priority was to get 
my firewall patched, so if there is more to come in terms of patching 
stock Debian kernels, I am disinclined to panic.

Mark

[toc] | [prev] | [next] | [standalone]

#190775

[Multipart message — attachments visible in raw view] — view raw

Hello Dan — thanks kindly, I had indeed not noticed….

I guess I’ll have a chance to test if the libelf-dev issue is really the fix when the patches do roll out.

In that vein, I would like to note that https://security-tracker.debian.org/tracker/CVE-2017-5754 <https://security-tracker.debian.org/tracker/CVE-2017-5754>  makes no mention of bpo kernels in backports.  Is this by design?

Cheers!
--
Boyan Penkov
www.boyanpenkov.com

> On Jan 7, 2018, at 18:44, Daniel Reichelt <debian@nachtgeist.net> wrote:
> 
> On 01/07/2018 07:47 PM, Boyan Penkov wrote:
>> and a backport (4.14.0-bpo2) -- in light of meltdown --
> 
> To avoid a false sense of security: according to [1], [2], [3], the
> current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
> yet include any mitigations against meltdown.
> 
> Daniel
> 
> 
> 
> [1] https://security-tracker.debian.org/tracker/CVE-2017-5753
> [2] https://security-tracker.debian.org/tracker/CVE-2017-5754
> [3] https://security-tracker.debian.org/tracker/CVE-2017-5715
> 

[toc] | [prev] | [next] | [standalone]

#190776

[Multipart message — attachments visible in raw view] — view raw

On 01/07/2018 07:47 PM, Boyan Penkov wrote:
> and a backport (4.14.0-bpo2) -- in light of meltdown --

To avoid a false sense of security: according to [1], [2], [3], the
current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
yet include any mitigations against meltdown.

Daniel



[1] https://security-tracker.debian.org/tracker/CVE-2017-5753
[2] https://security-tracker.debian.org/tracker/CVE-2017-5754
[3] https://security-tracker.debian.org/tracker/CVE-2017-5715

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web