l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
November 4: Social gathering
Next Installfest:
TBD
Latest News:
Oct. 10: LUGOD Installfests coming again soon
Page last updated:
2007 Jan 25 03:31

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Multiple displays and graphics cards
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Multiple displays and graphics cards



Mark K. Kim wrote:

>On Wed, Jan 24, 2007 at 07:56:50AM -0800, John Wojnaroski wrote:
>
>  
>
>>Mark K. Kim wrote:
>>
>>    
>>
>>>On Tue, Jan 23, 2007 at 11:15:34PM -0800, John Wojnaroski wrote:
>>>
>>>      
>>>
>>>>so after logging in via ssh, starting the program(s) is a no-brainer, 
>>>>but I'm puzzling over how to direct the output to a specific display.  
>>>>        
>>>>
>[snip]
>  
>
>>>	export DISPLAY=<ip>:0.0   # 0.0 is first screen
>>>	xclock &
>>>	export DISPLAY=<ip>:0.1   # 0.1 is second screen
>>>	xclock &
>>>
>>>	export DISPLAY=<ip>:0.0   # 0.0 is first screen
>>>	xclock &
>>>	export DISPLAY=<ip>:1.0   # 1.0 is second screen
>>>	xclock &
>>>
>>>	xclock -geometry +0+0 &   # +0+0 is top-left of screen
>>>	xclock -geometry -0+0 &   # -0+0 is top-right of screen
>>>      
>>>
>[snip]
>  
>
>>I played with the export option a bit late last night as you noted above
>>but nothing worked. OTH I was pretty tired.. I'll give it another go today.
>>
>>Do you have to do anything with the xhost list; something like "xhost
>>+127.0.0.1" or "xhost "ip of remote machine"?
>>    
>>
>
>I didn't see that you were using ssh.  That adds some interesting touch
>to the problem.
>
>Try it on your local system first.  That way you can just try:
>
>  export DISPLAY=localhost:0.0
>  export DISPLAY=localhost:0.1
>  export DISPLAY=localhost:1.1
>  xclock -geometry +0+0
>  xclock -geometry -0+0
>
>to figure out which option you should use to place the window on the
>screen you desire.  After that we'll figure out how to make it work over
>the remote connection.
>
>  
>
Okay, I kind of have it working....

Logging into the remote server and after starting X, I do the following:

castle@turret:~$ startx &

and that brings up X on the AGP and PCI cards and respective monitors. Next

castle@turret:~$ export DISPLAY=:0.1
castle@turret:~$ xclock &

and that starts a clock an sends it to one of the PCI cards ( the BIOS
is set for the agp slot as primary) , then

castle@turret:~$ export DISPLAY=:0.0
castle@turret:~$ xclock &

sends that clock to the other AGP card/screen.

Ideally I would like to be able to open two or three xterms on the
remote and start an application in each directed to the appropriate
remote monitor

When I try that from a "fresh" xterm (i.e; one that has not started the
X session) I get the following:

castle@turret:~$ export DISPLAY=:0.1
castle@turret:~$ xclock &
[1] 1580
castle@turret:~$ Xlib: connection to ":0.1" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0.1

At this point, I've exhausted my knowledge and understanding of setting
up X. I can get by with the first option but would prefer seperate
screens/xterms back on the client for controlling each app on the
server. Just have to get a little smarter on how all this fits together
and how to set things up. Any ideas??

Regards
John W.



_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.