Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Remove 165 MHz pixel clock limit; 4K over HDMI; overclocking

From reading the source i was afraid it was not the IOkit :(
I searched/looked at the differences in all the source files in the graphics sub project, but was not able to find anything.. Maybe it is a limit in the gpu specific kext files? I'm not a pro in this but maybe i can find something :). But i hope someone does it before me :)

I'm missing some headers to compile the iokit straight from the tarbal. Did not had the time to find them.
 
Hi folks!

Do you reckon this patch can do the job with Mac Pro too? (it's running HDMI 1.4 and I cannot understand why it doesn't support that anyway). VGA is AMD FirePro D300 (FireGL V)

Many thanks in advance!
 
dmayle said:
Have you been able to replace a manually compiled version of IOKit with the provided version? If you've got any pointers, I'm all ears.

As it turns out, Yosemite requires code signing all of the way down. I've disabled the kernel code signing requirement for kexts (nvram boot-args kext-dev-mode=1), but since IOKit was previously signed, you have to sign it (and use the flag -deep which wasn't in the current version).

With all of that, I'm able to get a patched IOKit running, but it still doesn't work to enable 4k (even with my modified patch that disables the new pixel clock patch). I'd love to compile from source and stick in all sorts of logging to see what's actually going wrong, but haven't been up to the effort of figuring that part out.
Click to expand...

I followed Floris' instructions and patched my 10.10.1 IOKit manually and signed it, but I have no way of knowing what the current pixel clock is set at? My two custom resolutions in SwitchResX show as "Not activated - invalid?" but I set them straight from the monitor's EDID text export:

Code: 
Descriptor #0 - Timing definition:
        Mode = 3840 x 2160 @ 59.997Hz
                Pixel Clock............. 533.25 MHz             Non-Interlaced

                                        Horizontal              Vertical
                Active.................. 3840 pixels            2160 lines
                Front Porch.............   48 pixels               3 lines
                Sync Width..............   32 pixels               5 lines
                Back Porch..............   80 pixels              54 lines
                Blanking................  160 pixels              62 lines
                Total................... 4000 pixels            2222 lines
                Scan Rate............... 133.312 kHz             59.997 Hz

                Image Size..............  621 mm                 341 mm
                Border..................    0 pixels               0 lines

                        Sync: Digital separate with
                                * Negative vertical polarity
                                * Positive horizontal polarity

I am trying all of this on non-apple hardware with an Asus PB287Q, but it works in Windows.
 
Last edited:
striatedglutes said:
I am trying all of this on non-apple hardware, but it works in Windows.
Click to expand...

I've posted some experience of me with editing the Frame buffer,
but i have no idea i what way this might damage hardware. (probably not)

I actually used some hackintosh tools.

be warned I found it quite hard to reset kext files..
even when deleting caches and the kext i might just load from idk where..

booting in safe mode is sometimes handy because it does not load the kext if it was altered,

https://code.google.com/p/mac-pixel-clock-patch/wiki/Documentation
read the comments there, it might helps you to get 4k.

good luck!

PS: can you post your results if your going to try it?
 
floris497 said:
I've posted some experience of me with editing the Frame buffer,
but i have no idea i what way this might damage hardware. (probably not)

PS: can you post your results if your going to try it?
Click to expand...

Looks like with Yosemite it might indeed not have anything to do with the pixel clock and more to do with a framebuffer? I'll look into that option more.
From https://code.google.com/p/mac-pixel-clock-patch/wiki/Documentation:

Your tip has worked for me. I copied only the AppleIntelFrameBufferCapri? kext from Mavericks to Yosemite using the Kext Utility and instructions from mmc above (but not using the AppleIntelHD4000Graphics kext). After rebooting, the System Report showed that the older version of the Frame Buffer kext was loaded as intended (version 8.28.32). Then applied the pixel clock patch command and rebooted. Then 4K display became available and works!

This is on a Mac Mini 2012 with Intel HD 4000 graphics.
Click to expand...

@Bill - Glad you figured it out. Seems my assumption was correct it was a change to driver and had nothing to do with pixel patch.
Click to expand...

Another option of mine might just be to install Mavericks instead and give that a shot.

Edit: Using Mavericks kexts for Azul didn't help. My last ditch effort would be to install Mavericks itself, but I'm not up for that tonight.
 
Last edited:
I managed to sort of "brick" my late 2012 dual core i5 Mac Mini (Intel HD4000) running 10.9.5 (Mavericks) doing this.
Machine starts booting, but gets stuck in some infinite loop of trying to choose an appropriate screen resolution. My Seiki 39" 4K keeps making an annoying sound and then occasionally displays 1920x1080 @ 60Hz message as it syncs up, only to lose it and then change over.
Not sure how to recover from this, as I stupidly didn't make a backup of the OS or files touched by this patch. Luckily, I religiously back up important files (docs, code, ... :), so I'm not worried about that.

If I can't recover from this easily, I may reinstall OS. Just trying to decide if I should downgrade to Mountain Lion (where apparently things worked out of the box), or if I should just reinstall Mavericks.

I may drop in a different graphics card in my MacPro and move that machine over to drive the Seiki 4k and move the Mac Mini back to the living room to drive the 1080p display.

Inexpensive and quiet graphics card recommendations for a MacPro 4,1?
I might also do the 5,1 flash and CPU upgrade at some point.





dmayle said:
The test version of the patch for 10.9.5 which removes both checks to IOKit can be applied with:

Code: 
sudo perl -i.bak -pe '$before = qr"\x0F\x85\x9D\x03\x00\x00"s;s/$before/\xE9\x84\x03\x00\x00\x90/g;$before2 = qr"\x25\x26\x00\x48\x85\xC9\x74\x10"s;s/$before2/\x25\x26\x00\x48\x85\xC9\xEB\x11/g' /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
Click to expand...
 
rpseguin said:
I managed to sort of "brick" my late 2012 dual core i5 Mac Mini (Intel HD4000) running 10.9.5 (Mavericks) doing this.
Machine starts booting, but gets stuck in some infinite loop of trying to choose an appropriate screen resolution. My Seiki 39" 4K keeps making an annoying sound and then occasionally displays 1920x1080 @ 60Hz message as it syncs up, only to lose it and then change over.
Not sure how to recover from this, as I stupidly didn't make a backup of the OS or files touched by this patch. Luckily, I religiously back up important files (docs, code, ... :), so I'm not worried about that.

If I can't recover from this easily, I may reinstall OS. Just trying to decide if I should downgrade to Mountain Lion (where apparently things worked out of the box), or if I should just reinstall Mavericks.

I may drop in a different graphics card in my MacPro and move that machine over to drive the Seiki 4k and move the Mac Mini back to the living room to drive the 1080p display.

Inexpensive and quiet graphics card recommendations for a MacPro 4,1?
I might also do the 5,1 flash and CPU upgrade at some point.
Click to expand...

clearing the nvram helps most of the times, for intel 4000 you can use the old appleIntelframebufferCapr.kext (or modify it) this gives you back 4k, you can reinstall your OS without loosing any files.
 
floris497 said:
clearing the nvram helps most of the times, for intel 4000 you can use the old appleIntelframebufferCapr.kext (or modify it) this gives you back 4k, you can reinstall your OS without loosing any files.
Click to expand...


Thanks! That is helpful!

I reset the NVRAM and booted and it did the slow cycling/blinking back and forth, having a hard time for a while, but then it gave me a login window.
I was able to log in.
I went into /System/Library/Frameworks/IOKit.framework/Versions/A/

And, as root, I did:
mv IOKit Broken-IOKit.bad
mv mv IOKit.bak IOKit

Rebooted and seems happier now.
So... where is one to find the "old" appleIntelframebufferCapr.kext that will provide 4K on the Mac Mini Intel HD4000? My Mac Mini is running OS X Mavericks 10.9.5

Thanks!

bash-4.2# pwd
/System/Library/Extensions
bash-4.2# ls -ald AppleIntel*
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelCPUPowerManagement.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelCPUPowerManagementClient.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelFramebufferAzul.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelFramebufferCapri.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD3000Graphics.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD3000GraphicsGA.plugin
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD3000GraphicsGLDriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD3000GraphicsVADriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD4000Graphics.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD4000GraphicsGLDriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD4000GraphicsVADriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD5000Graphics.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD5000GraphicsGLDriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHD5000GraphicsVADriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHDGraphics.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHDGraphicsFB.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHDGraphicsGA.plugin
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHDGraphicsGLDriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHDGraphicsVADriver.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelHSWVA.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelIVBVA.bundle
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelLpssDmac.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelLpssGspi.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelLpssSpiController.kext
drwxr-xr-x 3 root wheel 102 Jan 16 2014 AppleIntelMCEReporter.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelSNBGraphicsFB.kext
drwxr-xr-x 3 root wheel 102 Sep 19 2013 AppleIntelSNBVA.bundle
 
Last edited:
rpseguin said:
Thanks! That is helpful!
So... where is one to find the "old" appleIntelframebufferCapr.kext that will provide 4K on the Mac Mini Intel HD4000? My Mac Mini is running OS X Mavericks 10.9.5
Click to expand...

from a backup where you had 4k on an older os, but I think you figured that out.
(if so see this as info for people with the same problem.)
 
floris497 said:
from a backup where you had 4k on an older os, but I think you figured that out.
(if so see this as info for people with the same problem.)
Click to expand...

I have 4K working from my mini-DisplayPort on my late 2011 17" MacBook Pro running OS X 10.8.5 (Mountain Lion), so I will have a gander at grabbing the file from there.

I've had a weird spate of bad luck in the last day or two with some of my adapters or cables or something going bad on my Mac Mini i5 dual core and on my 17" MBP.

And I recently bought an Asus Nvidia GTX 660 Direct Cu II 2GB card used off of craigslist and it appears to run ok, but in the last 2 days I have had a number of spontaneous kernel panics where the machine will reset itself with no associated behavior. The kernel panics appear to be errors in trying to read from the PCIe card... :-(

Here's a "typical" panic report:
Anonymous UUID: 615142AF-2D55-9AC8-1A89-BD74B0C613F1

Sat Jan 17 09:30:27 2015
panic(cpu 4 caller 0xffffff7f878a3bb9): NVRM[0/5:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x8a000000 0xffffff81b9230000 0x0e6000a1, D0, P0/4
Backtrace (CPU 4), Frame : Return Address
0xffffff81b8a1b3f0 : 0xffffff8006e22f79
0xffffff81b8a1b470 : 0xffffff7f878a3bb9
0xffffff81b8a1b530 : 0xffffff7f8796debe
0xffffff81b8a1b570 : 0xffffff7f8796df2e
0xffffff81b8a1b5e0 : 0xffffff7f87ba29de
0xffffff81b8a1b650 : 0xffffff7f879909e5
0xffffff81b8a1b670 : 0xffffff7f878aa65d
0xffffff81b8a1b720 : 0xffffff7f878a8168
0xffffff81b8a1b920 : 0xffffff7f878a9ab7
0xffffff81b8a1b9f0 : 0xffffff7f8872e32b
0xffffff81b8a1bac0 : 0xffffff7f886bfb0b
0xffffff81b8a1baf0 : 0xffffff7f886be2f4
0xffffff81b8a1bb70 : 0xffffff80072cfbfa
0xffffff81b8a1bb90 : 0xffffff80072d075e
0xffffff81b8a1bbf0 : 0xffffff80072ce1af
0xffffff81b8a1bd40 : 0xffffff8006eb6998
0xffffff81b8a1be50 : 0xffffff8006e26bc1
0xffffff81b8a1be80 : 0xffffff8006e139c5
0xffffff81b8a1bef0 : 0xffffff8006e1e013
0xffffff81b8a1bf70 : 0xffffff8006ec9b9d
0xffffff81b8a1bfb0 : 0xffffff8006ef4196
Kernel Extensions in backtrace:
com.apple.nvidia.driver.NVDAResman(8.2.6)[272B6397-FEDB-32FC-9035-BDD749284455]@0xffffff7f87853000->0xffffff7f87ac6fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f874bf000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xffffff7f8783d000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f877fa000
dependency: com.apple.AppleGraphicsDeviceControl(3.6.22)[91D61DEC-2946-3790-8134-B808C016C4C9]@0xffffff7f8784d000
com.apple.nvidia.driver.NVDAGK100Hal(8.2.6)[EF73AF59-A574-3A5A-B410-7E4F2DA819B0]@0xffffff7f87ad2000->0xffffff7f87c7efff
dependency: com.apple.nvidia.driver.NVDAResman(8.2.6)[272B6397-FEDB-32FC-9035-BDD749284455]@0xffffff7f87853000
dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f874bf000
com.apple.iokit.IOAcceleratorFamily(98.23)[73D02C7B-A281-36D1-8443-5ADBE18A5EAE]@0xffffff7f886a8000->0xffffff7f88700fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f874bf000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f877fa000
com.apple.GeForce(8.2.6)[75C77E44-A947-3C15-B812-1DF761D61AFD]@0xffffff7f8870d000->0xffffff7f8879bfff
dependency: com.apple.iokit.IOAcceleratorFamily(98.23)[73D02C7B-A281-36D1-8443-5ADBE18A5EAE]@0xffffff7f886a8000
dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f874bf000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xffffff7f8783d000
dependency: com.apple.nvidia.driver.NVDAResman(8.2.6)[272B6397-FEDB-32FC-9035-BDD749284455]@0xffffff7f87853000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f877fa000

BSD process name corresponding to current thread: WindowServer

Mac OS version:
13F34

Kernel version:
Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64
Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0
Kernel slide: 0x0000000006c00000
Kernel text base: 0xffffff8006e00000
System model name: MacPro4,1 (Mac-F221BEC8)

System uptime in nanoseconds: 672976040776
last loaded kext at 249207297097: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f87c93000, size 65536)
last unloaded kext at 309669780818: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f88fc3000, size 8192)
loaded kexts:
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AGPM 100.14.34
com.apple.iokit.IOBluetoothSerialManager 4.2.7f3
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.driver.AppleHDA 2.6.3f4
com.apple.GeForce 8.2.6
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.7f3
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.iokit.IOUSBAttachedSCSI 1.0.5
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.iokit.SCSITaskUserClient 3.6.7
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AppleUSBHub 683.4.0
com.apple.driver.Intel82574L 2.6.2b1
com.apple.driver.AppleUSBXHCI 683.4.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.driver.IOBluetoothHIDDriver 4.2.7f3
com.apple.driver.AppleMultitouchDriver 245.13.1
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOAcceleratorFamily 98.23
com.apple.nvidia.driver.NVDAGK100Hal 8.2.6
com.apple.nvidia.driver.NVDAResman 8.2.6
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.7f3
com.apple.iokit.IOSurface 91.1
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.iokit.IOBluetoothFamily 4.2.7f3
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.7
com.apple.driver.AppleUSBHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.7
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.7
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IO80211Family 640.36
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 686.4.1
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacPro4,1, BootROM MP41.0081.B08, 8 processors, Quad-Core Intel Xeon, 2.26 GHz, 14 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GTX 660, NVIDIA GeForce GTX 660, PCIe, 2048 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463531323732415A2D3147314131
Memory Module: DIMM 2, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463531323732415A2D3147314131
Memory Module: DIMM 6, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x394A53463132383732415A2D314731443120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.7f3 14616, 3 services, 23 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: SSD2SB200GC2DH16T-T, 200.05 GB
Serial ATA Device: Hitachi HDS723030BLE640, 3 TB
Serial ATA Device: Hitachi HDS722020ALA330, 2 TB
Serial ATA Device: WDC WD30EZRX-00MMMB0, 3 TB
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: Backup+ Desk
USB Device: USB 3.0 HUB

USB Device: Backup+ Desk
USB Device: USB 2.0 HUB

USB Device: Hub
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: CP 1350C
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
 
Hi, I have 4k working on my macbook air, however I'm missing the HiDPI scale option for the 2560 x 1140 resolution, any ideas why that might be? Thanks.
 
matt.r said:
Hi Floris, certainly. I have a Mid 2012 Macbook Air(Intel HD Graphics 4000) and a Dell P2715Q. I used this(https://code.google.com/r/darkvoid-mac-pixel-clock/source/browse) in order to get the 3840x2160 resolution to show and be usable. The only issue I'm running into is the 2560x1140 is missing(all others are there) which makes it a little unusable for me right now.
Click to expand...

Do you use SwitchResX? you can make custom resolutions and select HiDPi resolutions.

you have to activate some HiDPi settings, google it (there are a lot of how-to's on this), but you can see/select them all with SwitchResX.
 
floris497 said:
Do you use SwitchResX? you can make custom resolutions and select HiDPi resolutions.

you have to activate some HiDPi settings, google it (there are a lot of how-to's on this), but you can see/select them all with SwitchResX.
Click to expand...

Thanks, however I can't seem to enter anything for the "scale to" option, I attached a screenshot.

-- Edit --
Looks like I had to set it as a "scaled" resolution in the dropdown. Rebooting to see if it works.
 

Attachments

  • Screen Shot 2015-03-15 at 11.48.57 AM.png
    Screen Shot 2015-03-15 at 11.48.57 AM.png
    303.7 KB · Views: 380
I'm currently trying to get a scaled resolution of 2560 x 1140 by choosing a scaled resolution of 5120x2280 in SwitchResX (which from what I read is how you do it), however I'm currently getting "Not Activated - Invalid?". I also have HiDPI enabled on OS X.
 

Attachments

  • Screen Shot 2015-03-15 at 12.31.08 PM.png
    Screen Shot 2015-03-15 at 12.31.08 PM.png
    223.6 KB · Views: 402
Last edited:
Yep that is a hardware limitation.. The pixelclock barely supports 4k but it does on 2011 and 2012 machines, but not on the 2013 machine. 5k is to much for a HD 4000. There is a slight chance that it is possible when altering the framebuffer kext. But i recommend you not to play around with kext files if you have no idea what you are doin.
 
floris497 said:
Yep that is a hardware limitation.. The pixelclock barely supports 4k but it does on 2011 and 2012 machines, but not on the 2013 machine. 5k is to much for a HD 4000. There is a slight chance that it is possible when altering the framebuffer kext. But i recommend you not to play around with kext files if you have no idea what you are doin.
Click to expand...

That's a real shame :/ 1920x1080 is a bit too large in my opinion and true 4k is way too tiny.
 
Last edited:
This thread is really interesting, so I have a mid 2012 non-retina MBP with the Nvidia GT650M, and I'm trying to figure out my best method of connecting it to a 4k display. I'm guessing that most people on this threat are using the built-in HDMI that was included on many models.

My laptop only has the Displayport 1.1 and USB. When using a passive MDP to HDMI adapter, it would seem that the 165mhz pixel clock limit is in play (as any resolution close to or over that value doesn't work in switchresx). I have a MDP to Displayport cable on its way but I'm not sure that will be any better.

Currently the best resolution that I can get is 3360x1890 at 24hz.

I have successfully patched the IOKIT from 10.10.5, but it doesn't seem to make any difference to the resolutions that will work.

Does the use of an "active" MDP to HDMI adapter make any difference?

Thanks.
 
jthunder said:
This thread is really interesting, so I have a mid 2012 non-retina MBP with the Nvidia GT650M, and I'm trying to figure out my best method of connecting it to a 4k display. I'm guessing that most people on this threat are using the built-in HDMI that was included on many models.
...
...
Click to expand...

EDIT: Ooops, you actually asked about the active adapters. I would definitely recommend trying one. I've been using them for years on various mac models, and generally they'll open up more options as the OS sees the connection as DP rather than HDMI.

Or you could go full eGPU using your thunderbolt port and get 4k x 60Hz. Much more of a pain to setup, but you have the side benefit of having a much, much better GPU.
 
Interesting - I hadn't seen any of the eGPU stuff before, seems pretty costly - I'll pick up an active adapter first and see how that goes.
 
jthunder said:
Interesting - I hadn't seen any of the eGPU stuff before, seems pretty costly - I'll pick up an active adapter first and see how that goes.
Click to expand...

With regards to active adapters, you should know that the Intel integrated graphics are wired up in such a way as to have two different pixel clocks for external displays, one for external display port, and one for HDMI. When you use a passive adapter, the graphics chip sees that an HDMI display has been connected to the displayport, and sends out an HDMI signal, using the HDMI pixel clock. When you use an active adapter, the adapter pretends to be an external display port device, and the graphics chip uses the display port pixel clock. At the time these older graphics chips were designed, the expectation was that display port displays had more capabilities, so that pixel clock was higher.

On the model you're talking about, you have both the GT 650M, and Intel HD graphics 4000, which is specifically a chip that's affected.

You should know that one of the Macbook models with dual graphics (may have been the first or second) was wired so that the external displays would only be handled by the discrete GPU, and not by the integrated graphics. If that has continued, it may be that having an active adapter will not help you.

If you get the active adapter anyway, and it's not helping, try disabling the discrete graphics, as the Intel HD graphics 4000 with this patch (OS X 10.9 or lower) is known to output 4k@30Hz
 
jthunder said:
This thread is really interesting, so I have a mid 2012 non-retina MBP with the Nvidia GT650M, and I'm trying to figure out my best method of connecting it to a 4k display. I'm guessing that most people on this threat are using the built-in HDMI that was included on many models.

My laptop only has the Displayport 1.1 and USB. When using a passive MDP to HDMI adapter, it would seem that the 165mhz pixel clock limit is in play (as any resolution close to or over that value doesn't work in switchresx). I have a MDP to Displayport cable on its way but I'm not sure that will be any better.

Currently the best resolution that I can get is 3360x1890 at 24hz.

I have successfully patched the IOKIT from 10.10.5, but it doesn't seem to make any difference to the resolutions that will work.

Does the use of an "active" MDP to HDMI adapter make any difference?

Thanks.
Click to expand...

The patch does not patch the latest Nvidia drivers. Try instaaling the nvidia web drivers, they might allow you to do more! Good luck
 
floris497 said:
The patch does not patch the latest Nvidia drivers. Try instaaling the nvidia web drivers, they might allow you to do more! Good luck
Click to expand...

Nvidia web drivers for OSX 10.10.5? Can you offer any pointers or links? Maybe there is a way to disable the discreet graphics altogether to test just the HD4000? More research required.

This is all starting to make a lot more sense thanks damsel and floris497. I couldn't find any web drivers for this specific card for OSX, I was able however to find a slight increase using switchers 3456x1944@24hz almost the full 4k resolution (no audio) using the passive mdp -> hdmi adapter.

I have a mini-displayport to displayport cable coming soon, and once I can test that I'm hoping that the Nvidia card will allow it to go much higher than the 165hz. It looks like I might not have to use the USB3 4k adapter at all, and that would be good to support the clamshell mode too (which doesn't work with the USB displaylink adapters).

Thanks again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back