Forum Replies Created
May 7, 2021 at 11:46 in reply to: Blank physical screen non-functional on Raspberry Pi #33298
sorry for the delay! We verified that indeed it doesn’t work and this issue is the reason:
so this seems to be a problem with the specific combination of graphics card and drivers. Even if sending data to the GPU for rendering can be fast, in some exceptional cases pulling data back from the GPU for screen capture can be much slower. When you stop lightdm, NoMachine creates a virtual framebuffer which is independent from the actual graphics card and drivers. Unfortunately that issue can’t be solved in NoMachine, but you may check for a different version of video drivers. For example, you may try to install proprietary Nvidia drivers or, in case you did already, install the open source ones.April 29, 2021 at 17:35 in reply to: Black screen: no protocol specified, warning! Failed to open display ‘:0’ #33174
is the server a headless machine (no monitor attached to it)? In that case, you can try one of the suggestions here: https://knowledgebase.nomachine.com/AR03P00973.
this is strange indeed. Did you have the chance to verify if this behaviour only occurs when connecting from the Mac? Does using the integrated monitor instead of the external one change anything? And would you run a debug package to gather more information?April 14, 2021 at 17:32 in reply to: Screen blanking issue with 7.4.1, works correctly with 6 #32909
we reproduced this issue in our labs and opened the following Trouble Report:
You can select to be notified when it is fixed. Thanks for reporting!
we can’t reproduce this problem in our labs. Can you explain exactly what you see in the video when it doesn’t work? You can attach a screenshot, if you want.
When using WRD, do you connect to the same desktop where also NoMachine is connected (that is the physical display)?
Finally, please make another test. While keeping ‘Use acceleration for display processing’ disabled, edit the ‘C:\Program Files (x86)\NoMachine\etc\node.cfg’ and add this line:
Restart the NoMachine server and try again.
surely the most recent sessions are the relevent ones. You can send only those or all logs, as you prefer.
I don’t see anything abnormal here. Tto reduce the GPU usage, you can try to check the ‘Disable client-side image post-processing’ and ‘Disable multi-pass display encoding’ options in the Display setttings in the session menu panel, but this is not necessarily what you want. To stop the NoMachine player from using the GPU completely, you would need to check instead the ‘Disable client side hardware decoding’ option. At this point the software fallback will be used, though fully optimized.
the original FR has been dismissed because the OMX framework, from our tests, revealed to be not suitable at its current state. MMAL is indeed under evaluation by our development team and you are right that it can be an interesting alternative.
yes, it could definitely have to do with the settings on the Linux system, but we can check NoMachine logs for any issue. Please find instructions for server side logs at https://www.nomachine.com/DT11R00181#1.1 (debug level, steps 1 and 2, is not necessary) and for client side logs at https://www.nomachine.com/DT11R00181#2.2.
Thank you for reporting!April 1, 2021 at 18:45 in reply to: After remote session freezes and killed, user kept logged without any connection #32718
please try to uncheck the following two options (one at a time) in the Server settings -> Performance tab of the computer where you are connecting to:
Use hardware encoding
Use acceleration for display processing
Does any of them help?
the problems you see are not caused by NoMachine and are described in this article:
You may try with a dummy HDMI display adapter or the suggestions at point 2) of the article.
please try to open Server settings –> Performance tab, on the server machine, and uncheck the ‘Use acceleration for display processing’ option. Let us know if that works.