Forum Replies Created
-
Posts
-
Hi all,
we would need the diagnostic reports requested by Britgirl to confirm it is the same problem described in the Trouble Report. If you are willing to test the possible fix for this issue, please contact us to forum[at]nomachine[dot]com.
Hi mopac!
Do you have NoMachine version 5 installed? Connecting to headless machine should work out of the box thanks to this implementation:
https://www.nomachine.com/FR10L02842
If you have this problem with version 5, please gather server side logs as exaplained in https://www.nomachine.com/DT07M00098 and send to forum[at]nomachine[dot]com.
Greetings
It is not possible at the moment, but it is something we are working on. It will be possible to encode a single monitor or even a portion of the remote screen selected by the user.
Hello,
thank you for reporting and for the very accurate analysis!
We have reproduced this issue in our labs and opened a Trouble Report to track it:
Thank you for letting us know!
The patch will be released with the next update.
You can track the status of this Trouble Report here:
I can’t find any documentation for how to enable this feature.
No configuration is needed. NoMachine is designed to select automatically the encoding method that will provide the best performance among the available ones. The hardware encoder will be chosen as the preferred one when supported.
Does it work with AVC?
It will work with any software or hardware decoder you may have on client side, NoMachine AVC pack included.
Does performance update rate improve if I use AVC and a server side graphics card?
Using the hardware encoder on server side can improve performance and most importantly will offload the CPU. AVC on client side should not be needed if you are running a Windows or Mac client. NoMachine will use anyway the hardware decoder that is provided on your client computer.
Lastly, will this work with Kepler based GPUs on AWS EC2?
Unfortunately only Maxwell based (or next ones) GPUs are supported. Hardware encoder is not used in Kepler or older GPUs due to their insufficient feature level.
Hi Ventec,
of course even on a slow network, a 15 seconds delay would have been very difficult to explain, so something must be very wrong.
We didn’t receive your email. Did you send it already?
Would you exclude a bandwidth problem exacerbated by the more graphics-intensive desktop environment of CentOS 7? In this scenario a test with the lightweight desktop (Xfce) would help to clarify.
Another possibility is a problem with video drivers, like in the other cases you mentioned, even though the CPU is not overloaded in your case. This could be verified by running a debug library. If you are willing to test this library, please contact us to forum[at]nomachine[dot]com. We will send you the library and instructions.
Would you help us debugging this issue by running a debug library? In this case, please contact us to forum[at]nomachine[dot]com so we can send you the library and instructions.
Hi!
Unfortunately we weren’t able to reproduce your issue in our labs with the same desktop environment. Are you sure that there are no NoMachine connections left at the moment of the black screen (e.g. you had connected from home and forgot to close the connection before going to work)?
More info about the hardware could help us match your environment more closely, mainly about graphics card and drivers.
Hi Ventec,
what does the ‘top’ command report about the CPU usage on the CentOS 7 box?
You may want to try a lightweight desktop environment, i.e. Xfce. That should also make your virtual sessions work (with built-in X server).
Hi Eric,
I’m happy that you found a way around the problem. Be aware that this case was already investigated in the past. We tested all methods (at least 5) provided by X for getting the screen content, but none of them demonstrated to be any faster than the method currently used by NoMachine.
That said, we are already working on a totally new method for screen capture that won’t require any interaction with the X server and that should solve that kind of slowness. It is currently in testing phase and it will be included in one of the next releases. It should be noted anyway that pulling data from the GPU shouldn’t be so slow, and this can’t be considered in any way a NoMachine bug.
You could say that this X.org bug is triggered by NoMachine, but only in the sense that the applications you mention usually perform drawing operations to the X server (in this case data is sent to video buffer) and very rarely ask for the screen content back (in this case data is received from video buffer).
NoMachine already makes sure of performing the minimum amount of operations to get the screen content, and this has been proven to not significantly overload the X server in the great majority of systems.
I am not aware of any problem with Radeon or Nvidia cards (for example we tested CentOS 6 with Radeon HD 6570).
You may try to install proprietary drivers from AMD (or remove them if you already did).