1 |
On Monday 13 October 2008 04:02:19 Iain Buchanan wrote: |
2 |
|
3 |
> [snip] |
4 |
> |
5 |
> > I've configured it with TwinView |
6 |
> |
7 |
> as in: |
8 |
> Option "TwinView" "True" |
9 |
|
10 |
Yes. Some output : |
11 |
|
12 |
$ sudo grep -i -e xinerama -e twinview /var/log/Xorg.0.log |
13 |
(**) Option "Xinerama" "1" |
14 |
(**) Xinerama: enabled |
15 |
(**) NVIDIA(0): Option "TwinView" "1" |
16 |
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0" |
17 |
(**) NVIDIA(0): TwinView enabled |
18 |
(II) Initializing built-in extension XINERAMA |
19 |
|
20 |
$ sudo grep -i -e xinerama -e twinview /etc/X11/xorg.conf |
21 |
Option "Xinerama" "1" |
22 |
Option "TwinView" "1" |
23 |
Option "TwinViewXineramaInfoOrder" "DFP-0" |
24 |
|
25 |
|
26 |
> > The viewports are aligned along the top edge |
27 |
> |
28 |
> you mean move the mouse up and it appears on the next screen? Don't you |
29 |
> want them aligned left / right of each other? |
30 |
|
31 |
My description wasn't clear. I mean the screens are physically and logically |
32 |
laid out like so: |
33 |
|
34 |
+------------------------------+ |
35 |
| | | |
36 |
| 1 | 2 | |
37 |
| |-----------+ |
38 |
+------------------+ |
39 |
|
40 |
1 is the notebook screen |
41 |
2 is the external lcd |
42 |
below 2 is dead space. The mouse works correctly. |
43 |
|
44 |
> > and the |
45 |
> > panel/kicker/plasma/whatever on every desktop environment insists on |
46 |
> > trying to stretch across both monitors, into dead space on the right hand |
47 |
> > one. |
48 |
> |
49 |
> Sounds like you haven't compiled stuff with the xinerama USE flag. I |
50 |
> put it in make.conf, and then did a emerge --newuse. |
51 |
|
52 |
OK, I did that. The packages that got rebuilt are: |
53 |
|
54 |
$ equery hasuse xinerama |
55 |
[ Searching for USE flag xinerama in all categories among: ] |
56 |
* installed packages |
57 |
[I--] [ ~] x11-apps/xdpyinfo-1.0.3 (0) |
58 |
[I--] [ ~] x11-libs/qt-3.3.8b (3) |
59 |
[I--] [ ~] x11-libs/gtk+-2.14.3-r2 (2) |
60 |
[I--] [ ~] x11-libs/qt-gui-4.4.2 (4) |
61 |
[I--] [ ] x11-misc/engage-9999 (0) |
62 |
[I--] [ ~] kde-base/ksplash-4.1.2 (4.1) |
63 |
[I--] [ ~] kde-base/plasma-workspace-4.1.2 (4.1) |
64 |
[I--] [ ~] kde-base/ksplashml-3.5.10 (3.5) |
65 |
[I--] [ ~] kde-base/systemsettings-4.1.2 (4.1) |
66 |
[I--] [ ~] kde-base/kwin-4.1.2 (4.1) |
67 |
[I--] [ ~] kde-base/libplasma-4.1.2 (4.1) |
68 |
[I--] [ ~] kde-misc/knetworkmanager-0.2.2_p20080528 (0) |
69 |
[I--] [ ~] kde-misc/filelight-1.0-r1 (0) |
70 |
[I--] [ ] media-libs/libsdl-1.2.13 (0) |
71 |
[I--] [ ] media-libs/xine-lib-1.1.15-r1 (1) |
72 |
[I--] [ ] net-libs/xulrunner-1.8.1.17 (1.8) |
73 |
[I--] [ ~] media-sound/kid3-1.0 (0) |
74 |
[I--] [ ~] media-sound/amarok-1.4.10-r1 (0) |
75 |
[I--] [ ~] media-video/mplayer-1.0_rc2_p27725-r1 (0) |
76 |
[I--] [ ] media-video/xine-ui-0.99.5-r1 (0) |
77 |
[I--] [ ~] media-video/gxine-0.5.903 (0) |
78 |
[I--] [ ~] app-cdr/k3b-1.0.5-r3 (0) |
79 |
|
80 |
|
81 |
Seems like the only things that would affect kde-3 apps is qt-3.3.8b. |
82 |
Plus x11-libs/libXinerama and x11-proto/xineramaproto (both latest unstable) |
83 |
are installed. |
84 |
|
85 |
[snip] |
86 |
|
87 |
> > I'd appreciate some pros and cons feedback from the list before I embark |
88 |
> > on a huge emerge -e world to include Xinerama support. |
89 |
> |
90 |
> Why would you do -e world? How about `emerge -uN world` The N being |
91 |
> --newuse. or `emerge -vauDN world`. |
92 |
|
93 |
I was running |
94 |
/bin/think --exaggerate --frustrated --logic-level -3 |
95 |
when I typed that :-) |
96 |
|
97 |
> check out my blog for how I did it: |
98 |
> |
99 |
> http://nthrbldyblg.blogspot.com/2008/08/nvidia-xinerama-on-dell-m6300.html |
100 |
|
101 |
Nice blog :-) |
102 |
|
103 |
I'll fiddle some more with these tips later in the day, but first a conceptual |
104 |
question: I read that huge collection of docs from nvidia-drivers, and |
105 |
concluded that Xinerama and TwinView are fundamentally different and |
106 |
incompatible. i.e. Xinerama starts with two classic X screens and joins them |
107 |
in software to make one big display - an abstraction layer if you will. |
108 |
TwinView rips out the guts of X, dispenses with the notion of separate |
109 |
screens for a TwinView display and gives you one giant screen with no API for |
110 |
an app to see how this big screen is composed. So, you either use Xinerama or |
111 |
TwinView, but not both. |
112 |
|
113 |
Obviously, this understanding of mine is flawed. Which bit did I get wrong? |
114 |
|
115 |
-- |
116 |
alan dot mckinnon at gmail dot com |