fra81

[fra81]

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:

https://kb.nomachine.com/AR03P00973

[fra81]

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 ; done

lsmod

[fra81]

Hi,

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"

[fra81]

Please try to installe the ‘vdpau-va-driver’ package and tell us if it helps.

[fra81]

Hi nxmac,

to confirm the issue you are reporting is the same that was reproduced in our labs, please answer the questions below.

Does the temporary workaround suggested by Britgirl work also in your case?

And can you try to press Capslock twice when the issue occurs? Does this also help?

[fra81]

Hi Piter,

logs show that DRM initialization fails, maybe due to some missing package. Please show us the output of this command:

dpkg -l | grep -i "libva\|vaapi\|vdpau"

[fra81]

Hi iv,

please try to run this command on the server machine and tell us if it reports any error:

sudo /etc/NX/nxserver --eglcapture yes

Then restart the display manager and the NoMachine server to make changes effective:

sudo systemctl restart display-manager
sudo /etc/NX/nxserver --restart

Let us know if that solves the problem.

[fra81]

Thank you for the report! It seems that what you were seeing is the expected behaviour. By default NoMachine uses progressive refinement of the image quality (what is called ‘multi-pass encoding’ in the option) in order to achieve the minimum response time. Alternatively to disabling those options, you may try to increase the display quality. This will make the progressive refinement quicker.

[fra81]

Hi,

would it be possible for you to show us a video of the behaviour you are seeing? In the meanwhile, you may try these options in the session menu, Display settings, Advanced:

– Disable network-adaptive display quality

– Disable multi-pass display encoding

[fra81]

Hi Kevin,

assuming you chose to see ALL remote monitors, you have two options to see both of them at once: in the Display panel of the session menu you can select the ‘Scale to window’ view mode, so that all remote screens will be scaled to fit the Player window area; in the same panel you can also select ‘Fullscreen on all monitors’, so that the remote screens will span across both your local screens. In a future NoMachine version we also plan to extend support for multiple monitors by allowing to show each remote monitor in a separate NoMachine Player window. Unfortunately at the moment I’m not able to say when this implementation will be completed.

[fra81]

Ok on 1 of the 2 iMacs we are using the 2nd monitor is not showing up as an option.

Do you confirm the desktop is extended on the second monitor and not mirrored? If that’s confirmed, would you send us the logs from the problematic iMac? You can do so by following the instructions in https://kb.nomachine.com/DT11R00182 and send the logs to forum[at]nomachine[dot]com.

Also the video is pixelated for a different iMac with just the built in display. Will adjusting the video options fix that?

You may try to increase Display quality and maybe disable ‘Scale to window’ mode if it’s enabled. If adjusting these settings doesn’t help, please send us a screenshot showing the problem.

[fra81]

Hi Kevin,

about your first question, you should be able to see all server monitors, one at a time or all at the same time, depending on the selected option. Can you please show us a screenshot of your Display settings panel (https://kb.nomachine.com/DT06S00218?s=menu%20panel#5.8)?

As for the second question, NoMachine can’t create virtual monitors on the server. NoMachine connects to the physical display of the server and shows all the monitors physically attached there.

[fra81]

Hi,

would you reproduce the issue again with hardware encoding enabled and send server side logs to forum[at]nomachine[dot]com? Please find instructions in https://kb.nomachine.com/DT11R00182.

[fra81]

Hi,

can you check if that still occurs after disabling hardware decoding on the client? To do so, open the session menu panel (by pressing Ctrl+Alt+0 or by the page peel), enter Display settings, click Modify for the advanced option and check ‘Disable client side hardware decoding’.

[fra81]

Hi,

you can already set the number of cores to be used for encoding in the ‘node.cfg’ file on the server, by editing the ‘DisplayEncoderThreads’ configuration key. That said, it has to be noted that NoMachine, by default, already chooses the best number of cores for encoding, basing on the number of available cores.

[Author]

Posts