11th Aug, 2024, 07:23 AM
Hello, friends!
Since 2019, I have been using the XBIAN 18.1 Leia on RPI 3B+ (VNC connection is successful!!!), now I have renewed to RPI 4B on the fresh Firmware Xbian 20.1.
But in any configuration, I was able to connect via VNC to Raspberry Pi, but having a black screen with a cursor.
Raspberry Pi is connected by HDMI cable to the Phillips 46 TV "1080p (TV Phillips
I have changed in the Nano/etc/default/vnc-autores file
VNCGROUP = CEA
Vncmode = 16
According to information about Phillips_edid, an OPT/VC/Bin/TVService -s
/opt/vc/bin/tvservice -s
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive)
The Windows 10 1709 Monitor = Dell UltraSharp 2516D 25" (2560x1440) is installed on the PC and I try to connect to the raspberry (the VNC-SERVER service is included in the atopype and operates on the RPI 4B) using the TightVNC 2.8.84 Viewer or Ultravnc 1.4.3.6 result. The result is a failure.
иIn both cases, black screen vnc-client conection
1.
Tell me who tuned it, because it is not always convenient to connect by SSH ...
I read it on the forum, but I did not find any specific instructions, everywhere there are some scraps of infromation.
-------------------------
Since 2019, I have been using the XBIAN 18.1 Leia on RPI 3B+ (VNC connection is successful!!!), now I have renewed to RPI 4B on the fresh Firmware Xbian 20.1.
But in any configuration, I was able to connect via VNC to Raspberry Pi, but having a black screen with a cursor.
Raspberry Pi is connected by HDMI cable to the Phillips 46 TV "1080p (TV Phillips
I have changed in the Nano/etc/default/vnc-autores file
VNCGROUP = CEA
Vncmode = 16
According to information about Phillips_edid, an OPT/VC/Bin/TVService -s
/opt/vc/bin/tvservice -s
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive)
The Windows 10 1709 Monitor = Dell UltraSharp 2516D 25" (2560x1440) is installed on the PC and I try to connect to the raspberry (the VNC-SERVER service is included in the atopype and operates on the RPI 4B) using the TightVNC 2.8.84 Viewer or Ultravnc 1.4.3.6 result. The result is a failure.
иIn both cases, black screen vnc-client conection
1.
Tell me who tuned it, because it is not always convenient to connect by SSH ...
I read it on the forum, but I did not find any specific instructions, everywhere there are some scraps of infromation.
-------------------------