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