Latest nvidia-open-dkms or something making my computer act really laggy and slow #ArchLinux 6.11.1 #Nvidia 560.35.3-9
=> More informations about this toot | More toots from meatlotion@mas.erb.pw
Temporarily mostly fixed it by doing this;
sudo downgrade hyprcursor=0.1.9-1 linux=6.10.10.arch1-1 linux-headers=6.10.10.arch1-1 nvidia-open-dkms=560.35.03-6 opencl-nvidia=560.35.03-3 qt6-base=6.7.3-1
Argh this is the first #ArchLinux fail I've had to suffer... not bad I suppose, but man I didn't wanna be troubleshooting this today lol.
=> More informations about this toot | More toots from meatlotion@mas.erb.pw
I did notice before I started downgrading, when I ran nvidia-smi there were only two processes running; /usr/lib/Xorg and hyprland, after "fixing" the system, kitty and Xwayland now show up again in nvidia-smi.
I did try downgrading each item individually to see which caused the issue, but that didn't help, so I re-upgraded and then downgraded everything that was upgraded when it broke to the previous versions (listed in previous post) which fixed it.
Anyone who is clued up know what might have happened and what a better way to fix it would be?
[#]ArchLinux #hyprland #nvidia #Xwayland #Xorg
=> More informations about this toot | More toots from meatlotion@mas.erb.pw
So I just stumbled upon a reddit post that may have given me the answer, but I wanna get opinions from people who actually know what they're doing...
Apparently, enable the framebuffer driver by creating /etc/modprobe.d/nvidia.conf and inside add;
option nvidia-drm fbdev=1
Then run "mkinitcpio -P" and reboot, then upgrade.
Does this sound like it will do the job? Anyone know about this already?
[#]ArchLinux #Arch #hyprland #linux
=> More informations about this toot | More toots from meatlotion@mas.erb.pw This content has been proxied by September (ba2dc).Proxy Information
text/gemini