Forum Replies Created
-
Posts
-
The latest version is what caused the problem.
Do you mean latest 6.11.2 or any version before that?
If the issue is present with version 6.11.2, would you try to reproduce again and send us the logs for debugging? You can find instructions in https://www.nomachine.com/AR10K00697 (for server side logs) and https://www.nomachine.com/DT10O00163#2 (client side). You can send everything to forum[at]nomachine[dot]com.
Is the remote computer “headless” (i.e. has no monitor attached)? Or, in case it is a laptop, is the lid closed?
In case, can you try to attach a monitor, or leave the lid open, and check again?
Hi,
is the server a Windows machine in your case? What version? Is it maybe a headless machine (no monitor attached), or has it the lid closed (in case it is a laptop)?
Would you mind sending server side logs from a problematic case, as explained in https://www.nomachine.com/AR10K00697?
Hi Zenith,
the fact that you don’t see glitches on the TV doesn’t rule out a problem with drivers. Rendering (pushing) to the GPU may work correctly, but pulling the screen content back from the video memory may not. Unfortunately this is not something that NoMachine can control.
It looks like libnvidia-encode.so can’t be loaded. The possible cause is that /usr/lib/x86_64-linux-gnu/nvidia/current/ is not in the library search path. You could try to create a symlink to that library:
sudo ln -s /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-encode.so /usr/lib/x86_64-linux-gnu/libnvidia-encode.soIf that won’t work, please try to check permissions for that library and other libraries linked to this one (you can find such linked libraries with the ‘ldd libnvidia-encode.so’ command).
Hi,
unfortunately there is nothing more that can be done in the NoMachine software. After excluding hardware encoding, GPU is not used by NoMachine directly. I have seen other similar cases where the local X server is slow to pull pixels data back from video memory. This is an issue on the video card/drivers side. You may try to use a different version of the drivers, but I can’t say if that will solve the problem.
Hi,
do you have maybe the monitor detached from the server, or is the lid closed (in case you have a laptop)?
Hello,
please run this command and show the output:
sudo find / -name libnvidia-encode.so -or -name libcuda.so 2>/dev/nullHi,
in some cases, even if the machine is headless, the GPU could be “turned off” if the monitor is switched off. Can this be the case? If so, could you try to switch on the monitor attached to the server and check again?
Also, to narrow things down, you can try to disable hardware encoding in NoMachine (‘EnableHardwareEncoding 0’ in /usr/NX/etc/node.cfg) and see if you still experience worse performance on Nvidia than on Intel.
Hi,
can you send the whole log where you see “Using H.264 software encoder”? You can pack the whole log directory as explained in https://www.nomachine.com/AR10K00697 and send to forum[at]nomachine[dot]com, if you prefer.
Since the machine is headless, probably it can’t use the GPU. Can you try to “turn off” the local X server on the server machine (i.e. stop the graphical session), so NoMachine will use its own embedded virtual frame buffer? You can find a couple of ways how to do it at points 1) and 2) in https://www.nomachine.com/AR03P00973.
Hello,
we investigated and found out that AutoHotKeys intentionally ignores input events injected on the system that are not coming from a physical device. NoMachine can’t overcome this, but you could still forward a keyboard to the server as a generic USB device from the NoMachine menu panel.
Further investigations identified two different issues. One is in the Intel drivers, occurring when the monitor on the client machine has a resolution higher than FullHD (1920×1080). That seems to be fixed in the last drivers but it doesn’t look to be your case.
Another issue was found in the NoMachine software, only occurring when the server machine has multiple monitors. This will be fixed in the next release, but if you wish to test a preliminary patch, just send an e-mail to forum[at]nomachine[dot]com to receive it.