Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistence in Fedora Silverblue #47

Open
ghost opened this issue Oct 10, 2022 · 1 comment
Open

Persistence in Fedora Silverblue #47

ghost opened this issue Oct 10, 2022 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 10, 2022

Hello, thanks for the great script! Worked just fine in Fedora Workstation. However, as expected I'm having issues adding the persistent service to /lib/systemd/system/ or /usr/lib/systemd/system-sleep in Fedora Silverblue as these folders are read-only. Would you have some pointers as to how to make the script persistent in Silverblue? Many thanks.

edit: It seems the service works when placed in /etc/systemd/system/ but I'm having no luck with the resume script so far. Would you say rewriting the service file to something like this would work to avoid having to add the suspend script?

@sibradzic
Copy link
Owner

Hi @mystrdat, thanks for the report.

The systemd files you can find in this repo are just a best effort examples, they are by no means limited to being placed into any particular directory, feel free to place them wherever your distro deems acceptable.

Regarding resume script, this seem to be yet another consequence of systemd design choices, and distros like Silverblue are only making it more difficult for some reason. Since amdgpu-clocks-resume was a contribution by a community in the first place, I do not feel confident to mess up with that (I am by no means systemd expert, quite the contrary), but further contributions are more than welcome.

@sibradzic sibradzic reopened this Jul 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant