Hi all, I have tried everything, and now I am coming here for help. Hopefully someone can tell me what’s happening here. So, I have this older pc that I have converted into a steam console, first with Bazzite and now with Chimera OS. Both work very nicely, but the one issue that persisted on both distros is that when I put the pc to sleep from game mode (press xbox button>power>sleep) then wake it up, the screen is not receiving a signal, it not even a black screen, just no signal. I would have to force reboot it to be able to get in. Nothing works. I can’t even get into a tty screen or do anything. It is connected to a samsung tv 65mu8000 via HDMI cable. I have UHD color input enabled for that input, just to give more details.
I have tried disabling the wake up animation like some folks suggested and that didn’t do anything. I have tried disabling the display core like some other searches suggested by putting amdgpu.dc=0 in modprob.d in its own file. I have tried blocking the intel iGPU, even though this CPU doesn’t have one. Nothing works. It has an intel core i7 5930k and an AMD RX 6600. I would appreciate any help or suggestions Thank you
You think it’s the screen/hdmi at fault, but it might not be. I’ve had the problem with two laptops in the past (the bug was with all distros I tried), and in one case it was a BIOS that Linux didn’t like, and the second one was the internal wifi that its linux driver was buggy. For the first laptop there was nothing to be done, so I disabled sleep completely in the bios, while for the second one, I disabled the wifi modules in the kernel’s blacklist, and then used a usb wifi that I knew it worked better. Both cases were appearing as a dead screen, but it wasn’t the screen/hdmi/gfx card to blame. In yet another case, with a thinkpad laptop, the wake up was working, but it would wake up 30 seconds later than anticipated. In that case, it was the fact that its thunderbolt was dead (hardware had gone bad), and only when I disabled it in the bios completely the laptop would wake up correctly and fast.
In all those cases, I had to look at the kernel logs to see what was the issue. There were traces of the problem of which hardware exactly was creating the problem. It might look like a screen/hdmi problem, but most of the times, it’s not.