EliteBook 840 G3 VGA resolution 1920 x 1200

[Toad96]

I have connected my EliteBook 840 G3 (Skylake CPU) to a HP 24-inch monitor (model L2335) via VGA. Its a direct connection, a VGA cable from the VGA connector on the EliteBook to the VGA connector on the 24-inch monitor.

The native resolution of the 24-inch monitor is 1920x1200, but the EliteBook is doing only 1920x1080. I cannot choose a higher resolution via the Intel graphics software utility or the  Windows OS.

Note that if I connect my Dell 27-inch monitor to the EliteBook via a Displayport-to-DisplayPort cable, a resolution of 2560x1440 is possible. So the EliteBook, as such,  is certainly capable of higher resolutions than 1920x1080.

EliteBook has BIOS 1.04 and Windows 7 64-bit Professional with lastest Intel graphics 520 drivers.

Can an EliteBook 840 G3 outpout 1920x1200 via its VGA output connector?

Thanks.

[banhien · Accepted solution]

Hi,

VGA port on your machine only supports 1920 x 1080 max.  VGA abd DP (Display Port) are two different technologies (VGA is analog and DP is digital) you can't compare apples with oranges.

Regards.

[Toad96]

Thanks for your reply!

Perhaps this is already mentioned in the HP EliteBook documentation, but I didn't find it.

I will try with a DisplayPort (digital) to VGA (analogue) active adapter - hopefully that will work! The DVI port of the L2335 monitor is already connected to another PC, so am obliged to use the VGA port on the monitor to connect my EliteBook.

[Toad96]

I also found this:

Link to HP SUPPORT COMMUNICATION - CUSTOMER ADVISORY

The EliteBook 840 G1 (1st generation) already had the VGA limitation of 1920x1080.

[Brian_Jones_HP]

The documentation for the HP EliteBook 840 G3 states that it has VGA resolution up to 1920x1200 @ 60hz... So, it should be working at that resolution. I'm having this same issue as I have two displayport monitors running at 1200, but my VGA monitor (since I can't ust the onboard displayport while the notebook is docked) doesn't have the option to go above 1080. Can anyone provide details on FW updates that solve this issue?