VMware Horizon Community
andymcvey
Contributor
Contributor

Screen resolution problems on physical workstation

Hi

Disclaimer: Yes, I know this is not supported.  Posting more in the hope someone else has seen/worked around the issue.

With a little effort I've got 2203/2206 View working on a physical workstation, however I'm not getting support for multiple monitors or dynamic display resizing.  The workstation is an old-ish one with a  Quadro M4000 and the intention is to try and run X with acceleration enabled.  I can connect but only get a single monitor working.  Resizing the client doesn't trigger an RANDR event on the Xorg server.  In /tmp/vmware-root/vmware-mks-<pid>.log I get

2022-10-10T16:51:57.470Z In(05) vnc-x11 VTHREAD 140371367896832 "vnc-x11" tid 10209
2022-10-10T16:51:57.471Z In(05) main LinuxNvFBCCapture: Loaded NVIDIA NvFBC
2022-10-10T16:51:57.471Z In(05) vnc-x11 XKeymap_PowerOn: use evdev keycode mapping.
2022-10-10T16:51:57.472Z Wa(03) vnc-x11 VNCServerOS: XInput available, XI2 used
2022-10-10T16:51:57.474Z Wa(03) vnc-x11 RandR >= 1.2 not usable

However running xrandr within a shell from the single screen session shows the RANDR extension are there and version 1.5. 

Any ideas?  Thanks!

Reply
0 Kudos
4 Replies
Albertovich
Enthusiast
Enthusiast

Hi:

i had a similar issue running vmware-view on raspberrry4, client don't start fullscreen on all monitors.

I had solve it by downgrading vmware-view from 2206 to 2111.

Regargs

Reply
0 Kudos
andymcvey
Contributor
Contributor

Thanks - were you running the view client on the raspberry pi, or the view agent?  In my case I've got the agent on the CentOS workstation, view client on a Win11 PC

Reply
0 Kudos
Albertovich
Enthusiast
Enthusiast

Hi:

I'm running the vmware-view client on raspberrys pi 3 and 4 models, running Raspberry pi OS (debian based distro)

Tell me if the downgrade works for your issue 😉

regards

Reply
0 Kudos
andymcvey
Contributor
Contributor

Unfortunately still getting the "2022-10-13T11:45:55.791Z Wa(03) vnc-x11 RandR >= 1.2 not usable" error in the logs after a downgrade.  I think we're testing different scenarios here though - in my case the client is working fine, it's the agent that's not working.  I'll maybe do a longer post on the setup, as there are some extra steps after the agent's deployed in order to get X working on the M4000 card.  The VMware EDID files may also be implicated 

Reply
0 Kudos