Good Morning!
I dont wanna push it after all the excellent help I got with my NVIDIA drivers yesterday, but…
My computer starts to sleep if I dont toch it for a while, and when I come back to move the mouse nothing happens and I have to restart.
I suspect that you’ve already talked about this isse here:
System freezes after sleep (Tumbleweed) - English / Applications - openSUSE Forums
The thread is locked so I cannot write in it anymore. I have som trouble understanding the answer though. The answer is linked in a forum from an arch-forum.
If Ill understand correctly, I should either write this line:
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
Somwhere, or downgrade SystemD (which appear to be like autoexec.bat for linux)
I prefer not to downgrade something, so my first question is if I understood this correctly? And where should I in that case write the line
[Service]
Environment=“SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false” ?
The fedora solution didnt help, but at least it didnt make things worse
I have a sinking feeling this has something to do with the Nvidia driver.
There are others like @karlmistelberger who has had similar issues.
Try looking at the journal logs for any priority 3 errors journalctl -p3
.
An easy solution could be to disable s2ram and use s2idle, it will consume more battery power though!
https://docs.kernel.org/admin-guide/pm/sleep-states.html
A lot of stuff came up then:
Nov 13 18:36:08 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2921]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 18:36:08 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2921]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 18:36:08 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2921]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 13 18:36:08 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2921]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 13 18:38:57 h-46-59-93-100.A463.priv.bahnhof.se (sd-pam)[1578]: pam_systemd(systemd-user:session): Failed to release session: Caller does not be>
– Boot 47ee0b06cf9d4f0c9f3f9023f4252960 –
Nov 13 18:57:13 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3716]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 18:57:13 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3716]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 13 18:57:13 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3716]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 18:57:13 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3716]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 13 19:07:17 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3985]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 19:07:17 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3985]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 13 19:07:17 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3985]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 19:07:17 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3985]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 13 19:12:54 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[4135]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 19:12:54 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[4135]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 13 19:12:54 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[4135]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 19:12:54 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[4135]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
– Boot d5c0ee23a2604f9abe55b970c516c27d –
Nov 13 19:40:58 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3238]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 19:40:58 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3238]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 13 19:40:58 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3238]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 19:40:58 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[3238]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
– Boot 359952403aa7470d8c782ab354167a5e –
Nov 13 19:54:37 h-46-59-93-100.A463.priv.bahnhof.se dbus-broker-launch[1577]: Activation request for ‘org.bluez.obex’ failed.
Nov 13 19:54:38 h-46-59-93-100.A463.priv.bahnhof.se kwin_x11[2902]: This application failed to start because no Qt platform plugin could be initiali>
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, >
Nov 13 19:54:38 h-46-59-93-100.A463.priv.bahnhof.se dbus-broker-launch[1577]: Activation request for ‘org.freedesktop.portal.Desktop’ failed.
– Boot 30d1084f59ac45d6bc287ce43c2ac7d8 –
Nov 13 20:03:56 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2997]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 13 20:03:56 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2997]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 13 20:03:56 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2997]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 13 20:03:56 h-46-59-93-100.A463.priv.bahnhof.se kscreenlocker_greet[2997]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
– Boot 4126a5fe4d4e4772bd8adfd03b617160 –
Nov 15 08:53:13 h-46-59-89-212.A463.priv.bahnhof.se (sd-pam)[37270]: pam_wtmpdb(login:session): update_logout: Updating logout time did not return S>
Nov 15 08:53:13 h-46-59-89-212.A463.priv.bahnhof.se (sd-pam)[37310]: pam_wtmpdb(login:session): update_logout: Updating logout time did not return S>
Nov 15 08:58:33 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[38559]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64>
Nov 15 08:58:33 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[38559]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 15 08:58:33 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[38559]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/>
Nov 15 08:58:33 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[38559]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
– Boot 8a571d58e4c644faa055ef3f771bec36 –
Nov 15 09:39:02 h-46-59-89-212.A463.priv.bahnhof.se hp-setup[8836]: hp-setup[8836]: error: No devices found on bus: net
Nov 15 09:39:02 h-46-59-89-212.A463.priv.bahnhof.se hp-setup[8836]: hp-setup[8836]: error: HPLIP cannot detect printers in your network. This may >
When you are in a trusted network environment, you may open the >
https://developers.hp.com/hp-linux-imaging-and-printing/Knowled >
– Boot 093ddc40cdcf49d59e9799e9f579fcfa –
Nov 15 11:19:18 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4304]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 15 11:19:18 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4304]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 15 11:19:18 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4304]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 15 11:19:18 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4304]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 15 11:27:02 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4642]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 15 11:27:02 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4642]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 15 11:27:02 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4642]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 15 11:27:02 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4642]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
– Boot 338ef9e1a7c243eb8e3e544179d278b1 –
Nov 15 12:11:56 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4246]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/>
Nov 15 12:11:56 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4246]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Nov 15 12:11:56 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4246]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/s>
Nov 15 12:11:56 h-46-59-89-212.A463.priv.bahnhof.se kscreenlocker_greet[4246]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Nov 15 12:29:00 h-46-59-89-212.A463.priv.bahnhof.se systemd-coredump[4976]: [🡕] Process 4590 (dolphin) of user 1000 dumped core.
I would also like to know more about ‘how to disable disable s2ram and use s2idle’ please
Ouch, that does not look like a healthy system
To fix the pam issues, do:
sudo zypper in --force pam_pkcs11 fprintd-pam
Check current suspend config:
pavin@suse-pc:~> cat /sys/power/state
freeze mem
pavin@suse-pc:~> cat /sys/power/mem_sleep
s2idle [deep]
deep
means s2ram is available. those square brackets mean it’s the default.
Test if s2idle works (save and close all apps prior to running just in case):
# run as root
echo freeze > /sys/power/state
Said to hear my system doesnt look healthy. I have finally managed to get the nvidia working and just tested a game on steam, so Ive never seen a healthier linux system…
so I did just solved the pam issue. (I think) Thank you for that.
staffan@h-46-59-89-212:~/Downloads> cat /sys/power/state freeze mem
freeze mem disk
cat: freeze: No such file or directory
cat: mem: No such file or directory
staffan@h-46-59-89-212:~/Downloads> cat /sys/power/Mem_sleep s2idle [deep]
cat: /sys/power/Mem_sleep: No such file or directory
cat: s2idle: No such file or directory
cat: '[deep]': No such file or directory
staffan@h-46-59-89-212:~/Downloads> cat /sys/power/mem_sleep s2idle [deep]
s2idle [deep]
cat: s2idle: No such file or directory
cat: '[deep]': No such file or directory
staffan@h-46-59-89-212:~/Downloads> ^C
I know the cat command list whats in a file, so Im not sure I did that correctly.
But when I open the sys/power/state file it says “freese mem disk”.
When I open the mem_sleep it says “s2idle [deep]”
I will now try and test s2idle
ok, that one didnt turn out well
h-46-59-89-212:/ # echo freeze > /sys/power/state
bash: echo: write error: Input/output error
hui
November 15, 2024, 3:07pm
9
You only want to list the content of the file via cat. That means cat and the filename needs to be used. As you are overhanding additional invalid parameters after the filename, the file cannot be read.
Wrong command:
cat /sys/power/mem_sleep s2idle [deep]
Correct command:
cat /sys/power/mem_sleep
1 Like
Hmm, could you try:
# run as root
echo s2idle > /sys/power/mem_sleep
# make sure s2idle is in square brackets (active) by running:
cat /sys/power/mem_sleep
# make system go into s2idle
echo mem > /sys/power/mem_sleep
# Wait few seconds, press some keyboard button to resume and provide output of
journalctl -p3 -b
h-46-59-89-212:/ # echo s2idle > /sys/power/mem_sleep
h-46-59-89-212:/ # cat /sys/power/mem_sleep
[s2idle] deep
h-46-59-89-212:/ # echo mem > /sys/power/mem_sleep
bash: echo: write error: Invalid argument
h-46-59-89-212:/ #
That went well until echo mem > /sys/power/mem_sleep
I might add though, that I can revive my screen if its only been sleping for a short while.
Looks like there’s some issue with s2idle too!
Could you provide the output of sudo journalctl -p3 -b
?
That most likely is just the screen being turned off by the DE and not an actual suspend/resume!
hui
November 15, 2024, 4:01pm
13
Nope. echo mem > /sys/power/mem_sleep
won’t work. The mem
parameter needs to be overhanded to /sys/power/state
and not /sys/power/mem_sleep
.
Check your instructions from this comment . They are wrong.
1 Like
You’re right, I just had a brainfart .
mem
is supposed to be written to /sys/power/state
.
Thats cool of course
But sadly it didnt work either:
staffan@h-46-59-89-212:~/Downloads> su
Password:
h-46-59-89-212:/home/staffan/Downloads # echo mem > /sys/power/state
bash: echo: write error: Input/output error
h-46-59-89-212:/home/staffan/Downloads # cat /sys/power/state
freeze mem disk
h-46-59-89-212:/home/staffan/Downloads #
can I edit the file in notepad and add around mem?
Editing won’t work as this is a pseudo file. You can read from it and write to it, but it’s really an API endpoint exposed as a file for sysadmins and users [1] to interact with the underlying features of the kernel.
[1] as opposed to programmers who would directly call the C functions.
pseudo file = endpoint api. This is great knowledge.
Any idea why it didnt work?
Chatgpt seem to think its the NVIDAI again. (I will never in my life buy NVIDIA again, but this computer is only 5 years old)
Hopefully someone with Nvidia can chime in, but you could search for similar issues on the forum. there are plenty sadly!
One idea I had for hibernation on @karlmistelberger 's machine was to do the following:
Stop the DE
Unload the proprietary driver
Load the open driver
Hibernate
On resume, reverse those actions essentially.
Little complicated and wouldn’t work for suspend.
Unload the properitary driver?
after doing all this:
Hello, Ive been trying out linux on varoius old laptops, but thought that thus time I should try it on my real dekstop. I was proad when I managed to get the broadcom drivers working using a usb stick However when I run the NVIDIA install I get the following error:
neither the ‘/usr/src/linux/include/linux/version.h’ nor the /usr/src/linux/generated/uapi/linux/version.h’ kernel header file exists. the most likely reason for this is that the kernel source files in ‘/usr/src/linux’…
…Im not sure I want to do that