Screen Freeze and Black Monitor Start

timbba

I have the same problem. I do not have any boot issues, but few times a day there will be a complete freeze: exactly same way than in amoyat video.

My laptop is Lenovo Yoga 910-13IKB, which has Intel HD Graphics 620. I can't remember what was the date when problem occurred the first time, but I assume that the culprit started once 5.2x kernel was taken into use. I will have to downgrade and see what happens with older kernels.

Edit: I have tried also setting i915.enable_psr=0 into kernel cmdline, but that didn't help. I found that tip over here, if that helps with someone else. At the moment, I'm testing older kernel 5.1.14-121.current

Justin

timbba You could try the LTS kernel.

colorado_chris

Permanent Fix

Install Linux-LTS from the software center.

Reboot into new kernel, then run

sudo clr-boot-manager update

timbba

Justin

Yeah, one option is to use LTS kernel and that may be the easiest solution. But my intention is to find the culprit 😁

timbba

So far no issues on kernel 5.1.14. I found this while googling and it seems to be the same issue. Anyway, if you browse that thread through, there is a mention about a fix that landed on kernel 5.2.8.

Does anyone know if kernel 5.2.8 or newer is going to be included in Solus repositories as linux-current?

Edit: Oh my god... kernel 5.2.9 is already on repositories! Need to test that one... 😃

v3l0ct

I have to run the lts kernel on my laptop with a 1070GTX on it

timbba

Maybe it is better to use LTS kernel 😀 . I tested kernel 5.2.9 and I didn't face into screen freezing issues so that you can only use mouse. Instead I faced into freeze that you cannot use mouse... so the problem in kernel 5.2.9 is quite opposite and you still face into weird freezings. When freeze happens for mouse, you cannot shutdown properly, because it will hang. You cannot either list your pci devices using lspci, because that will hang too. So kernel 5.2.x is quite unstable and I won't recommend it to anyone (at least from my experience).

I installed linux-ltsand I will continue to use that.

ishiken

So, I was able to run linux-current, but only with the proprietary nvidia-glx-current installed. It destroyed my battery life. However, the nouveau hang went away. Thankfully, I followed advice and had already installed the linux-lts kernel. I removed the nvidia drivers and nouveau drivers via TTY and reboot into the LTS kernel. Updated CLR to make it default. I really wish I could find out why it started doing this. I used to be able to run the linux-current package with the iGPU just fine. If I tried now, it would lock up any time I attempt to look at a pci device.

sgvd

Also for everybody experiencing hangs, try to disable hardware acceleration in Firefox. I am not sure whether the issue is still there, but it fixed my freezing (except mouse) completely.
(Edit: I have an AMD card)

kyrios

sgvd Except that hardware acceleration is not enabled by default in Solus

sgvd

@kyrios For Bungie and KDE* it was both enabled in Firefox after a fresh install. Hence the first thing I do after a fresh install is to turn it off.

*For Mate I am not sure, didn't check when trying that DE.

kyrios

sgvd It got nothing to do with the DE, it's the Firefox default settings and it is not enabled as you can see on the below link.

https://dev.getsol.us/source/firefox/browse/master/files/prefs.js$22

sgvd

kyrios Can you clear something up for me?
The line you specify (layers.acceleration.force-enabled) is indeed false. However, this setting does not influence the Hardware Acceleration option in the settings interface, that is only influenced by layers.acceleration.disabled.
So as far as I can see, it is indeed not forced (line 22 of the prefs file), but it is by default enabled, as the disabled option (layers.acceleration.disabled) is false and not present in the prefs file.

Whenever I check or uncheck the Hardware Acceleration option through the normal settings, I see layers.acceleration.disabled getting toggled, supporting this conclusion. Hence this option should be added to the prefs file (with 'True' value) to actually have Hardware Acceleration turned off by default.

Edit: Screenshot added. I unchecked it on the right, the left is just the result in about:config.

sgvd

Clear, thanks for pointing it out. I didn't know which about:config entry represents it, so I based my conclusions on the settings menu, which clearly suggests otherwise in two places*.

I will try a clean reinstall and see whether I can reproduce the freezing I experienced in february. And if it does, whether Firefox settings changes as I describe still fix it. I am wondering why it fixed my freezing issues back then when it apparently does not change the hardware acceleration setting.

*The option shows enabled when unchecking recommended, suggesting it was already enabled. Additionally the 'learn more' section linked there also mentions it's on by default under recommended settings.

kyrios

sgvd Long story short, hardware acceleration on firefox on linux is a complex thing.
You can have layers.acceleration.disabled set to false or the box checked and still have no hardware acceleration.

You may want to check this bug to get more info (I think that's the one cos I was too lazy to browse it).

If you really want to know if hardware acceleration is enabled on your system go in about:support and look for HW_COMPOSITING. On my machine, for example, although the HW acceleration box is ticked, I see blocked by env: Acceleration blocked by platform which actually means it is not enabled.
However if I set layers.acceleration.force-enabled to true, the value of HW_COMPOSITING becomes force_enabled by user: Force-enabled by pref this means it's really enabled and you can check the resources usage to confirm it's working. The thing is that forcing this setting cause issues with some GPU looks at NVIDIA with evil eyes and that's where people say hardware acceleration must be disabled to solve some issues.

PS: You have to restart firefox for the settings to apply I think.

sgvd

kyrios
Jup, my machine indeed has the same HW_COMPOSITING value as what you mention. Thanks for the additional clarification!

« Previous Page