- This topic has 3 replies, 2 voices, and was last updated 3 years, 6 months ago by
.
-
Posts
-
Just letting you know that I’m finding the option ‘Blank the physical screen when somebody connects’ to be completely non-functional (as in, the screen actually doesn’t get blanked – you can see everything that is going on).
Environment…
- Brand new Raspberry Pi 4 Model B 8GB RAM rev 1.4 (d03114)
- HDMI screen attached to it (it’s actually a Raspad 3, but yeah – basically a HDMI screen)
- SanDisk Ultra 128GB UHS-I microSD
- Fresh install of Ubuntu MATE 20.04 LTS for Raspberry Pi 64-bit (arm64)
- NoMachine 7.4.1 for Raspberry ARMv8 (installed from the arm64 .deb file found here)
Let me know if you need more information or require me to do further testing.
I’ll turn on notifications for this thread, so if someone says it’s been fixed I’ll know to give it another try.
Hi,
sorry for the delay! We verified that indeed it doesn’t work and this issue is the reason:
Why? Can you elaborate on why that is the issue?
Not only does most of that issue seem to revolve around gamma settings.
But whenever I’ve seen the screen be blanked on an x86 system, it’s just drawing black pixels across the entire framebuffer – it’s not actually communicating with the GPU or monitor to do something special… at least as far as I was aware anyway?
The screen blanking implementation is indeed about gamma settings. NoMachine encodes a copy of the framebuffer, so changing the framebuffer pixels would also affect what you see remotely.
As a possible alternative, you could turn the physical display off when you want to connect remotely, as explained at point 3 of this article: https://knowledgebase.nomachine.com/AR03P00973. At that point NoMachine will create a virtual (off-screen) framebuffer.
This topic was marked as solved, you can't post.