Suspend-Crash on Acer V3-574G-55SD
by Fonk from LinuxQuestions.org on (#4VFQX)
Hi all!
I bought an used Acer V3-574G-55SD for my wife and installed Fedora 31. Everything works fine, but it crashes when I try suspend to RAM: Screen goes off, keyboard lights and fan stay on. It needs a long press on the power button to reboot it.
As suspend problems usually come from the graphic drivers, I spotted that first:
The Laptop is an optimus device with two Graphiccards: Intel Integrated Graphics 5500 and a Geforce 940M. At the moment I'm not using the proprietary nvidia driver, but nouveau instead. I already tried to blacklist nouveau to fully disable that card (but I'm not sure if it's really disabled when it just has no driver). I'm also not sure, if it's worth a try to install to proprietary driver...
I already tried "nomodeset" and acpi_osi=! acpi_osi='Windows 2009' or acpi_osi='Windows 2015' without luck. I also tried debugging via /sys/power/pm_trace and RTC Clock, but only got a hint to "main.c" which might not be very useful ;-)
So I'm looking for ways to debug this problem better - does anyone have an idea? Or even better: Already fixed the problem on a similar device?
Thanks for any help and best regards,
Frank
PS: Hibernate doesn't work as well
I bought an used Acer V3-574G-55SD for my wife and installed Fedora 31. Everything works fine, but it crashes when I try suspend to RAM: Screen goes off, keyboard lights and fan stay on. It needs a long press on the power button to reboot it.
As suspend problems usually come from the graphic drivers, I spotted that first:
The Laptop is an optimus device with two Graphiccards: Intel Integrated Graphics 5500 and a Geforce 940M. At the moment I'm not using the proprietary nvidia driver, but nouveau instead. I already tried to blacklist nouveau to fully disable that card (but I'm not sure if it's really disabled when it just has no driver). I'm also not sure, if it's worth a try to install to proprietary driver...
I already tried "nomodeset" and acpi_osi=! acpi_osi='Windows 2009' or acpi_osi='Windows 2015' without luck. I also tried debugging via /sys/power/pm_trace and RTC Clock, but only got a hint to "main.c" which might not be very useful ;-)
So I'm looking for ways to debug this problem better - does anyone have an idea? Or even better: Already fixed the problem on a similar device?
Thanks for any help and best regards,
Frank
PS: Hibernate doesn't work as well