my os doesn't even go above init 2, but its ok, i think i managed to sort
everything out by treating x as a system service launched with user
credentials and then xinitrc brings up vncserver, so far so good

thanks again for everything



On Apr 10, 2017 8:19 PM, "DRC" <[email protected]> wrote:

> The 3D X server is connected to the GPU, so it has to be a full X
> server, not an X proxy like TurboVNC.  If you just need to use it under
> your own account, then you could run the 3D X server with startx, but in
> a multi-user scenario, the best approach is to start it from the display
> manager (e.g. GDM, KDM, LightDM, etc.)  The 3D X server needs to have a
> GPU attached (preferably nVidia or AMD/ATI) and preferably the 3D drivers.
>
> I'm surprised that your 3D workstation doesn't already start the X
> server at system start.  That is the way that every modern Linux
> distribution is configured, and VirtualGL is designed around that
> configuration.
>
> On 4/10/17 6:58 PM, Steve Volumetric wrote:
> > My use scenario is that I'm setting up a 3d-workstation that I almost
> > exclusively access remotely from my laptop.  GL is a must.
> >
> > I got 'vncserver' working from my pre-X, non-root account, so i've
> > passed at least those hurdles.  No troubleshooting needed there.    The
> > only remaining hiccup is virtualgl.  You said an X server is required on
> > the root display (I take this to mean Display:0)  Can that X server be
> > the turbovnc server, or does it have to be the standard x server?
> >
> >  Thanks for your help.
> >
> > On Mon, Apr 10, 2017 at 2:32 PM, DRC <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     VirtualGL requires an X server to be running on the root display, but
> >     TurboVNC doesn't.  I refer you to the VirtualGL User's Guide for
> details
> >     of that, but generally the "3D X server" that VirtualGL uses to
> access
> >     the GPU isn't launched with startx.  It's launched with
> init.d/systemd,
> >     and vglserver_config is used to modify the display manager startup
> >     environment so that VirtualGL users can get access to the 3D X server
> >     while it's sitting at the login prompt.
> >
> >     TurboVNC does not require any other X server to be running.  It is
> its
> >     own X server.  When you say things like "I haven't been able to run
> >     vncserver from the non-X console", it helps if you post information
> >     regarding how you are trying to launch it and how specifically it's
> not
> >     working.
> >
> >     DRC
> >
> >     On 4/10/17 12:49 PM, Steve Volumetric wrote:
> >     > That's odd, so I attempted to follow the guide, I must be doing
> >     > something wrong.  I'll have to post my output when I get home, but
> I
> >     > haven't been able to run vncserver from the non-X console.  It
> seems to
> >     > "just work" if I do 'startx' first, then open xterm and run
> vncserver
> >     > from there.
> >     >
> >     > Ideally, I'm trying to do exactly what you described - run
> vncserver as
> >     > a standalone virtual X server without 'startx'ing' first.  If I
> can get
> >     > vncserver to run like you've suggested, will VirtualGL still work?
> >     >
> >     > Thank you.
> >     >
> >     > On Mon, Apr 10, 2017 at 1:11 PM, DRC <
> [email protected]
> >     <mailto:[email protected]>
> >     > <mailto:[email protected]
> >     <mailto:[email protected]>>> wrote:
> >     >
> >     >     What are you trying to do?  TurboVNC is a standalone virtual X
> server,
> >     >     so you don't have to launch a completely separate X server in
> order to
> >     >     use it.  Just run /opt/TurboVNC/bin/vncserver, as instructed
> in the
> >     >     User's Guide.
> >     >
> >     >
> >     >     On 4/9/17 6:49 PM, Steve Volumetric wrote:
> >     >     > Currently, I've got turbovnc and virtualgl working, but what
> I'm doing
> >     >     > is logging in as root, starting x with startx, then once X
> starts, I
> >     >     > open a terminal and run 'vncserver'
> >     >     >
> >     >     > so far, it's been ok, but if I ever need to reboot the
> server, I have to
> >     >     > get in front of the server(down two flights of stairs), and
> redo all
> >     >     > those steps.  Surely, there must be a better way.
> >     >     >
> >     >     > is there a 'right' way to integrate the turbovnc server into
> some
> >     >     > automatic thing that gets launched when X starts?
> >     >     >
> >     >     > I've tried adding 'exec vncserver' to ~/.xinitrc but that
> didn't work,
> >     >     > also now I'm starting X when the system comes up, so X won't
> be pulling
> >     >     > in anything from anyone's home directory.
> >     >     >
> >     >     > I've been looking at /etc/X11/xinit/xserverrc but I'm not
> quite sure how
> >     >     > that file is supposed to look.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> TurboVNC-Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/turbovnc-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
TurboVNC-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/turbovnc-users

Reply via email to