Linux Mint Forums

Posted: **Sun Nov 22, 2020 3:11 pm**

I have an LG UHD monitor connected via HDMI cable to an Nvidia GeForce RTX 2070 graphics card, and am running Linux Mint 20 Cinnamon. A couple weeks ago I updated my graphics driver from nvidia-450 to nvidia-455 from the graphics-drivers PPA via the update manager and then found I couldn't boot the computer. After using a flash drive to timeshift back to the last working configuration, I tried the update from the command line. This time I was able to reboot, but the drivers manager app came up blank. I also found that I couldn't wake the monitor after it had gone into power-saving mode. I have an older computer with a Dell 1920 x 1200 monitor connected via DVI to an Nvidia GeForce GTX 660 graphics card. This is basically a reserve computer with substantially the same software configuration I have on my newer system. I performed the same upgrade on that computer and, although it booted up, and the monitor woke up from power-saving mode, I still got a blank drivers manager. Since I got the new driver from the PPA, and since PPAs are untrusted, I disabled the PPA and installed the latest nvidia driver from the official Ubuntu repository. This was nvidia-450. Everything worked fine after that.
A few days later, the update manager offered an update to the drivers manager, which I installed on both computers, and shortly after that another one. For some reason, on my newer computer it only showed two available drivers -- the one I was using and the nouveau driver. Then, nvidia-455 turned up on both the official repository and the drivers manager, which also indicated it was the recommended driver. I installed it from the drivers manager. Everything worked fine on the older computer, but on the newer computer I still couldn't wake up the monitor from power-saving mode (please note, this is NOT the same as suspend or hibernate -- the computer itself was still running.) Occasionally I could wake it after a while by pressing Ctrl+Alt+F2, and then once in TTY, pressing Ctrl+Alt+F7, but this clearly is not a satisfactory solution. And the drivers manager showed nvidia-450, nvidia-455 and nouveau as the only drivers available, with nvidia-455 recommended. However, going into the command line and typing "ubuntu-drivers devices" brings up a list that includes those plus three other drivers.
It gets even stranger. Nvidia lists 20 GeForce RTX 2070 compatible drivers. So why am I getting only two in the drivers manager and five from "ubuntu-drivers devices"? What's really strange is that nvidia-455 is not one of Nvidia's certified drivers. It is classified as a Linux Short Lived release -- more stable than a Beta, but not as stable as a long-lived release (which nvidia-450 is). Usually software in Ubuntu's repositories are a release or two behind the latest stable release. Here it is not only AHEAD of the latest stable release, but it is the recommended driver.
Anybody got any ideas? I've reverted back to nvidia-450 in my newer computer, but before I did, here's the inxi -Fzx output from it:

Code: Select all

System:    Kernel: 5.4.0-54-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 
           Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: Z390 Taichi serial: <filter> UEFI: American Megatrends v: P1.80 date: 12/10/2018 
CPU:       Topology: 8-Core model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 16.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 115200 
           Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 5: 800 6: 800 7: 800 8: 800 
           9: 800 10: 800 11: 801 12: 800 13: 800 14: 800 15: 800 16: 801 
Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2070] vendor: eVga.com. driver: nvidia v: 455.38 bus ID: 01:00.0 
           Display: server: X.Org 1.20.8 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA 455.38 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Device-2: NVIDIA TU106 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k5.4.0-54-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: 5000 bus ID: 04:00.0 
           IF: wlp4s0 state: down mac: <filter> 
           Device-3: Intel I211 Gigabit Network vendor: ASRock driver: igb v: 5.6.0-k port: 4000 bus ID: 05:00.0 
           IF: enp5s0 state: down mac: <filter> 
Drives:    Local Storage: total: 7.28 TiB used: 1.09 TiB (15.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
           ID-3: /dev/sdb vendor: Western Digital model: WD6003FZBX-00K5WB0 size: 5.46 TiB temp: 35 C 
Partition: ID-1: / size: 124.56 GiB used: 17.01 GiB (13.7%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /home size: 287.37 GiB used: 28.76 GiB (10.0%) fs: ext4 dev: /dev/nvme0n1p3 
           ID-3: swap-1 size: 23.44 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4 
Sensors:   System Temperatures: cpu: 39.5 C mobo: 38.0 C gpu: nvidia temp: 47 C 
           Fan Speeds (RPM): fan-1: 0 fan-2: 563 fan-3: 0 fan-4: 0 fan-5: 0 gpu: nvidia fan: 0% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.46 vbat: 3.28 
Info:      Processes: 334 Uptime: 7m Memory: 62.74 GiB used: 1.13 GiB (1.8%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
           Shell: bash v: 5.0.17 inxi: 3.0.38

And here's the output from the older system:

Code: Select all

System:    Kernel: 5.4.0-54-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Console: N/A Distro: Linux Mint 20 Ulyana 
           base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: Gigabyte model: Z77X-D3H v: x.x serial: N/A BIOS: American Megatrends v: F16 date: 10/24/2012 
CPU:       Topology: Quad Core model: Intel Core i5-3570K bits: 64 type: MCP arch: Ivy Bridge rev: 9 L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27226 
           Speed: 1602 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1602 2: 1602 3: 1602 4: 1602 
Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: eVga.com. driver: nvidia v: 455.38 bus ID: 01:00.0 
           Display: server: X.org 1.20.8 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa tty: 237x58 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Device-2: NVIDIA GK106 HDMI Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k5.4.0-54-generic 
Network:   Device-1: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: Gigabyte driver: alx v: kernel port: d000 
           bus ID: 06:00.0 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.29 TiB used: 450.00 GiB (19.2%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB 
           ID-3: /dev/sdc vendor: Western Digital model: WD1002FAEX-00Z3A0 size: 931.51 GiB temp: 30 C 
           ID-4: /dev/sdd vendor: Western Digital model: WD1002FAEX-00Z3A0 size: 931.51 GiB temp: 32 C 
Partition: ID-1: / size: 76.95 GiB used: 13.83 GiB (18.0%) fs: ext4 dev: /dev/sdb1 
           ID-2: /home size: 151.20 GiB used: 29.12 GiB (19.3%) fs: ext4 dev: /dev/sdb5 
           ID-3: swap-1 size: 6.05 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb6 
Sensors:   System Temperatures: cpu: 40.0 C mobo: 38.0 C 
           Fan Speeds (RPM): cpu: 1019 fan-1: 563 fan-3: 1445 fan-4: 0 fan-5: 0 
           Voltages: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.29 
Info:      Processes: 224 Uptime: 1d 1h 18m Memory: 15.60 GiB used: 1.09 GiB (7.0%) Init: systemd runlevel: 5 Compilers: 
           gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38

Posted: **Sun Nov 22, 2020 5:55 pm**

pmanger wrote: ↑
Sun Nov 22, 2020 3:11 pm
A couple weeks ago I updated my graphics driver from nvidia-450 to nvidia-455 from the graphics-drivers PPA via the update manager...

What problems were you having that you wanted to change the driver?

pmanger wrote: ↑
Sun Nov 22, 2020 3:11 pm
After using a flash drive to timeshift back to the last working configuration, I tried the update from the command line. This time I was able to reboot, but the drivers manager app came up blank. I also found that I couldn't wake the monitor after it had gone into power-saving mode. I have an older computer with a Dell 1920 x 1200 monitor connected via DVI to an Nvidia GeForce GTX 660 graphics card. This is basically a reserve computer with substantially the same software configuration I have on my newer system. I performed the same upgrade on that computer and, although it booted up, and the monitor woke up from power-saving mode, I still got a blank drivers manager. Since I got the new driver from the PPA, and since PPAs are untrusted, I disabled the PPA and installed the latest nvidia driver from the official Ubuntu repository. This was nvidia-450. Everything worked fine after that.

The drivers in Driver Manager are packaged for Ubuntu/Mint. They are not exactly the same files as what you get either from the PPA or directly from Nvidia's website. It is my understanding only drivers which came through Driver Manager will show up in Driver Manager.

pmanger wrote: ↑
Sun Nov 22, 2020 3:11 pm
A few days later, the update manager offered an update to the drivers manager, which I installed on both computers, and shortly after that another one.

Those updates were for the Driver Manager app and not for any drivers available in the app. There was a bug affecting some people with the first update which is why a second update came through so quickly. The second update fixed the bug.

pmanger wrote: ↑
Sun Nov 22, 2020 3:11 pm
What's really strange is that nvidia-455 is not one of Nvidia's certified drivers. It is classified as a Linux Short Lived release -- more stable than a Beta, but not as stable as a long-lived release (which nvidia-450 is).

This is correct.

It is my understanding Driver Manager works from a database which matches your Nvidia card ID to what drivers are available. The system is not perfect and I always recommend people check on the Nvidia site to see which driver they should use (but not to download from Nvidia's site).

What I am guessing is currently happening is Nvidia 3090 cards are out, but they need the 455 driver to work. They will not work with the 450 driver. Nvidia does list the 455 drivers as updates to the 450 drivers, but, as you noted, the 455 is not long-term release. So in order to get out the driver those with a RTX 3090 need, the 455 was made available in Driver Manager. That is my guess; I do not have inside information on this topic.

I'm sure the default in Driver Manager is to list the latest available driver as "recommended" which is why it showed as such for your two computers. However, did you get updates in Update Manager indicating you should use the 455 Driver or did you only notice it was in Driver Manager and decide to change?

Unless you are having a particular problem that you know is solved with the 455 driver, then I recommend you stay with the 450.

Posted: **Sun Nov 22, 2020 8:26 pm**

What problems were you having that you wanted to change the driver?

None, really. But I do some video editing and the open-source video editors I've been using use software-rendering rather than the 2,000+ CUDA cores in my video card. Recently Kdenlive started using the CUDA cores to render and I thought nvidia-455 might offer that capability.

Those updates were for the Driver Manager app and not for any drivers available in the app. There was a bug affecting some people with the first update which is why a second update came through so quickly. The second update fixed the bug.

Understood, but why are there a lot fewer drivers showing up in the new driver manager app?

I'm sure the default in Driver Manager is to list the latest available driver as "recommended" which is why it showed as such for your two computers. However, did you get updates in Update Manager indicating you should use the 455 Driver or did you only notice it was in Driver Manager and decide to change?

It was the update manager that first alerted me to the nvidia-455 driver and, as I do with most things that appear in update manager, I just left it checked and clicked on "install updates". It was after that that my system wouldn't reboot. When I got things working again, I installed from the command line.

Unless you are having a particular problem that you know is solved with the 455 driver, then I recommend you stay with the 450.

That's what I'm doing. What I'm worried about, though, is the minimal number of drivers being offered by the driver manager. Right now, except for nouveau, my only choices are nvidia-450 and nvidia-455.

Thanks for taking the time explain these things to me.

Posted: **Sun Nov 22, 2020 9:42 pm**

pmanger wrote: ↑
Sun Nov 22, 2020 8:26 pm
Understood, but why are there a lot fewer drivers showing up in the new driver manager app?

There are some versions of drivers, such as the 304, 340 and 390, that are the last ones available for certain Nvidia cards. Because of their hardware, they can not use the 440 or the 450 driver. If I recall correctly, I think every card that the 440 driver supported is also supported by the 450 driver. So the 450 completely replaced the 440. I think there may be some cards for which the 450 will be the last driver which supports them. If that is the case, the 450 will remain available in Driver Manager for much longer than the 440 was.

I would think it cuts down on the required testing and maintenance to only have the most recent package available in Driver Manager. Ubuntu would need to test their 450 driver package for each new release. If the 440 and 450 are for the exact same cards then it doesn't make sense to keep both.

pmanger wrote: ↑
Sun Nov 22, 2020 8:26 pm
It was the update manager that first alerted me to the nvidia-455 driver and, as I do with most things that appear in update manager, I just left it checked and clicked on "install updates". It was after that that my system wouldn't reboot.

That surprises me that Ubuntu pushed the 455 through as an update for the 450. Maybe they know something about the Nvidia release schedule that you or I do not.

pmanger wrote: ↑
Sun Nov 22, 2020 8:26 pm
What I'm worried about, though, is the minimal number of drivers being offered by the driver manager. Right now, except for nouveau, my only choices are nvidia-450 and nvidia-455.

Are you concerned you may run into issues with the 450? Is that why you want more options? You are taking snapshots so that gives you an option to return to a previous driver. I would also expect there would be a 460 available in the future.

Posted: **Fri Jan 08, 2021 3:49 pm**

Back again. Nvidia-driver-460 just came out. Installed it, and switched to it. Same problem as with Nvidia-455.

Posted: **Fri Jan 08, 2021 7:27 pm**

So the issue is "Everything worked fine on the older computer, but on the newer computer I still couldn't wake up the monitor from power-saving mode"?

Maybe someone more familiar with monitor issues will be able to give some ideas.

Posted: **Fri Jan 08, 2021 9:37 pm**

Thanks for getting back so soon. I don't think the problem is with the monitor. If I hold down Ctrl-Alt-F2 for a while, I go into the TTY terminal, and then if I press Ctrl-Alt-F7 I'm back in my usual GUI. It's just that neither moving the mouse nor hitting a key wakes the system up as was the case with the 450 driver. I've been through all the settings on my monitor (an LG 27UL650 UHD monitor) and haven't been able to find a setting that would affect the problem. I even did a reset of the monitor to its default settings. The result of that was that during boot-up the monitor displayed a message in the middle of the screen saying, "The screen is not currently set to the recommended resolution." It says the current resolution is 1280 x 1024, while the recommended resolution (which is set in the display settings) is 3840 x 2160. I suspect I got the message because the system BIOS doesn't support a resolution that high and the BIOS is in control during boot-up. Once I'm into Cinnamon, and graphics control has been handed over to my Nvidia card, the settings are correct and I get the desired UHD resolution. I was able to disable the pop-up message with the monitor controls. I don't know if that's the problem. I sort of doubt it, because I don't have the problem with the 450 driver, or with any of the previous drivers I've used with this system.

I guess I'll just have to go back to the 450 driver for now.

Posted: **Sat Jan 09, 2021 1:37 pm**

pmanger wrote: ↑
Fri Jan 08, 2021 9:37 pm
Thanks for getting back so soon. I don't think the problem is with the monitor.

I didn't mean to imply there was a problem with the monitor. I meant there are adjustments which can be made to the software on Mint to make monitors work, but I do now know enough about them to be able to help you with this situation. That is what I meant when I said "monitor issues", but I can see how you interpreted it the way you did. Sorry for the confusion.

I do not know why the newer Nvidia driver might be seeing the port connection/monitor differently, but it's fine to stay with the Nvidia-450 as long as it is working for you. This sounds like it could be a bug with the Nvidia driver. In checking the Release Highlights for Nvidia-460.32, there appear to be several changes which might affect monitor connections.

Posted: **Wed Jan 13, 2021 4:58 pm**

Problem solved!!! After poking around the Nvidia forums I discovered that other Linux users were having the same problem. I noticed that, when they listed their hardware, they all had used an HDMI cable to connect their card to their monitor. On a hunch, I tried connecting through a displayport. Voila!!! It worked. My monitor wakes up when I press a key or move the mouse, and it wakes up faster than it did when I was connecting through HDMI with the 450 driver. I suspect the problem was that my monitor doesn't have speakers and the HDMI audio channel didn't have anything to connect to, so the card couldn't complete the handshake and timed out. (I use separate speakers connected to my motherboard's on-board audio). This would also explain the slower wake-up times even with the 450 driver. But that's just a guess. Anyway, SMG, thanks for all your help.

Posted: **Wed Jan 13, 2021 5:24 pm**

Glad it is now working. Please edit the title of your first post in this thread and add [SOLVED] so others with a similar issue will know this is a good thread to read.

Linux Mint Forums

[SOLVED] Monitor won't wake up after driver update

[SOLVED] Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update

Re: Monitor won't wake up after driver update