I haven’t been able to find one. Using Zorin OS which is GNOME.
amdgpuhas a recovery mechanism built in that can be triggered usingsudo cat /sys/kernel/debug/dri/N/amdgpu_gpu_recoverwhere N is the number of the DRI device in question. You could bind a shortcut to doing that I presume.Hmm I have AMD but I’m getting
No such file or directoryWhich part of the path does not exist?
Is it the correct GPU number?
I have an AMDGPU machine - a hateful HP laptop with a Vega 6 chipset - and the display regularly goes garbled when I switch VTs. I too am looking for a way to “reset the graphics card”
and cat /sys/kernel/debug/dri/N/amdgpu_gpu_recoverain’t it: it resets it alright, but after that you get a frozen image and X is dead.Maybe Wayland survives that but Xorg definitely doesn’t.
The only reliable graphics card reset solution I’ve every found was to close then reopen the laptop to force the machine to go to sleep, then wake up and go through the restart rigmarole cleanly. I wish there was a way to do that sleep-wakeup routing with a keyboard shortcut, but I haven’t found one.
I think the real solution is to buy a decent replacement laptop though.
Yeah, Xorg (and the apps) will likely die. There is a wayland protocol in the works to be able to gracefully handle driver resets but I’m not sure on its implementation status.
Maybe
sudo systemctl restart gdm? That’s not quite the same as it restarts gnome display manager.When your computer freezes and you can’t get to a tty with Ctrl+alt+F4 then it likely encountered a kernel panic. A panic is not recoverable. In some senerios I’ve seen the amdgpu module run into a kernel oops which is recoverable. It doesn’t really effect the desktop other than a studder as the kernel reinitializes in the background.
If your system is freezing start by checking RAM and then try a different GPU. Its likely a hardware issue
Please explain why you need that in the post.
Average linux help post, someone comes along saying “why do you need that” instead of being helpful lol
And you know if I had actually given an answer he would have just told me why his way of doing things is better.
There used to exist a hotkey CTRL-ALT-BKSP for restarting your current X-Session, don’t know if this still exists
It’s turned off by default in a lot of distros these days but it can be turned back on. It used to be that editing /etc/X11/xorg.conf was recommended but because file inclusions are a thing these days, it makes more sense to create a new file /etc/X11/xorg.conf.d/enable-killing-xserver.conf:
Section "ServerFlags" Option "DontZap" "false" EndSection Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "yes" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSectionThen restart the X server (which, these days, is pretty much a reboot). Or, going through the x.org documentation archives, it looks like you could dispense with the config files and run
setxkbmap -option "terminate:ctrl_alt_bksp"in a terminal session and that’ll do the same thing.That doesn’t work for Wayland and I’m unsure which one Zorin uses
It uses Wayland
That is not an equivalent.
On Linux, if a graphical app does not crash from this, that is a rare exception.
On windows, if a graphical app crashes from that, that is an exception.
I was thinking of that when I read this and was like. windows has something like this???
Ctrl+alt+backspace
I think on some distros this is disabled by default. I have forgotten how you can re-enable it.