You are not logged in.
Pages: 1
Alright, I've noticed this comes up everytime I do: pacman -Suy, it conflicts with my nvidia driver that's alreayd instally(or so pacman says). Should I remove nvidia and install nvidia-utils instead?
Offline
Offline
Alright, so it's not really needed for me to install that pacage? Or should I just because it contains the new nvidia drivers?
Offline
It has no new drivers, just the way they are distributed is now a bit different I think. So i don't think you really need to install it. Not that there's a reason not to.
Offline
copied from nvidia site :
Linux Display Driver - IA32
Version: 1.0-8762
Operating System: Linux IA32
Release Date: May 22, 2006
Linux Display Driver - IA32
Version: 1.0-8756
Operating System: Linux IA32
Release Date: April 7, 2006
Linux Display Driver - IA32
Version: 1.0-8178
Operating System: Linux IA32
Release Date: December 22, 2005
Linux Display Driver - IA32
Version: 1.0-8174
Operating System: Linux IA32
Release Date: December 5, 2005
Until yesterday we used either 8174 or 8178 (not certain which it was), so the nvidia packages now have the latest drivers from nvidia.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
copied from nvidia site :
Linux Display Driver - IA32
Version: 1.0-8762
Operating System: Linux IA32
Release Date: May 22, 2006
Linux Display Driver - IA32
Version: 1.0-8756
Operating System: Linux IA32
Release Date: April 7, 2006
Linux Display Driver - IA32
Version: 1.0-8178
Operating System: Linux IA32
Release Date: December 22, 2005
Linux Display Driver - IA32
Version: 1.0-8174
Operating System: Linux IA32
Release Date: December 5, 2005Until yesterday we used either 8174 or 8178 (not certain which it was), so the nvidia packages now have the latest drivers from nvidia.
Thanks for the information Lone_wolf!
Offline
why are packages beeing split (nvidia, nvidia-utils, ndiswrapper, ndiswrapper-utils) i think it goes against the KISS philosophy
To provide kernel-specific compiled modules.
Some times splitting it up is the the most simple (and/or clean) way.
Offline
why are packages beeing split (nvidia, nvidia-utils, ndiswrapper, ndiswrapper-utils) i think it goes against the KISS philosophy
It's more kiss. Many people here choose to run multiple kernels from the repositories, and such, they would also like to have modules for each of those kernels installed from the repos too.
However, if the utils are included in the modules packages, then the two module packages will conflict, and they may not install both.
To the user, it shouldnt matter, you just pacman -S nvidia, and it will bring in nvidia-utils as a dependency, or pacman -S nvidia-beyond and it will bring in nvidia-utils as a dependency. And now you dont have to manually upgrade nvidia to work.
James
Offline
And for people who run their own compiled kernel: The nvidia PKGBUILD has a hardcoded kernel release in the PKGBUILD, so even using abs and makepkg to compile your own will still put the nvidia kernel module in the wrong place.
Easy fix: change the _kernver= line like this:
_kernver=`uname -r`
or use this[/URL] PKGBUILD found [url=http://www.bosselaar.net/arch/nvidia/]here
Offline
Pages: 1