You can just use screen for that and have a working terminal with color support et al.
I helped fix sleep-wake hangs on Linux with AMD GPUs
11–20 of 218 posts
Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#12Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#13Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#14I have an Nvidia GPU and a sporadic crash (black screen) with no logs on Linux. I suspect it's a driver issue too. Going to try some of these tips to enable the debug shell, but I'm not sure if they'll be effective. Anyone have other tips for this type of thing? I did try upgrading drivers/kernels already
If memtest shows a specific memory region as failing, swap out sticks to check which it is, and buy a new one. (Or if you're on a tight budget, you can disable that region with kernel boot options.)
If memtest gives errors in lots of places, might be a bad overclock. Loosen timings or give it more voltage.
Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#15Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#16Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#17> Through some digging, I found that when a desktop enters S3 sleep, the system cuts power to PCIe GPUs I am not sure how correct this assumption is. S3 is supposed to cut power to everything but RAM, but for example Gigabyte Aorus motherboards are notorious for an NVMe SSD sleep bug that randomly prevents the system from properly sleeping or waking. This is fixed by adding the following udev rule: # Generic PCIe fix…
Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#18If anyone has ideas what could fix this I'd really appreciate it. The machine is dual booted with Windows, and there sleep works without issue, so it's clearly possible, as it was for years before that on Linux as well.
Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#19Re: I helped fix sleep-wake hangs on Linux with AMD GPUs
#20I have an Nvidia GPU and a sporadic crash (black screen) with no logs on Linux. I suspect it's a driver issue too. Going to try some of these tips to enable the debug shell, but I'm not sure if they'll be effective. Anyone have other tips for this type of thing? I did try upgrading drivers/kernels already
Run a memtest. Graphics cards usually crash badly when given invalid data, which can happen sporadically if you have bad RAM. If memtest shows a specific memory region as failing, swap out sticks to check which it is, and buy a new one. (Or if you're on a tight budget, you can disable that region with kernel boot options.) If memtest gives errors in lots of places, might be a bad overclock. Loosen timings or give it…
Honestly, I'd always do that as the first option. In most cases you can still get years of life out of that stick of ram (but do check regularly, like after a week and then double the interval every time if it didn't get worse).