Arch Linux User Repository

@parsaazari: the errors you have mentioned are not related to the nvidia drivers.

I would say there are some ongoing issues on your current system which prevent the correct loading of different modules - and perhaps destabilizing also the nvidia driver. You did not provide your kernel version, or the nvidia driver version, or any other precise information. With the information given I would assume you tweaked some parameters on various config files without knowing what are the consequences.

Since the purpose of this thread is focused exclusively on nvidia 470xx, I would not expect too much guidance outside this subject; perhaps the Arch wiki article should be good enough put you on the right track ?

hi, I have been having this sleep freeze issue whenever a video player (vlc,stremio) is left open while the system goes into sleep. i tried to install the latest package and it failed due to these errors: libkmod: kmod_config_parse: /etc/modprobe.d/iwlwifi.conf line 2: ignoring bad line starting with 'swcrypto=1' ==> ERROR: Cannot acquire used modules. Unable to use autodetection.

==> Starting build: '6.9.5-arch1-1' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [keyboard] ==> ERROR: module not found: 'usbhid'

==> WARNING: errors were encountered during the build. The image may not be complete. error: command failed to execute correctly

could anyone help?

@kachelaqa: Can we consider the issue adressed, then ? Does it work as expected now ?

@SoftExpert Actually, those paths are now correct. It seems your previous fix must have used the paths from this earlier invalid commit.

My reading of the systemd.unit docs is that /usr/lib/systemd/ is the most appropriate root location, since it has the lowest precedence. Your modified PKGBUILD now matches the latest offical nvidia-utils one, so it should be okay.

@kachelaqa: I picked the target paths from https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-utils/-/blob/main/PKGBUILD?ref_type=heads.

It seems those paths are not effective, based on what you observed.

Which location would be the best to put both .conf files ?

Would /etc/systemd/sleep.conf.d/systemd-homed-override.conf and /etc/systemd/sleep.conf.d/systemd-suspend-override.conf be sufficient ?

Or it would suffice to modify the current target paths in the PKGBUILD as follows ?

    install -Dm644 "${srcdir}"/systemd-homed-override.conf "${pkgdir}"/usr/lib/systemd/system/systemd-homed.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/system/systemd-suspend-then-hibernate.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/system/systemd-hibernate.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/system/systemd-hybrid-sleep.service.d/10-nvidia-no-freeze-session.conf

edited to add alternative path

@SoftExpert The suspend service file is part of systemd itself, so of course everyone will have it installed by default, since systemd is in core.

The article you linked to seems a little confused because its title refers to the location of configuration files, whereas its text actually refers only to unit files. The systemd.unit docs state that the drop-in ".d/" directories should go alongside the corresponding service file. Thus, given that the location of the suspend service file is /usr/lib/systemd/system/systemd-suspend.service, its drop-in directory should be /usr/lib/systemd/system/systemd-suspend.service.d/.

@kachelaqa: If you have systemd-suspend.service installed and active, then the file /usr/lib/systemd/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf is seen and used by the unit systemd-suspend.service; you will need, however, to restart systemd. If you do not have the unit systemd-suspend.service I would expect the folder /etc/systemd/system/systemd-suspend.service.d/ to be ignored.

According to this article the location we used is perfectly valid.

Can you, please, describe which systemd units are installed on your environment and why they cannot see the .conf files we provided ?

@SoftExpert After the most recent update, I found that sleep still freezes. However, when I used the method described by OxHak (i.e. setting the envar within a file under /etc/systemd/system/systemd-suspend.service.d), everthing works as expected.

I don't really understand your previous comment - why should it be necessary to install anything extra to make the fix work?

@OxHaK: Hummm, maybe there is some misunderstanding here: the package will install the .conf files in the /usr/lib/systemd/ path in several sub-folders. Here is the relevant part of the package script:

    install -Dm644 "${srcdir}"/systemd-homed-override.conf "${pkgdir}"/usr/lib/systemd/systemd-homed.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/systemd-suspend-then-hibernate.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/systemd-hibernate.service.d/10-nvidia-no-freeze-session.conf
    install -Dm644 "${srcdir}"/systemd-suspend-override.conf "${pkgdir}"/usr/lib/systemd/systemd-hybrid-sleep.service.d/10-nvidia-no-freeze-session.conf

In my view, this will suffice to apply the 2 environment variables in the context of the following systemd services:

• systemd-suspend.service

• systemd-suspend-then-hibernate.service

• systemd-hibernate.service

• systemd-hybrid-sleep.service

• systemd-homed.service

However, this will require the correspponding systemd services to be installed (they are not in the default set). For example systemd-suspend-modules.

Obviously, if there is another special case not covered by the current configuration, we can add it to the package - we just need to make sure to pick the most "standard" approach.

*edited to fix a typo and the list

@SoftExpert The installation probably didn’t fix the issue because the directory /etc/systemd/system/systemd-suspend.service.d/ was missing on my system. I had to create it manually.