nvidia-390 fails to boot graphical display

[walkerstreet]

I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed.

[Igor Mokrushin (mcmcc)]

Same thing, after update and reboot I get only to console...

My notebook Asus ROG GL553VE with installed Kubuntu 18.04.

[x15 (x15)]

Same thing too. 18.04 Kubuntu with GTX 560, ASUS P6T Deluxe V2

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[x15 (x15)]

Before reboot there was no libGl....
After reboot the log says:

Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf "Option" is not a valid keyword in same section.
Problem parsing the config file
Error parsing the config file
Fatal server error:
no screens found(EE)

[Igor Mokrushin (mcmcc)]

This packages are broken, library files install in root directory /#...
Also, there is no replace of alternative symbolic links ones in /etc/alternatives, they remain from previous versions to non-existent files...

[Alberto Milone (albertomilone)]

The new driver is not going to work without libglvnd and xorg-server from bionic-proposed. Sorry for the inconvenience.

[Steve Langasek (vorlon)]

If it doesn't work without the libglvnd and xorg-server from bionic-proposed, then there should be versioned Depends: or versioned Breaks: expressing this. Alberto, can you make sure this is added in the next upload?

[Brian Murray (brian-murray)]

I had to install the following packages from bionic-proposed to get a working X session again.

libglvnd0, xserver-xorg-core, and libgl1-mesa-glx.

[Dejan V. (lnxsurf)]

Hi,
I have the same problem...

I tried to install
libglvnd0, xserver-xorg-core, and libgl1-mesa-glx

but it doesn't work for me...

[walkerstreet (dbonner)]

I added bionic-proposed and upgraded to the latest: libglvnd0, xserver-xorg-core, and libgl1-mesa-glx
After doing that, I get a blank screen. I have to Ctrl-Alt-F1 to go to tty console mode.
So the suggested fix did not work for me either.

[seahawk1986 (seahawk1986-hotmail)]

I encountered a dead symbolic link for libvdpau.so:

$ ls -l /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so
lrwxrwxrwx 1 root root 31 Feb 22 18:50 /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so -> vdpau/libvdpau_nvidia.so.390.25

libvdpau_nvidia.so.390.25 is located in the same directory, not in the subdirectory vdpau: https://packages.ubuntu.com/bionic/amd64/libnvidia-decode-390/filelist

Which can be fixed using the following commands:
cd /usr/lib/x86_64-linux-gnu/
sudo ln -sf libvdpau_nvidia.so.390.25 libvdpau_nvidia.so

[Chris (cmseuk)]

I already have libglvnd0, xserver-xorg-core, and libgl1-mesa-glx installed. I am not using an nvidia driver or hardware and I have the same problem. Unable to boot into system.

[Chris (cmseuk)]

 "Started gnome display manager.....service link was shutdown. Tried to start xserver and got libGl.so not found error.

[Chris (cmseuk)]

I upgraded to proposed and the issue is fixed.

[x15 (x15)]

I've able to run jwm (startx jwm) and rxvt. Firefox and konsole need libGl but Vialdi, OneTeam and Thunderbird work fine somehow....

[Thomas O'Keeffe (theghostinthemachine)]

Ive had this same problem. I have an nvidia 960m in my laptop using nvidia-390. After I upgraded, I got the “Option is not a valid keyword...” as well. For future refernce, you can get a rudamentary GUI
1. apt removing and apt purging all things nvidia then rebooting
2. At the GRUB screen, add “nomodeset” to the kernel parameters
3. Upon arriving at the lightdm login screen, switch to TTY 1 with ctrl + alt + F1 and chown the .Xauthority file to your_user:your_user
4. Switch back to the login with ctrl + alt + F7 and login like usual.

It’ll look ugly but it works. Tested on Unity.

[Thomas O'Keeffe (theghostinthemachine)]

I haven’t fully upgraded to proposed yet but adding the symlink and the packages Alberto specified did not solve my problem.

[Dejan V. (lnxsurf)]

How did you install the proposed packages? I think I did but no change appeared.

[Thomas O'Keeffe (theghostinthemachine)]

Uncomment proposed repo in `/etc/apt/sources.list` then run `sudo apt update` then you can either install the packages you want specifically or you can `sudo apt upgrade` to update all of them at once.

[Dejan V. (lnxsurf)]

Hmm... I don't have any line commented. So would you print me the lines which I have to uncomment, please?

[Sergei Beilin (saabeilin)]

Updating to `proposed` did not help me. I've tried uninstalling/purging `nvidia-*` and installing it back, still having the black screen.

Tried to switch to Intel adapter using prime-select, it complains that it's not supported.

Purging nvidia-390 and installing nvidia-340 works (though Nvidia always runs on top clock, even on battery, overheating my knees, and always on 100% brightness)

Dell Latitude 6430, NV520.

[Thomas O'Keeffe (theghostinthemachine)]

@lnxsurf, “deb http://us.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted” that line gets added to your sources file.

[Dejan V. (lnxsurf)]

Great! Thanks alot for your help.
I used “deb http://de.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted"
Then I installed the mentioned packages but still it did not work.
After I executed "sudo apt dist-upgrade" everything got better. I could start my desktop again.

[Thomas O'Keeffe (theghostinthemachine)]

Confirmed on Unity for me, adding proposed and running sudo apt update && sudo apt upgrade works. I can boot fully with no problems into lightdm and unity runs fine after logon.

[Chris McDonough (chrism-plope)]

After having the same problem, I dist-upgraded to proposed and can confirm that it fixed it (I did an apt-get purge nividia* before the dist-upgrade then a apt-get install nvidia-384 after the dist-upgrade)/

One thing that this minor bug pointed out to me is that it has become inconvenient in the current strategy to revert to an older Nvidia driver version, as nvidia-384 is now a transitional package that depends on nvidia-390. Even after adding the graphics-driver ppa, it was not trivially possible to downgrade from 390. I understand the intent (upgrade folks to the latest proprietary thing without them needing to take extra action), but I sort of wonder whether the packages should be renamed so they don't match the graphics-driver ppa names, such that we could purge nvidia, then add the ppa, then do e.g. apt-get install nvidia-387 and actually get 387 instead of 390.

[Nate Swanson (nswanson08)]

The proposed repo with dist-uprade worked for me

[walkerstreet (dbonner)]

I have successfully installed the driver using the proposed repo packages on my laptop. I need to try my desktop again.
Does anyone know how to use nvidia prime-select and bumblebee/optirun with this driver. My laptop battery might drain fast using this mode.

[Peter Silva (peter-bsqt)]

tried the *proposed* recipe above. no luck for me:
as it is installing, it errors:

npacking nvidia-dkms-390 (390.25-0ubuntu1) over (390.25-0ubuntu1) ...
Setting up nvidia-dkms-390 (390.25-0ubuntu1) ...
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
...

and the xorg doesn't find the nvidia driver on startup.

[Renaud Lepage (cybik)]

I managed to fix my setup by using the Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) and forcing the install of version 390.25-0ubuntu0~gpu18.04.1 (apt-get install nvidia-390=390.25-0ubuntu0~gpu18.04.1 or something). I suspect version 390.25-0ubuntu1 is broken.

[Brian Murray (brian-murray)]

For the development release of Ubuntu it is not recommended to install the packages from -proposed because they have not passed automated testing yet. I only installed the exact packages I needed and then disabled -proposed. Here's the full set of packages I installed incase I missed one.

Start-Date: 2018-02-27 10:58:32
Commandline: apt-get install nvidia-driver-390
Requested-By: bdmurray (1000)
Install: nvidia-compute-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-encode-390:amd64 (390.25-0ubuntu1, automatic), xserver-xorg-video-nvidia-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-fbc1-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-decode-390:amd64 (390.25-0ubuntu1, automatic), nvidia-compute-no-dkms-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-cfg1-390:amd64 (390.25-0ubuntu1, automatic), nvidia-utils-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-fbc1-390-i386:i386 (390.25-0ubuntu1, automatic), libnvidia-ifr1-390-i386:i386 (390.25-0ubuntu1, automatic), nvidia-compute-utils-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-ifr1-390:amd64 (390.25-0ubuntu1, automatic), nvidia-driver-390:amd64 (390.25-0ubuntu1), libnvidia-encode-390-i386:i386 (390.25-0ubuntu1, automatic), screen-resolution-extra:amd64 (0.17.2, automatic), libnvidia-decode-390-i386:i386 (390.25-0ubuntu1, automatic), nvidia-settings:amd64 (384.69-0ubuntu1, automatic)
End-Date: 2018-02-27 10:58:38

Start-Date: 2018-02-27 11:12:22
Commandline: apt-get install libgl1-mesa-glx
Requested-By: bdmurray (1000)
Install: libegl1:amd64 (1.0.0-2ubuntu1, automatic), libgl1:amd64 (1.0.0-2ubuntu1, automatic), libopengl0:amd64 (1.0.0-2ubuntu1, automatic), libgles2:amd64 (1.0.0-2ubuntu1, automatic), libglvnd-dev:amd64 (1.0.0-2ubuntu1, automatic), libglx0:amd64 (1.0.0-2ubuntu1, automatic), libglvnd-core-dev:amd64 (1.0.0-2ubuntu1, automatic), libglx-mesa0:amd64 (18.0.0~rc4-1ubuntu1, automatic)
Upgrade: libgles2-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libegl1-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libglapi-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), mesa-common-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libegl1-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libwayland-egl1-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgles2-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgl1-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgl1-mesa-glx:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1)
End-Date: 2018-02-27 11:12:26

[Bruce Pieterse (octoquad)]

I've installed the packages from proposed and I can see that X can now load the nvidia module, but out of curiosity, would it cause:

org.gnome.Shell.desktop[4934]: /usr/bin/gnome-shell: error while loading shared libraries: libEGL.so.1: cannot open shared object file: No such file or directory

Due to that the following occurs:

gnome-session-binary[4911]: Unrecoverable failure in required component org.gnome.Shell.desktop
gnome-session[4911]: gnome-session-binary[4911]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session-binary[4911]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[4911]: CRITICAL: We failed, but the fail whale is dead. Sorry....

$ locate -e libEGL.so.1
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0

Any ideas, or should this specific library problem be reported against gnome-shell?

[Brian Murray (brian-murray)]

 $ dpkg -S /usr/lib/x86_64-linux-gnu/libEGL.so.1
libegl1:amd64: /usr/lib/x86_64-linux-gnu/libEGL.so.1

So install libegl1.

[Francois Thirioux (fthx)]

Maybe it's not the place to do that but could it be possible that an Ubuntu developer tell us what are the changes in this new driver & packaging ?
Questions :
- will it be possible to use Wayland running Nvidia ?
- will it be possible to change GPU without rebooting ?
- will it be possible to do like Nouveau, I mean launch an app using the discrete GPU (right click menu) ?
- how can we now switch GPU on an Optimus configuration ?
Ubuntuforums dev section :
https://ubuntuforums.org/forumdisplay.php?f=427

[Alberto Milone (albertomilone)]

@walkerstreet: disabling the dGPU won't work, because of logind:
https://github.com/systemd/systemd/issues/6908

@Peter Silva: that is not an actual error. You are going to need the new xserver and the new libglvnd from bionic-proposed.

[walkerstreet (dbonner)]

My desktop computer won't display the X desktop on my monitor after installing the new driver with the Bionic-proposed packages. I get a blank screen except for a tty cursor in the top left corner of the screen. I can view the X desktop remotely using Teamviewer though, which is really wierd. Typing nvidia-smi verifies that driver 390.25 is installed and running. I have 2 nvidia 1080Ti cards. Since the new driver is unusable on my desktop, I have reverted back to nvidia-384. Does anyone have any suggestions as to how I can get the new driver to display the X desktop on my monitor?

[Peter Silva (peter-bsqt)]

I now have drivers from bionic proposed, the problem I had before
was that I had attempted to manually correc nvidia-drm-outputclass-ubuntu.conf by commenting out the lines which had caused errors before,
and re-installing wasn't overwriting it.
I returned it to default state. I can now get the lightdm up.

on xorg.0.log it seems to load now, I get to the login dialog,
but none of my sessions will load ( I just go back to the lightdm dialog.) there are no errors, it just dumps me back at the lightdm
screen. I added a bunch of -desktop packages to see if it was an
environment thing. The failure to login happens with *ubuntu*, *unity (default)*, *Ubuntu on Wayland*. With *mate* it doesn't exist, but I get a screen with a single icon, and no other elements of a desktop, so I can only open
shells.

[Thomas O'Keeffe (theghostinthemachine)]

Try switching to a TTY when the lightdm screen comes up and running “chown your_user:your_user .Xauthority” then try to login with lightdm.

[Peter Silva (peter-bsqt)]

OK, video is back now: apt-install ubuntu-mate-desktop fixed something.
It was already installed, but doing it again tickled something. I logged into
mater, and there was half a dozen core dumps of various components, and then
everything started working. (I don´t actually use mate, it was just trying
to see if issue was related to desktop environment in use.) I logged out, and now everything is now normal again.

now I can log in again, with the same environment I had before the problem.
I´ve now commented out bionic proposed from /etc/apt/sources.list
stuff looks ok.

[Bruce Pieterse (octoquad)]

Thanks Brian,

Looks like libegl1 landed today. Picked it up with a normal apt update and everything is good again.

[Chris McDonough (chrism-plope)]

Downgraded from proposed using pins and after a dist-upgrade it works, thanks!

[tikend (metodrybar)]

Purging

apt-get remove --purge nvidia*

and doing number #30 worked for me

apt-get install nvidia-driver-390

[linuxar (linuxar)]

I am affected by the same bug, on Xubuntu Bionic. I only managed to log in by

dpkg-reconfigure to gdm3

to obtain a login manager

and then choosing Gnome session.

I only manage to get... 640x480, but at least it is graphical environment.

When trying anything else (lightdm as login manager or anything else like Xubuntu, Mate or Ubuntu DEs), only black screen.

[Burt P. (pburt0)]

Using bionic Xubuntu with the updated nvidia driver I can log in and everything works, but in only 640x480.

dmesg looks like nvidia is loaded, but it ends up using llvmpipe anyway.

~~~
dmesg | grep nvidia:
[ 0.997785] nvidia: loading out-of-tree module taints kernel.
[ 0.997792] nvidia: module license 'NVIDIA' taints kernel.
[ 1.002303] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 1.008686] nvidia-nvlink: Nvlink Core is being initialized, major device number 243
[ 1.008940] nvidia 0000:07:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 1.022995] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.25 Wed Jan 24 19:29:37 PST 2018
[ 1.023352] [drm] [nvidia-drm] [GPU ID 0x00000700] Loading driver
[ 1.023353] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:07:00.0 on minor 0
[ 3.934224] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 241
[ 4.114021] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
[ 202.094928] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
~~~

[Burt P. (pburt0)]

Forgot to mention in #43 that using bionic proposed didn't help.

[Kyle Weber (kyew01)]

I had to wipe my system from an image I had made last week. I went through everything mentioned above--I was able to get video back, but as soon as I'd try logging in my UI would hang. I'd have to reboot from SSH. Everything is working now--I'm going to hold off running any upgrades for a few days though in hopes they fix the bug. Running GTX 1060.

[Chris McDonough (chrism-plope)]

Burt P wrt https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/comments/43, you might try this:

edit /etc/default/grub, editing:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

  GRUB_CMDLINE_LINUX_DEFAULT=""

And adding:

  GRUB_GFXMODE=1920x1080-32,auto
  GRUB_GFXPAYLOAD_LINUX=keep

(you will almost certainly need to change the GRUB_GFXMODE value if your main display is not native 1920x1080)

Then rerun sudo grub-mkconfig -o /boot/grub/grub.cfg.

I had the same symptom you did a while back, because for unknown reasons the hardware would get into a snit if the grub graphics mode didn't match the native mode. You may not need to comment out the splash and quiet, but I needed to in order to be able to successfully enter a decryption passphrase.

See also https://www.reddit.com/r/thinkpad/comments/5m9u00/installed_ubuntu_16041_on_thinkpad_p50_some_notes/de79o3n/

[Ron Bentley (rtbentley)]

The work-around suggested in #29 worked for me. That's using the Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa).

Just to be clear about the symptoms I was seeing:

- The splash screen DID appear
- LightDM would NOT appear (just a black, blank screen)
- I could go to a virtual terminal and start the desktop with "startx"
- I had no problems with the Nouveau drivers only the proprietary drivers

However, lightdm works fine with the nvidia-390 package from the Graphics Drivers PPA.

The hardware is an Asus GL-553-VD laptop with NVIDIA GeForce GTX 1050 Mobile.

[Daniel van Vugt (vanvugt)]

nvidia-90 support may/should be fixed now that Mesa 18.0 is in bionic. Please update and retest.

[Francois Thirioux (fthx)]

Quadro M1000M : works now without any tweak.

Nonetheless, if you mean "*full* support", laptop users like me will argue the lack of a GPU switching ability and the removing of the Wayland session.

[Chazall1 (lishdigg)]

All functioning as expected with the nvidia-driver-390.

Thank you

[Burt P. (pburt0)]

Regarding my comment #43:
The solution suggested in #46 doesn't work. While it does force 1920x1080, even after login, the nvidia driver is not working.

lspci -v does show "Kernel driver in use: nvidia" for the card, but nvidia-settings behaves as if the driver is not loaded and glxinfo shows llvmpipe as the OpenGL renderer.

[Branchus (jhong)]

I have a different issue.

it happened in Arch linux, Manjaro, Ubuntu 18.04 beta. if I didn't install the nvidia 390 driver, everything run smooth, after I installed nvidia 390 driver, I have no problem with GUI, however, the system doesn't turn off, restart itself properly. my monitor goes into sleep (power saving mode - no signal) while the fan and all leds are still on.

I initially thought it is a kernel or systemd issue, after asking questions on different forums and trying different distros, I think now I confirm it is a display driver issue.

my graphic card is nvidia quodra k2200

anyone got the same issue?

[Burt P. (pburt0)]

Regarding #43, #44, #51, here is what I did:
* Reset the grub config file
* Removed all nvidia* packages
* Reverted everything to the standard bionic as described here: https://askubuntu.com/a/229663
* Removed all the old package information using: dpkg --purge `dpkg --get-selections | grep deinstall | cut -f1`
* Installed nvidia-driver-390: apt-get install nvidia-driver-390
* Restarted

Everything seems to work.

[Burt P. (pburt0)]

I spoke too soon, the lock screen is still 640x480, but when unlocked it returns to 1920x1080. I can live with this, but something is still wrong with the driver.

[walkerstreet (dbonner)]

I still get a blank screen with a text cursor in the top left corner on my desktop computer. There is no login and no GUI after I install the nvidia-driver-390. It has 2 GTX 1080 Ti cards. My laptop is working OK. Can anyone help me or give me some tips on how to troubleshoot this?

[Alberto Milone (albertomilone)]

All the required components should be in Bionic now. I am closing this bug report. Feel free to file a new bug report, if you experience any further problems with the driver.

P.S. disabling the discrete GPU (on systems with hybrid graphics) does not work yet, but it will soon.

[Roman Dinga (roman-dinga)]

Is there an open bug for discrete GPU switch not working? Or should I open a new one?

[Roman Dinga (roman-dinga)]

Ok I see that there already is a bug for this
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739

[netslovdlyasnov (netslovdlyasnov)]

after nvidia-390 became nvidia-driver-390 I get back screen.
I have Acer vx5 laptop with nvidia 1050/Intel

[siddesh kadam (siddeshkadam91)]

same problem i got black flickering screen on del 5558 , i have 920m please suggest me which stable graphics driver can i use right now i am unable to use tensorflow because of this , right now it is working on nouveau drivers which has got set automatically by the sysytem , m running linux ubuntu 64 bit .

[Lysenko Denis (pharmasolin)]

You may try this ppa https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa just updated driver from this rep on 18.04 and succesfully booted.

[siddesh kadam (siddeshkadam91)]

i have tried the above link for Ubuntu 16.04 not working with nvidia drivers (390) i have del 5558 and 920m graphics . (same flickering screen ) , reverted back to nouveau drivers .

[netslovdlyasnov (netslovdlyasnov)]

I have tried graphics-drivers ppa and it doesn't work on 18.04.
On blank screen xrandr --listmonitors returns "Monitors: 0"

But everything works ok with ubuntu 16.04.

[Giraffe (dodger-forum)]

I'm having the shame issue with nvidia-390 just upgraded to Bionic i have a Dell Precision 7510 with a Quadro M2000M

[Bret Ancowitz (iiari)]

Same issue with Nvidia 390 with Ubuntu Budgie 18.04 beta 2, with an MX-150 Nvidia on a Xiaomi Air 13.

[Michael Brown (mikegb92121)]

Same issue with nvidia 390. I was able to fix for a couple of days by installing MATE, but am back to square one after updating packages today.

[Renaud Lepage (cybik)]

By accident, I upgraded some parts to 390, so I just gave up and tried to upgrade *all* the packages to 390, instead of having some from graphics-drivers and some from partner. Lo and behold, I think I'm on partner-provided drivers now, because everything works on 390.48 and I have multiple independent packages for the nvidia drivers, instead of the (simplified) limited number graphics-drivers provides.

No idea if I'm a unique case.

[Horst Schirmeier (horst)]

For me this is still broken with -proposed packages although this bug has "Fix Released" status: When I have xserver-xorg-video-nvidia-390 390.48-0ubuntu1 installed, the system boots into a back screen. Without, LightDM comes up as expected.

lspci excerpt (on a ThinkPad T460p):
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)

[Luke Williams (wililupy)]

I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG display, then flashes purple for a second (Grub menu splash before the Ubuntu splash logo, which doesn't display on the laptop, but does on the HDMI display) then goes blank and never comes online. Even pressing CTRL+ALT+F1-6 does not switch between virtual terminals on the laptop display, it does shift on the mirrored HDMI display. The only way to get a display is to hook up a monitor to the HDMI port and then logging in and setting the display to mirror mode. In fact, this is the only way to install Bionic on the device as even booting the install media with nouveau blacklisted doesn't work. In previous releases, running nouveau.modeset=0 would bring up the display properly and then you could install, but with Bionic, this is does not work. Also, installing the Bionic kernel in Xenial or Artful creates the same condition for those releases.
I have looked at the logs and settings everywhere, and from what I can tell everything appears to be loading properly. Gnome sees both displays when connected, but the laptop display remains black.

[Horst Schirmeier (horst)]

Additional side effect: Bionic sometimes fails to come back from S3 and stays frozen with a black screen.

[hunter` (hunter-87)]

(on ubuntu 18.04 beta 2)i had the same problem after upgrading to nvidia-drivers-390.48, than i could not login even using nouveau after removing all nvidia driver.

GDM3 could not manage to boot properly but just installing lightdm and setting it to default let me login successfully (i did not remove gdm so it was not necessary to do so to fix it)

[chadotter (chadotter)]

I upgraded to Bionic using a GeForce 950 and got a blank screen when lightdm should have been visible. The only way I have been able to get it working has been to delete /etc/X11/xorg.conf which was being used before since my card was overclocked. If nvidia-xconfig is used later and creates xorg.conf again the display breaks again until xorg.conf is removed.

The actual text in xorg.conf was the same as what was working previously with artful and nvidia-384.

[Biswajit biswas (xnorm)]

All things as mentioned above are garbage................

[Horst Schirmeier (horst)]

Seems to have been fixed by a recent update; boots into SDDM now as expected, using nvidia-drivers-390.

[Nguyen Xuan Viet (vietnx)]

I still encounter this issue after upgrade my bionic to the latest update.
The only way to boot to graphic shell is config to using lightdm as default.
Now I'm in unity session and try to install nvidia-396 to see if it fix this issue.

[Nguyen Xuan Viet (vietnx)]

Same issue with nvidia-396, I must config lightdm as default display manager.
After that I can login to ubuntu and ubuntu-unity sessions.

[netslovdlyasnov (netslovdlyasnov)]

It started to work with 390.48-0ubuntu3

Working xorg.conf:

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "None"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Monitor "Monitor0"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Monitor"
 Identifier "Monitor0"
 VendorName "Unknown"
 ModelName "Unknown"
 Option "DPMS" "on"
EndSection

[Ivan Antonijevic (iantonijevic)]

I have same problem. After dist-upgrade from 17.10 to 18.04. I get black screen, and tty only.

I can startx after removing nvidia

sudo apt-get purge nvidia*

sudo apt dist-upgrade

and remove old xorg.conf

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf_bck

Now I can get X with startx, but on boot I still getting only black screen and tty.

[Jean-Philippe Vignolo (popopow)]

Having more or less the same bug as anybody here, but with final Bionic 18.04.

I tried what proposed on #29 and #47 => installing from ppa : https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa without success (either 390 or 396 version of drivers) without success

Tried also installing lightdm instead of gdm3 which just get me a dark screen.

Reverted back to Nouveau drivers doing what Ivan did in #78, I managed to do a startx and get into gnome desktop. Then I rebooted, and gdm3 was just fine and managed to login.

But after another reboot I could just access to gdm3 but system seemed hangs after login (fixed cursor in middle of a dark screen). If I play with alt+ctrl+f1 , f2 It turns back to gdm3 login screen. alt+ctrl+f3 gets me to a standard text login.

I managed to properly boot again after doing a sudo dpkg-reconfigure gdm3 but it worked only once.

Finally, out of desperation, I did another sudo apt-get install nvidia-driver-396 and now everything is working :) Go figure...

My guess is that removing the old xorg.conf file did the trick for me

[Ivan Antonijevic (iantonijevic)]

It's better now. After #78 I run

sudo service gdm3 start
sudo dpkg-reconfigure gdm3

sudo add-apt-repository ppa:graphics-drivers/ppa

sudo apt-get update
sudo apt-get upgrade

activate nvidia-driver-396, and now works, but X is started on ctrl+alt+F2, not on F7, and on F1 I get only mouse pointer, and system blocked :(

[Haneef Mubarak (haneefmubarak)]

I upgraded from Kubuntu 17.10 to 18.04 and have the same issue. I was on the graphics-drivers ppa, so I did a ppa-purge but that was to no avail. For me, the weird thing is that it *seamlessly* says that it switched fine, but that it still just uses the NVidia dGPU instead of the Intel iGPU.

[Haneef Mubarak (haneefmubarak)]

I am also encountering this bug, after upgrading from Kubuntu 17.10 to 18.04.

For me, initially only my Intel driver wouldn't work (with PRIME) - it would instead just go ahead and use the NVidia driver (even when PRIME said Intel was in use).

However, upgrading to {xserver-xorg-video-nvidia-396,nvidia-driver-396,nvidia-utils-396} via the graphics-drivers ppa results in neither operating correctly and the fallback llvmpipe software renderer being used.

[Manvydas (manwiuxas)]

Upgraded from 17.10 to 18.04 less than an hour ago on my laptop.

I'm using nvidia-driver-396 from the graphics-drivers ppa (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) with gdm3. At first, I couldn't even get to the login screen.

#79 (Jean-Philippe Vignolo (popopow)) was right - it seems to be related to the xorg.conf file. Removing it solved the problem for me. Tried rebooting a few times and everything continues to work.

[claudio@ubuntu (claudio.ubuntu)]

To me it looks that there is something broken wider than what most comments touch.
On my laptop with a NVIDIA Corporation GK107M [GeForce GT 750M] (prime) card, since 17.10 (including 18.04):
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, drop frames, etc).
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, drop frames, etc).
- nvidia-340 drivers with prime selection of both nvidia and intel: No Xorg, no Wayland.
- nvidia-390 drivers with prime selection of nvidia: No Xorg, Waylang stuck in login loop.
- nvidia-390 drivers with prime selection of intel on Xorg: too slow to play video (tearing, drop frames, etc).
- nvidia-390 drivers with prime selection of intel on Wayland: everything seems to work.

I would prefer to run Xorg on 18.04 because Wayland on 17.10 crashed one in a while probably due to extensions.

Ping if more info is needed (logs, tests) or it this should be moved to its own ticket.

[Bernadette Addison (baddison1968)]

Having the same issue as most users here. Installed fresh copy of 18.04 to brand new hard drive, brand new dell XPS 15. Nvidia GTX 1050 on board....Installed drivers nvidia-390 from ppa. Now the machine will only boot to black dos screen and I am not even able to get to the tty because none of the combination key commands work. My only recourse is to install from scratch again. Tried this with the normal installation and with the minimal installation. Nvidia drivers simply do not work.

[Bernadette Addison (baddison1968)]

Edited to add: I’ve also tried disabling the nouveau-nvidia drivers before and then after installing the nvidia-390 drivers but still not working.

[Ibrahim Essam (egy-kid1)]

I had the same problem after upgrading from ubuntu 17.10
It was fixed by removing xorg.conf file

[netslovdlyasnov (netslovdlyasnov)]

In my case removing xorg.conf didn't help because nvidia driver reported "no device found", so I had to use minimal xorg.conf (from my previous answer) to make the driver find the card (BusID "PCI:1@0:0:0")

Also I confirm that nouveau driver is buggy and hangs computer on switching consoles.

[omar reddam (omarreddam)]

Still having the issue as today (18.04 final) with a GTX 1050 Ti (Asus Prime X299-Deluxe mobo).
Frozen black screen at startup after trying versions 390 & 396 of the NVidia drivers.

[Bernadette Addison (baddison1968)]

@omar reddam - I also have the GTX 1050 in my new dell XPS-15 laptop. After deleting xorg.conf as recommended here, I went a step further and performed this command to blacklist nouveau:

$ sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
$ sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"

Then I updated initramfs:
$ sudo update-initramfs -u

And lastly, I installed the nvidia software package via "sudo apt install nvidia-390" before rebooting.

BLACK SCREEN.....*sigh*

Has anyone tried to download the bin files directly from nvidia.com website?
What were the results?

I think I'll go ahead and try that. Will report back my findings.

[Bernadette Addison (baddison1968)]

so, I downloaded various versions of the Linux drivers directly from Nvidia.com website. Went thru the installation process - each time starting over from scratch, formatting and reinstalling Ubuntu 18.04 so I would have a "blank canvas" to work with. This process failed too. My thinking was that perhaps the Nvidia drivers may/may not contain a component that would not break the laptop. But this was a futile effort.

Guess I will wait for a few more suggestions/ideas on how to get this graphics card working once and for all.

[Kyle Weber (kyew01)]

Hopeful this bug was fixed (as it improperly states above), I did a fresh install on my machine with an Nvidia 1060. It will boot, then go to a black screen on login, etc. I tried what people mentioned above, but was not able to get a stable working system. I went back to 17.10 and have not had any issues since.

[Alexander Kops (alexkops)]

Dell XPS-15 with GTX 1050 user reporting in, for me just deleting xorg.conf and rebooting worked (using nvidia-390).
I had upgraded from 17.10.

[Nguyen Xuan Viet (vietnx)]

I think there is something wrong with gdm3/wayland/NVIDIA proprietary driver.
If I config gdm3 as default display manager, when rebooted, I have a black screen but I'm able to switch to other tty by press crtl-alt-f2 to f7.
Then I edit /etc/gdm3/custom.conf uncomment line 7th to WaylandEnable=false then rebooted, then I have system hange after reboot :(. It seems that the OS is stuck in gdm3 service.
I tried to change/regenerate/delete xorg.conf but it simply doesn't work. So I think xorg.conf is not the root cause for me.

If I uninstall all nvidia stubs and install nouveau xorg driver, the system is able to boot to graphic shell with gdm3 as a display manager. Unfortunately, the nouveau driver does not support CUDA computing framework and the performance of this driver is very poor when compare to the binary one.

If I config to use lightdm as default DM, it works with NVIDIA binary driver, but this is not what I expected. I expect the system have to work with gdm3, ubuntu-xorg session and NVIDIA proprietary driver. I have an app that need xorg session and CUDA, so I must install NVIDIA binary driver.

PS: If you are able to boot to graphic mode but stuck with login loop, you could try to delete the ~/.Xauthority file then reboot. It worked for me.

[Nguyen Xuan Viet (vietnx)]

My hardware configuration is CPU Intel E3 1231 v3 (no iGPU), GPU NVIDIA GTX 1060 6GB, RAM DDR3 16GB

[Tom (tom-lorinthe)]

Dell XPS15 9560 - System is now usable, after nightmare of trials and about 50 reboots.
If I recall correctly: Ctrl-Alt-F2 / F3 on login prompt; sudo update; sudo apt purge nvidia*; sudo apt install nvidia-390;
I switched to Wayland and back, all broken again, so then again in tty at login prompt: sudo nvidia-xconfig (to create /etc/X11/xorg.conf) and then sudo rm /etc/X11/xorg.conf No idea why to rm xorg directly after creating to make discrete graphics work and put Nvidia back in its cage, but it did. Tried sudo nvidia-settings but that does not work as system is convinced nvidia is not loaded...

Also for what it is worth, I added GRUB_CMDLINE_LINUX_DEFAULT="splash acpi_rev_override=1 nouveau.runpm=0" as without the acpi override logout takes ages...

I wont even dream about the good old days of 17.04/17.10 when I could switch Nvidia / Prime on and off... Note to myself: avoid Nvidia in laptops like the plague. Please... read this again, Tom, in 3 years when a new laptop is due **no optimus/prime/Nvidia on laptops** ... !!

[Bernadette Addison (baddison1968)]

@Tom - I have the same exact machine. I tried each of your steps in order, and I still get only a black screen boot with a few PCIe Bus Errors. Did you perform a fresh install from scratch or was this coming from an upgraded OS? Does that even matter???

[Tom (tom-lorinthe)]

@Benadette: I've done both several times: upgrade and fresh reinstall; same troubles so it does not seem to matter. I also got the pci bus errors at first, before the nvidia driver took it's place . Do you get to the login prompt? My procedure above, starting at the login prompt with Ctrl-AltF2 or F3, needed to be repeated a few times with a system boot after nvidia-xconfig and then rm of the xorg.conf with another reboot... weird stuff...
I know things will fail as soon as the login asks me password twice, complaining first time was wrong. If it asks password once, I am confident to end up to my desktop...

For what it's worth, my /etc/default/grub has now, and this seems best so far:

GRUB_CMDLINE_LINUX_DEFAULT='acpi_osi=Linux acpi_osi=! acpi_osi="Windows 2009"'

That said, my system still suffers from 1 minute+ long shutdown times, so I am not there yet. Other than that it seems to run... I keep you posted...

[Kyle Weber (kyew01)]

At the top of this page it says "Fix Released". Does anyone know to to get them to change the status to an open bug and re-evaluate it? It's clearly not fixed.

[Bernadette Addison (baddison1968)]

I agree! This issue is definitely NOT FIXED!

[Princeash (ashrefalhor)]

I am still facing the same issue with Nvidia 820m , it's not fixed

[Willem Holleder (raice-f4h)]

Same problem here with 4 1050TI cards. Installed 18.04, installed 390 driver, system doesn't boot anymore

[Donjan Rodic (bryonak)]

Upgraded 17.10 -> 18.04, Thinkpad X460p with GeForce 940MX.
No issues before (even both prime AND bumblebee worked).
Exhaustively tried combinations of blacklisting modules, nvidia.modeset kernel lines and reinstalls of both default and ppa 390/396 drivers.
The system will not boot past the filesystem check with nvidia drivers (and prime/bumblebee can't load them either), which renders the GPU unusable.

[Milan Pultar (pultami1)]

Hi. I am new to this forum. I have recently bought Dell XPS 15 9560 with GTX 1050 graphic card. I am trying Ubuntu 18.04, but I can't find any working nvidia driver. From ppa I tried 384, 390 as well as 396, each installation results in black screen. If I uninstall nvidia driver, laptop boots normally. I also tried the proprietary driver from Nvidia website, which didn't work as well. I also tried to switch using nvidia-prime after installation, which broke Ubuntu and I had to reinstall the system. So... are there any fixes coming? I don't have xorg.conf file so deleting it is not an option.

I did not imagine this hardware has so bad support on Linux. Did anybody have good experience with older Ubuntu and GTX 1050? I don't want to give up and agree this issue is NOT FIXED.

[James Kent (jkentjnr)]

Reiterating the above experiences regarding the Dell XPS 9560. Black screen with nvidia drivers. Cannot workaround this issue unless I remove the drivers.

[Ruslan (guyfulla)]

The issue is affecting me as well, GTX 1050, ASUS laptop.
None of the resolution tactics proposed so far helped in loading the drivers properly.
The only way to load the system is to add nomodeset and acpi=off in the grub menu.

[Tim Richardson (tim-richardson)]

This is not a new problem, and it affects every gdm3-based distro that I have used. Long story short; if you want to use modeset=1 with nvidia to get rid of tearing (which would be every linux Optimus user on the planet), gdm3 doesn't work. No one seems to know why.
Change your display manager to lightdm and enjoy life again. I have two Optimus laptops.

sudo dpkg-reconfigure lightdm

[Nicolae Righeriu (nrigheriu)]

no fix is released, please change the status. Things are definetly not fine yet

[Nicolae Righeriu (nrigheriu)]

I'm running Ubuntu 18 (although I had exactly the same issue on 16 too) and instalation of Nvidia drivers works fine, until I choose to change to Intel graphics card. Then, after rebooting I can't open the Nvidia GUI anymore. This means I can't use my Hdmi port. Seems like I'll have to get back to Windows for a while because of this matter unfortunately

[Jean-Sébastien Herbaux (convly)]

I've upgraded from ubuntu 17.10 to 18.04 and I got the same issue.

When I boot on my laptop with a gtx 1070, I can see on my laptop screen and my monitor connected through a USB-C adapter the startup console starting all the modules. On the other hand I have the login screen working well on my external monitor (through HDMI).

It is important to notice that I cannot detect any of the two others display through the device manager or any command.

I believe that the monitor connected through HDMI only is using the integrated Intel GPU while my two other screens uses the nvidia graphic card.

This bug is definitively not fixed at all and it is astonishing to see that it has been marked as 'resolved' while a lot of users are still getting blocked from using their computer (personal or work...).

[claudio@ubuntu (claudio.ubuntu)]

There are two setups where the solution is with my setup (NVIDIA Corporation GK107M [GeForce GT 750M], laptop with nvidia and intel):
- Use Wayland with nouveau drivers: performance OK.
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" (see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when you install the binary drivers).

What doesn't work (black or too slow):
- nvidia drivers.
- nvidia drivers with intel selected by prime.
- nouveau drivers on Xorg.

Here are the more expanded instructions. Be sure to know what you do, you won't loose files, but you may make your system unbootable if you type an error.

1. Make sure nvidia is not blacklisted. E.g. remove bumblebee. Have a look in /etc/modules and /etc/modprobe.d/*:
$ sudo apt-get remove --purge bumblebee
$ grep nvidia /etc/modules /etc/modprobe.d/*

"blacklist nvidia" is what's mostly used.

2. Add "modeset=1" to grub:
$ sudo vi /etc/default/grub
(or sudo nano /etc/default/grub)

Add nvidia-drm.modeset=1 to the GRUB_CMDLINE line (with the quotes):
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

Activate the changes:
$ sudo update-grub

4. Install Nvidia drivers:
$ sudo ubuntu-drivers autoinstall
$ sudo prime-select nvidia

5. Reboot

Be warned that modeset=1 disabled the virtual consoles (ctl+alt+f<nr>).

[claudio@ubuntu (claudio.ubuntu)]

Forgot to add:
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" (see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when you install the binary drivers). Performance: very good.

[iuuuuan (ivan-janes)]

I have managed to work nvidia binary drivers version 340.102 with kernel 4.15 with patch https://pastebin.com/raw/fVJVvQy7 , which is mentioned on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1-patches-for-384-98-and-340-104.

My nvidia m720 graphics is working again on Ubuntu 18.04.

1. Install prerequisites
# apt-get install build-essential libc6:i386

2. Download nvidia binary drivers from http://www.nvidia.com/content/DriverDownload-March2009/confirmation.php?url=/XFree86/Linux-x86_64/340.104/NVIDIA-Linux-x86_64-340.104.run&lang=us&type=TITAN

3. Download patch for nvidia binary drivers in same directory
# wget -O nv_patch_340.104_linux_kernel_4.15 https://pastebin.com/raw/fVJVvQy7

4. Boot ubuntu in single mode https://linuxconfig.org/how-to-boot-ubuntu-18-04-into-emergency-and-rescue-mode (How to access emergency.target at boot)

5. Enter root password

6. Unload nouveau driver
# rmmod nouveau

7. Blacklist nouveau driver
# echo "blacklist nouveau" > /etc/modprobe.d/blacklist-nouveau.conf
# echo "options nouveau modeset=0" >> /etc/modprobe.d/blacklist-nouveau.conf

File /etc/modprobe.d/blacklist-nouveau.conf should have following entries:

blacklist nouveau
options nouveau modeset=0

8. Update initial ramdisk
# update-initramfs -u

9. Go to directory which contains downloaded nvidia-340 binary driver and set executable attribute
# chmod +x NVIDIA-Linux-x86_64-340.104.run

10. Apply the patch to driver (maybe this could be done after downloading kernel 4.15 patch - have not tried it ...)
# ./NVIDIA-Linux-x86_64-340.104.run --apply-patch nv_patch_340.104_linux_kernel_4.15

This will build custom NVIDIA binary driver package with name NVIDIA-Linux-x86_64-340.104-custom.run

11. Set executable attribute for custom driver package
# chmod +x NVIDIA-Linux-x86_64-340.104-custom.run

12. Install the driver with command
# ./NVIDIA-Linux-x86_64-340.104-custom.run

Ignore errors and enable DKMS

13. Reboot computer
# reboot

Nvidia driver 340.120 should be loaded now and graphics fully working. This method is to complicated so I will also try methods mention in #112 and #113.

[Tom (tom-lorinthe)]

Today I got all working, but although prime-select query showed me "nvidia", nvidia drivers were not loaded and nvidia-settings did not start. I regret that I decided to run "sudo prime-select intel". Login worked but it broke suspend mode and my logout/shutdown times are horrible: 1,5 minutes.

* This makes the intel mode unusable for the XPS and I think all optimus prime Nvidia laptops, so if you need that, downgrage to 17.10 might be only solution for now ?

Running prime-select nvidia gives good performance and suspend and logout work again, but with running fans and hot laptop.

[Jaume (minterior)]

Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade.
Finally solved after lots of retries and reboots. I have now:
Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
- sudo add-apt-repository ppa:graphics-drivers/ppa
- sudo apt update
- sudo apt dist-upgrade
Replaced manually nvidia 390 drivers by the newest 396
Purged nouveau package because I saw a "segmentation fault" log in /var/log/Xorg.0.log
- sudo apt purge xserver-xorg-video-nouveau
- sudo vi /etc/X11/xorg.conf -> uncomment line #Driver "nvidia" of Section "Device". So my xorg.conf file is exactly the same as the pasted in comment #77 without the last Section "Monitor".
- sudo reboot

After the reboot I see my previous sddm login screen instead of a tty and I can login normally :)

[netslovdlyasnov (netslovdlyasnov)]

For PRIME users: as a workaround you can make you X session work with Intel driver with this minimal xorg.conf

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "Screen0" 0 0
    Option "Xinerama" "0"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    Option "DPMS" "on"
EndSection

Section "Device"
    Identifier "intel"
    Driver "intel"
    Option "AccelMethod" "sna"
    Option "TearFree" "true"
    BusID "PCI:0@0:2:0"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
    Monitor "Monitor0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "intel"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Virtual 1920 1080
        Depth 24
    EndSubSection
EndSection

Make sure to put your own BusID and screen size. Both are mandatory.

[Jean-Sébastien Herbaux (convly)]

#116 worked for me, thanks

[Tom (tom-lorinthe)]

#117 worked for me, although "suspend" is still shaky; 50% of time I need to force power off.

[Bernadette Addison (baddison1968)]

tried #116 and also #108. Now all I get is a boot loop at the lighdm login screen. Put in password and it brings me back to login screen. This is so frustrating....smh

[Tom (tom-lorinthe)]

@Bernadette: If I would have same situation again, I think I would:

1 - Ctrl-Alt-F3/2 at login prompt
2 - sudo apt purge nvidia*
3 - sudo apt install nvidia-390
4 - sudo prime-select intel
5 - sudo nvidia-xconfig
6 - sudo nano /etc/X11/xorg.conf
7 - .. and replace with contents of #117
8 - sudo nano /etc/default/grub
9 - .. GRUB_CMDLINE_LINUX_DEFAULT="'quiet splash acpi_osi=Linux acpi_osi=! acpi_osi=Windows 2009' nouveau.runpm=0"
10- sudo update-grub
11 - sudo reboot
12 - login...
13 - and start praying...

[Bernadette Addison (baddison1968)]

@Tom - getting closer! I can now login...but icons are HUGE!!! Lol. Need to fix resolution

[Thijs Kaper (thijs-kaper)]

I'm using a Dell m4800, with "NVIDIA GK107GLM Quadro K1100M" (3840x2160 pixels). Symptom; gdm login screen shows normally, but after typing password and hitting enter, I end up on black screen. This is after upgrade from 17.10 to 18.04.

I found a silly workaround (after trying many many other suggestions / driver re-installs), now using nvidia-driver-396 or nvidia-driver-390; create (if not exists) a file /etc/rc.local, with this content:

#!/bin/bash

sleep 1

exit 0

And make it executable: chmod 755 /etc/rc.local

What also worked for me, is start laptop, wait for login screen, and use another machine to ssh into the laptop, and execute "sudo service gdm stop ; sleep 5 ; sudo service gdm start".
After that, I could normally log on.

For me this seems to indicate some sort of timing or initialization issue...

[Cédric (cedricbonhomme)]

@Thijs Kaper: I have the exact same problem.

My alternative workaround:
Like you I authenticate, black screen after typing the password and hitting enter. Then I go to tty2, authenticate in the terminal, and type 'startx' (and 4 times Ctrl+C). And finally KDE starts without problem on tty2. This is crazy.

Like @Bernadette Addison I had huge icons. It was impossible to set a higher resolution with the KDE display manager. So I used xrandr:
xrandr --output eDP-1-1 --mode 1920x1200 --scale 1x1
for example.
The resolution is fine even after a reboot.

I also want to add that I am actually using the nvidia driver 396.24. Because I had so much problems before... I tried to add the graphics-driver ppa as advised by @Chris McDonough. I do not know if finally this helped me a little. Maybe I should switch back to 390.

My graphical interface is really a mess since the upgrade to 18.04 :-(

[Emiliano (retorquere)]

I've just ran do-release-upgrade on a Lenovo P51, and the systems hangs just after "Starting Session c1 of user gdm". I get a little further by purging nvidia-* (I get the GDM greeter again) but after logging in there, the screen freezes and a little later I'm kicked back to the greeter.

[Emiliano (retorquere)]

I tried #116 by @minterior, and I now have a working desktop, but it feels substantially more sluggish than it was under 17.10.

[Kirill Romanov (djaler1)]

Why this have "Fix released" status? I cannot login after "prime-select intel", I see only a black screen

[Jan Wester (j-vester)]

I just tested the thing in #123 and I can only conclude: i am writing this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can only agree to what Thijs says. This sounds like a timing problem.....

[Bernadette Addison (baddison1968)]

Back to where I started with a non-bootable machine, after modifying xorg.conf listed in post #121. I will go aheada purge these nvidia drivers again, and try #123 to see if that works. This is a crazy mess!!

[Bernadette Addison (baddison1968)]

Is there any way possible to gain early access to the "FIX RELEASED" files???

[Tom (tom-lorinthe)]

This all might be related to https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363 I think...

[Symin (symin)]

In my case it was... complicated.

Turns out that after upgrade to 18.04 wayland was on by default for me.
prime-select intel worked fine
prime-select nvidia gdm would not show

Changing wayland to xorg in gdm (with intel) would not work - login screen just kept reapearing. Forcing xorg through /etc/gdm3/custom.conf only made it worse.

In the end I have decided to try and unplug my DP cable from the mainboard and plug it into the gfx card. This has worked. After the reboot GDM has showed up and only xorg was available (I have switched to xorg before I swapped the cable, though).

No reverse prime for me :( Hopefuly plymouth works with nvidia these days or this gets fixed soon.

[Kyle Weber (kyew01)]

I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to give up on Ubuntu and give that a try. Some word of reassurance from the Ubuntu team here would be nice. Where they marked this as fixed, I'm not hopeful of a fix--at least anytime soon. If anyone has found a true and simple workaround, please let us know! Otherwise, I think my hardware will require me to look somewhere else...

[Joseph S Rebeirro (teddy-rebeirro)]

hey

There i am using ubuntu bionic 18.04 kernel 04.15.21

cant login on gdm or lightdm freezes on entering password or access tty on install nvidia-390 , nvidia 396 from ppa:graphics-drivers/ppa and nvidia-driver-390 from bionic main repo

used to have black screen on boot suddenly rectified

nouveau driver ends up in cpu hard and soft lock

need help desperately. not able to access GPU

[Tom (tom-lorinthe)]

@Joseph: did you try #121 ?

[Joseph S Rebeirro (teddy-rebeirro)]

@tom-lorinthe

I have no issues with accessing Intel I just blacklisted nouveau for that purpose. I wanted to use Nvidia but on evry install it seems to crash the OS

will try and fix nvidia-prime after getting nvidia driver working

there is also dkms seems not to install in the kernel 4.15.21

anyways as you suggested it will attempt it thank you

[Joseph S Rebeirro (teddy-rebeirro)]

no #121 don't work for me

I can access my desktop because i have blacklisted nouveau and using my intel gpu system which I assume is functioning via mesa drivers nomodeset also works
only issue is if i try to run nvidia

[iuuuuan (ivan-janes)]

I have finally getting to work my ubuntu 18.04 with drivers installed from additional drivers.

After update from ubuntu 17.10 to 18.04 nvidia-390 drivers were installed, nvidia-340 package was metapackage for nvidia-390.

Today I was able to install nvidia-340.106 driver directly from additional drivers, but they unfortunately did not work.

I have described method how to compile nvidia-340.104 for kernel 4.15 in #114 and this worked without problems.

I did comparison of nvidia-340.104 and nvidia-340.106 and found out that in nvidia-340.106 driver has fix for issue between the NVIDIA kernel driver's Page Attribute Table (PAT) support and the KPTI page table isolation.
no

After few tries with different kernel settings I have noticed that I have nopat option enabled in grub kernel boot.

Simple fix for that was to remove nopat option in grub

1. Open grub configuration file /etc/default/grub
# sudo vi /etc/default/grub

or

# sudo nano /etc/default/grub

2. Remove nopat from GRUB_CMDLINE_LINUX_DEFAULT

My current options looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw"

3. Save file and exit editor

4. Update grub configuration

# sudo update-grub2

5. Reboot
# sudo reboot

6. Install recommended drivers
# sudo ubuntu-drivers autoinstall

7. Reboot
# sudo reboot

[Dedas (andreas-winkler)]

Ivan Janes,

With those options NVidia card seems to be disabled properly but now the systems hang whenever I plug in the laptop power charger. Also, I can only use Wayland and not Xorg (freeze again). Maybe the last one is a bad xorg.conf?

[iuuuuan (ivan-janes)]

Andreas, nvidia on my notebook is enabled and working properly. It is not disabled.

Currently I only one option enabled for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="splash"

I do not have /etc/X11/xorg.conf file.

If you backup file /etc/X11/xorg.conf, remove it and reboot laptop, does it help ?

I have disabled wayland in /etc/gdm3/custom.conf with option (uncomment option in file):
WaylandEnable=false

What is prime-select query output ? - on my notebook it returns nvidia
$ prime-select query
nvidia

[Dedas (andreas-winkler)]

Thank you for your answer. I solved the problem with nvidia prime not really disabling the nvidia card (still drawing power) when switching to Intel with:

sh -c 'echo auto > /sys/bus/pci/devices/0000\:01\:00.0/power/control'

Almost halved the power draw on my Dell XPS 15.

[Tom (tom-lorinthe)]

@Dedas can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?

[Volodymyr Buell (vbuell)]

Got back screen yesterday but for my case it was a disk space issue. Booted into recovery mode, freed up space in root partition and rebooted. Everything seems work ok after that... Apparently nvidia does need some free space to boot up (it wasn't an issue before i think. My system partition is really tiny so it's almost normal to have zero free space on it)

[Milan Pultar (pultami1)]

I am not sure whether it is ok to post here, but I have lately found this github repo dedicated to making Ubuntu run on XPS 9560. It works for Ubuntu 17.10 and 18.04 will be hopefully added as well. Many of us have this laptop and the repo partly adresses the issues mentioned here so I thought posting the link here might not be a bad idea. I have not tried this myself yet, but I guess installing U17.10 is the only option now because of the drivers problem...

https://github.com/stockmind/dell-xps-9560-ubuntu-respin

[Dedas (andreas-winkler)]

@Tom

"can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?"

Yes it should be safe. It it freezes just restart your machine, the setting will be gone.

It turns off the nvidia gpu så no.

It is needed every time you boot. So use rc.local or something similar.

[Kyle Weber (kyew01)]

I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I purged the nvidia drivers, installed 396 through the PPA, rebooted, and it came up and worked. It is a tower with GTX 1060.

[Tom (tom-lorinthe)]

@Dedas: I cant see any difference; power consumption on Dell XPS 15 9560 stays the same...

[Tom (tom-lorinthe)]

It seems with the following two commands, I can get my power from ~15W to ~8W on Dell XPS 15 9560:

 # move from Nvidia to intel graphics (if not already done)
 prime-select intel
 # switch of power to Nvidia (repeat after each laptop start)
 sudo sh -c 'echo auto > /sys/bus/pci/devices/0000\:01\:00.0/power/control'
 sudo sh -c "echo "1" > remove"

[Dedas (andreas-winkler)]

If you want it to stay create a file /etc/rc.local and make it executable:

sudo chmod +x /etc/rc.local

In rc.local type:

#!/bin/sh -e
sh -c 'echo auto > /sys/bus/pci/devices/0000\:01\:00.0/power/control'
sh -c "echo "1" > remove" (I didn't need this)
exit 0

[Tom (tom-lorinthe)]

echo "1" > /sys/bus/pci/devices/0000\:01\:00.0/remove is required for me to powerdown nvidia, but it results in powerdown freeze

Still investigating ... ((

[Bernadette Addison (baddison1968)]

also, still investigating. every one of these fixes all lead to the same outcome for me - cannot boot with nvidia proprietary drivers installed, or else stuck in a boot-loop after entering password at gdm screen.

[Gmgarciam (gmgarciam)]

Hello. My situation was very complicated, and none of the fixes I found would work. I am running a Nvidia GTX970 with an Intel CPU and using a dual monitor setup. Ubuntu 17.04 was working very well. Later upgrading to Ubuntu 17.10, the Nvidia graphics became an issue because of Wayland, but I followed this guide and was able to set it working for 17.10, https://charlienewey.github.io/getting-nvidia-drivers-working-on-ubuntu-17-10/ . For 18.04, nothing I found online was working. I was able to setup Openbox and use that to investigate the matter. I suspected it was some sort of opengl problem since all applications requiring it would fail to run and cheking with the terminal, it would say that the libGLU1.1.so was not found, or one of those opengl libraries. Upon further investigating, it turned out that the xorg that comes stock with 18.04 does not have the latest Mesa patch that supports nvidia graphics cards. So I ended up getting the padoka ppa in order to get the latest xorg and mesa. Upon doing so, everything is working fine. I thought this fix was a little unorthodox being that I believed that Padoka was for Nouvou and AMD cards but, apparently it fixed the issue with the proprietary 396 drivers. I had the same issue with the 384, and 390. So I am not sure if this fix only pertains to the Nvidia 396 drivers, but I believe the problem stems from an Xorg that does not have the latest Mesa.

https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa

[Tom (tom-lorinthe)]

@bernadette, it baffels me. Today my Xps 15, 9560 works flawlessly fast and nimble. I also nailed the power drain and now have ~5W running on battery, see https://github.com/stockmind/dell-xps-9560-ubuntu-respin/issues/8

Makes me thinking... what BIOS version do you have ? I run 1.9.4

[ulyses (jose-abrural)]

The only working solution for me for the Nvidia graphic card problem in Ubuntu 18.04, was to follow the instructions from this page:

https://medium.com/@emtudo/ubuntu-18-04-travamento-com-placa-nvidia-3720dfe7410a

and then start the system through recovery mode.

[claudio@ubuntu (claudio.ubuntu)]

So, if this bug is marked as "fixed released" and 500 comments further it's clear it doesn't fix anything, should we open a new bug report?

[Aurélien PIERRE (aurelienpierre)]

I have the same problem of power drains even when prime-select is on intel. I know for sure that the nvidia GPU is running because the external HDMI port is working and shouldn't since it's wired to the GPU.

 sudo sh -c 'echo auto > /sys/bus/pci/devices/0000\:01\:00.0/power/control'
 sudo sh -c "echo "1" > remove"

gives no result on my system (Nvidia Quadro M2000M/Thinkpad P51).

[Tom (tom-lorinthe)]

@aurelienpierre: are you sure your laptop uses the same device number as the Dell XPS 15 this script was for (0000:01:00.0)?

[Adrian H (adrelino)]

I had working proprietary drivers for my GTX 1080 Ti and then I upgraded from 17.10 to 18.04. Everything worked well, gdm login screen appears, but AFTER entering username and password and hitting ENTER, I only get a black screen.

For me #123 solved the problem, thanks for the detailed description.

Just wanted to add that when booting in recovery mode, the timing issue also did not appear and I was able to login.

[maf2 (sw-mariusz)]

The graphical display failed to boot on laptop. The same system Ubuntu 18.04 works on the desktop.

https://drive.google.com/file/d/19i41gRcpzIErlU82Ekk-Hq5JUpUByHEw/view?usp=sharing

[Nicolae Righeriu (nrigheriu)]

I opened a new bug report since nobody seems to be able to change the status of "Fix Released" which is clearly not the case. Please comment and subscribe to this one
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113

[Battant (mparchet)]

Hello,
The GUI (graphicc user interface)!dose not start If i have no internet connection (offline )
An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme
The internet must connect at start (Ethernet or WiFi)
Same problem whith the live dvd ?
Why this internet connection deprndence
Why the GUI coud’nt Start ofline
Could you confirme this and help me to fix this issue
Thanks for your supporters
Best regards

Battant

[William S Gregory (0c-bill)]

Also having a this problem. Why is this marked fixed?

[Tom (tom-lorinthe)]

It's indeed a big mystery when one of the maybe most serious bugs in 18.04 is marked as fixed while it clearly is not....

[samurailink3 (samurailink3)]

This is not fixed.

[Chris (chris12599)]

I started to experience this problem for the first time on July 2nd, 2018 after upgrading to kernel 4.15.0-24-generic. It only happens on machines with a Nvidia card. It does not matter if ANY Nvidia drivers are installed or not. I downgraded to kernel 4.15.0-20, 0-22 and 0-23 but it didn't fix the issue. I confirmed this on 2 machines with Nvidia cards.

adding deb http://de.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted

to /etc/apt/sources.list

and running apt install libglvnd0 xserver-xorg-core libgl1-mesa-glx did not help. At least not on Linux Lite v4.0.

It's takes about 3mins and 6 seconds to get to the desktop. Everything works as normal after that.

So i ran some tests....

Lenovo ThinkPad W530
Model Type: 2436CTO GB
16GB RAM
Intel i7-3920XM @ 2.90Ghz
4 Core
256 SSD

lspci -vnn | grep VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller])

Xubuntu 18.04 LTS (This is my main OS) - Broken

Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install.

Works after fresh install but not after updates applied through Software Update.

Also tried kernel v4.17.0 and v4.17.3

login with ctrl+alt+f1 and after a few seconds i see:

nouveau 0000:01:00.0: msvld: unable to find firmware data

dmesg | grep nouveau

[ 34.304193] nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
[ 34.304206] nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2
[ 34.304210] nouveau 0000:01:00.0: msvld: unable to load firmware data
[ 34.304277] nouveau 0000:01:00.0: msvld: init failed, -19

Kubuntu 18.04 LTS - Works

Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install and after updates applied through Discover application.

KDE neon User Edition 5.13 - Works
16.04

Kernel v4.13.0-45 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install.

Works after fresh install and after updates applied through Discover application.

Installed nVidia driver v384.130 (nvidia-384) and still working.

Lubuntu - 18.04 LTS – Works

Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install and after updates applied through Software Updater application.

Installed nVidia driver v390 (nvidia-driver-390) and still working.

Mate 18.04 LTS - Broken

Kernel v4.15.0-24 after updates.

Updates downloaded during fresh install. Full install selected.

Works after fresh install but not after updates applied through Software Update.

"Could not update ICEauthority file /home/user/.ICEauthority" appears during auto login. Desktop does not finishing loading but keyboard shortcuts work.

Elementary OS 0.4.1 Loki – Works

Kernel v4.15.0-24 after updates.

Update...

[hoan (hoan)]

you might be interested to try liveiso xubuntu-bionic nvidia-390.48

a live_iso bionic-xubuntu with nvidia-390.48 prime-switchabled to experiment :
it's working on Acer VN7 4GB ram

boot the live iso http://sourceforge.net/projects/toysbox/ xubuntu-18.04-4.15.0-24-nvidia390.48.iso
open a terminal ctrl-T : inxi -G to check on which graphic card it is running
sudo prime-select query gives equivalent result on running graphic card
sudo prime-select intel to switch to the intel graphic
sudo prime-select nvidia to switch to the nvidia graphic

The prime version here is from Mathieu Gras ( problem and partial solution originally raised up by Tim Richardson )

https://devtalk.nvidia.com/default/topic/1032482/linux/optimus-on-ubuntu-18-04-is-a-step-backwards-but-i-found-the-first-good-solution/4

but to make the whole stuff running as liveIso requires lots of sweats ...and funs !!!!!

Here is a short log :

$ cat Live-xubuntu-bionic-nvidia-390.log

xubuntu@xubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=(loop)/casper/vmlinuz iso-scan/filename=/iso/xubuntu-18.04-4.15.0-24-nvidia0.iso file=/cdrom/preseed/xubuntu.seed waitusb=5 boot=casper systemd.debug-shell=1 systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on

xubuntu@xubuntu:~$ uname -a
Linux xubuntu 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

xubuntu@xubuntu:~$ inxi -G Graphics:
Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
Card-2: NVIDIA GM107M [GeForce GTX 860M]
Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@60.02hz OpenGL: renderer: GeForce GTX 860M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.48

xubuntu@xubuntu:~$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x23a cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 1 name:NVIDIA-0 Provider 1: id: 0x44 cap: 0x6, Sink Output, Source Offload crtcs: 3 outputs: 2 associated providers: 1 name:modesetting

xubuntu@xubuntu:~$ glxinfo | grep NVIDIA
server glx vendor string: NVIDIA Corporation client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
OpenGL core profile version string: 4.6.0 NVIDIA 390.48
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 390.48
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string:
OpenGL ES 3.2 NVIDIA 390.48

xubuntu@xubuntu:~$ glxgears
Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate.
69297 frames in 5.0 seconds = 13859.334 FPS
68090 frames in 5.0 seconds = 13617.823 FPS

xubuntu@xubuntu:~$ glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres) Visual ID of window: 0xa8 Context is Direct OpenGL Renderer: GeForce GTX 860M/PCIe/SSE2
1914.953887 frames/sec - 2137.088538 Mpixels/sec
1964.035952 frames/sec - 2191.864122 Mpixels/sec

Troublshootings

1 If at boot you get a black screen ...really nothing else after 2min don't panic ;
Open a VT2 with ctrl-F2 Login as xubuntu user with blank password ;
sudo su to get root permission
lsmod | grep nvidi...

[hoan (hoan)]

https://sourceforge.net/projects/toysbox/files/bionic-nvidia/xubuntu-18.04-4.15.0-24-nvidia.iso/

 sorry for typo

[Mathew Garland (kromosome)]

Ubuntu 18.04
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)

Same issue faced here. Initially everything was running well until I tried installing the CUDA libraries for Machine Learning purposes. This was the start of this disaster.

This Issue should be considered a show stopper!

[masato-hi (masato-hi)]

I am using Google Translate because English is not very good.
I am sorry if there is content difficult to understand.

```
$ uname -srvpio
Linux 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 GNU/Linux

$ nvidia-smi
Fri Jul 13 14:12:01 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.67 Driver Version: 390.67 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce 940MX Off | 00000000:01:00.0 Off | N/A |
| N/A 47C P0 N/A / N/A | 726MiB / 2004MiB | 4% Default |
+-------------------------------+----------------------+----------------------+

```

If you are using a NVIDIA GPU built-in laptop please try the following method.

Execute `prime-select query`.
If the output is not `nvidia`, execute `prime-select nvidia` and restart it.

Please execute `lshw -C display`.

■ *-display UNCLAIMED If is a device of `vendor: Intel Corporation`
If `nomodeset` or `i915.modeset=0` is included in GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX in `/etc/default/grub`, delete it, run update-grub and restart it.

■ *-display UNCLAIMED If is a device of `vendor: NVIDIA Corporation`
If `nomodeset` or `nvidia-drm.modeset=0` is included in GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX in `/etc/default/grub`, delete it, run update-grub and restart it.

If `inxi` is not installed, please run `apt-get install -y inxi`.

Please execute `inxi -G`.

If `drivers: nvidia` is displayed, you need to add the following to `/etc/X11/xorg.conf`.
```
Section "Device"
    Identifier "intel"
    Driver "modesetting"
    Option "AccelMethod" "None"
EndSection
```

If `drivers: modesetting,nvidia` is displayed, please delete or comment out `Monitor "Monitor 0"` from `Section "Screen"` including `Device "nvidia"`.
```
Section "Screen"
    Identifier "intel"
    Device "intel"
    Monitor "Monitor 0"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
# Monitor "Monitor 0"
    DefaultDepth 24
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
    Option "ConstrainCursor" "off"
    SubSection "Display"
        Depth 24
        Modes "nvidia-auto-select"
    EndSubSection
EndSection
```
Then restart it or execute `service gdm3 restart`.
that's all.

This problem is caused by the fact that nvidia-xconfig generated /etc/X11/xorg.conf does not include the loading of the modesetting driver, and the monitor output is connected to the nvidia device.
(I am not familiar with X11 so I do not know if that is correct)

Perhaps the smallest /etc/X11/xorg.conf that solves this problem is:
(BusID varies depending on the environment)
```
Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "m...

[Nguyen Xuan Viet (vietnx)]

Solution in #123 did not work for me, even with higher sleep time.
So I have to switch back to lightdm.

[Artyom (artyom-szasa)]

I think I have the same issue.
Difference is that everything worked as charm until I've updated some non-nvidia packages. Since then I'm stuck to uning nouveau as none of the workarounds worked.

HW:
ROG STRIX GL503VM-FY022
nVIDIA GeForce GTX 1060 6GB

What worked fine before update:
kernel 4.15.x-x with nvidia 390 (ubuntu repository)
kernel 4.17.x with nvidia 396 (ppa)

After the update it worked one more time with 4.15.x with
options nvidia_390_drm modeset=1
in /etc/modprobe.d/xxxx.conf

Since after next reboot nothing has worked except purge-ing nvidia and switching to nouveau...

Attaching apt log for that update. mono was updated as well adding a lot of noise, but the relevant part seems to be grub:

Kibontás előkészítése: .../14-grub-efi-amd64_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64 (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../15-grub2-common_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub2-common (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../16-grub-efi-amd64-signed_1.93.3+2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64-signed (1.93.3+2.02-2ubuntu8.2) e helyett: 1.93.2+2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../17-grub-efi-amd64-bin_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64-bin (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../18-grub-common_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-common (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...

i.e. grub was updated from 2.02-2ubuntu8.1 to 2.02-2ubuntu8.2.

Not sure if any of these can help, but for me nvidia has been completely broken since this update. Since then I'm constantly getting the following lines in kern.log (egrep -i '(nvidia|nvrm)'):

kernel: [ 1.675561] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 396.24.10 Tue Jul 10 10:00:18 PDT 2018 (using threaded interrupts)
kernel: [ 1.682807] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 396.24.10 Tue Jul 10 08:53:56 PDT 2018
kernel: [ 1.685191] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
kernel: [ 2.543799] nvidia-modeset: Allocated GPU:0 (GPU-ca4d2121-189c-752b-9cba-302ed81038d4) @ PCI:0000:01:00.0
kernel: [ 2.595623] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
kernel: [ 3.244611] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 236
kernel: [ 5.310256] NVRM: GPU at PCI:0000:01:00: GPU-ca4d2121-189c-752b-9cba-302ed81038d4
kernel: [ 5.310259] NVRM: Xid (PCI:0000:01:00): 61, 0ac0(2f10) 00000000 00000000
kernel: [ 12.366052] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
kernel: [ 15.124364] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0

[Layke (layke1123)]

So I was able to get everything working on 16.04 with nvidia-384. I tried many a different things on 18.04 with nvidia-390 and nvidia-396 but no luck including using proposed Bionic Beaver but no luck. If I can help report anything though I'd be glad to post it if you tell me what you need from my system. I hope this bug is fixed soon. 18.04 LTS is an improvement on 16.04 LTS I thought from my brief exposure to the system. This setup seems to run slower compared to Bionic Beaver.

[siyman (siyman)]

I am affected by this bug, too. Using an nVidia GTX 660 with legacy nvidia-340 (both mainline as well as graphics-driver ppa) my system is working as before. Switching to 390 or even 396 leaves me at a blinking cursor DM both on sddm and gdm3. The only DM I could use has been lightdm but only after I chowned the .Xauthority file of my user home dir whilst it was running (sadly this is a no go for me as I rely on multi user sessions which do not work anymore since the upgrade to bionic).

[Omar Alvarez (osurfer3)]

I am also having this issue, system fully updated, nvidia-driver-396, GTX 1050Ti, kernel 4.15.0-33-generic. Also happens with nvidia-driver-390. The fix for me was #123:

sudo service gdm stop ; sleep 5 ; sudo service gdm start

This is definitely not fixed.

[Tom (tom-lorinthe)]

It remains weird that a complete ciritical-show-stopping bug receives no attention from the true experts... What are we doing wrong to report it here?

[NiBu (niko-buzki)]

After upgrading from 18.04 to 18.10 the gnome freezes after GDM login.

[Saeed Tabrizi (saeed.tabrizi)]

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

[Eric CHAMPAGNE (ericchampagne)]

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

[ccdisle (sim-blk)]

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

[Melvin1981 (melvis)]

New install ubuntu 18.10. Nvidia-390, nvidia-410 freezes before login.
Only purge drivers makes system back to boot

[Saeed Tabrizi (saeed.tabrizi)]

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

[ccdisle (sim-blk)]

Yes this is exactly the problem I have. Every-time I install the Nvidia-drivers the machine won't boot up it hangs and displays

 "Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg--root"

I even tried installing earlier drivers -340 or 361 . The problem persists.

The only time it boots up is when I purge the Nvidia drivers.

This started soon after I upgraded to 18.10.

[Pinni (t-pinhammer)]

Same problem here.

[Melvin1981 (melvis)]

Texted to NVidia support about the issue. Got reply

Your case is being escalated to our Level 2 Tech Support group. The Level 2 agents will review the case notes and may attempt to recreate your issue or find a workaround solution if possible. As this process may take some time we ask that you be patient and a Level 2 tech will contact you as soon they can to help resolve your issue.

[Timo Aaltonen (tjaalton)]

this bug is closed, if you are seeing issues with current versions please file a new bug instead of posting here

[Tom (tom-lorinthe)]

@tjaalton ... funny, >185 persons report they have same issue here without any solution.. and then bug reports get closed without reference to where to duplicate all reports ? ))

Do you have bug number where we can copy and paste this to ?

[Konstantin Vlasenko (mlnk1981)]

Found this opened report related to the nvidia driver
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1795808

[Konstantin Vlasenko (mlnk1981)]

Solution found with NVidia support.
GDM3 causing Ubuntu 18.10 to "freeze" before login screen
After remove GDM3 and LightDM installation Ununtu booted as usually

[Konstantin Vlasenko (mlnk1981)]

I would say workaround not solution

[Nebojša Stošić (andrea1999)]

Please try, in the /etc/gdm3/custom.conf, uncomment WaylandEnable=false and Nvidia driver will work with gdm3.

[Konstantin Vlasenko (mlnk1981)]

OMG! Where u were all this time?! Thank you very much!

[Nebojša Stošić (andrea1999)]

:) You're welcome.

[ccdisle (sim-blk)]

I just tested this. It worked for me as well. Thanks, Nebojša.

[ccdisle (sim-blk)]

Uncommenting "WaylandEnable=false " worked.

Removing gdm3 did not work, I just got redirected to a tty3 login shell.

Thanks again

[Nebojša Stošić (andrea1999)]

You're welcome, Ccdisle.

[Kyle Weber (kyew01)]

I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway...

> On Oct 24, 2018, at 11:56 PM, ccdisle <email address hidden> wrote:
>
> Uncommenting "WaylandEnable=false " worked.
>
> Removing gdm3 did not work, I just got redirected to a tty3 login shell.
>
> Thanks again
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1752053
>
> Title:
> nvidia-390 fails to boot graphical display
>
> Status in mesa package in Ubuntu:
> Fix Released
> Status in nvidia-graphics-drivers-390 package in Ubuntu:
> Fix Released
> Status in xserver-xorg-video-nouveau package in Ubuntu:
> Invalid
>
> Bug description:
> I'm using Bionic with the new 4.15 kernel. I've been using the
> nvidia-384 driver with no problem for a while. Today I issued "sudo
> apt-get upgrade" and I was prompted to upgrade the nvidia driver to
> the nvidia-390. After installing the driver and rebooting, I was only
> able to boot in to the tty terminal. The graphical display failed to
> boot. I have had similar problems with nvidia driver version 390 with
> Arch Linux and with Open Suse Tumbleweed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Wei (weiwanse)]

I had the same problem after upgrading to 18.10. Uncommenting "WaylandEnable=false" worked.

[Simon Brereton (sbrereton63)]

The uncommenting #WaylandEnable=false worked a treat for me as with the previous posters. This is the answer to this problem and needs pinning to the thread!

[bblrlo (bblrlo-gmail)]

On KUbuntu 18.04 same problem with card GT630M and 390,396 nvidia drivers
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# cat /etc/X11/default-display-manager
/usr/bin/sddm

[Skander Guarbàa (skope)]

Guys ..
I have Nvidia 1050ti with nvidia-390 driver installed.

When i boot am on 900 resolution instead of a 1920x1080 normal resolution.

Anyone got a solution for that ??

Thanks in advance.

[Alexey Sys (alexey107)]

Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install and applying nvidia-390

[Wayne Bell (kingramze)]

Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390, 396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from beta and previously 18.04 as original install)

Resolved by switching to lightdm and booting into Cinnamon Desktop instead of Gnome. Mate works as well.
Also uncommented "WaylandEnable=false" for future possible use of gdm3 and gnome desktop.

Can someone either mark this as "not fixed" or "won't fix" since it's clearly not resolved.

[Daniel van Vugt (vanvugt)]

Please note this bug is closed, so generally will be ignored by developers.

If you have any ongoing problems please consider joining one of these open bugs instead:

  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=nvidia

or log a new bug by running the command:

  ubuntu-bug gdm3

Only if the original reporter would like this bug reopened should it be reopened.

[Michael Lazin (microlaser)]

I am running ubuntu 18.04 and using the low latency kernel rather than the default kernel. Since the "upgrade" to nvidia 390 it looks like the kernel module is actually missing from my filesystem. Running dmesg | grep nvidia and modprobe | grep nvidia tells me the nvidia driver is not loaded. When I try to load it with modprobe it's not in the proper path so it can't load. I tried reverting the nvidia driver and the kernel but the kernel module is still mysteriously missing. I'm going to reinstall with ubuntu studio 18.10 because this update has basically destroyed the functionality of my desktop. I need 1920x1068 resolution and that's not an option with the xrandr command without the nvidia driver. I did not check to see of nouveau was loaded as a kernel module, I just gotta reinstall. I hope this helps someone.

[Gert Kruger (hgkrug1)]

I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04 installed. After installing the lastest Nvidia driver-430, the dektop GUI is lost when you reboot (18.10 gave the same issue). I tried many proposed solutions, including the one above. Nothing worked.
I finally found a solution for this Nvidia driver issue (on ubuntu 18 and 19). See instructions at the top at https://ubuntuforums.org/showthread.php?t=2419319&highlight=nvidia+drivers, it worked for me!

[Alexander Trufanov (truf)]

Faced with this problem in Lenovo G780, NVIDIA 635M and nvidia-driver-390 package

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
Kernel Version: 5.0.0-29-generic

Addition of "WaylandEnable=false" to /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf resolved the problem.