fra81

[fra81]

Hi,

is the Linux server headless?

Please gather server side logs (possibly after disabling hardware encoding) as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

you can disable the desktop manager permanently:

systemctl stop display-manager
systemctl disable display-manager

Alternatively you can use a HDMI Dummy Plug adapter.

[fra81]

Hi,

any chance to get NoMachine logs from the non-working case? To do that, you would have to restore the Radeon card, reproduce the issue and gather logs as explained in https://www.nomachine.com/AR10K00697. You can also send them to forum[at]nomachine[dot]com. If you do that, please also try to uncheck the ‘Use acceleration for display processing’ box in Server preferences -> Performance tab and see if it solves the problem.

[fra81]

when I login, the screen resets to 1920 x 1080

Probably I didn’t get it right before. I thought “login” as “connect to the server”. Do you mean that you log in the remote user into its desktop, i.e. you connect to the login screen on the physical display and then log in?

In that case, it is likely that the desktop environment stores the last resolution set and uses that when starting up. If you change the resolution via the system preferences inside the session, then the new resolution would be stored.

[fra81]

So it seems the official ones are affected. Thank you for the info 😉

[fra81]

Hi,

would you tell us what new drivers exactly?

[fra81]

Hi,

please check that the ‘Match the client resolution upon connecting’ box is unchecked in the NoMachine menu inside the session -> Display -> Change settings panel.

[fra81]

Unfortunately we’re not able to reproduce the issue with hardware encoding in our labs. Would you test one more thing? That would be to restore the EnableHardwareEncoding key back to the original value and change the encoder’s rate control mode instead (EncoderMode key), i.e.:

EnableHardwareEncoding 1

EncoderMode bitrate

[fra81]

This is strange indeed. Is it possible that the problem is with screen refresh and not with mouse and keyboard? Do you have any other means for accessing the server’s physical screen and verify?

You may try to check the ‘Use acceleration for display processing’ option in Server preferences -> Performance tab. You can do this before assigning the problematic card, then restart the server and try to connect.

Please also gather logs from the server as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

I’m not sure I understand, do you have this problem only when the Mac is the client? Or also when the client is Linux or Windows?

I assume you are using an external keyboard on your Mac. Could you show a picture of the keyboard?

Aren’t you able to switch the NumLock status of the Linux/Windows server via the Clear key on your Mac keyboard?

[fra81]

Note that server and client side can either use the GPU or the CPU independently: server side can use the hardware encoder or a software fallback; client side can use the hardware decoder or a software fallback. And both sides can use the hardware (GPU) at the same time, or one of them can, or none. It will depend on hardware capabilities and on settings you’re using. To answer your question, when the GPU is not used (on either side), the CPU does the work.

That said, it seems there is a problem with hardware encoding. Please provide more info so we can investigate further:

– server OS version (as I understand Fedora 29)

– Nvidia card model

– video drivers type and version

Also server side logs would be useful. You can gather them as explained in https://www.nomachine.com/AR10K00697 and send them to forum[at]nomachine[dot]com, if you prefer.

[fra81]

Hi,

can I assume you already tried to use VP8 encoder and that solved the problem?

Please check if any of the following options solves the problem with H.264 (try them in this order):

1) disable hardware decoding by checking the ‘Disable client side hardware decoding’ option in the session menu, Display settings

2) disable hardware encoding on server side by adding this line to the /usr/NX/etc/node.cfg  file (then restart the server):

EnableHardwareEncoding 0

[fra81]

Hi Dario,

generally reducing image quality doesn’t decrease CPU usage, but reducing frame rate does. It is possible to set any value from 1  to 1000 by editing manually the node.cfg file on server side. For example, to have 10 frames per second, you can uncomment and set the following keys:

DisplayServerVideoFrameRate 10

DisplayServerUseVideoFrameRate 1

Another thing you can do is disabling the “lossless refinement” algorithm:

DisplayServerExtraOptions “-refinement 0”

[fra81]

Hi Dario,

at the moment NoMachine needs Nvidia Video Codec (NVENC) and that is not supported on Jetson.

There is work in progress to leverage OMX encoders and decoders in the future, mainly for mobile and embedded platforms, but I wouldn’t be able to say a date yet.

[fra81]

Please send us logs from the host machine as explained in https://www.nomachine.com/AR10K00697.

And client side logs as explained in https://www.nomachine.com/DT10O00163#2.3.

You can also send them to forum[at]nomachine[dot]com.

[Author]

Posts