You are not logged in.
Whenever my computer wakes from suspend, I get corrupted images such as this: screenshot.
I am using Gnome, and I have the NVDIA driver.
According to this post, creating a modprobe configuration file might help performance.
$ cat /etc/modprobe.d/50-nvidia.conf
options nvidia NVreg_RegisterForACPIEvents=1 NVreg_EnableMSI=1I've generated my own EDID file from the nvidia-settings, and placed it in /usr/lib/firmware/edid/. Then I added it to the files section of /etc/mkinitcpio.conf, then regenerated my initramfs. On a side note, this actually fixed an error I was receiving, no longer seeing the following:
$ journalctl -p4 | grep -i NVIDIA
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device LG Electronics W2353 (HDMI-0)I added nvidia, nvidia_modeset, nvidia_uvm, and nvidia_drm to the MODULES portion of /etc/mkinitcpio.conf
But unfortunately, I just feel like I'm shooting in the dark here. Any suggestions?
Offline
Try options nvidia_drm modeset=1 in addition to the other lines
Offline
Looooooooooooooongstanding issue w/ the nvidia driver, see eg.
https://devtalk.nvidia.com/default/topi … ume-from-/
https://devtalk.nvidia.com/default/topi … -378-13-/1
or
https://askubuntu.com/questions/1043398 … from-suspe
Our current software architecture doesn't preserve the contents of FBOs across modeswitches or power events. As a result, our implementation relies on applications re-rendering to their FBOs every frame. This is a fundamental limitation of our design that will be fixed in the future.
Corrupted textures are one of the more benign results, this can outright crash the session.
Offline
Thanks for the suggestion, V1del.
Actually, I had options nvidia_drm modeset=1 in the kernel parameter. I should have mentioned it.
Hey, Seth - I don't know if this is a "fix" or not, but by adding acpi_osi=! acpi_osi="Windows 2009" to the kernel parameter, the problem goes away.
Is this actually fixing the problem or just sweeping it under a rug?
Currently my systemd boot file looks like this
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=LABEL=Arch_Linux rw rootflags=subvol=@root acpi_osi=! acpi_osi="Windows 2009" nvidia-drm.modeset=1And it works now. So far.
Last edited by renordw (2019-04-10 07:23:07)
Offline
The behavior is not deterministic and usually depends on the length of the S3 cycle, so see whether you go issue-free for three nights or so.
Offline
Seems like you're right. I removed all that stuff, and it's still working.
It's bizarre behavior since before when I posted, I was rebooting every few minutes (about ten times), and suspending to see if I could get the issue to reproduce every time, and the textures were corrupt every time.
Offline
Deepin virtually /is/ gnome and this is more related to OpenGL than to the actual GL client.
I won't question your anecdotal evidence, but it lacks any kind of supporting theory.
Since this only affects the nvidia blob, the nouveau behavior is not surprising, though.
I guess nvidia would have to store the VRAM in RAM, but possibly runs into some GPL issues (but I don't know that for a fact)
Offline
Deepin virtually /is/ gnome and this is more related to OpenGL than to the actual GL client.
I won't question your anecdotal evidence, but it lacks any kind of supporting theory.Since this only affects the nvidia blob, the nouveau behavior is not surprising, though.
I guess nvidia would have to store the VRAM in RAM, but possibly runs into some GPL issues (but I don't know that for a fact)
deepin is written from scratch in qt, it's not related to gnome at all.
Offline
Offline
yes it includes modified versions of metacity and mutter,
but I said I have problem for GTK apps, not QT. after wakeup from suspend all GTK apps are corrupt 'till I resize them
Last edited by mmdamin (2019-04-10 12:25:00)
Offline
Deepin does not rely on Qt at all - it's a gnome fork.
Whether or not you're running some "deepin" tagged Qt clients on the Deepin desktop is an entirely different matter and boils down to the question whether the clients in question use OpenGL as backend or Xrender or software based rendering. Especially if you're using metacity as window manager. Because again: the driving factor here is the use of OpenGL FBOs.
Offline
Deepin does not rely on Qt at all - it's a gnome fork.
Whether or not you're running some "deepin" tagged Qt clients on the Deepin desktop is an entirely different matter and boils down to the question whether the clients in question use OpenGL as backend or Xrender or software based rendering. Especially if you're using metacity as window manager. Because again: the driving factor here is the use of OpenGL FBOs.
I think mutter uses OpenGL, as it has some effects like Window Shadows and Transparency, Animations and some other.
By disabling "Window Effects" option from control center it kills mutter and starts metacity that doesn't include this effects.
Last edited by mmdamin (2019-04-10 12:29:21)
Offline