Re: [gentoo-user] nvidia driver 177.80 + xorg 1.5.1 + Compiz
Nicola wrote: > Hi! > Somebody out there try to set up the latest xorg server (and all the ~x86 > dependency) the latest nvidia driver and compiz? > I would like to try, but my latest attempt three weeks ago caused same crazy > problems (X didn't start at all), and I am not so crazy to do the same > mistake twice in a row, without some prior advices. Well in my latest attempt > I used xorg 1.4.2 and 173.14 nvidia drivers (I don't like Marked beta > software). I may have had the same problem a week ago. X would start, kdm would let me log in, but just about when the kde desktop would finish loading kde would quit back to kdm. Couldn't find any hint in /var/log. Started backing out various things ended up getting the system working again by masking hal 0.5.11: # cat /etc/portage/package.mask/monolithic =sys-fs/encfs-1.4.2 ~sys-apps/hal-0.5.11 =media-video/mplayer-1.0_rc2_p27725 At the time I was suspecting that hal 0.5.11 was requiring evdev (which with 20+ hours of unsuccessfully trying to get it to work over the last year, I wouldn't be surprised if it's the culprit). Haven't had time to dig further. HTH, Roy
RE: [gentoo-user] Re: Wine + USB to serial adapter
Also; absydos adam # setserial /dev/ttyUSB0 Cannot get serial info: Invalid argument And absydos adam # stty -F /dev/ttyUSB0 speed 9600 baud; line = 0; -brkint -imaxbel absydos adam #
Re: [gentoo-user] Kernel crash - howto find out what happened?
On Sun, Oct 12, 2008 at 07:08, Alexander Puchmayr <[EMAIL PROTECTED]> wrote: > Hi there! > > MY gentoo system (an [EMAIL PROTECTED], 2GB ram, nforce4-chipset) worked fine > for > nearly two years, but now it frequently freezes, sometimes (not always) > scrollock and capslock LED blinking). > > Since I'm using the box as desktop, I have only a frozen X-server and no > possibility to switch to console (maybe there's some hint whats happened?). > > How do I find out what happened, why it crashed? Modern systems have > MCE-logs, but how do I read it in this case? After reboot, all information > seems to be gone since mcelog is always empty. > > I assume there's some problem with some hardware, I already tested RAM with > memtest86, but no errors. > I had one of this freezes today. Simply killed X using CTRL+SYSREQ+K and got back a console with error messages. Have you tried the SYSREQ keys? -- Daniel da Veiga
[gentoo-user] Re: Wine + USB to serial adapter
Adam Carter optus.com.au> writes: > It works fine with minicom. Its just not responding in wine or vwmare > (when mapped to a windows com port). OK, good. Sorry, I never tried to use with wine or vmware James
RE: [gentoo-user] Re: Wine + USB to serial adapter
> FTDI work very well under windows or linux. Once you add the > appropriate driver (via the linux kernel) you can boot > either winblows or linux and use the 9pin-serial-to-usb > as you like with either OS. The device is setup and works (hence the existance of the /dev/ttyUSB0 device). If the driver wasn't setup that device wouldn't be created. It works fine with minicom. Its just not responding in wine or vwmare (when mapped to a windows com port).
[gentoo-user] Easily coping with a domain password
Hi, Some weeks go well, some don't. For me, this one isn't. The AD at work was moaning that I needed to change the password, which I duly did under protest. Then all hell broke loose. 30 seconds later the account was locked. That turned out to be kontact checking Exchange once a minute when I thought I had unset auto checks. Phoned IT, got the account unlocked. And it happened again, this time kwallet had cached something. Fixed by manually going through everything in kwallet, changing all old passwords I found. And I got locked out a third time, which appears to be due to ldap lookups (more than one). $DEITY only knows where these are coming from, I've been doing some experimenting lately IT are getting a wee bit upset with me, and this happens regularly once a month but today was especially bad. Methinks I should consolidate all the many apps and URLs that auth against the domain. And I'm wondering how best to do this as I'm clueless about it actually - I normally avoid MS stuff like the plague. Should I be looking into winbind? Or configure kerberos to join the domain and have all my apps use that? Some ldap-proxy type setup? Pointers to howtos and opinions on what's worth the effort are all that I'm after today - I can read the details in the man pages myself once I have a known direction to follow. If my three ideas above sound stupid, that's because they probably are :-) -- alan dot mckinnon at gmail dot com
[gentoo-user] Re: {OT} Webcam packages (motion segfaults)
Grant gmail.com> writes: > > Have you customized the /etc/motion.conf file? > > No luck so far but I'm working on it. I'm not sure about the latest version of motion, but here's a note I save from version 3.2.7 (that may provide some examples): * You need to setup /etc/motion.conf before running * motion for the first time. * Examples are available at /usr/share/doc/motion-3.2.7/examples James
[gentoo-user] nvidia driver 177.80 + xorg 1.5.1 + Compiz
Hi! Somebody out there try to set up the latest xorg server (and all the ~x86 dependency) the latest nvidia driver and compiz? I would like to try, but my latest attempt three weeks ago caused same crazy problems (X didn't start at all), and I am not so crazy to do the same mistake twice in a row, without some prior advices. Well in my latest attempt I used xorg 1.4.2 and 173.14 nvidia drivers (I don't like Marked beta software). Thanks Nicola
Re: [gentoo-user] Re: {OT} Webcam packages (motion segfaults)
>> motion looks about right, but segfaults for me like this: > > Have you customized the /etc/motion.conf file? I get the same error whether I customize the file or use the default one. > Googling should produce some wikis or example files to follow. No luck so far but I'm working on it. - Grant
[gentoo-user] Re: Wine + USB to serial adapter
Adam Carter optus.com.au> writes: > Is /dev/ttyUSB0 as > functional as a regular /etc/ttyS0? I have a USB to serial adapter > that uses the pl2303 driver, and have It's listed in the kernel sources so it should work.. make menuconfig -->device drivers -->usb -->USB Serial Converter Support --> Prolific 2303 Single Port Serial Driver > - will other USB to > serial adapter with better linux drivers work? > - or will i have to > try a PCCard serial adapter? FTDI work very well under windows or linux. Once you add the appropriate driver (via the linux kernel) you can boot either winblows or linux and use the 9pin-serial-to-usb as you like with either OS. These sorts of products are build upon various chipsets from different vendors, but, there are standards so as long as a linux driver exists for the chipset that is used in your product, it should work reliably and consistently, under linux or winblows. hth, James
[gentoo-user] Re: {OT} Webcam packages (motion segfaults)
Grant gmail.com> writes: > motion looks about right, but segfaults for me like this: Have you customized the /etc/motion.conf file? Googling should produce some wikis or example files to follow. James
[gentoo-user] Re: Xinerama vs TwinView for dual monitor setup
On 2008-10-13, Grant Edwards <[EMAIL PROTECTED]> wrote: >>>* Displays can have different resolutions, sizes, depths. >> >> So can xinerama / twinview :) > > I thought I had read somewhere that they had to have the same > depth at least. Based on what little I do know about Xlib I'm also pretty surprised that a window can span two displays that have different resolutions (DPI). -- Grant Edwards grante Yow! ... he dominates the at DECADENT SUBWAY SCENE. visi.com
Re: [gentoo-user] Kernel crash - howto find out what happened?
2008/10/12 Alexander Puchmayr <[EMAIL PROTECTED]>: > MY gentoo system (an [EMAIL PROTECTED], 2GB ram, nforce4-chipset) > worked fine for nearly two years, but now it frequently freezes, sometimes > (not always) scrollock and capslock LED blinking). If you have another machine lying around, try setting up netconsole and/or serial console logging. They should catch any dying messages from your kernel. Blinking LEDs indicates a panic, which means you should get a message in those cases, at least. Using serial console is the easiest and most reliable way, but requires a serial cable. Netconsole just uses ethernet but isn't as reliable. Take a look at Documentation/serial-console.txt and Documentation/networking/netconsole.txt under your kernel source directory for more info. Cheers, Duane. -- "I never could learn to drink that blood and call it wine" - Bob Dylan
[gentoo-user] Re: Xinerama vs TwinView for dual monitor setup
On 2008-10-13, Iain Buchanan <[EMAIL PROTECTED]> wrote: > Grant Edwards wrote: > [snip] >> >> There's a third option you haven't mentioned: two different >> displays rather than a large virtual display spread across two >> monitors. > > [snip] > >> Pros: >> >>* Mouse movement and focus still act like one large display. >> >>* Each display can have it's own set of virtual desktops and >> they can be switched indpendantly. > > Really? When I set up separate X screens, changing virtual desktops on > one display (eg from "VD1" to "VD2") also changed it on the other display. It probably depends on your window manager. I'm using XFCE, and switching "workspaces" as they're called in XFCE is independant for the two displays. >>* Things like window-manager panels/docs/taskbars are managed >> separately for the two displays. >> >>* Displays can have different resolutions, sizes, depths. > > So can xinerama / twinview :) I thought I had read somewhere that they had to have the same depth at least. -- Grant Edwards grante Yow! I'm having fun at HITCHHIKING to CINCINNATI visi.comor FAR ROCKAWAY!!
Re: [gentoo-user] Xinerama vs TwinView for dual monitor setup
On Monday 13 October 2008 13:53:49 YoYo siska wrote: > tabletka ~ # equery hasuse xinerama | wc -l > 285 > > most of them are apps from kde-base/* (3.5.9), seems that it changed > between 3.5.9 and 3.5.10, plus iwndow managers like fluxbox, openbox... That looks better. I was convinced that most kde-3 apps had a xinerama USE flag, hence my 'emerge -e world' comment that Iain picked up on. I wonder why it was changed for KDE-3.5.10, it seems that Xinerama support is now automatically built for most of KDE-3 (deduced by examining the ebuild and ldd output) > > Obviously, this understanding of mine is flawed. Which bit did I get > > wrong? > > Xinerama consists basically of two parts, the protocol to communicate the > position/sizes of screen between the Xserver and the applications (which > you usually get by enabling the xinerama use flag) and an xserver part > (module?) that you can use to set up the screens. What you said is > correct for the Xserver setup part... > You use either xinerama setup to put together completely different > displays (might be different cards, such as one nvidia, one ati, ...) > or twinview in case of a dualhead nvidia setup. But both this setups use > the xinerama protocol to let the apps/wm know the placement of the > monitors. OK, so there's a xinerama protocol and a xinerama lib and these are not the same thing -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Xinerama vs TwinView for dual monitor setup
On Mon, Oct 13, 2008 at 09:10:34AM +0200, Alan McKinnon wrote: > On Monday 13 October 2008 04:02:19 Iain Buchanan wrote: > > > [snip] > > > > > I've configured it with TwinView > > > > as in: > > Option "TwinView" "True" > > Yes. Some output : > > $ sudo grep -i -e xinerama -e twinview /var/log/Xorg.0.log > (**) Option "Xinerama" "1" > (**) Xinerama: enabled > (**) NVIDIA(0): Option "TwinView" "1" > (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0" > (**) NVIDIA(0): TwinView enabled > (II) Initializing built-in extension XINERAMA > > $ sudo grep -i -e xinerama -e twinview /etc/X11/xorg.conf > Option "Xinerama" "1" > Option "TwinView" "1" > Option "TwinViewXineramaInfoOrder" "DFP-0" > > > > > The viewports are aligned along the top edge > > > > you mean move the mouse up and it appears on the next screen? Don't you > > want them aligned left / right of each other? > > My description wasn't clear. I mean the screens are physically and logically > laid out like so: > > +--+ > | | | > |1 | 2 | > | |---+ > +--+ > > 1 is the notebook screen > 2 is the external lcd > below 2 is dead space. The mouse works correctly. > > > > and the > > > panel/kicker/plasma/whatever on every desktop environment insists on > > > trying to stretch across both monitors, into dead space on the right hand > > > one. > > > > Sounds like you haven't compiled stuff with the xinerama USE flag. I > > put it in make.conf, and then did a emerge --newuse. > > OK, I did that. The packages that got rebuilt are: > > $ equery hasuse xinerama > [ Searching for USE flag xinerama in all categories among: ] > * installed packages > [I--] [ ~] x11-apps/xdpyinfo-1.0.3 (0) > [I--] [ ~] x11-libs/qt-3.3.8b (3) > [I--] [ ~] x11-libs/gtk+-2.14.3-r2 (2) > [I--] [ ~] x11-libs/qt-gui-4.4.2 (4) > [I--] [ ] x11-misc/engage- (0) > [I--] [ ~] kde-base/ksplash-4.1.2 (4.1) > [I--] [ ~] kde-base/plasma-workspace-4.1.2 (4.1) > [I--] [ ~] kde-base/ksplashml-3.5.10 (3.5) > [I--] [ ~] kde-base/systemsettings-4.1.2 (4.1) > [I--] [ ~] kde-base/kwin-4.1.2 (4.1) > [I--] [ ~] kde-base/libplasma-4.1.2 (4.1) > [I--] [ ~] kde-misc/knetworkmanager-0.2.2_p20080528 (0) > [I--] [ ~] kde-misc/filelight-1.0-r1 (0) > [I--] [ ] media-libs/libsdl-1.2.13 (0) > [I--] [ ] media-libs/xine-lib-1.1.15-r1 (1) > [I--] [ ] net-libs/xulrunner-1.8.1.17 (1.8) > [I--] [ ~] media-sound/kid3-1.0 (0) > [I--] [ ~] media-sound/amarok-1.4.10-r1 (0) > [I--] [ ~] media-video/mplayer-1.0_rc2_p27725-r1 (0) > [I--] [ ] media-video/xine-ui-0.99.5-r1 (0) > [I--] [ ~] media-video/gxine-0.5.903 (0) > [I--] [ ~] app-cdr/k3b-1.0.5-r3 (0) tabletka ~ # equery hasuse xinerama | wc -l 285 most of them are apps from kde-base/* (3.5.9), seems that it changed between 3.5.9 and 3.5.10, plus iwndow managers like fluxbox, openbox... > > Seems like the only things that would affect kde-3 apps is qt-3.3.8b. > Plus x11-libs/libXinerama and x11-proto/xineramaproto (both latest unstable) > are installed. > > [snip] > > > > I'd appreciate some pros and cons feedback from the list before I embark > > > on a huge emerge -e world to include Xinerama support. > > > > Why would you do -e world? How about `emerge -uN world` The N being > > --newuse. or `emerge -vauDN world`. > > I was running > /bin/think --exaggerate --frustrated --logic-level -3 > when I typed that :-) > > > check out my blog for how I did it: > > > > http://nthrbldyblg.blogspot.com/2008/08/nvidia-xinerama-on-dell-m6300.html > > Nice blog :-) > > I'll fiddle some more with these tips later in the day, but first a > conceptual > question: I read that huge collection of docs from nvidia-drivers, and > concluded that Xinerama and TwinView are fundamentally different and > incompatible. i.e. Xinerama starts with two classic X screens and joins them > in software to make one big display - an abstraction layer if you will. > TwinView rips out the guts of X, dispenses with the notion of separate > screens for a TwinView display and gives you one giant screen with no API for > an app to see how this big screen is composed. So, you either use Xinerama or > TwinView, but not both. > > Obviously, this understanding of mine is flawed. Which bit did I get wrong? Xinerama consists basically of two parts, the protocol to communicate the position/sizes of screen between the Xserver and the applications (which you usually get by enabling the xinerama use flag) and an xserver part (module?) that you can use to set up the screens. What you said is correct for the Xserver setup part... You use either xinerama setup to put together completely different displays (might be different cards, such as one nvidia, one ati, ...) or twinview in case of a dualhead nvidia setup. But both this setups use the xinerama protocol to let the a
Re: [gentoo-user] error emerge hal
sori to open this topic again.
last night, i try to emerge hal-0.5.11-r3 and it pulled glib-2.18.1 as
its depedency. but emerging glib failed. i'm already run revdep
rebuild, but nothing happend. here is the error log:
>>> Unpacking source...
>>> Unpacking glib-2.18.1.tar.bz2 to /var/tmp/portage/dev-libs/glib-2.18.1/work
[32;01m*[0m Applying glib-2.18.1-gdesktopappinfo-memleak-fix.patch ...
[A[130C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Applying
glib-2.18.1-workaround-gio-test-failure-without-userpriv.patch ...
[A[130C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Applying glib-2.12.12-fbsd.patch ...
[A[130C [34;01m[ [32;01mok[34;01m ][0m
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/glib-2.18.1/work/glib-2.18.1
>>> ...
[32;01m*[0m Removing useless C++ checks ...
[A[130C [34;01m[ [32;01mok[34;01m ][0m
* econf: updating glib-2.18.1/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating glib-2.18.1/config.guess with
/usr/share/gnuconfig/config.guess
./configure --prefix=/usr --host=i686-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --disable-xattr
--disable-man --disable-gtk-doc --enable-fam --disable-selinux
--enable-static --with-threads=posix --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... checking for style of include
used by make... GNU
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
no
checking whether to enable garbage collector friendliness... no
checking whether to disable memory pools... no
checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89...
(cached) none needed
checking dependency style of i686-pc-linux-gnu-gcc... (cached) gcc3
checking for c++... c++
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking dependency style of c++... gcc3
checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89...
(cached) none needed
checking dependency style of i686-pc-linux-gnu-gcc... (cached) gcc3
checking whether i686-pc-linux-gnu-gcc and cc understand -c and -o
together... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for pkg-config... /usr/bin/pkg-config
checking for gawk... (cached) gawk
checking for perl5... no
checking for perl... perl
checking for indent... no
checking for perl... /usr/bin/perl
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.4
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.4/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.4/site-packages
checking for iconv_open... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether we are using the GNU C Library 2.1 or newer... yes
checking Whether to cache iconv descriptors... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libint
Re: [gentoo-user] Xinerama vs TwinView for dual monitor setup
On Monday 13 October 2008 04:02:19 Iain Buchanan wrote: > [snip] > > > I've configured it with TwinView > > as in: > Option "TwinView" "True" Yes. Some output : $ sudo grep -i -e xinerama -e twinview /var/log/Xorg.0.log (**) Option "Xinerama" "1" (**) Xinerama: enabled (**) NVIDIA(0): Option "TwinView" "1" (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0" (**) NVIDIA(0): TwinView enabled (II) Initializing built-in extension XINERAMA $ sudo grep -i -e xinerama -e twinview /etc/X11/xorg.conf Option "Xinerama" "1" Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-0" > > The viewports are aligned along the top edge > > you mean move the mouse up and it appears on the next screen? Don't you > want them aligned left / right of each other? My description wasn't clear. I mean the screens are physically and logically laid out like so: +--+ | | | |1 | 2 | | |---+ +--+ 1 is the notebook screen 2 is the external lcd below 2 is dead space. The mouse works correctly. > > and the > > panel/kicker/plasma/whatever on every desktop environment insists on > > trying to stretch across both monitors, into dead space on the right hand > > one. > > Sounds like you haven't compiled stuff with the xinerama USE flag. I > put it in make.conf, and then did a emerge --newuse. OK, I did that. The packages that got rebuilt are: $ equery hasuse xinerama [ Searching for USE flag xinerama in all categories among: ] * installed packages [I--] [ ~] x11-apps/xdpyinfo-1.0.3 (0) [I--] [ ~] x11-libs/qt-3.3.8b (3) [I--] [ ~] x11-libs/gtk+-2.14.3-r2 (2) [I--] [ ~] x11-libs/qt-gui-4.4.2 (4) [I--] [ ] x11-misc/engage- (0) [I--] [ ~] kde-base/ksplash-4.1.2 (4.1) [I--] [ ~] kde-base/plasma-workspace-4.1.2 (4.1) [I--] [ ~] kde-base/ksplashml-3.5.10 (3.5) [I--] [ ~] kde-base/systemsettings-4.1.2 (4.1) [I--] [ ~] kde-base/kwin-4.1.2 (4.1) [I--] [ ~] kde-base/libplasma-4.1.2 (4.1) [I--] [ ~] kde-misc/knetworkmanager-0.2.2_p20080528 (0) [I--] [ ~] kde-misc/filelight-1.0-r1 (0) [I--] [ ] media-libs/libsdl-1.2.13 (0) [I--] [ ] media-libs/xine-lib-1.1.15-r1 (1) [I--] [ ] net-libs/xulrunner-1.8.1.17 (1.8) [I--] [ ~] media-sound/kid3-1.0 (0) [I--] [ ~] media-sound/amarok-1.4.10-r1 (0) [I--] [ ~] media-video/mplayer-1.0_rc2_p27725-r1 (0) [I--] [ ] media-video/xine-ui-0.99.5-r1 (0) [I--] [ ~] media-video/gxine-0.5.903 (0) [I--] [ ~] app-cdr/k3b-1.0.5-r3 (0) Seems like the only things that would affect kde-3 apps is qt-3.3.8b. Plus x11-libs/libXinerama and x11-proto/xineramaproto (both latest unstable) are installed. [snip] > > I'd appreciate some pros and cons feedback from the list before I embark > > on a huge emerge -e world to include Xinerama support. > > Why would you do -e world? How about `emerge -uN world` The N being > --newuse. or `emerge -vauDN world`. I was running /bin/think --exaggerate --frustrated --logic-level -3 when I typed that :-) > check out my blog for how I did it: > > http://nthrbldyblg.blogspot.com/2008/08/nvidia-xinerama-on-dell-m6300.html Nice blog :-) I'll fiddle some more with these tips later in the day, but first a conceptual question: I read that huge collection of docs from nvidia-drivers, and concluded that Xinerama and TwinView are fundamentally different and incompatible. i.e. Xinerama starts with two classic X screens and joins them in software to make one big display - an abstraction layer if you will. TwinView rips out the guts of X, dispenses with the notion of separate screens for a TwinView display and gives you one giant screen with no API for an app to see how this big screen is composed. So, you either use Xinerama or TwinView, but not both. Obviously, this understanding of mine is flawed. Which bit did I get wrong? -- alan dot mckinnon at gmail dot com
