Ubuntu 18.04 stopped working with NVIDIA drivers
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am running Ubuntu 18.04 on a CLEVO notebook and have the nvida-390 drivers and Cuda installed. It worked fine for a month, but - suddenly today it stopped working. I can still access the login screen, but the screen remains purple.
I've already tried to purge and reinstall the nvidia-390 drivers (I've also tried the 396 drivers version) without success. After the login the computer always stops working. I cannot even access tty. After purging the drivers I can login and all works fine with nouveau
, but I really need Cuda for my work.
My specs:
- i7-6700HQ
- 8GB RAM
- Nvidia GeForce GTX 970M
- Intel Wireless 8260
Can someone please help me? Thanks.
drivers nvidia 18.04
add a comment |
I am running Ubuntu 18.04 on a CLEVO notebook and have the nvida-390 drivers and Cuda installed. It worked fine for a month, but - suddenly today it stopped working. I can still access the login screen, but the screen remains purple.
I've already tried to purge and reinstall the nvidia-390 drivers (I've also tried the 396 drivers version) without success. After the login the computer always stops working. I cannot even access tty. After purging the drivers I can login and all works fine with nouveau
, but I really need Cuda for my work.
My specs:
- i7-6700HQ
- 8GB RAM
- Nvidia GeForce GTX 970M
- Intel Wireless 8260
Can someone please help me? Thanks.
drivers nvidia 18.04
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
1
Please try out whether booting with the parameternvidia-drm.modeset=1
solves the problem. :)
– cl-netbox
Jun 20 '18 at 17:40
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58
add a comment |
I am running Ubuntu 18.04 on a CLEVO notebook and have the nvida-390 drivers and Cuda installed. It worked fine for a month, but - suddenly today it stopped working. I can still access the login screen, but the screen remains purple.
I've already tried to purge and reinstall the nvidia-390 drivers (I've also tried the 396 drivers version) without success. After the login the computer always stops working. I cannot even access tty. After purging the drivers I can login and all works fine with nouveau
, but I really need Cuda for my work.
My specs:
- i7-6700HQ
- 8GB RAM
- Nvidia GeForce GTX 970M
- Intel Wireless 8260
Can someone please help me? Thanks.
drivers nvidia 18.04
I am running Ubuntu 18.04 on a CLEVO notebook and have the nvida-390 drivers and Cuda installed. It worked fine for a month, but - suddenly today it stopped working. I can still access the login screen, but the screen remains purple.
I've already tried to purge and reinstall the nvidia-390 drivers (I've also tried the 396 drivers version) without success. After the login the computer always stops working. I cannot even access tty. After purging the drivers I can login and all works fine with nouveau
, but I really need Cuda for my work.
My specs:
- i7-6700HQ
- 8GB RAM
- Nvidia GeForce GTX 970M
- Intel Wireless 8260
Can someone please help me? Thanks.
drivers nvidia 18.04
drivers nvidia 18.04
edited Jun 26 '18 at 18:59
user364819
asked Jun 20 '18 at 17:04
Daniele GambaDaniele Gamba
2881110
2881110
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
1
Please try out whether booting with the parameternvidia-drm.modeset=1
solves the problem. :)
– cl-netbox
Jun 20 '18 at 17:40
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58
add a comment |
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
1
Please try out whether booting with the parameternvidia-drm.modeset=1
solves the problem. :)
– cl-netbox
Jun 20 '18 at 17:40
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
1
1
Please try out whether booting with the parameter
nvidia-drm.modeset=1
solves the problem. :)– cl-netbox
Jun 20 '18 at 17:40
Please try out whether booting with the parameter
nvidia-drm.modeset=1
solves the problem. :)– cl-netbox
Jun 20 '18 at 17:40
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58
add a comment |
2 Answers
2
active
oldest
votes
You might need to have Direct Rendering Manager Kernel Mode Setting enabled on system boot.
NVIDIA driver's PRIME Synchronization support relies on DRM-KMS, which is disabled by default.
Find more comprehensive information in the discussion on the NVIDIA GPU Unix Graphics Forums.
Execute sudo nano /etc/default/grub
and add the parameter nvidia-drm.modeset=1
to the line GRUB_CMDLINE_LINUX_DEFAULT
. Save the change you've made and run sudo update-grub
.
Restart the Ubuntu operating system, and now, everything should work properly - right as expected.
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
|
show 2 more comments
I was able to get it working with the latest Nvidia-418 drivers on a Lenovo W530 with the Nvidia GK107GLM Quadro K2000M:
- Edit the
sudo nano /etc/default/grub
and remove "quiet splash" from GRUB_CMDLINE_LINUX_DEFAULT and thensudo update-grub
(that may be similar then addingnvidia-drm.modeset=1
)
- Switch to LightDM:
sudo dpkg-reconfigure lightdm
(necessary so my second monitor was recognized)
- Install PPA with latest drivers:
sudo add-apt-repository ppa:graphics-drivers/ppa
andsudo apt-get update
- Install latest recommended driver (in my case Nvidia 418):
sudo ubuntu-drivers autoinstall
add a comment |
protected by WinEunuuchs2Unix Jun 24 '18 at 19:49
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You might need to have Direct Rendering Manager Kernel Mode Setting enabled on system boot.
NVIDIA driver's PRIME Synchronization support relies on DRM-KMS, which is disabled by default.
Find more comprehensive information in the discussion on the NVIDIA GPU Unix Graphics Forums.
Execute sudo nano /etc/default/grub
and add the parameter nvidia-drm.modeset=1
to the line GRUB_CMDLINE_LINUX_DEFAULT
. Save the change you've made and run sudo update-grub
.
Restart the Ubuntu operating system, and now, everything should work properly - right as expected.
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
|
show 2 more comments
You might need to have Direct Rendering Manager Kernel Mode Setting enabled on system boot.
NVIDIA driver's PRIME Synchronization support relies on DRM-KMS, which is disabled by default.
Find more comprehensive information in the discussion on the NVIDIA GPU Unix Graphics Forums.
Execute sudo nano /etc/default/grub
and add the parameter nvidia-drm.modeset=1
to the line GRUB_CMDLINE_LINUX_DEFAULT
. Save the change you've made and run sudo update-grub
.
Restart the Ubuntu operating system, and now, everything should work properly - right as expected.
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
|
show 2 more comments
You might need to have Direct Rendering Manager Kernel Mode Setting enabled on system boot.
NVIDIA driver's PRIME Synchronization support relies on DRM-KMS, which is disabled by default.
Find more comprehensive information in the discussion on the NVIDIA GPU Unix Graphics Forums.
Execute sudo nano /etc/default/grub
and add the parameter nvidia-drm.modeset=1
to the line GRUB_CMDLINE_LINUX_DEFAULT
. Save the change you've made and run sudo update-grub
.
Restart the Ubuntu operating system, and now, everything should work properly - right as expected.
You might need to have Direct Rendering Manager Kernel Mode Setting enabled on system boot.
NVIDIA driver's PRIME Synchronization support relies on DRM-KMS, which is disabled by default.
Find more comprehensive information in the discussion on the NVIDIA GPU Unix Graphics Forums.
Execute sudo nano /etc/default/grub
and add the parameter nvidia-drm.modeset=1
to the line GRUB_CMDLINE_LINUX_DEFAULT
. Save the change you've made and run sudo update-grub
.
Restart the Ubuntu operating system, and now, everything should work properly - right as expected.
edited Jun 21 '18 at 15:55
answered Jun 21 '18 at 10:25
cl-netboxcl-netbox
25.6k577114
25.6k577114
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
|
show 2 more comments
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
4
4
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Congrats on bounty you deserve it :)
– WinEunuuchs2Unix
Jun 24 '18 at 17:27
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
Once I do this, the monitor running on NVidia will block on "Starting Gnome DISPLAY Manager" however the other monitor is fine. Remove the modeset from GRUB then all is fine, except screen tearing on NVidia. Any ideas how to diagnose or fix ?
– abdelrahman-sinno
Nov 14 '18 at 14:24
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@abdelrahman-sinno Without knowing any further details providing you with a correctly working solution is not possible. I suggest that you ask a new question including as much information as possible about your specific hardware and system setup and about what you have already tried so far to solve the problem. :)
– cl-netbox
Nov 14 '18 at 15:25
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
@cl-netbox I have posted my question here (askubuntu.com/questions/1093409/…), please let me know if you need any further info
– abdelrahman-sinno
Nov 16 '18 at 9:15
1
1
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
didn't work for me
– fccoelho
Dec 10 '18 at 14:35
|
show 2 more comments
I was able to get it working with the latest Nvidia-418 drivers on a Lenovo W530 with the Nvidia GK107GLM Quadro K2000M:
- Edit the
sudo nano /etc/default/grub
and remove "quiet splash" from GRUB_CMDLINE_LINUX_DEFAULT and thensudo update-grub
(that may be similar then addingnvidia-drm.modeset=1
)
- Switch to LightDM:
sudo dpkg-reconfigure lightdm
(necessary so my second monitor was recognized)
- Install PPA with latest drivers:
sudo add-apt-repository ppa:graphics-drivers/ppa
andsudo apt-get update
- Install latest recommended driver (in my case Nvidia 418):
sudo ubuntu-drivers autoinstall
add a comment |
I was able to get it working with the latest Nvidia-418 drivers on a Lenovo W530 with the Nvidia GK107GLM Quadro K2000M:
- Edit the
sudo nano /etc/default/grub
and remove "quiet splash" from GRUB_CMDLINE_LINUX_DEFAULT and thensudo update-grub
(that may be similar then addingnvidia-drm.modeset=1
)
- Switch to LightDM:
sudo dpkg-reconfigure lightdm
(necessary so my second monitor was recognized)
- Install PPA with latest drivers:
sudo add-apt-repository ppa:graphics-drivers/ppa
andsudo apt-get update
- Install latest recommended driver (in my case Nvidia 418):
sudo ubuntu-drivers autoinstall
add a comment |
I was able to get it working with the latest Nvidia-418 drivers on a Lenovo W530 with the Nvidia GK107GLM Quadro K2000M:
- Edit the
sudo nano /etc/default/grub
and remove "quiet splash" from GRUB_CMDLINE_LINUX_DEFAULT and thensudo update-grub
(that may be similar then addingnvidia-drm.modeset=1
)
- Switch to LightDM:
sudo dpkg-reconfigure lightdm
(necessary so my second monitor was recognized)
- Install PPA with latest drivers:
sudo add-apt-repository ppa:graphics-drivers/ppa
andsudo apt-get update
- Install latest recommended driver (in my case Nvidia 418):
sudo ubuntu-drivers autoinstall
I was able to get it working with the latest Nvidia-418 drivers on a Lenovo W530 with the Nvidia GK107GLM Quadro K2000M:
- Edit the
sudo nano /etc/default/grub
and remove "quiet splash" from GRUB_CMDLINE_LINUX_DEFAULT and thensudo update-grub
(that may be similar then addingnvidia-drm.modeset=1
)
- Switch to LightDM:
sudo dpkg-reconfigure lightdm
(necessary so my second monitor was recognized)
- Install PPA with latest drivers:
sudo add-apt-repository ppa:graphics-drivers/ppa
andsudo apt-get update
- Install latest recommended driver (in my case Nvidia 418):
sudo ubuntu-drivers autoinstall
edited 16 hours ago
answered 17 hours ago
SinaSina
793820
793820
add a comment |
add a comment |
protected by WinEunuuchs2Unix Jun 24 '18 at 19:49
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Try booting an old kernel
– Panther
Jun 20 '18 at 17:28
1
Please try out whether booting with the parameter
nvidia-drm.modeset=1
solves the problem. :)– cl-netbox
Jun 20 '18 at 17:40
@cl-netbox it worked!! Thank you! Please answer the question so i can give you the actual right answer :)
– Daniele Gamba
Jun 20 '18 at 17:58