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

macOS 10.14 Mojave on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
10.14.4 is running really well on my Mid-2010 Macbook Pro. Thanks for all of the hard work to those who spent time on this, I'm really happy this machine can run Mojave.

How much better would this machine run with more RAM, is it worth upgrading it? I already have an SSD which has made a massive difference in speed, but I'm still running the 4GB of RAM it came with. I read on Everymac that it unofficially supports 16GB and was wondering if it's worth upgrading to get more performance out of.

Edit: It's a 2.4GHZ Core 2 Duo with the Nvidia Geforce 320M.
 
  • Like
Reactions: webg3 and TimothyR734
ASentientBot said:
PM'ed you.
Click to expand...
Thank you That working perfect ;)
I am really appreciate what you have done

EDIT *** All working nice , Sleep/wake, screen saver

captu603.png
 
Last edited:
  • Like
Reactions: Larsvonhier, jackluke, avz and 3 others
ASentientBot said:
I had a lot of unnecessary replacements. Cleaned things up to the following list, for full acceleration on MacBook7,1:

from 10.13.6 (same as before):
/S*/L*/E*/NVDAResmanTesla.kext
/S*/L*/E*/NVDANV50HalTesla.kext
/S*/L*/E*/GeForceTesla.kext (with my previous patch)
/S*/L*/E*/GeForceGA.bundle
/S*/L*/E*/GeForceTeslaGLDriver.bundle
/S*/L*/E*/GeForceTeslaVADriver.bundle

plus:
NDRVShim (or alternative*)

plus, from 10.14.3:
/S*/L*/P*F*/GPUSupport.framework
/S*/L*/F*/OpenGL.framework
/S*/L*/F*/CoreDisplay.framework

I don't, however, have brightness control or sleep working yet. Brightness control and sleep are working fine now. I'm not clear on what changed though...

Also, not sure if you and @dosdude1 and co. saw my previous message about it, but it seems that USB patches are no longer necessary for functional keyboard and touchpad, at least on this MacBook.

Please test and report your findings!

* Replacing IONDRVSupport.kext and IOGraphicsFamily.kext will also provide a working _VSLGestalt symbol without the shim kext. However, this now causes some other (non-fatal) errors during boot. Alternately, NVDAResmanTesla.kext itself can be "fixed" to not need the symbol at all by NOP-ing the call to _VSLGestalt and editing the "VSLGestalt" in the string table to a different (existing) function name of the same length (I used "IOLockLock"). However, @parrotgeek1's shim kext is obviously cleaner and simpler than either of these.

Update: Siri and News+ are still crashing. I'm tentatively suspecting some SSE4.2-related shenanigans may be the culprit. I'll investigate further. Flurry is fine though, and I'm not seeing any of the blur-related weirdness that @jackluke (I think?) mentioned earlier.

Finally, to everyone reading this: Hold onto a copy of 10.14.3 if you decide to update. Please.
Click to expand...
CoreDisplay completing the GL retro-patch makes sense to me from my logging of what Flurry and other GL based programs are currently blocking on... I am still on .4 and will see how that affects the GL environment.

Thanks - some good spelunking...
 
  • Like
Reactions: tenortim, webg3, jackluke and 3 others
pkouame said:
CoreDisplay completing the GL retro-patch makes sense to me from my logging of what Flurry and other GL based programs are currently blocking on... I am still on .4 and will see how that affects the GL environment.

Thanks - some good spelunking...
Click to expand...
Awesome. I'd be curious if replacing CoreDisplay.framework on .4 would fix some of the weirdness there too.
 
  • Like
Reactions: webg3, jackluke, avz and 1 other person
ASentientBot said:
I had a lot of unnecessary replacements. Cleaned things up to the following list, for full acceleration on MacBook7,1:

from 10.13.6 (same as before):
/S*/L*/E*/NVDAResmanTesla.kext
/S*/L*/E*/NVDANV50HalTesla.kext
/S*/L*/E*/GeForceTesla.kext (with my previous patch)
/S*/L*/E*/GeForceGA.bundle
/S*/L*/E*/GeForceTeslaGLDriver.bundle
/S*/L*/E*/GeForceTeslaVADriver.bundle

plus:
NDRVShim (or alternative*)

plus, from 10.14.3:
/S*/L*/P*F*/GPUSupport.framework
/S*/L*/F*/OpenGL.framework
/S*/L*/F*/CoreDisplay.framework

I don't, however, have brightness control or sleep working yet. Brightness control and sleep are working fine now. I'm not clear on what changed though...

Also, not sure if you and @dosdude1 and co. saw my previous message about it, but it seems that USB patches are no longer necessary for functional keyboard and touchpad, at least on this MacBook.

Please test and report your findings!

* Replacing IONDRVSupport.kext and IOGraphicsFamily.kext will also provide a working _VSLGestalt symbol without the shim kext. However, this now causes some other (non-fatal) errors during boot. Alternately, NVDAResmanTesla.kext itself can be "fixed" to not need the symbol at all by NOP-ing the call to _VSLGestalt and editing the "VSLGestalt" in the string table to a different (existing) function name of the same length (I used "IOLockLock"). However, @parrotgeek1's shim kext is obviously cleaner and simpler than either of these.

Update: Siri and News+ are still crashing. I'm tentatively suspecting some SSE4.2-related shenanigans may be the culprit. I'll investigate further. Flurry is fine though, and I'm not seeing any of the blur-related weirdness that @jackluke (I think?) mentioned earlier.

Finally, to everyone reading this: Hold onto a copy of 10.14.3 if you decide to update. Please.
Click to expand...
Hi - yours is a single GPU macBook right? I'm on a dual-gpu mbp 5,3 and just tried adding .3 CoreDisplay to my .4 patched mbp 5,3 and still the same GL behavior (Flurry, Chess, News+ etc.)

I think @jackluke noted some differences between single and dual GPU machines

I will OTA upgrade my .4 to .5b2 (again) and apply dude's post-install + CoreDisplay : that should equate to your recommended configuration. Last time I tried this it wasn't pretty...I'll report.
[doublepost=1555302188][/doublepost]
ASentientBot said:
Awesome. I'd be curious if replacing CoreDisplay.framework on .4 would fix some of the weirdness there too.
Click to expand...
It worked! .5b2 Accelerated after an OTA update from .4 using 1.30 post-install + .3 CoreDisplay.framework.

Thanks to @ASentientBot for finding the secret sauce... You beat us all to it! (Glad you did)

Tested on : mbp 5,3 dual Nvidia GPUs APFS previously on .4 (see below)

I took the simple route : adding CoreDisplay.framework to @dosdude1 's 1.30 post-install legacyGPUPatch.sh (and the .3 CoreDisplay.framework to the gfxshared folder of course). Proof:

Screen Shot 2019-04-15 at 12.10.39 AM.png


By the way, Flurry running as well as other OpenGL based screensavers now.

I will leave this up and running for a while to test reliability and benchmark, but it's already humming and doing well.

Thanks.

EDIT: I meant legacyGPUPatch.sh
 
Last edited:
  • Like
Reactions: tenortim, Larsvonhier, K two and 8 others
boyan said:
Hi guys,

Thank you for the amazing patches and support.
I have Macmini3,1 and managed to upgrade the os to 10.14.4 after converting file system to apfs, running the installator and applying the patches from the tool ver 1.3.0

Unfortunately my computer started crashing without a reason.
The crashes are happening at random sequence.

This is the system report.
Could you help me to solve that problem.
Thank you

Code: 
Sun Apr 14 22:34:53 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8ee962ee): "Bad tailq elm 0xffffff80217c55a0 next->prev != elm"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-945.250.134/nx/obj.c:2080
Backtrace (CPU 0), Frame : Return Address
0xffffff911abbb580 : 0xffffff800d9af82d
0xffffff911abbb5d0 : 0xffffff800daeb795
0xffffff911abbb610 : 0xffffff800dadcf4a
0xffffff911abbb680 : 0xffffff800d95cae0
0xffffff911abbb6a0 : 0xffffff800d9af247
0xffffff911abbb7c0 : 0xffffff800d9af093
0xffffff911abbb830 : 0xffffff7f8ee962ee
0xffffff911abbb870 : 0xffffff7f8ee95873
0xffffff911abbb970 : 0xffffff7f8ee74d19
0xffffff911abbba40 : 0xffffff7f8ee74ba5
0xffffff911abbbab0 : 0xffffff7f8ee753e4
0xffffff911abbbbd0 : 0xffffff7f8ee99394
0xffffff911abbbc50 : 0xffffff7f8ee926fe
0xffffff911abbbcf0 : 0xffffff7f8ee91f91
0xffffff911abbbdd0 : 0xffffff7f8ee9185b
0xffffff911abbbe40 : 0xffffff7f8eea770e
0xffffff911abbbf50 : 0xffffff7f8eea75c8
0xffffff911abbbfa0 : 0xffffff800d95c0ce
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(945.250.134)[ED6CC0AB-28A7-3677-AC9F-762D613F91DA]@0xffffff7f8ede6000->0xffffff7f8eee6fff
            dependency: com.apple.kec.corecrypto(1.0)[5AB8B6D3-C4F2-3457-A0D5-EB3A341EB22B]@0xffffff7f8e6c7000
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[AC061D0B-F4FF-34BB-9B05-9A9FC01DF807]@0xffffff7f8ed52000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[C322B8D1-C27F-3EFA-8A45-D7035ACC8D07]@0xffffff7f8e585000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check

Mac OS version:
18E226

Kernel version:
Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64
Kernel UUID: 4170BF94-38B6-364F-A1B0-2F7C2C30F9A9
Kernel slide:     0x000000000d600000
Kernel text base: 0xffffff800d800000
__HIB  text base: 0xffffff800d700000
System model name: Macmini3,1 (Mac-F22C86C8)

System uptime in nanoseconds: 1097400196754
last loaded kext at 252255787741: com.apple.filesystems.msdosfs    1.10 (addr 0xffffff7f8ea86000, size 69632)
last unloaded kext at 313033199448: com.apple.driver.AppleUSBMergeNub    900.4.2 (addr 0xffffff7f90377000, size 12288)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp    5.2.22
org.virtualbox.kext.VBoxNetFlt    5.2.22
org.virtualbox.kext.VBoxUSB    5.2.22
org.virtualbox.kext.VBoxDrv    5.2.22
com.parrotgeek.NDRVShim    1
com.parrotgeek.SIPManager    1
com.apple.filesystems.smbfs    3.3.2
com.apple.fileutil    20.036.15
com.apple.driver.AppleBluetoothMultitouch    96
com.apple.driver.AppleHWSensor    1.9.5d0
com.apple.filesystems.autofs    3.0
com.apple.driver.ApplePlatformEnabler    2.7.0d0
com.apple.driver.AGPM    110.25.2
com.apple.driver.AppleHDA    281.52
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleMCCSControl    1.5.6
com.apple.AGDCPluginDisplayMetrics    3.30.14
com.apple.driver.AudioAUUC    1.70
com.apple.driver.AppleHV    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.GeForceTesla    10.0.4
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleOSXWatchdog    1
com.apple.iokit.IOBluetoothSerialManager    6.0.11f4
com.apple.driver.pmtelemetry    1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.driver.AppleLPC    3.1
com.apple.driver.AppleIRController    354
com.apple.iokit.SCSITaskUserClient    408.250.3
com.apple.filesystems.apfs    945.250.134
com.apple.driver.AppleVirtIO    2.1.3
com.apple.filesystems.hfs.kext    407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.BootCache    40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.AppleSystemPolicy    1.0
com.apple.private.KextAudit    1.0
com.apple.driver.AirPort.Brcm4331    800.21.31
com.apple.driver.AppleFWOHCI    5.6.0
com.apple.nvenet    2.0.22
com.apple.driver.AppleAHCIPort    329.200.2
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleAPIC    1.7
com.apple.driver.AppleIntelCPUPowerManagementClient    220.0.0
com.apple.nke.applicationfirewall    190
com.apple.security.TMSafetyNet    8
com.apple.driver.AppleIntelCPUPowerManagement    220.0.0
com.apple.driver.AppleBluetoothHIDKeyboard    208
com.apple.driver.AppleHIDKeyboard    208
com.apple.iokit.IOUSBUserClient    900.4.2
com.apple.driver.IOBluetoothHIDDriver    6.0.11f4
com.apple.driver.AppleMultitouchDriver    2440.7
com.apple.driver.AppleInputDeviceSupport    2440.2
com.apple.kext.triggers    1.0
com.apple.driver.DspFuncLib    281.52
com.apple.kext.OSvKernDSPLib    528
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.nvidia.classic.NVDANV50HalTesla    10.0.4
com.apple.iokit.IOAVBFamily    740.1
com.apple.plugin.IOgPTPPlugin    740.2
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.iokit.IOSkywalkFamily    1
com.apple.nvidia.classic.NVDAResmanTesla    10.0.4
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.iokit.IOFireWireIP    2.3.0
com.apple.driver.AppleSSE    1.0
com.apple.iokit.IOSurface    255.4.2
com.apple.AppleGPUWrangler    3.30.14
com.apple.AppleGraphicsDeviceControl    3.30.14
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.driver.AppleHDAController    281.52
com.apple.iokit.IOHDAFamily    281.52
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.iokit.IONDRVSupport    530.51
com.apple.iokit.IOGraphicsFamily    530.60
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    6.0.11f4
com.apple.iokit.IOBluetoothHostControllerUSBTransport    6.0.11f4
com.apple.iokit.IOBluetoothHostControllerTransport    6.0.11f4
com.apple.iokit.IOBluetoothFamily    6.0.11f4
com.apple.driver.usb.AppleUSBHub    1.2
com.apple.driver.AppleUSBAudio    315.6
com.apple.driver.usb.IOUSBHostHIDDevice    1.2
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.2
com.apple.iokit.IOSCSIMultimediaCommandsDevice    408.250.3
com.apple.iokit.IOBDStorageFamily    1.8
com.apple.iokit.IODVDStorageFamily    1.8
com.apple.iokit.IOCDStorageFamily    1.8
com.apple.iokit.IOSerialFamily    11
com.apple.filesystems.hfs.encodings.kext    1
com.apple.iokit.IOAHCISerialATAPI    267.50.1
com.apple.iokit.IOAHCIBlockStorage    301.250.5
com.apple.iokit.IO80211Family    1200.12.2
com.apple.driver.corecapture    1.0.4
com.apple.iokit.IOFireWireFamily    4.7.3
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.iokit.IOAHCIFamily    288
com.apple.driver.usb.AppleUSBEHCIPCI    1.2
com.apple.driver.NVSMU    2.2.9
com.apple.driver.usb.AppleUSBOHCIPCI    1.2
com.apple.driver.usb.AppleUSBOHCI    1.2
com.apple.driver.usb.AppleUSBEHCI    1.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.driver.AppleUSBHostMergeProperties    1.2
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.quarantine    3
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.DiskImages    493.0.0
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    456.250.6
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.iokit.IOUSBMassStorageDriver    145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice    408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily    408.250.3
com.apple.iokit.IOStorageFamily    2.1
com.apple.kext.CoreTrust    1
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.iokit.IOReportFamily    47
com.apple.iokit.IOTimeSyncFamily    740.2
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.pthread    1
com.apple.kec.Libm    1
com.apple.kec.corecrypto    1.0

EOF
Model: Macmini3,1, BootROM MM31.00AD.B00, 2 processors, Intel Core 2 Duo, 2.66 GHz, 8 GB, SMC 1.35f1
Graphics: kHW_NVidiaGeForce9400Item, NVIDIA GeForce 9400, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0000, -
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0000, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Bluetooth: Version 6.0.11f4, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB
Serial ATA Device: PIONEER DVD-RW  DVRTS08
USB Device: USB Bus
USB Device: IR Receiver
USB Device: USB PnP Sound Device
USB Device: USB Bus
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
Thunderbolt Bus:
Click to expand...
Hi @dosdude1 any ideas about that problem. Thanks
 
  • Like
Reactions: K two
TianjinMBP said:
Oh, I keep copies of everything! :D
[doublepost=1555285093][/doublepost]I have a question and wondering if you've pondered this as well... My backup devices are HFS+ format from back when we all were. Now that I've upgraded to Mojave and APFS, should I reformat my backup devices to APFS as well? I'm wondering about a full recovery in that they are very different filesystems.

Any thoughts?
Click to expand...
My machines are formatted as APFS, my backups are all HFS, and there is absolutely no problem in restoring from them.

Cheers :)

Hugh
 
  • Like
Reactions: jackluke, roronl and TianjinMBP
ASentientBot said:
I had a lot of unnecessary replacements. Cleaned things up to the following list, for full acceleration on MacBook7,1:

from 10.13.6 (same as before):
/S*/L*/E*/NVDAResmanTesla.kext
/S*/L*/E*/NVDANV50HalTesla.kext
/S*/L*/E*/GeForceTesla.kext (with my previous patch)
/S*/L*/E*/GeForceGA.bundle
/S*/L*/E*/GeForceTeslaGLDriver.bundle
/S*/L*/E*/GeForceTeslaVADriver.bundle

plus:
NDRVShim (or alternative*)

plus, from 10.14.3:
/S*/L*/P*F*/GPUSupport.framework
/S*/L*/F*/OpenGL.framework
/S*/L*/F*/CoreDisplay.framework

I don't, however, have brightness control or sleep working yet. Brightness control and sleep are working fine now. I'm not clear on what changed though...

Also, not sure if you and @dosdude1 and co. saw my previous message about it, but it seems that USB patches are no longer necessary for functional keyboard and touchpad, at least on this MacBook.

Please test and report your findings!

* Replacing IONDRVSupport.kext and IOGraphicsFamily.kext will also provide a working _VSLGestalt symbol without the shim kext. However, this now causes some other (non-fatal) errors during boot. Alternately, NVDAResmanTesla.kext itself can be "fixed" to not need the symbol at all by NOP-ing the call to _VSLGestalt and editing the "VSLGestalt" in the string table to a different (existing) function name of the same length (I used "IOLockLock"). However, @parrotgeek1's shim kext is obviously cleaner and simpler than either of these.

Update: Siri and News+ are still crashing. I'm tentatively suspecting some SSE4.2-related shenanigans may be the culprit. I'll investigate further. Flurry is fine though, and I'm not seeing any of the blur-related weirdness that @jackluke (I think?) mentioned earlier.

Finally, to everyone reading this: Hold onto a copy of 10.14.3 if you decide to update. Please.
Click to expand...

Amazing work!

Will give a try later with my usual non-clever tests.

edit:
Using the stock .5 beta2 AGC kext group, even if I get some AppleGraphicsDevicePolicy and AppleMuxControl unresolved symbols the graphics acceleration now does work fine especially with your CoreDisplay framework fix.

And I noticed is possible to use also the .4 OpenGL and GPUSupport if are being used too the IOGraphicsFamily, IONDRVSupport, IOAccel* from .4 , but I guess it doesn't worth it since they work the same way with .3 OpenGL and GPUSupport.

Your CoreDisplay fix does bring back .5 beta2 Acceleration also on dualGPUs machines and IntelHD graphics.

@pkouame did already tested dualGraphics but it was a dual Nvidia Tesla machine, I just confirm it works too on dual mixed GPUs machines.

And I add your "non-metal 10.14.5accel fix" works perfectly on IntelHD3000 single GPU machines.

From .5 beta2 I don't have more the News+ tab from News.app so can't test it.
 
Last edited:
  • Like
Reactions: pkouame, avz, ASentientBot and 2 others
ASentientBot said:
Awesome. I'd be curious if replacing CoreDisplay.framework on .4 would fix some of the weirdness there too.
Click to expand...

CoreDisplay.framework did not seem to resurrect Flurry, Siri's soundwave and Chess.app on 10.14.4. I am wondering if you are getting Siri's soundwave on 10.14.5?
In any case it seems that there is a chance that 10.14.5 might be even better than 10.14.4. Great news!
 
Last edited:
  • Like
Reactions: K two, webg3 and jackluke
ASentientBot said:
Awesome. I'd be curious if replacing CoreDisplay.framework on .4 would fix some of the weirdness there too.
Click to expand...

@ASentientBot , I misunderstood a bit your post, here is my clarification:

pre-edit:
I've tested and can confirm that 10.14.5 beta2 does work also with the .4 CoreDisplay compiled by apple on March 28th, while the one I guess you used for your fix was compiled on February 5th.

re-edit:
Instead, using the .3 CoreDisplay on 10.14.4 does NOT fix the Flurry issue and other GL side effects (Chess, Siri and maybe others on the way).

So after your fix 10.14.5 beta2 is considered better than 10.14.4 .

I attach it, if you want to test .4 CoreDisplay on your .5 beta2, it does still work even keeping the .3 OpenGL and GPUSupport (the dosdude1 10.14.4accel patch) and it's just a way to keep a more recent CoreDisplay framework, that's all.

Anyway Flurry screensaver after your CoreDisplay patch is working correctly on .5 beta2 accelerated.

THANKS!
 

Attachments

  • 10144CoreDisplay.framework.zip
    538.6 KB · Views: 430
Last edited:
  • Like
Reactions: Larsvonhier, K two, ASentientBot and 2 others
avz said:
CoreDisplay.framework did not seem to resurrect Flurry, Siri's soundwave and Chess.app on 10.14.4. I am wondering if you are getting Siri's soundwave on 10.14.5?
In any case it seems that there is a chance that 10.14.5 might be even better than 10.14.4. Great news!
Click to expand...

I find agree, legacy OpenGL acceleration (after ASentientBot fix) works better on .5 beta2 than 10.14.4 final build.

You know, to me Flurry screensaver working again is a clear signal that all the main "GL issues" are gone, apart the Siri oscilloscope wave that @gosvamih has already tested, another big proof is that, I've tested right now, Chess.app version 3.16 is working correctly on .5 beta2 OpenGL rendering accelerated.

These are positive signals that on late June 10.15 with OpenGL will be still possible.
 
Last edited:
  • Like
Reactions: Larsvonhier, pkouame, avz and 3 others
michaelrommel said:
Thank so much guys! I had a look at all the threads, especially the one "Flacko" linked to and it seems, that either 14.3 is the end of the line for me or I have to go the way of the CPU upgrade, which on a normal PC I would do in a hearbeat, but where I am scared is that complicated process of delidding and also getting the torque right without breaking the CPU tray (which one cannot easily replace here in Germany - I think...).



I tried already various combinations and settings with some effect but no ultimate success.

Thanks anyway guys! Great help here!!
Click to expand...

I looked a little deeper and apparently there's a good chance that the issue is connected to the older CPUs.
It seems like there is an incompatibility between the cMP 4,1 only CPUs and Mojave.
(Which would actually make sense since the E5520 wasn't used in the original cMP 5,1)
I would suggest a CPU upgrade which is pretty easy if you buy already delidded CPUs.

I just read that you're located in Germany.
Have a look at this link: https://www.ebay.de/itm/2x-Intel-Xe...853385?hash=item543a267b89:g:HO4AAOSwNRdX78VP
I bought from this seller a couple of years ago and everything was fine.
Mac-Factory is also a really nice shop in Berlin, they have an ebay store as well.
(Though I didn't see a delidded X5690 at their store)
If you use delidded CPUs it would be quite hard to break the CPU tray. Most of the time this happens when people are using lidded CPUs on the 4,1 dual CPU board. Don't do that.
If you untighten the screws, do it in a cross pattern.
Start with the lower left and just do two turns with the screwdriver.
Go to the upper right and do the same.
Next one would be the upper left and after that the lower right.
Then back to the lower left, where you started and give it two more turns, etc.
Repeat this until all the screws are loose. Always hold the heatsink by its sides and never use force.
Tighten the screws the same way you've untighten them before.
It is really not that complicated. Just make sure you have enough time and the right tools. There are many tutorials out there, not all of them are good but it might help you to get an impression.

Viel Erfolg!
 
Last edited:
  • Like
Reactions: michaelrommel and Larsvonhier
Does the option with the exchange of the core.Display from 10.14.3 also with my nVidia 9100M Tesla graphics, in the laptop Medion Akoya P8610 with MCP79 nForce Chipdatz? under 10.14.5 Beta 2
 
Kyle4 said:
10.14.4 is running really well on my Mid-2010 Macbook Pro. Thanks for all of the hard work to those who spent time on this, I'm really happy this machine can run Mojave.

How much better would this machine run with more RAM, is it worth upgrading it? I already have an SSD which has made a massive difference in speed, but I'm still running the 4GB of RAM it came with. I read on Everymac that it unofficially supports 16GB and was wondering if it's worth upgrading to get more performance out of.

Edit: It's a 2.4GHZ Core 2 Duo with the Nvidia Geforce 320M.
Click to expand...

I have the same hardware as you, I opted upgrade to 8GB and then to 16GB, the system is not very different between 8GB and 16GB, however if you work with Final Cut Pro or Logic Pro, you will notice a big difference with the amount of memory.

What makes this machine better is the SSD.

NVidia GeForce 320m is much better than any Intel HD Graphics 2000-4000
 
  • Like
Reactions: ASentientBot and 480951
michaelrommel said:
Thank so much guys! I had a look at all the threads, especially the one "Flacko" linked to and it seems, that either 14.3 is the end of the line for me or I have to go the way of the CPU upgrade, which on a normal PC I would do in a hearbeat, but where I am scared is that complicated process of delidding and also getting the torque right without breaking the CPU tray (which one cannot easily replace here in Germany - I think...).



I tried already various combinations and settings with some effect but no ultimate success.

Thanks anyway guys! Great help here!!
Click to expand...
I would be very tempted to go with a cpu upgrade. A quick search on eBay for delidded Xeon produced some very reasonable prices. I would think using a delidded cpu would be a straight forward process. You would also benefit from a performance boost. Good luck
 
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