1 |
Hi, |
2 |
|
3 |
My notebook has this graphics hardware. |
4 |
|
5 |
alan@nazgul ~ $ sudo lspci | grep VGA |
6 |
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev |
7 |
a1) |
8 |
alan@nazgul ~ $ sudo xdpyinfo | grep -A4 'screen #0' |
9 |
screen #0: |
10 |
print screen: no |
11 |
dimensions: 1920x1200 pixels (332x210 millimeters) |
12 |
resolution: 147x145 dots per inch |
13 |
depths (7): 24, 1, 4, 8, 15, 16, 32 |
14 |
|
15 |
I also have a second LCD monitor at work, a 1280x1024 that is physically |
16 |
slightly larger than the notebook screen, with a corresponding lower dpi. |
17 |
|
18 |
I've configured it with TwinView to have the second monitor on the right, and |
19 |
how I usually use it is to put a user's support mail on that where I can read |
20 |
it and fix their issues using the tools on the main monitor. So it's a very |
21 |
unsophisticated setup, I have no need for massive 3D accel for eg games, or |
22 |
even for placing windows across two monitors. Windows are always on one |
23 |
screen or the other (because of the huge dpi difference). There are two |
24 |
smallish issues: |
25 |
|
26 |
The viewports are aligned along the top edge and the |
27 |
panel/kicker/plasma/whatever on every desktop environment insists on trying |
28 |
to stretch across both monitors, into dead space on the right hand one. I'm |
29 |
getting use to right-click on panel, configure, set width to 57% at work, |
30 |
100% at home. If I align the viewports on the bottom edges, windows managers |
31 |
tend to want to position new windows with their title bars in the dead space |
32 |
at the top. |
33 |
|
34 |
kdm and entrance want to stretch over both monitors. I definitely do not want |
35 |
this. Murphy dictates that all useful DM menus will end up in the dead space |
36 |
regardless of the theme I use <grrrr> |
37 |
|
38 |
My research into nvidia's docs leads me to believe that TwinView is designed |
39 |
to make the presence of two physical monitors invisible and present one giant |
40 |
X screen, with a funky API for dead spaces (which may or may not work). I'm |
41 |
thinking Xinerama is the better option, despite the fact that it's old, |
42 |
clunky, hopeless at dealing with XRandR and can't be changed on the fly. I'm |
43 |
happy to set up two ServerLayouts to deal with this. |
44 |
|
45 |
I'd appreciate some pros and cons feedback from the list before I embark on a |
46 |
huge emerge -e world to include Xinerama support. |
47 |
|
48 |
-- |
49 |
alan dot mckinnon at gmail dot com |