System locking up after idle time - - GeForce 950 Nvidia driver issue?

When I crawl out of bed in the morning, after my PC has been idle for 8 hours or so, I normally just power on my monitor and get to work. But since the December 30 upgrade, my LG monitor says: ‘No Signal’. I can’t even switch VTs and Magick Syrq doesn’t work either. I need to do a cold boot.

I figure this might be related to the nvidia driver issue other people are experiencing as described in official Manjaro forum support thread but I am not 100% sure. Is there any other information I could provide to confirm this either way?

The recent main support thread (that I linked to above) explains how to compile old nvidia drivers but these instructions are not relevant in my case because I’ve got a Maxwell chip so I do not require legacy drivers (<= v390 for Fermi and below) and the current v455.x is compatible with my GeForce 950 hardware, is this correct?

My system otherwise boots, is stable, and runs well I guess.

Maybe it’s not a driver issue. Is there any other potential power-related feature for me to check? I’ve double checked my Xfce power settings and have ensured that everything is turned off, including the screen saver and the hibernate feature. But is there any other power switch I could try changing?

Here is my dmesg.

Here is: $ inxi -Fazy:

   System:
  Kernel: 5.10.2-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=6403b740-9546-4f5d-95fc-646e358e098d rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: Xfce 4.14.3 tk: Gtk 3.24.23 info: xfce4-panel, latte-dock 
  wm: Compiz 0.8.18 dm: GDM 3.38.2.1, LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop System: Gigabyte product: X470 AORUS ULTRA GAMING v: N/A 
  serial: <filter> 
  Mobo: Gigabyte model: X470 AORUS ULTRA GAMING-CF v: x.x serial: <filter> 
  UEFI: American Megatrends v: F2 date: 03/14/2018 
CPU:
  Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
  family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D L2 cache: 4 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 102430 
  Speed: 2663 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 
  1: 2663 2: 2896 3: 2467 4: 1814 5: 2624 6: 1701 7: 2972 8: 2429 9: 1530 
  10: 1632 11: 2616 12: 1943 13: 3261 14: 2670 15: 2912 16: 2650 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia 
  v: 455.45.01 alternate: nouveau,nvidia_drm bus ID: 0a:00.0 
  chip ID: 10de:1402 
  Display: x11 server: X.Org 1.20.10 compositor: compiz v: 0.8.18 
  driver: nvidia display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 3840x1600 s-dpi: 96 s-size: 1016x423mm (40.0x16.7") 
  s-diag: 1101mm (43.3") 
  Monitor-1: HDMI-0 res: 3840x1600 hz: 60 dpi: 111 
  size: 879x366mm (34.6x14.4") diag: 952mm (37.5") 
  OpenGL: renderer: GeForce GTX 950/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GM206 High Definition Audio vendor: eVga.com. 
  driver: snd_hda_intel v: kernel bus ID: 0a:00.1 chip ID: 10de:0fba 
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 0c:00.3 chip ID: 1022:1457 
  Sound Server: ALSA v: k5.10.2-2-MANJARO 
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel 
  port: f000 bus ID: 07:00.0 chip ID: 8086:1539 
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 2.28 TiB used: 821.9 GiB (35.2%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB 
  size: 232.89 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: 2B2QEXE7 temp: 41.9 C 
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: M4-CT256M4SSD2 
  size: 238.47 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 000F 
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD20EFRX-68AX9N0 
  size: 1.82 TiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 0A80 
Partition:
  ID-1: / raw size: 83.01 GiB size: 81.2 GiB (97.83%) used: 32.66 GiB (40.2%) 
  fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:1 
  ID-2: /boot/efi raw size: 1000 MiB size: 998 MiB (99.80%) 
  used: 272 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:3 
  ID-3: /home raw size: 960.25 GiB size: 944.18 GiB (98.33%) 
  used: 789.24 GiB (83.6%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 
Swap:
  Alert: No Swap data was found. 
Sensors:
  System Temperatures: cpu: 59.2 C mobo: N/A gpu: nvidia temp: 50 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 489 Uptime: 2h 04m wakeups: 0 Memory: 62.82 GiB 
  used: 15.73 GiB (25.0%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  Packages: pacman: 1847 lib: 468 flatpak: 0 Shell: Zsh v: 5.8 
  running in: gnome-terminal inxi: 3.2.01

I had the same Issue with my GTX 970. The GTX 760 I put back in doesn’t have this Issue. Well one Game does, but that either a problem with that game or related to Xfce…

This may just be a Major Issue with Nvidia 900 Series Cards.

The recent main support thread (that I linked to above) explains how to compile old nvidia drivers but these instructions are not relevant in my case because I’ve got a Maxwell chip so I do not require legacy drivers (<= v390 for Fermi and below) and the current v455.x is compatible with my GeForce 950 hardware, is this correct?

To answer my own question, this is incorrect. I re-read the original official forum post for dealing with this new nvidia driver issue. Near the bottom of the thread’s initial post, it shows how to rebuild an older driver against any kernel.

Here is the solution that worked for me for linux54 (kernel 5.4):

$ git clone https://gitlab.manjaro.org/packages/extra/nvidia-435xx-utils.git
$ git clone https://gitlab.manjaro.org/packages/multilib/lib32-nvidia-435xx-utils.git
$ git clone https://gitlab.manjaro.org/packages/extra/linux54-extramodules/nvidia-435xx.git

Then I cd’ed into all three and for each and ran: $ makepkg -si.

It took me a few tries because I needed to remove the pre-existing 460.xx drivers (the drivers with the problem). I dealt with that issue using pamac-manager.

I believe I could have swapped out ‘linux54’ from the above command and chose a more up to date kernel and it still would have worked. The original support thread indicates that when 5.4 is upgraded, I will need to rebuild these nvidia drivers against the new kernel. So I am annotating this here for my future reference.

During my two hour troubleshooting session today, at one point I borked my drivers completely to the point where I lost access to my GUI natively. Lucky for me I had a Manjaro live USB ready and managed to chroot into my environment to execute the winning commands (above)!

I’m stoked that I have my Manjaro back. I haven’t actually had any idle time yet so I haven’t completely tested whether this new driver installation resolves my issue. I will find out tomorrow morning for the final verdict. If you folks don’t hear from me, then that means today’s troubleshooting process work. No news will be good news I guess. :wink:

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.