Bug#901919: nvidia-driver: black screen with the latest Linux kernel - general protection fault

Kent West westk at acu.edu
Fri Jun 22 16:29:14 BST 2018


1. Apologies for not knowing how to properly add to this bug report.

2. I seem to be having the same issue. (Or very similar.)

I updated yesterday, got a new kernel of 4.16.0-2-amd64 #1 SMP Debian
4.16.16-1 (2018-06-19) x86_64 GNU/Linux, and on reboot just got a black
screen, with an apparently unresponsive console. I could remote-ssh in, and
reboot, or hard-power the button, but that's all.

When I renamed my xorg.conf file and purged all the nvidia stuff I could
find from aptitude, I was able to get a working system again (using the
NEAUVEAU (?) driver?). But the display is sluggish, most notably in screen
scrolls of lots of text, and very noticeable in VirtualBox-Win10 on my
Debian Buster/Sid machine.

(I also lost networking and audio, but I figure those are unrelated - got
networking back, but I don't know how; don't think I actually changed
anything; but five or eight boots later, it was working - it continued
working fine in reboots to an older kernel, so I know it wasn't an
external-to-my-box issue.)

Before swapping out the xorg.conf and purging nvidia stuff, I was able to
boot into a kernel two versions (in my grub menu) older - 4.15.0-2-amd64,
and the system worked fine. Later, after removing/purging nvidia, and then
later restoring xorg.conf and reinstalling what I that was the same nvidia
stuff (though it's likely not exactly the same packages), booting into the
older kernel causes the same system lockup as with the new kernel. Moving
xorg.conf out of the way again (removing nvidia driver, and using
NEAUVEAA(?)) fixes the problem

The kernel parameter mentioned at the bottom of the bug report did not help
me (although, being unfamiliar with such tweaks, it's possible I did it
wrong, but I don't think so).

Currently I'm on the new kernel, with networking working, no audio, and X
working (sluggishly, but usable for a while) with the NEAUVEAU(? I really
should look up that spelling) driver (I think).

Again, apologies for not knowing how to properly add to your bug-report
information, but I figured you having more info in a bad format is better
than not having any info from another person possibly hit by some
nvidia/kernel bug.

Thanks!

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20180622/2967a7e5/attachment.html>


More information about the pkg-nvidia-devel mailing list