Thank you for your quick reply,
I can at least provide more information regarding some of the short
testing you had said to do.
When using the command: xauth merge /etc/opt/VirtualGL/vgl_xauth_key
It returns back nothing.
When using the command: xdpyinfo -display :0
It returns: xdpyinfo: unable to open display ":0".
(also these commands are being done through ssh. If they need to be
done directly I can)
Further more When adding the line you requested into the
/etc/mdm/Init/Default script (which is in the correct location) did
not actually create file/folder that it should have. I wanted to
verify that mdm is actually the display manager and it is (command
used: cat /etc/X11/default-display-manager).
I made sure that I was part of the vglusers group.
I tried to redirect the output of the vglgenkey but it seems to not be
touching the /etc/mdm/Init/Default script.
I hope this sheds a little more light onto what is going on and if
there is anything further I can provide i'd be happy to do as such. I
appreciate your time suggestions.
Thank you,
Marshall Stageberg
Michigan State University
Quoting DRC via VirtualGL-Users <virtualgl-users@lists.sourceforge.net>:
The first thing to try, as indicated in the "Sanity Check" section of
the docs
(https://urldefense.proofpoint.com/v2/url?u=https-3A__cdn.rawgit.com_VirtualGL_virtualgl_master_doc_index.html-23hd006002&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=is60q22IcyABEXnsSrzYNQ&m=o2rLPFelD8-NEVKAzy69YMV_WeYzc4l-R3NRWKaDzLg&s=nlo4lHrLMFYP_Xf98qQ9cYZp7a4TF08aoFc0x7h2EEY&e=
),
is:
xauth merge /etc/opt/VirtualGL/vgl_xauth_key
xdpyinfo -display :0
That may reveal the underlying cause of the problem. If the xauth
command fails, then check the following:
- Make sure that your installation of MDM keeps its initialization
script in the standard place (/etc/mdm/Init/Default). I've tested Linux
Mint before, so it should work, but maybe they moved something in a more
recent release.
- Make sure that /etc/mdm/Init/Default is being modified properly by
vglserver_config. It should have a 'vglgenkey' line at the top if all
is well.
- Edit /etc/mdm/Init/Default and add 'echo here >/tmp/here', then
restart the display manager and verify that /tmp/here is created. If
not, then the display manager isn't executing the initialization script
as it should. This is known to be an issue with some versions of GDM:
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D851769&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=is60q22IcyABEXnsSrzYNQ&m=o2rLPFelD8-NEVKAzy69YMV_WeYzc4l-R3NRWKaDzLg&s=Rn4PmhNvGhcUbs7hyAtSVAqsn3QY5YkZOj6UmgSE7nI&e= . Maybe the
issue
creeped into MATE as well? (I hope not.)
- Make sure you added yourself to the vglusers group and logged
out/logged back in to activate the new group permissions.
- Edit /etc/mdm/Init/Default and redirect the output of vglgenkey to a
file. Restart the DM and look at the file to see if there are any error
messages reported by vglgenkey.
This is generally the process I use when diagnosing failures to access
display :0. Thus far, I have yet to encounter such a failure that
wasn't due to one of the issues above.
On 8/1/17 9:54 AM, stage...@msu.edu wrote:
Hi All,
I have setup a headless server with 2 - Nvidia GTX 1080i video cards
using Linux Mint 18.1 as the OS. I am using the Nvidia 384.59 drivers.
Output from nvidia-xconfig --query-gpu-info:
Number of GPUs: 2
GPU #0:
Name : GeForce GTX 1080 Ti
UUID : GPU-cc7afa9d-a61d-950a-0f45-511bd6f1f340
PCI BusID : PCI:4:0:0
Number of Display Devices: 0
GPU #1:
Name : GeForce GTX 1080 Ti
UUID : GPU-def710e8-b54f-d87d-be43-538d7395c0d8
PCI BusID : PCI:65:0:0
Number of Display Devices: 0
Pertinent output from lspci:
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
41:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
I am using the default mdm display manager (comes stock with linux mint)
When I plug a monitor into the computer directly all video functions
work correctly (glxgears, glxinfo, etc..)
I setup the vncserver and then use the vncviewer to connect to the
headless server. When I try to execute vglrun glxgears I get the error:
[VGL] ERROR: Could not open display :0.
I have ran the vglserver_config script with stopping the following
modules: nvidia_drm, nvidia_uvm, nvidia_modeset, and nvidia. I also
stopped the killed the nvidia persistence process prior to the setup
along with mdm. The config seemed to complete perfectly and I have
restarted the computer.
I appreciate any further advice with this issue.
Thank you,
Marshall Stageberg
Michigan State University
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=is60q22IcyABEXnsSrzYNQ&m=o2rLPFelD8-NEVKAzy69YMV_WeYzc4l-R3NRWKaDzLg&s=2DnymlF_P6OfmuqWSvKktwOclnXtDFWKeWpmltkquPI&e=
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_virtualgl-2Dusers&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=is60q22IcyABEXnsSrzYNQ&m=o2rLPFelD8-NEVKAzy69YMV_WeYzc4l-R3NRWKaDzLg&s=Le6gHqAsmAIFTznxf6jo1Dy89Dd-A1p1e0D5DTLrrtc&e=
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
