On Fri, 2010-01-22 at 13:11 +0100, YoYo siska wrote:
> maybe it is even enough to run the --probe-dpys according to what you
> say about selecting
> "detect displays" in the gui...
Thanks! This is the closest I've got so far, but it still isn't quite
right.
I can run `./nv-control-dpy --probe-dpys` and see the two devices:
Using NV-CONTROL extension 1.20 on :0.0
Connected Display Devices:
DFP-0 (0x00010000): Seiko
DFP-2 (0x00040000): DELL 2408WFP
but running set-associated-displays to 0x50000 just returns:
Using NV-CONTROL extension 1.20 on :0.0
Connected Display Devices:
DFP-0 (0x00010000): Seiko
DFP-2 (0x00040000): DELL 2408WFP
set the associated display device mask to 0x00050000
and "nothing" happens. I can use any combination of 0x10000 and 0x40000
but it doesn't actually do anything to my displays.
The only way I got nv-control-dpy to do anything was to use
--dynamic-twinview and then xrandr to try and change to the new mode,
however it didn't quite work, leaving one screen black (except for the
cursor). In the end I still had to run nvidia-settings to fix it...
I'm getting closer! Maybe I should just look at the nvidia-settings
source...
Does anyone know if the nvnews forums are good with this kind of thing?
thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>
I always wake up at the crack of ice.
-- Joe E. Lewis
