GTI-11 HDMI working only partly (not Monitor but on TV)

GfoKl43

Hi,

my GTi-11 (1135g/, 16GB, 500GB) does seem to have some HDMI problem:

When connecting directly HDMI to Monitor the scren turns on and of repeatedly. I tried several times, always the same. In Linux, in Windows, in BIOS, everywhere! Tried on another Monitor and there I cannot even get a signal for whatever reason.

However, when connecting to a TV (I tried two different ones), the HDMI signal is stable and without problem.

I also used USB-C to HDMI and this works fine with a Monitor.

DO you have any idea what is going on and how to remedy this problem?

Thank you very much and best regards!

Support-03

Hello there,
Please send us a picture of the SN on the bottom of the PC.
Maybe you need to update the  graphic driver.

GfoKl43

Hi,

I do not think it can be a driver problem if this happens outside of OS, even in BIOS or Bootup Selection Window.



Thank you!

GfoKl43

I checked a three output devices setup:

Monitor via DP, Monitor via USB-C HDMI and TV via HDMI. The output is never stable. Monitor on USB-C HDMI is flickering, Changing setup and connecting direct (no USB) HDMI to Monitor instead of TV gives zero output (cable tested and working 100%!) on Monitor.

Are there HDMI firmware drivers available. Could this be a firmware problem?

Support-03

Hello there,

Here is the driver https://beelink.oss-cn-hongkong. ... 4_V1.0_20210528.zip
Please uninstall the graphic driver in the device manager and then install the new one.

GfoKl43

Has the driver a firmware component or is it just a windows driver?

GfoKl43

If anybody has a similar problem: It is definitely a compatibility problem!

I finally have set up the GTi-11 in a three-output-devices setup. The one monitor via DP, another one via HDMI to DVD and a TV USB-C to HDMI. The monitor now connected via DVI did not accept the raw HDMI signal.

This means the GTI-11 has a weakness in this regard: it is rather selective on which monitor it works with when using HDMI connection. This seems to be an Intel related problem as you find numerous posts about this problem with other devices of similar specification but different manufacturer.