Britgirl

[Britgirl]

So you could try the Enterprise Desktop product – it’s available as evaluation software.

[Britgirl]

We have checked MX Linux and have not been able to reproduce any similar behaviour. It would have been useful to know the desktop envirionment on the MX Linux system. It could well be x.org crashing. What’s not clear is your setup. Are you are using MX Linux on the Raspberry or are you using a MX Linux NoMachine client to connect to the Raspberry? If the latter, what is the OS and desktop env is on the Raspberry? If you wish for us to investigate further, please provide us with the full set of NoMachine logs as requested from client and server sides? (link in previous reply).

edit: in your case, using Wayland instead of X.org could help.

[Britgirl]

Hi, do you have a second monitor attached to the M1 laptop? We can reproduce this behaviour if another monitor is attached to the laptop. If this is not your case, please describe precise steps to reproduce.

[Britgirl]

Hi, we will be adding a timeout parameter to the scripts. This will allow you to set a timeout that fits your custom script setup.

so for example, UserScriptAfterLogin "/usr/script/afterLogin.sh --timeout 180.

This will be implemented for version 9.

[Britgirl]

The most reasonable implementation would be to send a WOL packet just before the connection attempt, so that if the server is not running, it would restart its run, or send the WOL packet if the server is not immediately responding in a reasonable time, like a couple of seconds. The WOL packet, instead, is now sent after the connection timeout, if the remote host is not responding. The reason it was done like this was to overcome a few WOL problems and incompatibilities we encountered at the time of the first implementation. We actually retested all of this and it doesn’t seem that these problems and incompatibilities still hold. This means that a more reasonable implementation should come shortly, actually resolving the problem you detected. Thanks for reporting.

[Britgirl]

I’m assuming you’ve got the free edition installed on the Windows 11 PC. A NoMachine Free Edition installation will accept 1 connection. If you’ve started a connection to your Windows 11 PC and then start a second connection to the same PC, the first connection will close. Two NoMachine players connecting to the same Windows desktop requires Enterprise Desktop.

https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop

[Britgirl]

Not quite sure what to make of what you wrote. With HW encoding/decoding enabled, then NoMachine uses the graphics card available on the host in order to encode or decode. If that’s not possible, NoMachine reverts to H.264 software encoding. This is explained in the material that I pointed to.

As for hypervisor technologies, NoMachine works out-of-the-box with most of them and we test with quite a few including Proxmox.

[Britgirl]

NoMachine can be used with VOIP applications in the following scenario https://forum.nomachine.com/topic/audio-from-user-to-user#post-41572

[Britgirl]

All’s good then 🙂

[Britgirl]

Hi, can you submit all attachments and images to forum[at]nomachine[dot]com? Also confirm distro and version on the server side and what OS you are connecting from. Desktop env will be useful as well.

I had in mind that NoMachine was able to adapt the remote resolution as the client window is resized.

It does 🙂 provided the following conditions are met:

When the connection is to the physical desktop (any OS) , the supported resolutions are those of the remote graphics card as listed in the System settings on the server. The session resolution on the client side cannot be higher than the maximum resolution supported by the remote graphics card (server side).

The supported resolution for virtual NoMachine desktop sessions (Terminal Server for Linux products) doesn’t depend on the remote hardware and thus the remote screen can be resized to whichever resolution is supported by the user’s local monitor.

I pasted this text from the article here:

Some tips about resize and scaling options for NoMachine remote desktop software
https://kb.nomachine.com/AR02M00835

 

[Britgirl]

Hi, we can reproduce and will be opening a Trouble Report. Thanks for reporting 🙂

The workaround in the meantime is to connect over ssh or change TTY (ctrl+alt+F2) – and remove the mentioned line greeter-setup-script=/usr/NX/scripts/vgl/vglgenkey or restore the orginal key:

sudo cp /etc/lightdm/lightdm.conf.orig.vgl /etc/lightdm/lightdm.conf

[Britgirl]

We’re still investigating. In the meantime, can you take a look at the following link and try the steps there? This will at least check that everything is functional (without NoMachine in the mix).

export LIBVA_DRIVER_NAME=iHD
wget https://github.com/lu-zero/fate-samples/raw/master/h264-conformance/AUD_MW_E.264

# Decode H.264 video stream w/ maximum speed
/usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264

# Decode H.264 video stream and dump output YUV
/usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 -o AUD_MW_E.yuv -i420
# You can verify the result comparing with the following checksum:
# sha1sum AUD_MW_E.yuv
e17a3f8cfeeeb1cc46218c3c797d24dd84e82b59 AUD_MW_E.yuv

# Encode H.264 stream w/ Low Power encoder on gen9+ (skl+)
/usr/share/mfx/samples/sample_encode h264 \
-w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff \
-i AUD_MW_E.yuv -o encoded_AUD_MW_E.264

and tell us the outcome.

[Britgirl]

Thanks for letting us know. SSH tunnels aside, if you have any other questions about player and the server, or other components of NoMachine software, let us know here 🙂

[Britgirl]

Interesting. So NoMachine is now working in your set-up?

[Britgirl]

With regards to the sound issue, check what is indicated in your Windows sound settings. Are you able to change to another audio output? With regards to the no access on Jetson issue, are you not even able to SSH into it? Have you tried rebooting? Rebooting with a monitor attached or HDMI dongle (if you don’t have a monitor)?

[Author]

Posts