Sal,

Getting the various freesurfer GUIs to display over remote connections with completely different operating systems at the server and client side is fraught with a multitude of potential issues, not necessarily freesurfer related, and which I am not always able to solve. That said, I can try and help. A couple things:

1) In regards to the first issue below: You say your are using Xming,,, so the client machine is Windows? So your client is a Windows machine and the host is Ubuntu. Please make sure that the host Ubuntu machine is able to run freeview AND glxgears locally first. 'Glxgears' must work locally AND remotely before you can expect freeview to work. Also, Im fairly certain that the presence of CUDA 5.0 compatible drivers one the host machine is NOT the cause of the problem although it may be related in some way. We obviously have CUDA 5.0 compatible drivers and we are able to run freeview remotely, although Ive never tested it with a Windows client.

2) This is a strange issue... In short you are saying that freeview will display correctly remotely but not locally? CUDA comptible graphics cards and drivers not required for freeview so the the fact the the nvidia card predates CUDA is not a concern. In this case all I can think of is to make sure that you have the most up to date drivers for the graphics card.

Please note, the presence of CUDA graphics cards and libraries is not in any way required for displaying freeview. They are unrelated.

Lastly, here is page I created for diagnosing various GUI related issues. Your exact issue is not listed here but if you make progress and something else comes up, it may be of some use:

http://ftp.nmr.mgh.harvard.edu/fswiki/freesurfer_GUIs_troubleshooting

-Zeke

On 08/19/2013 01:07 AM, Salil Soman wrote:

Thank you Zeke. I am trying to run freeview remotely and display locally on a machine (using Xming). The computer from which I am connecting can successfully run freeview from a different ubuntu 13 machine (one which does not have a cuda graphics card / cuda drivers). When I run glxgears (required me to install mesa-utils), for the NV-GLX missing on display localhost:10.0. A window did popup via xming, but it was black. While it was up the remote machien kept listing x frames in y seconds = z fps

The machine did have cuda 5.0 working with the nvidia 319 linux driver, so freesurfer could be gpu accerlated. Any suggestions on how to fix this would be great.

A similar problem I would like to run by you is regarding the local display on the other ubunut machine I mentioned above. I can connect to this other machien remotely and run freeview, however if I actually use the local monitor attached to the machine, the frreeview window comes up, but in place of imaging data or black, it shows a kind of tie-dye color pattern. The rest of the screen is normal ubuntu, but the freeview window has problems. This other machine has an nivida card that predates cuda (and so no cuda drivers are installed). Any suggestions on how to fix this problem would also be a great help.

Best wishes,

Sal

On Fri, Aug 16, 2013 at 8:13 AM, Z K <zkaufman@nmr.mgh.harvard.edu mailto:zkaufman@nmr.mgh.harvard.edu> wrote:

Hello Sal,

Are your trying to run freeview remotely and display locally
machine? If you type 'glxgears' at the command line does a window
popup displaying spinning gears?

-Zeke



On 08/16/2013 05:55 AM, Salil Soman wrote:

    Hi,

    When I try to run freeview on my ubuntu 13 machine, running the
    nvidia
    5.0 cuda drivers, I get the following errors:

    Xlib:  extension "NV-GLX" missing on display "localhost:10.0".
    Xlib:  extension "NV-GLX" missing on display "localhost:10.0".
    Xlib:  extension "NV-GLX" missing on display "localhost:10.0".
    Xlib:  extension "NV-GLX" missing on display "localhost:10.0".
    X Error: GLXBadContext 150
        Extension:    143 (Uknown extension)
        Minor opcode: 5 (Unknown request)
        Resource id:  0x8000c0
    X Error: GLXBadContext 150
        Extension:    143 (Uknown extension)
        Minor opcode: 5 (Unknown request)
        Resource id:  0x8000c0
    X Error: GLXBadContext 150
        Extension:    143 (Uknown extension)
        Minor opcode: 5 (Unknown request)
        Resource id:  0x8000c0

    Any suggestions on how i can fix this problem?

    Thanks!

    Sal


    _________________________________________________
    Freesurfer mailing list
    Freesurfer@nmr.mgh.harvard.edu
    <mailto:Freesurfer@nmr.mgh.harvard.edu>
    https://mail.nmr.mgh.harvard.__edu/mailman/listinfo/__freesurfer
    <https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer>



The information in this e-mail is intended only for the person to
whom it is
addressed. If you believe this e-mail was sent to you in error and
the e-mail
contains patient information, please contact the Partners Compliance
HelpLine at
http://www.partners.org/__complianceline
<http://www.partners.org/complianceline> . If the e-mail was sent to
you in error
but does not contain patient information, please contact the sender
and properly
dispose of the e-mail.

-- Salil Soman, MD, MS Postdoctoral Research Fellow - Stanford Radiological Sciences Laboratory Fellow - Palo Alto War Related Illness and Injury Study Center WOC Neuroradiology Attending - Veterans Affairs Palo Alto Health Care System