Package Details: system76-power 1.2.1-1

Git Clone URL: https://aur.archlinux.org/system76-power.git (read-only, click to copy)
Package Base: system76-power
Description: System76 Power Management
Upstream URL: https://github.com/pop-os/system76-power
Licenses: GPL
Provides: power-profiles-daemon
Submitter: ebobby
Maintainer: tleydxdy
Last Packager: tleydxdy
Votes: 13
Popularity: 0.68
First Submitted: 2018-07-05 23:47 (UTC)
Last Updated: 2024-08-22 18:09 (UTC)

Dependencies (7)

Required by (22)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

solarmarten commented on 2022-04-13 23:07 (UTC) (edited on 2022-04-14 12:47 (UTC) by solarmarten)

For anybody wondering how to fix this issue (Getting stuck on compute mode), check /etc/modules-load.d/, /etc/modprobe.d/, and /usr/lib/modules-load.d/ for any files that load nvidia-utils. For me, the problem was fixed by deleting nvidia-utils.conf in /usr/lib/modules-load.d/, setting the graphics back to integrated, and then rebooting.

Related GitHub issue: https://github.com/pop-os/system76-power/issues/252

Vektor82 commented on 2022-03-20 13:50 (UTC)

@hossamdash Hello, thanks for the reply. I am on pure Arch, with no other switching method. Maybe i need another package, aside from system76-power?

hossamdash commented on 2022-03-20 09:31 (UTC)

@Vektor82 if you're on manjaro ( or any distro that ships the mhwd script ) check to see if there are any files generated by that script that load the nvidia kernel module. paths to check are /etc/modules-load.d/ /usr/lib/modules-load.d/

and maybe /etc/modprobe.d/ /usr/lib/modprobe.d/

delete that file and re run the system76-power command and you should be golden

Vektor82 commented on 2022-03-19 21:19 (UTC)

For me it's not working. I am unable to switch to integrated mode. there are no errors. It simply sets integrated, and after a reboot, the laptop starts in compute mode.

lethedata commented on 2022-01-15 14:18 (UTC)

@tleydxdy I don't have enough of an understanding of rust to know exactly why, but it seems to be related rusts linker-plugin-lto or LLVM not working correctly with the devtools implementation. devtools probably has a flag enabled that either just breaks things or requires rust to have additional arguments to work properly. Alternatively, makechrootpkg might spawn in such a way that rust's linker is unable to find what is needed to successfully link.

The aurutils issue reference from earlier makes use of makechrootpkg, which is what the Convenience Way of Building in a clean chroot does. I did test both ways and only the classic way worked.

Sources: (Solved) Can't link any Rust program linker-plugin-lto stopped working in Rust 1.45.0 -Clinker-plugin-lto doesn't work without extra manual work Regression on nightly since LLVM 8 upgrade: thread sanitizer doesn't compile anymore

tleydxdy commented on 2022-01-07 02:42 (UTC)

@echo can you explain a little more about the issue? lto seems like a nice to have, why is it not working in this particular case?

lethedata commented on 2022-01-07 01:55 (UTC)

Rust fails to link (error: linking with 'cc' failed: exit status: 1) when using devtools due to lto being enabled by default. Adding options=(!lto) to PKGBUILD allows it compile.

Issue Reference

yochananmarqos commented on 2021-09-19 19:13 (UTC)

@tleydxdy: Ah, I didn't see that commit earlier.

I just built it without that just fine, odd.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »