<https://lh3.googleusercontent.com/-BQI0uYFAIv0/WmnbOq3o7EI/AAAAAAAABOE/Ye8Wv0FlEkkHWGUX1ak7q28DWfX7dt2OgCLcBGAs/s1600/VNC_error.PNG>
<https://lh3.googleusercontent.com/-BQI0uYFAIv0/WmnbOq3o7EI/AAAAAAAABOE/Ye8Wv0FlEkkHWGUX1ak7q28DWfX7dt2OgCLcBGAs/s1600/VNC_error.PNG>
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
On Wednesday, January 24, 2018 at 4:20:00 PM UTC-5, DRC wrote:
>
> 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.
>
> On 1/24/18 2:03 PM, curts wrote:
> > 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
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/6289194e-db0c-4346-92ec-40fddf977992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
