Laptop doesn't properly turn on after suspend

GladiusDX

On Solus 4.0, my laptop doesn't turn back on after suspend: the backlight doesn't turn on and the screen is completely blank, so I can't do anything unless i force shutdown holding the power button.

CorvusRuber

GladiusDX my laptop

A lot of people lately has a lot of problems with this specific model......

GladiusDX

Sorry about that.
My laptop is an Asus E402M with a dual-core Intel Celeron N2840, 2 GB of RAM and a 32 GB SSD. I'm running Solus 4.0 and the Gnome version (according to the "Informations" tab in settings) is 3.32.1

CorvusRuber

Well, at a minimum you could take a look at the logs with journalctl (quick list of basic tricks) and see if there's something strange at suspend and resume.
That should at least give some pointers to what is going wrong (by the way, I'm pretty surprised that Gnome is running well on an hardware so....minimalist, so to speak)

GladiusDX

Thank you, I'll get to it shortly.
By the way, I have installed the Budgie edition, and if I remember correctly it is based of Gnome (probably that's why "Informations" lists the Gnome version)

GladiusDX

https://docs.google.com/document/d/1vGnNgxF10Op3_OQVBcuRfqsbM0SVUk2RTvhk1RfTH0I/edit?usp=sharing

I didn't have (at least that I know of) any other good way of posting the log (the forum doesn't allow the uploading of .txt files)

To obtain the log, i powered on the laptop and put it in suspend mode; then I tried to exit suspend and turned off the system. I hope that I did everything right, if not let me know what to do

Scotty-Trees

I have an Acer Aspire E5-576G laptop running Gnome 3.32.2 running kernel 5.2.9-125 (aka the current kernel), and I experience a similar issue. Once a try to wake it up from suspend, it just turns black and becomes unresponsive so I have to power down manually. So because of this issue, I just don't use suspend, I just power off my laptop.

However, if you're like me and got a little curious, if you try to suspend on the 4.9 LTS kernel, I found that the suspend function works just fine.

TL;DR, Suspend might work on the 4.9 LTS kernel, but might be borked on the 5.2 current kernel. Hope this helps some! Happy Friday Sync!

GladiusDX

Ok, I intalled the linux-lts kernel and, when rebooting, changed the kernel. It now seems to work perfectly! Now, can i ask you if is there a way to force the use of the LTS kernel?

EDIT:
I did it! All it took was runningsudo clr-boot-manager update with the right kernel in execution; thanks a lot

jrynkiew

I also had this issue.

On Acer Aspire V3-371 kernel 5.10.5-167 built by Solus (Budgie).

WiFi would crash the suspend mechanism, due to errors during unloading modules. Hibernate was working (after creating respective swapfile), but suspension was not. Turning off WiFi and Bluetooth manually before suspending the machine would fix the issue, but I didn't want to turn off wireless radios before every suspension, so I was determined to fix it.

Funny thing is that the live-disc didn't have these issues, only started occurring after installing to hard drive, which led me to this forum (and others) trying to find the solution.

I created a file 20-wmi-bmof-blacklist.conf in /usr/lib64/modprobe.d with the following line:

blacklist wmi_bmof

And then in file /usr/lib64/dist-blacklist.conf I added the following line:

#Prevent wmi_bmof from installing if requested. It is blacklisted in 20-wmi-bmof-blacklist.conf file. We have a specific acer_wmi to handle wireless!
install wmi_bmof /bin/false

After performing these tasks, and rebooting computer, I can successfully suspend the computer. All modules unload fine.

jrynkiew

jrynkiew It's broken again, I might have fluked it somewhere and accidentally crashed wmi before suspending, and thats why it worked? I don't know, but maybe related to https://bugzilla.kernel.org/show_bug.cgi?id=32052

palto42

jrynkiew I have also issues with wake-up after suspend with current kernel 5.10.5-167. First all looks good and seems to work, I get the lock-screen and can unlock it and use all my running apps. But after short time (minute?) the session seems to crash and I get the login screen like after boot. If I then login, all previously running apps are closed.
From the logs I haven't been able to identify what exactly causes the "crash".

With LTS kernel 4.14.213-163 this issue doesn't happen.

palto42

Now same issue with LTS kernel, so my issue most likely not related to the kernel.

In the journalctl I can see several errors about display :0 not available, e.g.

Jan 10 17:27:55 cubitus gnome-screensav[921]: gnome-screensaver: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.

Next many apps exit with error code 1, e.g.

Jan 10 17:27:55 cubitus gnome-session[878]: gnome-session-binary[878]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1

and then the session is stopped and daemons killed:

Jan 10 17:27:55 cubitus systemd[1]: Stopping Session 1 of user matthias.
Jan 10 17:27:55 cubitus kernel: rfkill: input handler enabled
Jan 10 17:27:55 cubitus gnome-session[878]: gnome-session-binary[878]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 1
Jan 10 17:27:55 cubitus gnome-session[878]: gnome-session-binary[878]: WARNING: Application 'org.gnome.SettingsDaemon.Datetime.desktop' killed by signal 1
...

Still not clear what is causing this problem.

jrynkiew

palto42 I managed to solve the issue by commenting out the following line from:

/usr/lib/NetworkManager/conf.d/NetworkManager.conf

[device] #wifi.scan-rand-mac-address=no

Restart, and suspend will start working🙂
If it doesn't, please note down the system time on your machine, trigger the suspend, and after a hard reset, post your system logs.
You can get all system logs by the following command (change the date/time to be a minute before you trigger the suspend)

sudo journalctl --since "2021-01-11 02:20:00" > logfile.txt

and then post the context of the logfile. I can try to help you as much as I can 🙂

palto42

jrynkiew Thanks for your support, but in my case the root cause seems different. The NetworkManager settings didn't change anything.

So I started to test with different apps running when suspending, starting with none (including some background apps like Nextcloud client). After several tests with suspend and wake-up cycles, I currently think that the Brave browser is causing the issue, but need some more tests to be sure.

jrynkiew

palto42 Did you run journalctl command to try to identify what is happening with your system when it initiates the suspend mode?

palto42

jrynkiew Yes, I tried to identify what triggers the force-logout, but couldn't identify the root cause.
Since not using Brave anymore I had no issue, but was also not using suspend that often.
I tried a slightly newer version 1.18.78 of Brave than in repository (compiled with solbuild), but had same issue while using it yesterday.

I'll only continue troubleshooting if I should face same issue while not using Brave.

palto42

Meanwhile I think that the bug is not directly in Brave since I face same issue if I have a running VS Code session. So I assume that Brave and VS Code use some other function which triggers the bug which causes Xorg to crash.
In journalctrl I found an entry which seems to indicate an Xorg issue:

audit[696]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=696 comm="Xorg" exe="/usr/lib64/xorg-server/Xorg" sig=6 res=1

But still not clear what causes this crash.

palto42

It seems that the Solus upadet hasn't this solved my problem. First it looked better, but just had another Xorg crash after resume from sleep.

uniquegch

for the last two weeks or so when I suspend or hibernate my laptop and turn it back on it logged me out completely. How can I investigate this issue, which log files should I look at? Like in the past when I resumed the computer I could continue were it was when suspended. Now no apps are kept open.

uniquegch

did some changes in the BIOS and the network manager by turning off Wake-on-LAN. The laptop is a barrier client, so moving the mouse and keyboard on the server seems recently to interfere with the Suspend on the Solus Laptop.

uniquegch

uniquegch
I did further investigation, because the adjustment did not solve the suspend situation. it is the bluetooth which causes the problem (as jrynkiew has mention in his blog on Jan 10th). I have turned off Bluetooth and Suspend works.
Only I cannot turn on Bluetooth after suspend. I have not rebooted my laptop. Because I do not need Bluetooth, this works for me. I hope that helped somehow.