Bug 117212

Created attachment 50020 [details]
hwinfo --monitor

Hmm I need a bit more information. If you don't mind do the following:  
  
- switch to runlevel 3 and login as root  
- run   
  
    sax2 -r  
  
- click on "change configuration" and do exactly the same as you did  
  in your report. After this "test" your configuration and adapt the screen  
  as you did before.  
  
- save this configuration and exit sax  
  
- send me the log file  
  
    /var/log/SaX.log  
  
Thanks for helping 

Created attachment 50186 [details]
sax log

Let me know if you need anything else.

Hmm I cannot see a problem and I cannot reproduce this. The program doing 
the adjustment can be called like this: 
 
  /usr/sbin/xfine 
 
you must be root to do this. Once the application appears please adjust as 
you did before and click on "Save". xfine will store the information in 
 
  /var/cache/xfine/ 
 
would be fine if you could send the file located there. 
 
Thanks 

Created attachment 50320 [details]
xfine file

I have attached the file, and after a reboot, the same problem happened (ie, the
changes were not saved)

Ok, now I know what is going on. The configuration file provides a valid 
modeline accepted by the NV driver: 
 
  (**) NV(0): *Mode "1280x1024": 108.9 MHz, 63.6 kHz, 60.0 Hz 
  (II) NV(0): Modeline "1280x1024"  108.88  1280 1360 1496 1712  1024 1025 
1028 1060 
 
The X-Server starts and SaX runs the xfine program which asks the X-Server 
for the current active timing values which have to be the same as the 
log told us but the timings are different: 
 
   1280 1328 1440 1688 1024 1025 1028 1066 
 
As you can see the NV driver internally is using other timings which are not 
part of the configuration or the log file. xfine is searching for this 
"wrong" reference modeline to exchange it with the new mode you created while 
using xfine, but this is impossible because the reference modeline doesn't 
exist in the xorg.conf file. The result: no changes can be saved 
 
 
 

Hmm ... I thought these timings were changed by xfine? So why should these 
still be the same as the one in the logfile when the Xserver starts? 

xfine is first asking the X-server for the current mode timings. These 
information is used as reference and if these timings aren't the same as 
in the config file xfine has no change to save the new mode 
 
Well we tested with a NVidia Quadro FX 3000 and it works for us like 
it should so I'm sorry but we cannot reproduce that problem here 

(In reply to comment #10)

> Well we tested with a NVidia Quadro FX 3000 and it works for us like 
> it should so I'm sorry but we cannot reproduce that problem here 

Is there any more information I can gather on my side to help troubleshoot this
issue?

Raymund, in case you can get the Quadro2 MXR from Heiko, we would like to 
have it for a small test (see above). 

Finally I could try to verify this problem on a Quadro2 MXR/MX/Go (10de:0113,
10de:0070), but I can't reproduce. I tried exactly the same modeline as
mentioned above.

  (Modeline "1280x1024"  108.88  1280 1360 1496 1712  1024 1025 1028 1060)

reconfigured this resolution with SaX2 (xfine) and configuration has been saved
by SaX2 and works. Need to close this one as WORKSFORME.

As I stated before. I am more than willing to get more troubleshooting
information. I can reproduce this here, so please let me know what you need next
and I will provide it.

I don't think that any more information I would request in this case will help.
It's unlikely that we're able to fix this issue for you. :-(

Trying to close this as WONTFIX.

(In reply to comment #15)
> I don't think that any more information I would request in this case will help.
> It's unlikely that we're able to fix this issue for you. :-(

What if I setup the exact same machine in a lab here in Provo and gave you full
access to it. Would that help? Seems if you can't duplicate it and I can provide
a workstation to you for the duplication that we could move forward on this.