Monitors with the same name not being recognized?

JackRives · 12-20-2021, 08:05 AM

Hello everyone!

I have a MBA M1 with a ThinkPad Hybrid USB-C with USB-A Dock and three monitors:

- a 4K MSI MAG321CURV which is connected directly to the M1 via USB-C
- two ASUS VN279 monitors which are connected to the DisplayLink dock.

The two Asus monitors are plugged in via HDMI and DP, and while both are working, only one is recognized:

Code:

Apple M1:

  Chipset Model:	Apple M1
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	7
  Vendor:	Apple (0x106b)
  Metal Family:	Supported, Metal GPUFamily Apple 7
  Displays:
Vn279:
  Resolution:	1920x1080 (1080p FHD - Full High Definition)
  UI Looks like:	1920 x 1080 @ 60.00Hz
  Mirror:	Off
  Online:	Yes
  Rotation:	Supported
  Automatically Adjust Brightness:	Yes

Here's how the monitors look:

I'm also using Display Link Manager 1.6 Beta 2.

JackRives · 12-25-2021, 08:55 AM

Issue seems to have been solved in DisplayLink Manager 1.6 (Build 59.128).

12-20-2021, 08:05 AM	#1
JackRives Junior Member Join Date: Dec 2021 Posts: 2	Monitors with the same name not being recognized? Hello everyone! I have a MBA M1 with a ThinkPad Hybrid USB-C with USB-A Dock and three monitors: - a 4K MSI MAG321CURV which is connected directly to the M1 via USB-C - two ASUS VN279 monitors which are connected to the DisplayLink dock. The two Asus monitors are plugged in via HDMI and DP, and while both are working, only one is recognized: Code: Apple M1: Chipset Model: Apple M1 Type: GPU Bus: Built-In Total Number of Cores: 7 Vendor: Apple (0x106b) Metal Family: Supported, Metal GPUFamily Apple 7 Displays: Vn279: Resolution: 1920x1080 (1080p FHD - Full High Definition) UI Looks like: 1920 x 1080 @ 60.00Hz Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: Yes Here's how the monitors look: I'm also using Display Link Manager 1.6 Beta 2. Last edited by JackRives; 12-20-2021 at 08:09 AM. Reason: Huge image

12-25-2021, 08:55 AM	#2
JackRives Junior Member Join Date: Dec 2021 Posts: 2	Issue seems to have been solved in DisplayLink Manager 1.6 (Build 59.128).