-
Notifications
You must be signed in to change notification settings - Fork 61
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
[QUESTION] #174
Comments
@Xdavius I've been out of the loop but AFAIK the primary GPU selection on Wayland is DE/WM specific |
My experience has been, as @Xdavius mentioned that at least with Fedora Workstation up to 39, because Wayland is implemented via the Xwayland adapter - envycontrol seems to work fine.
But I did do a project using Pytorch that needs CUDA support and also was using Once X11 is completely dropped in version 41 I believe things will change. Even getting the nvidia driver installed in version 40 has been dicey for me. So the situation will need to be monitored closely once version 41 is released. But realistically, I have stopped using envycontrol at this point in favor of the stock, out-of-the-box hybrid mode which works fine for me. I just gave up on the battery life pursuit. I simply just expect to keep my laptop plugged into power except for brief excursions unplugged - less than 2 hours. |
I have found something but I don't know if it can be useful for envycontrol. You can add theses lines to /etc/environment to force the use of the Nvidia GPU by default
Maybe it needs more investigations to have the switch option on your app. Maybe it's not useful for you but, I share the info in case :) |
Hi,
Now that 555 drivers are released and Wayland is working, is there a possibility to use envycontrol with Wayland ? (Is it works on Wayland as it works on X11)
Thanks for spending time to answer.
Regards.
The text was updated successfully, but these errors were encountered: