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 <zkauf...@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 >> 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
_______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu 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 . 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.
