github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #125] Immediate crash on Macbook pro 10.14.6 #91

New issue

Closed

opened 2026-05-05 05:02:21 -06:00 by gitea-mirror · 13 comments

gitea-mirror commented

2026-05-05 05:02:21 -06:00

Owner

Originally created by @nedelec on GitHub (Sep 17, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/125

My mac immediately freezes when I start Monitor Control 1.7.0, forcing me to reboot.
It was working fine before I updated to Mojave.
Sorry but I am not sure what is going on or how to find out...

Originally created by @nedelec on GitHub (Sep 17, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/125 My mac immediately freezes when I start Monitor Control 1.7.0, forcing me to reboot. It was working fine before I updated to Mojave. Sorry but I am not sure what is going on or how to find out...

gitea-mirror

2026-05-05 05:02:21 -06:00

closed this issue
added the
bug

duplicate
labels

gitea-mirror commented

2026-05-05 05:02:29 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 17, 2019):

What Monitor, GPU and cable are you using?

@JoniVR commented on GitHub (Sep 17, 2019): What Monitor, GPU and cable are you using?

gitea-mirror commented

2026-05-05 05:02:31 -06:00

Author

Owner

@nedelec commented on GitHub (Sep 17, 2019):

NVIDIA GeForce GT 750M:

Chipset Model: NVIDIA GeForce GT 750M
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Total): 2 GB
Vendor: NVIDIA (0x10de)
Device ID: 0x0fe9
Revision ID: 0x00a2
ROM Revision: 3776
Automatic Graphics Switching: Supported
gMux Version: 4.0.8 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v4

Displays:
DELL U2412M:
Resolution: 1920 x 1200 (WUXGA - Widescreen Ultra eXtended Graphics Array)
UI Looks like: 1920 x 1200
Framebuffer Depth: 24-Bit Color (ARGB8888)
Display Serial Number: Y1H5T29I1H1L
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort

@nedelec commented on GitHub (Sep 17, 2019): NVIDIA GeForce GT 750M: Chipset Model: NVIDIA GeForce GT 750M Type: GPU Bus: PCIe PCIe Lane Width: x8 VRAM (Total): 2 GB Vendor: NVIDIA (0x10de) Device ID: 0x0fe9 Revision ID: 0x00a2 ROM Revision: 3776 Automatic Graphics Switching: Supported gMux Version: 4.0.8 [3.2.8] Metal: Supported, feature set macOS GPUFamily1 v4 Displays: DELL U2412M: Resolution: 1920 x 1200 (WUXGA - Widescreen Ultra eXtended Graphics Array) UI Looks like: 1920 x 1200 Framebuffer Depth: 24-Bit Color (ARGB8888) Display Serial Number: Y1H5T29I1H1L Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No Connection Type: DisplayPort

gitea-mirror commented

2026-05-05 05:02:34 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 17, 2019):

Thanks for the detailed info!
Can you confirm that it did work on 1.6.0 or other versions?

@JoniVR commented on GitHub (Sep 17, 2019): Thanks for the detailed info! Can you confirm that it did work on 1.6.0 or other versions?

gitea-mirror commented

2026-05-05 05:02:38 -06:00

Author

Owner

@nedelec commented on GitHub (Sep 17, 2019):

I believe that MonitorControl 1.6.0 on the same system also crashed.
but it worked back in July, before I upgraded to Mojave.

@nedelec commented on GitHub (Sep 17, 2019): I believe that MonitorControl 1.6.0 on the same system also crashed. but it worked back in July, before I upgraded to Mojave.

gitea-mirror commented

2026-05-05 05:02:40 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 17, 2019):

Might be related to your Nvidia card then. My guess would be that the minReplyDelay is too high but I could be wrong, we'll need to look into this.

Your system freezes completely right? Like no mouse cursor movement either?

@JoniVR commented on GitHub (Sep 17, 2019): Might be related to your Nvidia card then. My guess would be that the `minReplyDelay` is too high but I could be wrong, we'll need to look into this. Your system freezes completely right? Like no mouse cursor movement either?

gitea-mirror commented

2026-05-05 05:02:42 -06:00

Author

Owner

@nedelec commented on GitHub (Sep 17, 2019):

Yes, complete freeze, including the mouse, and I see nothing in the logs.

@nedelec commented on GitHub (Sep 17, 2019): Yes, complete freeze, including the mouse, and I see nothing in the logs.

gitea-mirror commented

2026-05-05 05:02:45 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 17, 2019):

My guess is that the issue explained in this forum post is what’s happening:

The biggest issue is NVidia seems to interpret minReplyDelay differently; where a value of 30 * kMillisecondScale is appropriate for ATI/AMD and doesn't require running the same request several times, 30 is a more appropriate value for NVidia, and 0 still returns a garbage response. If true, this means that DDC Panel never actually KPed an NVidia machine, the kernel was simply waiting 1000 * 1000 times longer for the DDC/CI reply.
Timing is very important for I2C buses as I've been reading, so a "good" value here is critical. If the reply is taken too early, the data will be garbage and fail to checksum, too long and it may mimic a Kernel Panic. Running several successful requests in series is the only real test. Feel free to try different values and report back.

So we’d have to play around with a shorter delay and give you a test build to see if that fixes it.

You could also test this yourself using kfix/ddcctl.

@JoniVR commented on GitHub (Sep 17, 2019): My guess is that the issue explained in [this forum post](https://www.tonymacx86.com/threads/controlling-your-monitor-with-osx-ddc-panel.90077/post-581242) is what’s happening: > The biggest issue is NVidia seems to interpret minReplyDelay differently; where a value of 30 * kMillisecondScale is appropriate for ATI/AMD and doesn't require running the same request several times, 30 is a more appropriate value for NVidia, and 0 still returns a garbage response. If true, this means that DDC Panel never actually KPed an NVidia machine, the kernel was simply waiting 1000 * 1000 times longer for the DDC/CI reply. Timing is very important for I2C buses as I've been reading, so a "good" value here is critical. If the reply is taken too early, the data will be garbage and fail to checksum, too long and it may mimic a Kernel Panic. Running several successful requests in series is the only real test. Feel free to try different values and report back. So we’d have to play around with a shorter delay and give you a test build to see if that fixes it. You could also test this yourself using [kfix/ddcctl](https://github.com/kfix/ddcctl).

gitea-mirror commented

2026-05-05 05:02:47 -06:00

Author

Owner

@nedelec commented on GitHub (Sep 17, 2019):

Hello, 'ddcctl' does not crash, and detect the monitor, but the brightness does not change. Is there something you would like me to try?

mac:ddcctl-master$ ./ddcctl -d 1 -b 1
D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: Y1H5T29I1H1L
I: got edid.name: DELL U2412M
D: action: b: 1
D: setting VCP control #16 => 1

mac:ddcctl-master$ ./ddcctl -d 1 -b 100
D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: Y1H5T29I1H1L
I: got edid.name: DELL U2412M
D: action: b: 100
D: setting VCP control #16 => 100

@nedelec commented on GitHub (Sep 17, 2019): Hello, 'ddcctl' does not crash, and detect the monitor, but the brightness does not change. Is there something you would like me to try? mac:ddcctl-master$ ./ddcctl -d 1 -b 1 D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: Y1H5T29I1H1L I: got edid.name: DELL U2412M D: action: b: 1 D: setting VCP control #16 => 1 mac:ddcctl-master$ ./ddcctl -d 1 -b 100 D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: Y1H5T29I1H1L I: got edid.name: DELL U2412M D: action: b: 100 D: setting VCP control #16 => 100

gitea-mirror commented

2026-05-05 05:02:50 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 17, 2019):

Yes, please test changing volume too as brightness is less prone to causing issues than volume. :)

@JoniVR commented on GitHub (Sep 17, 2019): Yes, please test changing volume too as brightness is less prone to causing issues than volume. :)

gitea-mirror commented

2026-05-05 05:02:51 -06:00

Author

Owner

@nedelec commented on GitHub (Sep 17, 2019):

It did not crash, but this monitor has no speakers, as far as I know.

mac:ddcctl-master$ ./ddcctl -d 1 -v 10
D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: Y1H5T29I1H1L
I: got edid.name: DELL U2412M
D: action: v: 10
D: setting VCP control #98 => 10

@nedelec commented on GitHub (Sep 17, 2019): It did not crash, but this monitor has no speakers, as far as I know. mac:ddcctl-master$ ./ddcctl -d 1 -v 10 D: NSScreen #724053908 (1920x1200 0°) 94.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: Y1H5T29I1H1L I: got edid.name: DELL U2412M D: action: v: 10 D: setting VCP control #98 => 10

gitea-mirror commented

2026-05-05 05:02:53 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 18, 2019):

Hmm might be difficult to debug.. could you try a few of the previous versions and let me know if any of them work? Make sure to test 1.4.0

@JoniVR commented on GitHub (Sep 18, 2019): Hmm might be difficult to debug.. could you try a few of the previous versions and let me know if any of them work? Make sure to test 1.4.0

gitea-mirror commented

2026-05-05 05:02:55 -06:00

Author

Owner

@SongHoang commented on GitHub (Apr 5, 2020):

I had this issue on a 650M and same Dell U2412M monitor on 2.0.0 I can confirm 1.4.0 works.

@SongHoang commented on GitHub (Apr 5, 2020): I had this issue on a 650M and same Dell U2412M monitor on 2.0.0 I can confirm 1.4.0 works.

gitea-mirror commented

2026-05-05 05:02:59 -06:00

Author

Owner

@JoniVR commented on GitHub (Apr 10, 2020):

I'm going to close this one as we will continue tracking this issue in #193

@JoniVR commented on GitHub (Apr 10, 2020): I'm going to close this one as we will continue tracking this issue in #193

gitea-mirror referenced this issue

2026-05-05 07:03:00 -06:00

[PR #91] [MERGED] Add sound feedback #1043