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

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

backports on kernel 4.15 and nvidia-driver 390 crashes x

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

Contents

  backports on kernel 4.15 and nvidia-driver 390 crashes x Boyan Penkov <boyan.penkov@gmail.com> - 2018-05-04 02:30 +0200
    Re: backports on kernel 4.15 and nvidia-driver 390 crashes x Francisco M Neto <fmneto@gmail.com> - 2018-05-04 23:30 +0200
      Re: backports on kernel 4.15 and nvidia-driver 390 crashes x Boyan Penkov <boyan.penkov@gmail.com> - 2018-05-06 17:30 +0200
        Re: backports on kernel 4.15 and nvidia-driver 390 crashes x Francisco M Neto <fmneto@gmail.com> - 2018-05-07 14:30 +0200

#195272 — backports on kernel 4.15 and nvidia-driver 390 crashes x

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

Hello,

I have upgraded to the current stretch backports nvidia-driver, and this crashes on the current stretch backports kernel.  Have folks seen this combination work?

I see the following:

kernel — nvidia — status
4.15 — 390 — fail
4.15 — 370 — untested
4.9 — 390 — fail
4.9 — 375 — success

Anything I can do to help debug? What’s annoying is that the fails on 390 print a blank screen with no X cursor and a prompt to log out, so I don’t know where to look for logs or traces….

Cheers!
--
Boyan Penkov
www.boyanpenkov.com

[toc] | [next] | [standalone]

#195292

Hello,

	I had a similar problem when I upgraded from Stretch (4.9) to
Buster (4.15). The nvidia driver stopped working but after reinstalling
it started to work again, supposedly because it needed to rebuild the
kernel module with headers from the new kernel. Maybe you're having a
similar issue?

	Which nvidia card are you using?

--
Francisco

On Thu, 2018-05-03 at 20:24 -0400, Boyan Penkov wrote:
> Hello,
> 
> I have upgraded to the current stretch backports nvidia-driver, and
> this crashes on the current stretch backports kernel.  Have folks seen
> this combination work?
> 
> I see the following:
> 
> kernel — nvidia — status
> 4.15 — 390 — fail
> 4.15 — 370 — untested
> 4.9 — 390 — fail
> 4.9 — 375 — success
> 
> Anything I can do to help debug? What’s annoying is that the fails on
> 390 print a blank screen with no X cursor and a prompt to log out, so
> I don’t know where to look for logs or traces….
> 
> Cheers!
> --
> Boyan Penkov
> www.boyanpenkov.com
> 
-- 
--
[]'s,

Francisco M Neto
Institut für Anorganische Chemie
Universität Duisburg-Essen

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

#195348

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

--
Boyan Penkov
www.boyanpenkov.com

> On May 4, 2018, at 17:19, Francisco M Neto <fmneto@gmail.com> wrote:
> 
> Hello,
> 
> 	I had a similar problem when I upgraded from Stretch (4.9) to
> Buster (4.15). The nvidia driver stopped working but after reinstalling
> it started to work again, supposedly because it needed to rebuild the
> kernel module with headers from the new kernel. Maybe you're having a
> similar issue?

I don’t think so, as the experiment matrix I tried above involved rebuilding the module using the correct headers every time.

Updating sources to buster and pulling in kernel-image, kernel-headers, then restarting to 4.16 to recovery mode, uninstalling nvidia-driver and then reinstalling the nvidia-driver package seems to have worked…. However, this cannot be the orthodox approach to solve this…..

> 
> 	Which nvidia card are you using?

GTX 560 Ti, which is Fermi, which is indeed old — wikipedia says it’s going to legacy after 390 — is that where I may be getting in trouble?  Should I try nvidia-legacy in debian?

> 
> --
> Francisco
> 
> On Thu, 2018-05-03 at 20:24 -0400, Boyan Penkov wrote:
>> Hello,
>> 
>> I have upgraded to the current stretch backports nvidia-driver, and
>> this crashes on the current stretch backports kernel.  Have folks seen
>> this combination work?
>> 
>> I see the following:
>> 
>> kernel — nvidia — status
>> 4.15 — 390 — fail
>> 4.15 — 370 — untested
>> 4.9 — 390 — fail
>> 4.9 — 375 — success
>> 
>> Anything I can do to help debug? What’s annoying is that the fails on
>> 390 print a blank screen with no X cursor and a prompt to log out, so
>> I don’t know where to look for logs or traces….
>> 
>> Cheers!
>> --
>> Boyan Penkov
>> www.boyanpenkov.com
>> 
> -- 
> --
> []'s,
> 
> Francisco M Neto
> Institut für Anorganische Chemie
> Universität Duisburg-Essen
> 

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

#195406

On Sun, 2018-05-06 at 16:34 -0400, Boyan Penkov wrote:
> On Sun, 2018-05-06 at 11:20 -0400, Boyan Penkov wrote:
> > > Updating sources to buster and pulling in kernel-image, kernel-
> > > headers, then restarting to 4.16 to recovery mode, uninstalling
> > > nvidia-driver and then reinstalling the nvidia-driver package
> > > seems to
> > > have worked…. However, this cannot be the orthodox approach to
> > > solve
> > > this…..
> > 
> > 	Actually I think it might just be. The problem is that it
> > involves a kernel module so a reboot might be mandatory... 
> > 	However, installing the kernel (with headers) and running apt-
> > get --reinstall and then rebooting might be enough.
> 
> That’s totally fair — and I’m happy and won’t be playing with this
> till I go all buster at the freeze — but should there be a hook in
> apt to make this more transparent?  Something like, if nvidia-driver
> is installed and the kernel changes, check for the relevant headers,
> and recompile the module?
> 
> I’ve verb bitten by this before, and it seems straightforward to do
> as part of the package post-hook, so am I missing something?

	I've been thinking the same thing since my last bout with the
drivers. I don't know what's happening - maybe the hook is there but
it's not working properly, or maybe the package maintainers is not
aware of this issue (which I think is unlikely). 

	I think the hook is there, somewhere. I've recently upgraded
from 4.15 to 4.16 and everything worked out fine, and I didn't need to
reinstall the drivers nor build any kernel module. It might be a
version-related issue.

	Checking Debian's bug tracker I've found a bug that seems to be
related to what happened to us, from 2014 (last updated in 2015), and
it's still flagged as outstanding.

	We need some tests to be sure. I have an extra partition that I
can use for testing, but it might take some time.

--
Francisco

[toc] | [prev] | [standalone]

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

csiph-web