[gentoo-user] Re: Xinerama and Xrandr

2010-03-10 Thread Allistar
Dan Johansson wrote:

 I have been playing with my X-configuration this weekend and I can not
 really get it to work the way I like. My desktop box has two Nvidia cards
 installed with one monitor connected to each. On to of that I am running
 KDE (v 4.3.5 at the moment).
 
 # lspci | grep VGA
 01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400
 GS] (rev a1)
 05:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400
 GS] (rev a1)
 
 If I have Option Xinerama on in the ServerLayout section in xorg.conf
 then KDE uses both monitors (in Xinerama mode) but I can not use any
 Desktop effects as Compositing is not supported. Also a lot of GUI
 programs reports
 Xlib:  extension RANDR missing on display :0.0.
 
 If I set Option Xinerama off in xorg.conf then KDE only runs on one of
 the monitors and the Desktop effects works great. And the other GUI's
 does not
 give me that Xlkib error message.  But now the only way to start a GUI on
 the second Monitor is to prefix it with DISPLAY=:0.1 or use --display
 :0.1.
 
 Does someone have any suggestion how I can get the best of both worlds?
 i.e. Compositing  KDE using both monitors.

You cannot do compositing or XRandR and Xinerama at the same time. Each of
those NVidia cards has two outputs. One approach is to only use one of the
cards and us NVidia's TwinView, which gets around having to use the
Xinerama extension. Then you can have a single big desktop spanning both
monitors, and the eye candy of desktop effects.




[gentoo-user] Re: corss compile 64bit on 32bit os

2009-09-16 Thread Allistar
Xi Shen wrote:

 Hi,
 
 i want to use discc to speed my emerge compilation. but the problem is
 that i have 32bit and 64bit mixed environment, and some of the cpus do
 not support amd64 mode. so i just wonder if i could do cross compile.
 
 has anyone done this before? any suggestions/comments are welcomed.

I have an amd64 system which is used with distcc to help speed up compiling
of an x86 system and cross compiling works without any issues. I followed
the cross compiling instructions on gentoo.org.

Note that this is compiling 32bit on a 64bit box, not the other way around.





[gentoo-user] Re: vmware fails: Virtual Machine Monitor does not start

2008-11-11 Thread Allistar
Neil Bothwick wrote:

 On Mon, 10 Nov 2008 19:24:15 -0800, Kevin O'Gorman wrote:
 
 I've re-emerge vmware-modules, re-run ...vmware-config.pl, and prayed.
 I still cannot do
/etc/init.d/vmware start
 because this one part fails: Virutal machine Monitor
 and trying vmware says I need to run the config script (again).
 
 I'm getting nowhere and I really do want to run that VM again.
 
 
 Have you updated your kernel? VMware Workstation gives me problems like
 this with each new kernel, which is why I'm still running 2.6.26 on my
 desktop.

You're running 2.6.26 and have VMWare Workstation working properly? What
architecture? I am still on 2.6.19 because any later kernels result in
Workstation not working (it crashes when starting a VM, and also stops my
keyboard from working).




[gentoo-user] Re: vmware fails: Virtual Machine Monitor does not start

2008-11-11 Thread Allistar
Kevin O'Gorman wrote:

 On Tue, Nov 11, 2008 at 12:43 AM, Neil Bothwick [EMAIL PROTECTED]
 wrote:
 On Mon, 10 Nov 2008 19:24:15 -0800, Kevin O'Gorman wrote:

 I've re-emerge vmware-modules, re-run ...vmware-config.pl, and prayed.
 I still cannot do
/etc/init.d/vmware start
 because this one part fails: Virutal machine Monitor
 and trying vmware says I need to run the config script (again).

 I'm getting nowhere and I really do want to run that VM again.


 Have you updated your kernel? VMware Workstation gives me problems like
 this with each new kernel, which is why I'm still running 2.6.26 on my
 desktop.

 
 I'm running 2.6.25-r8.  I probably have updated since the last time I
 ran VMware.
 But I thought the above steps took care of that.  I guess not.
 
 So what do I do now?

From what I've experienced, the order you emerge vmware-workstation and
vmware-modules is important. When getting the error you mention, a simple
re-emerge of vmware-modules did the job.