RHEL 7 and NVIDIA driver support?

[curts]

I gather from my searching of the TurboVNC documentation that RHEL 7 using a NVIDIA driver is not currently supported? I'm trying to use TurboVNC 2.1.2 and VirtualGL 2.5.2 with Linux kernel 4.4.86.

I've used TurboVNC & VirtualGL successfully with RHEL 6.5 using a NVIDIA driver.

Kind regards,

Curt

[DRC]

Huh? Where are you seeing that?! It is 100% supported, and in fact,
that's probably the most common platform on which people are running
VirtualGL and TurboVNC these days.

[curts]

Well, it is actually a Concurrent Real-Time RedHawk 7.3.2 OS system, but it is effectively a modified version of the RHEL 7.3 kernel and a slightly modified NVIDIA 375.51 driver to improve stability and real-time performance. VirtualGL & TurboVNC work just fine on the older RedHawk 6.5 OS (i.e. RHEL 6.5).

When I try to open a VNC connection I get the "Oh no! Something has gone wrong." screen. I have included the -3dwm option in the vncserver invocation.


I don't see any errors in the VNC log. What else should I look at? I would really like to get this working!

Thanks for your help,

Curt

[DRC]

In my testing (https://turbovnc.org/Documentation/Compatibility), GNOME
3 works with -3dwm, so I'm not sure why it isn't working for you, but
also, GNOME 3 is not an ideal window manager to use in a VNC
environment. It's a compositing window manager, so even if you get it
working, it will be slow, and there are a handful of known issues with
it in a VNC environment
(https://github.com/TurboVNC/turbovnc/issues?utf8=%E2%9C%93&q=label%3A%22GNOME%203%22).
Some have workarounds, but not all.

My suggestion would be to install and enable MATE using the instructions
here:
https://turbovnc.org/Documentation/Compatibility
(under "Red Hat Enterprise Linux 7 (and equivalents)"). That will give
you a similar window manager to the GNOME 2 window manager that you used
with RHEL 6 (MATE is a fork of GNOME 2.) MATE is a 2D window manager,
so it will run in TurboVNC without -3dwm. If you absolutely need to use
GNOME 3, then try the dev/2.2 evolving pre-release build
(https://turbovnc.org/DeveloperInfo/PreReleases), which has a built-in
software OpenGL implementation that (again, in my testing) works with
GNOME 3 without using -3dwm (although, again, performance will not be
stellar.)

DRC

On 1/25/18 7:38 AM, curts wrote:
>
> <https://lh3.googleusercontent.com/-BQI0uYFAIv0/WmnbOq3o7EI/AAAAAAAABOE/Ye8Wv0FlEkkHWGUX1ak7q28DWfX7dt2OgCLcBGAs/s1600/VNC_error.PNG>
>
> <https://lh3.googleusercontent.com/-BQI0uYFAIv0/WmnbOq3o7EI/AAAAAAAABOE/Ye8Wv0FlEkkHWGUX1ak7q28DWfX7dt2OgCLcBGAs/s1600/VNC_error.PNG>

> --
> You received this message because you are subscribed to the Google
> Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to turbovnc-user...@googlegroups.com
> <mailto:turbovnc-user...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/turbovnc-users/6289194e-db0c-4346-92ec-40fddf977992%40googlegroups.com
> <https://groups.google.com/d/msgid/turbovnc-users/6289194e-db0c-4346-92ec-40fddf977992%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[curts]

OK, I've installed MATE, changed from GDM to LightDM, and verified both are working on the console. I've also created a .dmrc file in my home directory with the contents:
[Desktop]
session=mate

I've removed the -3dwm option from the vncserver invocation, but I still get the "Oh no!" screen when I try to connect remotely using TurboVNC. What else could be getting in the way?

Kind regards,

Curt

[curts]

The only "error" in the vncserver log file is:
gnome-session-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256

** (process:18171): WARNING **: software acceleration check failed: Child process exited with code 1

I assume this is to be expected if not using -3dwm, correct?

The Windows TurboVNC client log looks OK:

WinTab library not available                      
Connected to eddie port 5911                      
RFB server supports protocol version 3.8          
Connected to RFB server, using protocol version 3.8
Authentication scheme: Standard VNC authentication
Authentication successful                         
Desktop name "TurboVNC: eddie:11 (cms0620)"       
Enabling GII                                      
Enabling continuous updates                       
Enabling continuous updates                       

Kind regards,

Curt

[DRC]

As I said, "install and enable MATE using the instructions here":

https://turbovnc.org/Documentation/Compatibility

You obviously did not do that.

On 1/29/18 1:12 PM, curts wrote:
> OK, I've installed MATE, changed from GDM to LightDM, and verified both
> are working on the console. I've also created a .dmrc file in my home
> directory with the contents:
> [Desktop]
> session=mate
>
> I've removed the -3dwm option from the vncserver invocation, but I still
> get the "Oh no!" screen when I try to connect remotely using TurboVNC.
> What else could be getting in the way?
>
> Kind regards,
>
> Curt
>
> On Thursday, January 25, 2018 at 2:22:08 PM UTC-5, DRC wrote:
>
> In my testing (https://turbovnc.org/Documentation/Compatibility

> <https://turbovnc.org/Documentation/Compatibility>), GNOME

> 3 works with -3dwm, so I'm not sure why it isn't working for you, but
> also, GNOME 3 is not an ideal window manager to use in a VNC
> environment. It's a compositing window manager, so even if you get it
> working, it will be slow, and there are a handful of known issues with
> it in a VNC environment
> (https://github.com/TurboVNC/turbovnc/issues?utf8=%E2%9C%93&q=label%3A%22GNOME%203%22

> <https://github.com/TurboVNC/turbovnc/issues?utf8=%E2%9C%93&q=label%3A%22GNOME%203%22>).

>
> Some have workarounds, but not all.
>
> My suggestion would be to install and enable MATE using the
> instructions
> here:
> https://turbovnc.org/Documentation/Compatibility
> <https://turbovnc.org/Documentation/Compatibility>
> (under "Red Hat Enterprise Linux 7 (and equivalents)"). That will give
> you a similar window manager to the GNOME 2 window manager that you
> used
> with RHEL 6 (MATE is a fork of GNOME 2.) MATE is a 2D window manager,
> so it will run in TurboVNC without -3dwm. If you absolutely need to
> use
> GNOME 3, then try the dev/2.2 evolving pre-release build
> (https://turbovnc.org/DeveloperInfo/PreReleases

> <https://turbovnc.org/DeveloperInfo/PreReleases>), which has a built-in

> software OpenGL implementation that (again, in my testing) works with
> GNOME 3 without using -3dwm (although, again, performance will not be
> stellar.)
>
> DRC
>

> --
> You received this message because you are subscribed to the Google
> Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to turbovnc-user...@googlegroups.com
> <mailto:turbovnc-user...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/turbovnc-users/f2b46492-4b30-4d21-927b-7c30c48c5e69%40googlegroups.com
> <https://groups.google.com/d/msgid/turbovnc-users/f2b46492-4b30-4d21-927b-7c30c48c5e69%40googlegroups.com?utm_medium=email&utm_source=footer>.

[curts]

My apologies, because I am using a modified RHEL 7 kernel (Concurrent RedHawk 7.3.2) I have been working this issue with both you and Concurrent Support. I had missed the instruction on the Compatibility page to set 'export TVNC_WM=mate-session'. Now that I have added this to my shell environment TurboVNC is working.

Thank you ever so much for your help,

Curt