PDA

View Full Version : Macbook A1 not Identifying 2nd Display


pdjmuxl
01-03-2025, 08:51 PM
Hello, posting as I'm having the same error others are. My 2nd monitor is showing a black screen. I have done both:
- Screen Recording Permission is still granted and the USB device can access the System
- Used End-User Cleaner and then once again install DisplayLink Manager 1.11.0

It's still not working.

Device is Apple Macbook Pro A1 chip, running Sequoia 15.0, HyperDrive 4K Dual HDMI.

DanielSznicer
01-09-2025, 11:57 AM
Hello, posting as I'm having the same error others are. My 2nd monitor is showing a black screen. I have done both:
- Screen Recording Permission is still granted and the USB device can access the System
- Used End-User Cleaner and then once again install DisplayLink Manager 1.11.0

It's still not working.

Device is Apple Macbook Pro A1 chip, running Sequoia 15.0, HyperDrive 4K Dual HDMI.


Hello,

Can you please share more details I will need logfiles to check the feedback from the driver. For instructions on how to gather the logfiles please navigate to the following article How to report macOS issues to DisplayLink (https://support.displaylink.com/knowledgebase/articles/755301-how-to-report-macos-issues-to-displaylink)


And aslo for speedy support please send an email with the logfiles and detailed problem description to: technical-enquiries@synaptics.com
__________________

lineararrest
01-10-2025, 10:06 AM
Hello happy wheels (https://happy-wheels.co), posting as I'm having the same error others are. My 2nd monitor is showing a black screen. I have done both:
- Screen Recording Permission is still granted and the USB device can access the System
- Used End-User Cleaner and then once again install DisplayLink Manager 1.11.0

It's still not working.

Device is Apple Macbook Pro A1 chip, running Sequoia 15.0, HyperDrive 4K Dual HDMI.

Same problem

benorgana
01-11-2025, 09:11 PM
Same problem

same here M3 Air, Sequoia 15.2, Anker 10 in 1 dock, DisplayLink Manager 1.11.0

Update: Reverting back to version 1.10.1 has fixed the issue