I have an ASUS laptop with a Ryzen 5 (mobile) and Nvidia 1650 graphics. I installed F31 a few days ago, and have been having problems with resuming the session after suspending it (to the RAM). I tried every possible step (installed Nvidia drivers, updated the kernel and everything), but they don’t work for me.
I am not sure what I should pursue next. It’s my first time with Nvidia graphics and hence am unsure if it is Nvidia’s fault or not. I am now running on the Nouveau drivers (reverted back), and would like to know what should I do next.
I am experiencing the same problem. Once the kernel got updated to 5.5.5-200, when my laptop attends to resume from sleep, the display shows horizontal lines and the system is totally unresponsive. Being patient, I wait for whatever regression has been introduced by the new kernel is resolved.
Inxi showing the relevant bits…
please don’t stone the noob for saying, “me too”.
Attached inxi if that helps.
So far, when I have a brand new install, kernel 5.3.7, suspend (closing lid) “mostly works” especially when plugged in, things go back to normal when I open the lid again. After I updated to a new kernel (5.4.19), the system freezes when I open the lid, no kbd, touchpad, etc.
When on battery, suspend doesn’t. Either way I seldom have a clean system off, the system hanging at some last line. I’ll go open my own thread, just wanted to mention that this suspend issue might not be related to Nvidia at all, but something else?
Did your problem happen right away when you installed Fedora? or did it start not working after you did an update?
I am asking because I have exactly the same thing - no resume after suspend - but only when running a new kernel, after an update/upgrade. If I select the old kernel 5.3.7 in GRUB during boot, things “mostly work”, sometimes I don’t get suspend when closing the lid, system stays ON, but when it does suspend, system resumes normally after opening lid and flicking the power button, no freeze
BTW, I don’t have Nvidia, and I respectfully don’t think Nvidia is the problem, though we all know Nvidia has had a lot of issues in Linux, been there
To avoid having to select the old kernel manually every time, this is what I did, might work for you or not: rpm -qa \*kernel-core\*
gives me a list of kernels I have, like this:
Then, to remove the one I don’t want, sudo dnf remove kernel-core-5.5.7-200.fc31.x86_64
From now on, the system will boot automatically to the old kernel
Of course this is not a solution, just a way to keep going until this problem gets solved. Best to y’all!
you’re quite right that this problem is showing up all over, if you do a search for “Fedora” “suspend” you’ll see something like this showing up from F29 on, and also in other OSs (ArchLinux, Centos). Apparently tablet people have this also. I would be curious if 5.5.7 works for you. I tried, didn’t work for me.
There is a suggestion about downgrading systemd, and then upgrading kernel, as if the problem actually might be with systemd and not in the kernel. I will try that. My memory is that there was a time when suspend worked flawlessly, at least for me, and then not anymore… Oh well, we’ll see. Thank you
I recently got a new laptop, and installed Fedora on it. I naturally assumed that it was because of the NVidia graphics since my previous laptop was AMD and everything worked flawlessly. However, I do have to say earlier I used GNOME and this time I am trying out KDE Plasma. So, maybe it’s related to KDE (if you people are also using KDE)…
This might be a kernel issue, but I don’t know how to log the issues such that it can be reported to the devs. journalctl?
In my experience with Fedora, around the time of releasing a beta for an upcoming version, all sorts of minor annoyances crop up. Historically this was about the time I would try another distro, and would return to Fedora a few versions later. This time I’m staying put, for the simple reason that I have a shared wireless Epson printer and with other distros it is a nightmare to configure this printer, whereas with Fedora it is a breeze.
Hi all, I’m new to Ask Fedora, but non so new about Fedora or linux in general. Anyway, as I’ve been far from the linux world for some time (few years…) and I came back with Fedora 30 KDE, now I need some help.
I’m having an issue when resuming from suspend to ram soon after the upgrade process from 31 to 32. Maybe it’s useful to say I upgraded from 30 to 31 without any issue and then thi s happened the other day after going from 31 to 32.
The only solution I found is to use the erlier kernel 5.5.17-200.fc31.x86_64 for Fedora 31.
Is there a way I can go back to use the actual kernel and solve the suspend/resume issue?
EDIT: I just tried the 5.6.8 and 5.5.18 kernels and I these are the dmseg errors I get with the 5.6.x serie (when resume after suspend doesn’t work) that I don’t see with 5.5.18:
[ 14.222988] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.224223] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.226409] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.227001] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.228061] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.228063] sony_laptop: couldn’t set up lid resume function (-5)
[ 14.228305] sony_laptop: Invalid acpi_object: expected 0x1 got 0x3
[ 14.228306] sony_laptop: couldn’t to read the thermal profiles
[ 14.228307] sony_laptop: couldn’t set up thermal profile function (-22)