Since the last package update, my laptop monitor is not functioning correctly. However, my external monitors, which are connected, work fine, and I can see all of them in the display configuration. I can still use the laptop monitor in the BIOS settings.
Surprises from computers are rarely good – they are often symptom of deeper problems.
It could help others with the same issue if you can provie more data. Fedora’s journactl comand-line tool collects a massive amount of detail, so it is an art to extract the lines that are relevant to your issue. Making a note of the time the built-in display wakes up will help. The frst step is to make sure your system is fully updated (including Lenovo firmware) so you aren’t chasing a bug that has been fixed and so other users will have the same software.
Unfortunately, the issue is recurring. I am using the latest BIOS version for the model, and based on the commands, there don’t seem to be any other updates available for my device.
Hello @clueless-user ,
Please run these commands in a terminal cat /sys/firmware/acpi/platform_profile_choices and cat /sys/devices/system/cpu/amd_pstate/status and … sudo ls /sys/devices/system/cpu/cpufreq/policy0/*amd* and also sudo cpupower frequency-info it could be related to the choice of drivers for your AMD CPU, there is poor ACPI support and newer CPU’s from AMD use pstate instead which gives better fine grained control and better responses to wake up from suspend.
>> cat /sys/firmware/acpi/platform_profile_choices
low-power balanced performance
>> cat /sys/devices/system/cpu/amd_pstate/status
active
>> sudo ls /sys/devices/system/cpu/cpufreq/policy0/*amd*
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_highest_perf /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_lowest_nonlinear_freq /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_max_freq
>> sudo cpupower frequency-info
analyzing CPU 6:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 6
CPUs which need to have their frequency coordinated by software: 6
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.79 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.79 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.80 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.79 GHz.
AMD PSTATE Nominal Performance: 111. Nominal Frequency: 3.20 GHz.
AMD PSTATE Lowest Non-linear Performance: 38. Lowest Non-linear Frequency: 1.09 GHz.
AMD PSTATE Lowest Performance: 14. Lowest Frequency: 400 MHz.
So you are using the amd-pstate-epp driver, which is the better one for power management than the ACPI one. So I am not too certain that this isn’t something else causing your issue of coming out of suspend. Unfortunately I don’t have a Laptop with an AMD cpu to test on.
Alright, if you have another idea I can test let me know.
Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default
Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: PAM unable to dlopen(/usr/lib64/security/pam_console.so): /usr/lib64/security/pam_console.so: cannot open shared object file: No such file or directory
Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: PAM adding faulty module: /usr/lib64/security/pam_console.so
I also found these. When I use “ls /usr/lib64/security/” I can’t find pam_console.so. In the changelogs it is also written that this has been removed because it is not activated by default. Maybe I’ll try to reinstall my system soon even if I don’t like this option.
Definitely, if there is an issue with returning from suspend then the password access module could be involved. An alternative to a fresh install could be to use the “repair an existing Fedora System” option of the installation media (everything iso I believe).
Thanks for your help guys. After the Christmas holidays, I went back to the problem. For some reason I haven’t tried this yet, but in the end I reinstalled the packages pam and kscreenlocker with the command sudo dnf reinstall pam and the same for kscreenlocker. Now it seems to work