Issue? Report it in a bugged component repository: https://pagure.io/group/system76/
This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/szydell/system76/
This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/szydell/system76/
To this day, system76-power is the only package that even comes close to getting me the same or better battery life that I get in WIndows (Gigabyte Aero 15x). TLP, powertop, and tuned have not helped at all, and the Arch wiki’s section on fully powering down the NVIDIA GPU and disabling turbo boost doesn’t help. Big bless
Hello,
I have just purchased a new Oryx Pro, and installed Fedora 33 on it. Finding this page has been great!
After following your instructions (added COPR repo, installed system76-* packages, adding the negativo repo and installing the nvidia packages), I have nvidia driver 460.56 installed.
I can successfully run system76-power graphics nvidia and after a reboot, it shows I am using the nvidia driver.
However, nvidia-settings does not work. It says that it is unable to find display on any available system
$DISPLAY shows :1
If I boot up with an external HDMI monitor plugged in, I get display on the external monitor, but I cannot get the laptop lcd to work
Any suggestions?
Thank you for this. I have system76-power working nicely on Fedora 33 Silverblue on a t440p with dGPU and it’s making all the difference. For Silverblue you need to download the copr repo and copy it into your /etc/yum.repos.d/ folder and then install it via rpm-ostree. I had initially been lazy and tried to install all the packages but it had trouble with dkms and one other, so I just went with system76-power, which is all I needed.
I also managed to get the gnome-extension-system76-power installed and working perfectly. You need to clone the repo and the make file can do it all from there inc using gnome-extensions to enable the extension (make, make install, make enable). On Silverblue I did the basic Make in toolbox (after installing Typescript via npm there), but switched out of the container to run make install and make enable. You do need to install one package to make the extension work (dbus-x11). But once that works you have a lovely extension in the power area to switch between Integrated Graphics only, Dedicated Graphics Only, Hybrid and their special “compute graphics”.
1 Like
Thank you for your efforts!
Works perfectly on a System76 Gazelle with Nvidia GTX 1660 Ti. It lets me switch the graphics (although I mostly stick with hybrid and use Prime Render Offloading when I need it), restores usage of all of the function keys (touchpad disable, brightness, airplane mode, etc.), and, best of all, enables the ability to change the keyboard and lid backlights!
In case this helps anyone I have a thelio mira so I am not sure about other systems that they have.
The Fedora 35 to 36 upgrade has some issues with both system76-power and system76-driver. You need to remove both packages before attempting the upgrade or it will fail.
edit I had a second system to upgrade and the kernel reinstall was not needed. What worked was:
531 sudo dnf remove system76-dkms system76-io-dkms system76-power system76-driver
532 sudo dnf install system76-dkms system76-io-dkms system76-power system76-driver
533 sudo systemctl enable --now system76-power.service
534 sudo reboot
1 Like
Thank you for sharing your resolution steps. This just helped me fix the issue.
Hi, the latest 1.1.22-4 system76-power package fails to produce a system76-power.service systemd file.
Fedora 36
$ sudo systemctl enable --now system76-power.service
Failed to enable unit: Unit file system76-power.service does not exist.
I was able to fix the issue in Fedora 36.
Create the systemd service file.
sudo nano /etc/systemd/system/system76-power.service
Paste this into the new file.
[Unit]
Description=System76 Power Daemon
[Service]
ExecStart=/usr/bin/system76-power daemon
Restart=on-failure
Type=dbus
BusName=com.system76.PowerDaemon
[Install]
WantedBy=multi-user.target
Alias=system76-power.service
Then disable Fedora’s power service that conflicts with System76’s.
sudo systemctl mask power-profiles-daemon
Run a systemd reload.
sudo systemctl daemon-reload
Lastly, reboot for good measure.
Fedora 37: requires the power-profiles-daemon to be masked. Everything else ran smoothly.
sudo systemctl mask power-profiles-daemon
sudo systemctl daemon-reload
Did anyone of you manage to run the firmware-manager to be able to update the BIOS in silverblue? I only managed to run the Power.Daemon but I still need to mask it.
These commands work for Fedora 38 as well. Two thumbs up!
Hi. I bought a System76 workstation and installed Fedora Silverblue 38. I tried to follow the instructions provided in this forum and was able to install the Power packages via rpm-ostree, but now I am stuck. System76’s support doesn’t include Silverblue. My only issue is the constant noise of the fans. Any suggestion will be appreciated.
Hey Francisco, I’m not familiar with ostree, but running these commands in Fedora Workstation (then a reboot) consistently clears up the fan noise on my Thelio.
Hi Tom. Yes, I applied those commands but didn’t work. In Silverblue, I have the following packages layered: firmware-manager, nodejs-typescript, system76-firmware & system76-power. System76 Driver and Firmware Manager windows are available but not operational. I’m attaching screenshots.
Hey Francisco, I really can’t speak for Silverblue in this issue. I know for sure my notes above work on Fedora 36-38 Workstation.
It’s OK Tom. Your suggestions were the closest thing I got for a solution for Silverblue, so I got to try them. I know a fix will appear sooner or later.
1 Like
Thank you very much for this - It’s been working brilliantly for me under Fedora 38 on both a lemur pro and a thelio mira.
I did have to re-enable system76-power after a recent dnf update. I had to enable the service name “com.system76.PowerDaemon.service” (as given in the installation instructions). The service name “system76-power.service” mentioned in some of the other (otherwise very helpful) comments did not work.
Hey, just checking in. With Fedora 39 dropping next week, there are still some issues showing up when trying to upgrade. Any ETA on a fix? Not sure if they renamed/deprecated python3.11, but that looks like the core issue? I haven’t tried uninstalling/upgrading/reinstalling yet. Might work. But the existing dnf upgrade to 39 reports this error.
Problem 1: problem with installed package system76-driver-20.04.79-1.x86_64
- package system76-driver-20.04.79-1.x86_64 from copr:copr.fedorainfracloud.org:szydell:system76 requires python(abi) = 3.11, but none of the providers can be installed
- system76-driver-20.04.79-1.x86_64 from @System does not belong to a distupgrade repository
- python3-3.11.6-1.fc38.x86_64 from @System does not belong to a distupgrade repository
Problem 2: package system76-firmware-1.0.52-1.x86_64 from copr:copr.fedorainfracloud.org:szydell:system76 requires system76-driver, but none of the providers can be installed
- package system76-driver-20.04.79-1.x86_64 from @System requires python(abi) = 3.11, but none of the providers can be installed
- package system76-driver-20.04.79-1.x86_64 from copr:copr.fedorainfracloud.org:szydell:system76 requires python(abi) = 3.11, but none of the providers can be installed
- problem with installed package system76-firmware-1.0.52-1.x86_64
- package python3-3.11.6-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.6-1.fc38, but none of the providers can be installed
- system76-firmware-1.0.52-1.x86_64 from @System does not belong to a distupgrade repository
- python3-libs-3.11.6-1.fc38.x86_64 from @System does not belong to a distupgrade repository
1 Like