-
Notifications
You must be signed in to change notification settings - Fork 3k
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
If nvidia drivers are installed, Alacritty wakes up the dGPU despite not using it #6366
Comments
Can you try 0.11.0, just to be sure it's still broken with the latest version? |
I am having the same problem with the same symptoms, on version 0.11.0. It takes about 1.3s to start when the nvidia card is sleeping. It's even slow to startup for me when the dGPU is disabled in bios but I still have the nvidia driver installed. If I remove the nvidia drivers the startup time is ~130ms as expected. These are the options i use in NixOS: services.xserver.videoDrivers = [ "nvidia" ];
hardware.nvidia = {
modesetting.enable = true;
powerManagement = {
enable = true;
finegrained = true;
};
prime = {
offload.enable = true;
nvidiaBusId = "PCI:1:00:0";
amdgpuBusId = "PCI:4:00:0";
};
}; |
I'd suggest to try latest master. Also the issue is not related to alacritty, but Would suggest to try disabling nvidia config in libglvnd, but not sure how to do that on nixos... |
same issue met here, alacritty would try loading nvidia modules on launch though the nvidia card is already using vfio-pci driver it slows down the launching |
It seems that the libnvidia-glsi.so in nvidia-utils causes the problem. |
To address slow lunch time issue a possible workaround could be to rename the file /usr/bin/nvidia-modprobe. |
You might try latest master, it might do something better. But if you want to solve it, the solution is to address it on On systems with only mesa or only nvidia that won't be an issue(or if you keep only mesa/nvidia in libglvnd). |
Yes, renaming the bin is just a temporary and dirty workaround... I have just found another solution, just set env variable
or
to choose a vendor. The environment variable is used in libglvnd |
Any updates? The temporary solution would be to uninstall the dGPU drivers entirely and just use the integrated GPU, it seems. |
Setup The variable was already suggest here. |
NixOS environment.sessionVariables = {
"__EGL_VENDOR_LIBRARY_FILENAMES" = "/run/opengl-driver/share/glvnd/egl_vendor.d/50_mesa.json";
}; |
With setting |
@moreka is it with the |
After updating to |
I use a laptop (ASUS Zephyrus G15 (2021), GA503QM) with AMD integrated graphics (from the Ryzen 5800HS) and an NVIDIA dedicated GPU. Normally I don’t have a driver installed for the NVIDIA GPU.
supergfxctl --get
reportshybrid
, andsupergfxctl --status
will reportsuspended
.But recently I’ve taken to sometimes having the
nvidia-dkms
package installed.Observation: When it is installed, starting Alacritty loads the
nvidia
kernel module, spins up the dGPU if it is suspended (which it almost certainly is), which makes startup take 2–5 seconds instead of a couple of hundred milliseconds, and consumes a bunch of extra power, even though Alacritty doesn’t end up using the dGPU, according tonvtop
and the observation that the dGPU goes back to sleep after ten seconds or something (supergfxctl --status
goes from reportingactive
back to reportingsuspended
, and power consumption drops significantly), after just having shortened my battery life by a minute or so each time. Alacritty also prevents me from unloading the nvidia kernel module. (lsof
tells me it’s keeping /dev/nvidia0 and /dev/nvidiactl open).Expectation: If Alacritty isn’t going to use the dGPU, I expect it to not wake it up or load its kernel module. And given a dual-GPU configuration like mine, I expect it to stick with the iGPU and not touch the dGPU.
System
Arch Linux, Sway (Wayland). Alacritty 0.10.1.
The text was updated successfully, but these errors were encountered: