Bug 2502

Summary: nvidia-settings incompatibility with 173xx drivers
Product: Fedora Reporter: michlinux
Component: nvidia-settingsAssignee: Nicolas Chauvet <kwizart>
Status: RESOLVED FIXED    
Severity: normal CC: leigh123linux
Priority: P5    
Version: 17   
Hardware: All   
OS: GNU/Linux   
namespace:
Attachments: screenshot

Description michlinux 2012-09-29 08:14:19 CEST
Created attachment 971 [details]
screenshot

nvidia-settings

Version: 1.0-20

Seams partly incompatible with 173xx version of the nvidia drivers. I included a screen shot of version 1.0-20 how it displays on an geforce FX card. I tried a few different versions 1.0-18 and below works fine with 173xx drivers. I believe this because of the switch from 295.xx to 30x.xx drivers, shown below. All 30x.xx I compiled and tested fails in same way as 1.0-20. I guess it's time for a nvidia-settings-173xx package.


From Changelog of nvidia-settings

* Sun Jun 17 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-20(broke for 173xx)
- Update to 302.17

* Tue May 22 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-19(untested)
- Update to 302.11

* Tue May 22 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-18(works)
- Update to 295.53
Comment 1 leigh scott 2012-10-06 11:03:48 CEST
(In reply to comment #0)
> Created attachment 971 [details]
> screenshot
> 
> nvidia-settings
> 
> Version: 1.0-20
> 
> Seams partly incompatible with 173xx version of the nvidia drivers. I included
> a screen shot of version 1.0-20 how it displays on an geforce FX card. I tried
> a few different versions 1.0-18 and below works fine with 173xx drivers. I
> believe this because of the switch from 295.xx to 30x.xx drivers, shown below.
> All 30x.xx I compiled and tested fails in same way as 1.0-20. I guess it's time
> for a nvidia-settings-173xx package.

This is one possible solution, the downside is it would need a package review ( is 173xx worth this effort as it's support is likely to lag behind the X server, will Nvidia ever add 1.13 support?) package  .
Another solution which I favour is to include it (and nvidia-xconfig) in the xorg-x11-drv-nvidia-173xx package (we currently detele them in the build process).



> 
> 
> From Changelog of nvidia-settings
> 
> * Sun Jun 17 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-20(broke for
> 173xx)
> - Update to 302.17
> 
> * Tue May 22 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-19(untested)
> - Update to 302.11
> 
> * Tue May 22 2012 leigh scott <leigh123linux@googlemail.com> - 1.0-18(works)
> - Update to 295.53
Comment 2 Nicolas Chauvet 2012-10-06 11:23:53 CEST
We already experienced such kind of issue, this could be solved by fixing the source code to behave appropriately for each release. I don't know if it's doable in this case at the first sight.
Comment 3 Nicolas Chauvet 2012-10-06 11:27:24 CEST
Well, the main diff is the support for xrandr among other purposes.
So maybe it would worth to make a nvidia-(tools)legacy. (thoses would work for 173xx/96xx).
Comment 4 Nicolas Chauvet 2013-07-14 10:04:42 CEST
I've changed my mind and I will reintroduce the tools into the driver instead.
Changes going on for all drivers.
Comment 5 Nicolas Chauvet 2013-07-26 08:01:29 CEST
This is been fixed in the F-17 case and later.
The driver now bundle again the tools so the version matches.