Comment # 3 on bug 1135237 from Stefan Dirsch

Gemini Lake.

Hmm. Seems for some reason modeset driver doesn't detect any outputs.

+ (II) modeset(0): Output HDMI-1 has no monitor section
+ (II) modeset(0): Output DP-1 has no monitor section
+ (II) modeset(0): Output HDMI-2 has no monitor section
+ (II) modeset(0): EDID for output HDMI-1
+ (II) modeset(0): EDID for output DP-1
+ (II) modeset(0): EDID for output HDMI-2
+ (II) modeset(0): Output HDMI-1 disconnected
+ (II) modeset(0): Output DP-1 disconnected
+ (II) modeset(0): Output HDMI-2 disconnected
+ (WW) modeset(0): No outputs definitely connected, trying again...
+ (II) modeset(0): Output HDMI-1 disconnected
+ (II) modeset(0): Output DP-1 disconnected
+ (II) modeset(0): Output HDMI-2 disconnected
+ (WW) modeset(0): Unable to find connected outputs - setting 1024x768 initial
framebuffer

What's the output of 'xrandr' on intel and modesetting?

modeset uses glamor (Intel's Mesa driver) for 2D support, whereas intel driver
still uses SNA as default for 2D acceleration. You may see the
same problems when using "glamor" as acceleration for intel driver instead of
"SNA".

I feel confused with what you mean with Xvnc and x11vnc_ssh. Xvnc is completely
independant of a running Xorg server binary, so why should Xvnc raise the CPU
load for the Xorg binary? I no longer remember what x11vnc_ssh does and how it
works. It may raise the CPU load of a running Xserver somehow ... You would
need to help me here to get a better understanding of this.