Forum Replies Created
-
Posts
-
Hi,
please gather server side logs as exaplained in https://kb.nomachine.com/DT11R00182. You can send them to forum[at]nomachine[dot]com.
Then open the /usr/NX/etc/node.cfg file on the server, uncomment the WaylandModes key and set it to the following value:
WaylandModes drm,compositor,eglIf that doesn’t help, gather the logs again with the changed key.
It seems your graphics card goes into some low power mode. Very likely not something that can be controlled programmatically. I’d try one of the suggestions in this article: https://kb.nomachine.com/AR03P00973.
But before that, it would be nice to gather some more info on the system status. Do you have the possibility to ssh into the server and show the output of the following commands?
DISPLAY=:0 xset -q DISPLAY=:0 xrandr --verboseIf possible, run the commands both before and after the problem occurs.
And finally, what system was installed on the server before you reinstalled it?
Hi,
do you have a Nvidia card on the server? In that case you may try the suggestion in this article: https://kb.nomachine.com/AR12T01182.
If that doesn’t help, please gather server side logs by following the instructions in https://kb.nomachine.com/DT07S00243. You can send the logs to forum[at]nomachine[dot]com.
Hi hexwit,
on a headless system, it’s very likely that the GPU is not functional and so no acceleration is available, but that doesn’t always mean that performance can’t be acceptable. What you have seems a system configuration issue, that it’s not easy to pinpoint. As I understand you tried option 2 of https://kb.nomachine.com/AR03P00973. What about option 3 of the article instead? Did you give it a try? With that option NoMachine will create its own virtual display, that would be less dependent from the system configuration.
Hi Ilgaz,
please show us the client side logs for your case (https://kb.nomachine.com/DT07S00244?s=client%20logs#2). You can attach them here or send to forum[at]nomachine[dot]com, by referencing this topic.
Hi manzaiya,
sorry for the delay. I’m not sure this is the same as the known issue, given that you aren’t using a scaled display. Can you reproduce the issue right now or you downgraded the NoMachine server version in the meanwhile? If you can reproduce, would you send us the logs as explained in https://kb.nomachine.com/AR07K00677? You can send them to forum[at]nomachine[dot]com, by referencing this topic. Then please try to disable hardware decoding on the client (Open the session menu -> Display settings -> Advanced options) and hardware encoding on the server (Server settings -> Performance).
Hi Doug, I examined your logs (sorry for the delay). It seems that something is delaying the startup of the session until a timeout is reached, but unfortunately it isn’t clear what exactly. Did you maybe set up the forward of some device through the session? In that case, please try to connect with a newly created connection file. And would you exclude network problems?
The Mac is an M1 Mini
What model year?
it seems like my hardware and OS should support hardware H264
Yes, it does. The problem is that the hardware encoder doesn’t provide all the capabilities NoMachine relies upon.
That having been said, certain things are still very poorly rendered
Have you tried to increase the display quality in the Display settings panel of the session menu? You can also try to click on the ‘Disable client side post-processing’, in the advanced options.
would a complete re-install still be recommended
Yes, I would do that, just to be sure.
Hi nxmac, sorry for the delay. We identified 3 issues in your logs, not all dependent on NoMachine, that explain your observations. The first one is that the library used for software H.264 encoding is missing in your NoMachine installation, probably due to a problem occurred during the upgrade. We suggest to uninstall NoMachine completely on the Mac and reinstall it from scratch. The second issue is that the hardware H.264 encoder on the Mac lacks the capabilities needed for encoding by NoMachine. This doesn’t depend on NoMachine but it would be interesting to know the exact model of your Mac and the macOS version. These 2 issues prevented H.264 from being used at all and the VP8 encoder was used as a fallback, resulting in lower quality images. The third issue is a bug in the code responsible for falling back from H.264 encoding failures and it was causing the blanked screen issue. This will be fixed in the next NoMachine update.
Hi Rey,
sorry for the delay. What you describe shouldn’t happen normally as NoMachine already suppresses unwanted repeated keys. To investigate further your specific case we would need more info about your setup, in particular we would need to confirm if the server is using X or Wayland. If it’s more convenient for you, we could get such info from the logs. If you are willing to provide them, please follow the instructions in https://kb.nomachine.com/AR07K00677 and send them to forum[at]nomachine[dot]com, by referencing this topic.
Hi Piter, sorry for the the late reply.
Isn’t the problem related to the drop of vdpau-va-driver by Debian?
Yes, it seems so. Anyway this isn’t something that can be fixed in the NoMachine software.
Hi,
the “non-working” case occurs when NoMachine detects that there is already a X session running on the systems and it attaches to it. The fact this X session has a limited set of resolutions doesn’t depend on NoMachine.
The “working case” is when NoMachine doesn’t detect a X server already running on the system and creates its own virtual display. The fact a X server is running or not also doesn’t depend on NoMachine.
However you can work around this problem by stopping the display manager and so avoiding a X session is created in all cases. To do so, you can follow the instructions at point 3 of this article:
Hi,
can you show us the output of these two commands?
for DEVICE in /dev/dri/* ; do echo "*** Trying $DEVICE ***" && LIBVA_DRIVER_NAME=nvidia vainfo --display drm --device $DEVICE ; donelsmodHi,
recent Windows versions have an optimization that disables rendering when the monitor is turned off, and this doesn’t depend on NoMachine. You can try to add the following option to the ‘C:\Program Files\NoMachine\etc\node.cfg’ file, even though I’m not sure it will work if the monitor is turned off by the power button:
DisplayServerExtraOptions "-displayrequired 1"You may also try to change the screen capture method in NoMachine by specifying the following option (the two options can also be concatenated):
DisplayServerExtraOptions "-nodxgigrab"