Hi there, I am very new to Linux and I am still learning so any help is much appreciated.
I have recently installed the latest NVIDIA drivers on Ubuntu Budgie and I thought all was well until I rebooted into a black screen. I am able to access the terminal from that screen by ctlr alt F1 and after purging NVIDIA I was able to log in again. It seems that the driver is causing my laptop to black screen, is there any fix around this at all. I did a bit of a search and couldn’t find anything recent.
My laptop is using a GTX 675m, to add to this I was previously using Ubuntu 16.04 LTS and had no issues with NVIDIA drivers but I don’t believe it was the 390 version.
Thank you everyone I appreciate the time and help.
just a quick guess: check if your kernel version works with NVIDIA v390. Going back to v389 might be a good idea.
I had the same issue with (X)ubuntu at kernels prior to 4.13.0 as the DKMS module fails to install. Currently I use kernel 4.13.0-36-generic and NVIDIA 390.25 which works fine.
You could also try the previous version (387.34). You can install the nvidia graphics PPA and install that specific version to see if it works for you:
Unfortunately I had no luck with either solution, I ended up installing the 17.10.1 LTS build of Budgie rather than 18.04 and had no problems with the drivers on this release. Thank you again for all of your help!
to be honest @vinzv I don’t know how Ubuntu deals with proprietary driver issues - not sure if there is a linux part of nvidia website to report issues.
it mentions black-screens with the nvidia drivers - it appears the nvidia X driver is buggy for some cards and does not (always) activate the modesetting part of X
Their workaround was to add to lightdm.conf display-setup-script=xrandr --output eDP-1-1 --mode 1920x1080 where eDP-1-1 corresponded to the xrandr display. Think it is well worth having a read of that bug report
This happened to me installing Nvidia 390 with 18.04 beta 2. Purging via ctrl-alt-F1 terminal got me back to normal. Any progress on this front yet? Thanks!
@nroetert the very latest from today is that the canonical dev has identified the issue and says it is straightforward to fix. So we are all just waiting for the update to be pushed hopefully very soon.