[GH-ISSUE #1010] M1Pro Macbook lost connection after installing #611

New issue

Closed

opened 2026-05-05 06:22:15 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:22:15 -06:00

Owner

Originally created by @ethanmiller16 on GitHub (Apr 20, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1010

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

Hi Guys,

I just installed monitorcontrol. After a couple of minutes and playing around with some settings I had a bit of a matrix looking screen flash up and then lost all feed from my macbook. My monitor now reads (HDMI 1 No signal). I've switched this out to my xbox and it works fine and restarted both monitor and mac and still no luck.

Any idea what could've caused this and how to fix it?

Steps to reproduce

Install on m1pro macbook.

Expected behavior

Not sure

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:12.2.1 Monterey
- Mac model: 14 inch m1 pro
- MonitorControl version: 4.0
- Monitor(s): Gigabyte m32u
- Apple Silicon/M1 (yes or no): Yes

Originally created by @ethanmiller16 on GitHub (Apr 20, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1010 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug Hi Guys, I just installed monitorcontrol. After a couple of minutes and playing around with some settings I had a bit of a matrix looking screen flash up and then lost all feed from my macbook. My monitor now reads (HDMI 1 No signal). I've switched this out to my xbox and it works fine and restarted both monitor and mac and still no luck. Any idea what could've caused this and how to fix it? ### Steps to reproduce Install on m1pro macbook. ### Expected behavior Not sure ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version:12.2.1 Monterey - Mac model: 14 inch m1 pro - MonitorControl version: 4.0 - Monitor(s): Gigabyte m32u - Apple Silicon/M1 (yes or no): Yes ```

gitea-mirror closed this issue

2026-05-05 06:22:16 -06:00

gitea-mirror commented

2026-05-05 06:22:20 -06:00

Author

Owner

@waydabber commented on GitHub (Apr 20, 2022):

Hi @ethanmiller16 - unfortunately the HDMI port of the new MBP does not work for proper control, you need to use USB-C.

If you connect your macbook to an other HDMI display (a TV for example), do you experience the same problem?

If you try to switch the resolution or enable/disable HDR, do you still have this problem? You should try switching to a non-native based unscaled one (you might have to use an app for that like BetterDummy - enable Show additional resolution options and switch to Use resolution submenu under Preferences/Resolutions) that might reset things. Also you can delete com.apple.windowserver.displays... by following steps 3,4 and 6 from here: https://github.com/waydabber/BetterDummy/discussions/191#discussioncomment-1763550

If these don't help then some hardware level reset might be needed if processing the DDC command somehow messed up the HDMI converter chip inside the macbook (this is the component that is problematic on m1 macs with HDMI port). https://github.com/MonitorControl/MonitorControl/discussions/750

@waydabber commented on GitHub (Apr 20, 2022): Hi @ethanmiller16 - unfortunately the HDMI port of the new MBP does not work for proper control, you need to use USB-C. If you connect your macbook to an other HDMI display (a TV for example), do you experience the same problem? If you try to switch the resolution or enable/disable HDR, do you still have this problem? You should try switching to a non-native based unscaled one (you might have to use an app for that like [BetterDummy](https://github.com/waydabber/BetterDummy/releases/tag/v1.1.12-rc) - enable `Show additional resolution options` and switch to `Use resolution submenu` under Preferences/Resolutions) that _might_ reset things. Also you can delete `com.apple.windowserver.displays...` by following steps 3,4 and 6 from here: https://github.com/waydabber/BetterDummy/discussions/191#discussioncomment-1763550 If these don't help then some hardware level reset might be needed if processing the DDC command somehow messed up the HDMI converter chip inside the macbook (this is the component that is problematic on m1 macs with HDMI port). https://github.com/MonitorControl/MonitorControl/discussions/750

gitea-mirror referenced this issue

2026-05-05 07:05:42 -06:00

[PR #611] [CLOSED] Update French translations #1135