DisplayLink device not detected with Lenovo ThinkVision p27h-20

[tim-hilt]

I use two Lenovo ThinkVision p27h-20 displays in a daisy-chain. The monitors themselves are USB-C (3.2) enabled, the daisy-chaining is realized via DisplayPort 1.2. I use the monitors on a MacBook Air M1, which runs the latest MacOS Sonoma.

When I open the DisplayLink Manager UI from the menu-bar, I see a message that prompts me to allow my accessories to connect to the device. However, I don't get such a popup when I replug the USB-C cable. Rebooting also hasn't worked.

That means that MacOS default behavior (mirroring the first display to the daisy-chained monitor) is still what I'm seeing.

Is there anything else I can try? Do you have experience with this particular model?

[rboerner]

Originally Posted by tim-hilt

I use two Lenovo ThinkVision p27h-20 displays in a daisy-chain. The monitors themselves are USB-C (3.2) enabled, the daisy-chaining is realized via DisplayPort 1.2. I use the monitors on a MacBook Air M1, which runs the latest MacOS Sonoma.

When I open the DisplayLink Manager UI from the menu-bar, I see a message that prompts me to allow my accessories to connect to the device. However, I don't get such a popup when I replug the USB-C cable. Rebooting also hasn't worked.

That means that MacOS default behavior (mirroring the first display to the daisy-chained monitor) is still what I'm seeing.

Is there anything else I can try? Do you have experience with this particular model?

According to the information provided by Lenovo about your displays here --> https://pcsupport.lenovo.com/us/en/p...-panel-monitor the monitors you are using do NOT have DisplayLink technology inside of them. As a result, DisplayLink will not be able to assist you.

The monitors you are using have a DisplayPort Multi-stream (also known as DP MST) hub inside of them that allows them to be daisy-chained together.

Apple Mac computers running macOS do NOT support DP MST technology (which is why both monitors are showing a mirror image) and there is no workaround for this behavior.

[tim-hilt]

Thank you! I didn't know that and would likely not have found that out by myself. Thanks for your reply