mac-pixel-clock-patch
mac-pixel-clock-patch copied to clipboard
vinc3m1
Patch for 10.10.2
I get the following md5 hash for the IOKit file:
a94dc8e1b6bb6491e5f610f0a3caf960
So I guess the patch has to be updated for 10.10.2 to work.
Would be great if someone who's familiar with this work could do that :+1:
Under 10.10 it has worked like a charm on my MacBook Air late 2013 to get 2560 pixel res out of it.
Wow that was blazing fast. Works like a charm (again). Thank you so much!
Only needed to add the md5 to the script, I'm happy we didn't have to calculate it again :-)
There seems to be a 350 MHz DisplayPort cap even on my MacBook Pro (Late 2013 / Thunderbolt 2 / Iris Pro 5200 / GT750M). I have an Asus PG278Q (2560x1440@144 Hz ~540 MHz pixel clock). It needs this patch to go above 2560x1440@85 Hz ~350 MHz pixel clock.
Please keep up the good work! It's much appreciated.
@kathampy Both the HDMI and DP cap are fully removed by this script.. this only leaves hardware limits and framebuffer limits IIRC
Floris497's patch for 10.10.2 works for me on a Mac mini Late 2014 with a Seiki 39" SE39UY04. I used SwitchResX, and then I was able to run 3840x2160@30hz.
On my late-2014 Mac Mini running 10.10.2, when I run the .command file, I get this:
./macPixelClockPatcher.command: line 4: syntax error near unexpected token `newline'
./macPixelClockPatcher.command: line 4: `<!DOCTYPE html>'
Any ideas?
@ajhuntsman did you use my fork? i guess you downloaded the webpage and not the raw file 😁
@Floris497 yep, got the raw file, ran it, and nothing happened. So, I ran the MD5 checksum and then verified that mine is not in the script:
MacMini:~ ajhuntsman$ md5 -q /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
711906ad2d10b93a70ca4cf86e55627e
MacMini:~ ajhuntsman$ grep md5 -q /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit macPixelClockPatcher.command
MacMini:~ ajhuntsman$
Would you mind adding it for posterity?
Here are my Mac specs, if it helps anyone else:
- Mac Mini (Late 2014)
- 3 GHz Intel Core i7
- 8 GB RAM 1600MHz DDR3
- Intel Iris 1536 MB
My md5 is again different.
Running on 10.10.2 security update 2. I think it's better to state the build version 10.10.2 (14C1514)
Mac-mini:Downloads admin$ md5 -q /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit a94dc8e1b6bb6491e5f610f0a3caf960 Mac-mini:Downloads admin$ grep md5 -q /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit macPixelClockPatcher.command nothing
Can anyone update the patcher? Or make it so that it just works?
@Basilmir sorry for the late response, I have added 10.10.3 hope that works :smile:
@Floris497
Just letting you know the patch works great on my Late 2013 MacBook Pro Retina running 10.10.3. Connected to Seiki 4k 39" monitor using HDMI port on the MacBook Pro.
Now I have the resolutions: 3840 x 2160 3200 x 1800 (low resolution)
3840 x 2160 looks better since that's the native resolution.
Before update, I only had 1080p and MacOS think it's a 1080p 30" Display. Now MacOS thinks it's a 4k 38.5" Display.
@hyteckid My computer still thinks it is sending 4k to a 1080p monitor.. I only get it to recognize it when i change the framebuffer, but that makes the system verry unstable.. Those (low resolution) things are normal, i have a few of them, and i'm not sure why they are there.. Or what they mean.
@Floris497 I noticed something weird, I'm on a Late-2012 Mac Mini running on H4000. On the HDMI port I can't do 4K@30hz with or without the patch. The TV is blank no matter what.
Using an active miniDisplayport to HDMI converter and no patch I need to use SwitchResX to add a custom 4K@30hz and it works.
If I uninstall SwitchResX and install the IOKit patch I can see the 4K@30hz resolution directly and I can select it. But there is something weird about the screen, at first I thought font smoothing was off but it's not, the icons and the edges of windows seem very rough, you have to see the detail, it's as if quartz antialiasing is wrong, but I've made print screens for before and after compare and they look the same.
I can only conclude that patching IOKit to push the pixel clock, manages to confuse or affect the active miniDisplayPort to HDMI converter. The difference is slight, located everywhere, but instantly noticeable, a lot of detail around letters is gone and even the letters seem affected, the letter "L" which is perfectly straight manages to have tiny pixel to and bottom protruding out of it.
Sometimes turning the TV on and off seems to fix the issue but 15 min later it's there again.
Is this even possible? Unlocking the miniDisplayPort clock seems to affect the active converter?
PS. Now I'm back to active converter + SwitchResX and no issues for 1h so that effect is there only with the patch.
@basilmir this is possible, the hardware is not fully made to do 4k but it works, the pach only stops IOKit to check an invalid pixel clock, some weird side effects can occur with different displays and converters and macs, the pixel clock check is there for a reason. I'm running 4k@40Hz (hd3000) and when there is a lot of activity on my screen antialiasing turns of on the left right side of my display.. Unlocking the pixelclock sometimes makes the driver see your display/adapter as a different one.
Floris497, can you update your patch to 10.10.4 please? I think IOKit hasn't change. Just the version strings need to be updated for posterity sake. Could you also enable Issues on the repository so people can comment there?
@kathampy EDIT: (whoops, didn't read :P) yes i will change it, also i enabled Issues. didn't know that must be turned on.
I've downloaded the patch and executed the commands in terminal.. and literally... nothing happens. I don't get a prompt to enter my admin password... nothing! I don't get it. I have a late 2012 Mac Mini as well and am trying to use a LG UltraWide 29" screen but right now, I'm getting NO love even with a mini display port to HDMI converter.
You don't need the patch to get the LG 21:9 Ultrawide monitor to work. I have the same monitor and it has 2560x1080 which works out of the box even on 2010 mac minis. You need a minidisplayport to displayport cable like this and it will work without issues. http://www.amazon.com/Cable-Matters®-DisplayPort-Thunderbolt-Compatible/dp/B00C7RJQPY
Hey there... right, I understand but it only has HDMI ports -- no display port... this is the model I have. http://www.bestbuy.com/site/lg-29-ips-led-hd-219-ultrawide-monitor-black/7937084.p?id=1219686595126&skuId=7937084
That's why I'm thinking I have to return it. :(
Mircea S. wrote:
You don't need the patch to get the LG 21:9 Ultrawide monitor to work. I have the same monitor and it has 2560x1080 which works out of the box even on 2010 mac minis. You need a minidisplayport to displayport cable like this and it will work without issues. http://www.amazon.com/Cable-Matters®-DisplayPort-Thunderbolt-Compatible/dp/B00C7RJQPY
http://www.amazon.com/Cable-Matters%C2%AE-DisplayPort-Thunderbolt-Compatible/dp/B00C7RJQPY
— Reply to this email directly or view it on GitHub https://github.com/vinc3m1/mac-pixel-clock-patch/issues/7#issuecomment-134034870.
@kelleychambers I think this should work if you add the rather odd resolution to your system with SwitchResX. Monitors with a resolution of 2560x1440@60Hz are also supported over hdmi. Oh, also if it turns out you need the patch use mine: https://github.com/Floris497/mac-pixel-clock-patch It is updated every OS X update.
@Floris497 Hi there, I'm hoping that this is the answer to all of my woes! I am trying to connect a 3440x1440 monitor to my MBPr mid-2012. DisplayPort spec is only 1.1. Monitor supports this res @60hz and I can achieve this via windows. But Macs pure grief.
I followed your instructions and downloaded the latest .command file. However, I get the following error message in terminal:
./macPixelClockPatcher.command: line 4: syntax error near unexpected token newline' ./macPixelClockPatcher.command: line 4:'
Thoughts or ideas regarding this issue?
you downloaded the html file of github of the script, not the file :) try downloading the zip
@Floris497 Lol. Oh dear (school boy error) - I'll give it a shot!
Do you think that I will have much success with what I am trying to achieve?
sadly no, 2012 and 2013 machines have a lot of trouble with 4k.. :( 2011 do great and 2014 is supported by apple. but there are succes stories. if you have dedicated graphics i can make a patch for those.
@Floris497 Thanks for the feedback. I hit an issue - while I was applying the patch, I received a dialog box which said that I needed to install xcode tools. I installed it and then attempted to 're-run' the commands; however, now I don't get any feedback in terminal i.e. it doesn't ask me to enter password or anything. Is there a way to roll back and start again?
Hi there.. I managed to roll back and apply again. It went through okay this time as I had downloaded the xcode tools on the previous run. Answering your questions:
- I'm on 10.10.5
- I presently have a dedicated NVIDIA GT650M and an integrated intel 4000 (the GT650M kicks in everytime I connect an external display)
I'm presently trying to fool around with SwitchresX with no joy at all.. I'm adding a custom resolution, reboot, but do not get any status message (it is blank) and of course can't change anything in display settings.. this doesn't look good :/
I can help you tomorrow, for the time, read the other issues, I will see if a can update the NVID patch tomorrow.
@Floris497 Thanks for this.. I just looked at the beta version of SwitchResX, I can see that it talks about SIP there.. I presume this doesn't apply to me (yet) as I don't have El Capitan.. I really hope to get this working! Speak tomorrow :)
@Floris497 Any more thoughts on this? Would be great to have my Mac output 3440x1440@60hz! :)