Anyways, being new to EOS, I’m wondering what suggestions everyone has. Is it worth it to just downgrade Python? If so, is there a way to block updates for now up until this is resolved?
Or is there another way to overclock and undervolt my GPU along with fan control?
This is urgent for me, so I may need to go back to Windows for the meantime if there’s no good resolution.
Well hello again! As you can see from the issue trackers, it’s been an ongoing issue for 2 months now. I doubt there’ll be a fix by tomorrow. Perhaps a fix by the end of this week or more realistically by the end of this month, but nothing is ever certain when it comes to issues like this. And since the flatpak doesn’t seem to work as well now, I’d say you don’t have many options. gwe is not a deal-breaker for me, I don’t overclock myself, so I can’t offer the best advice other than to wait and see. Downgrading could be an option, but I don’t think many users would recommend partial upgrades since that could lead to a whole other set of issues. Hopefully some other users have more solid advice to offer, but I don’t think I offered much good news for you, sorry about that!
Hey again @Scotty_Trees - no worries, I don’t expect an immediate fix, and actually what I asked for was a workaround solution which I’m still hoping for I would rather not need to go back to Windows since I’m pretty used to things on Linux/EOS at the moment.
@ajgringo619 Thanks for the suggestion. I did revert to a couple of lower Flatpak versions with the help of your instructions, but it came up with the same error in Flatpak as before about the NVLM Shared Library not being found. But, I may not have the knowledge needed to understand which version I should be reverting to
Typically, clock and voltage offsets inserted in the nvidia-settings interface are not saved, being lost after a reboot. Fortunately, there are tools that offer an interface for overclocking under the proprietary driver, able to save the user’s overclocking preferences and automatically applying them on boot. Some of them are:
gweAUR - graphical, applies settings on desktop session start
PutridPete [1] added the following comment to gwe [2]:
Seems like the update has been pushed into flathub already, so now if
you run flatpak update it should pull the latest version
and restore functionality to GWE. I can confirm the flatpak version is
working again for me.
Anyways, all in all, this was a learning experience. nvidia-settings can handle almost everything except the proper fan control settings, since it can only set the fans at a static speed. Which is nice if everything runs okay, but it’s not ideal in case my computer starts to overheat for some reason.
GWE also shows that there’s a safety kill-switch, that if my GPU reaches 98c, that it will shut it down.
I don’t know if this automatically happens without GWE or not, but it’s nice having that peace of mind.
Hmm, I tried running yay to update python-injector, it’s not seeing an update, it wants to reinstall the same version. I’m still getting the same launch problems with gwe as before.
I would rather not need to go back to Windows since I’m pretty used to things on Linux/EOS at the moment.
