Would u suggest installing Mojave on a 8,2 MacBook Pro with an AMD 6x series GPU even when it works and its not defective? I feel it is a severely incapacitated machine under Mojave without the dGPU enabled
Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Would u suggest installing Mojave on a 8,2 MacBook Pro with an AMD 6x series GPU even when it works and its not defective? I feel it is a severely incapacitated machine under Mojave without the dGPU enabled
Hi, I have an early 2009 20 inch iMac. I actually use it for light Python program development. Although it has 10 years it actually performs incredibly well because I have installed an SSD and updated the RAM to 8Gb.
I run MacOS El Capitan, and I have some programs incompatibility. I wonder if it is worthy to updated unofficially to Mojave, and if it has any risks. I have checked that the graphics card is compatible and also the wifi.
My main question is that if performance is good in Mojave and if I can upgrade to Mojave without losing my files and programs.
Thank you very much.
I run MacOS El Capitan, and I have some programs incompatibility. I wonder if it is worthy to updated unofficially to Mojave, and if it has any risks. I have checked that the graphics card is compatible and also the wifi.
My main question is that if performance is good in Mojave and if I can upgrade to Mojave without losing my files and programs.
Thank you very much.
Yes Flurry works on .3 , I've tried to understand how Flurry is invoked from 10.14.3, but also replacing the Screensaver.framework doesn't make it work, and playing with Core* framework is not much suited:
Code:
otool -L /System/Library/Screen\ Savers/Flurry.saver/Contents/MacOS/Flurry
/System/Library/Screen Savers/Flurry.saver/Contents/MacOS/Flurry:
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 23.0.0)
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/ScreenSaver.framework/Versions/A/ScreenSaver (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1561.0.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1671.20.103)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1561.0.0)I noticed that I get random kernel panic on 10.14.4 when I do large use of Safari's "websites with GL engine contents".
Other experiments:
- using their stock "OpenGL binary exec" both in 10.14.4 and 10.14.5 still boot correctly the machines;
- can use the stock .5 GPUWrangler.framework only when there is no NDRVShim.kext or other patched IOGraphics IOAccel kext in SLE , so I guess the expert developers here need to update their "Shim" kext.
One more thing: if you want to boot 10.14.5 beta1 from an IntelHD3000 use all the known retro patches in addition with GPUWrangler.framework from 10.14.4 , you will get brightness control, night shift, airplay mirroring and Framebuffer, but no sleep function and no OpenGL acceleration.
Last edited:
Not sure if it has been noted before, but I found some oddities that might be related with the issues ".4 flurry" and ".5 OpenGL" and helpful to resolve at least the more important one of the two ;-)
In 10.14.4 there are two "CoreImage.framework" instances, one directly in /S/L/Frameworks (there v14.2.0) and another one as plugin part of QuartzCore.framework (v.10.3.5). Both have different binary file sizes (7.8MB vs 8.9MB).
Apple seems to have sorted out things (as imho they should be) to only one CoreImage.framework in 10.14.5b1 (v.14.4.0 and size 8.9MB).
(It seems part of an ongoing de-emphasis away from not only OpenGL but also Quartz. Just my interpretation.)
Quick comparison: Yosemite handled it that way that there the ONLY instance of CoreImage.framework is located in the QuartzCore.framework as a plugin.
This might be a valid entry point of correcting things for our unsupported machines.
(I´ve messed around only to the avail that I get "too many corpses being created" at boot time with an unbootable system).
In 10.14.4 there are two "CoreImage.framework" instances, one directly in /S/L/Frameworks (there v14.2.0) and another one as plugin part of QuartzCore.framework (v.10.3.5). Both have different binary file sizes (7.8MB vs 8.9MB).
Apple seems to have sorted out things (as imho they should be) to only one CoreImage.framework in 10.14.5b1 (v.14.4.0 and size 8.9MB).
(It seems part of an ongoing de-emphasis away from not only OpenGL but also Quartz. Just my interpretation.)
Quick comparison: Yosemite handled it that way that there the ONLY instance of CoreImage.framework is located in the QuartzCore.framework as a plugin.
This might be a valid entry point of correcting things for our unsupported machines.
(I´ve messed around only to the avail that I get "too many corpses being created" at boot time with an unbootable system).
I've checked both in 10.13.6 , 10.14.3 , .4 and .5 beta1 and I have only one CoreImage.framework for each Frameworks folder , no other duplicates inside Quartz /QuartzCore framework and inside those Quartz* folders there are no Plugins subfolders.
[doublepost=1554462416][/doublepost]
My forecast: in the worst case we'll have 10.15 without OpenGL Acceleration but still a new bootable OSX from this thread machines.
Anyway to me the "big innovation" with 10.14 was the introduction of dark mode UI, I don't see another news like this in 10.15 maybe universal iOS and macOS apps, I can do without them, new wallpapers and screensaver I can copy them back to Mojave.
Last edited:
Hm. Must then be some leftover from previous installs or related to some patch?
Checked another 10.14.4 machine, no doubles there.
I´ve deleted the CoreImage in the QuartzCore on my MB Air and indeed it does not seem to be missed by any app or function...
Checked another 10.14.4 machine, no doubles there.
I´ve deleted the CoreImage in the QuartzCore on my MB Air and indeed it does not seem to be missed by any app or function...
For me it was homekit and the almost-perfect integration of homepod/airplay2.
I would upgrade to High Sierra instead. High Sierra is still supported by Apple (unlike El Capitan), and almost all programs will still run on it. But because it has been superseded by Mojave, High Sierra will only get security updates that won't break your unsupported installation. With Mojave, you never know if the next version will still work.
Performance with High Sierra will be just as good as with El Capitan, and you won't lose any files and programs if you do an upgrade installation. (You should still have a backup, of course.) You can find dosdude's how-to here: http://dosdude1.com/highsierra/
As far as Flurry is concerned it is definitely sensitive to the OpenGL version. I found an old github project with source here https://github.com/calumr/flurry. May be worth recompiling this sucker against .4 to even .5 OpenGL just for kicks.
Safari and OpenGL is definitely an issue - probably why Apple issued that warning.
The most significant change I found on .4 OpenGL is support for "ExtendedTextures". So the .3 based retro-patches will destabilize any new app or framework leveraging it. Since a plist setting can activate it, it may be worth scanning the system libraries (and preferences) for the string. I'm still not sure how "breaking" a change it is but, even though I don't KP as yet, it may account for the instability some folks are experiencing.
I would like to also scan the .5 OpenGL, GPUSupport, GPUInfo and Wrangler. If you have the time PM me with the stock .5 binaries. My test box is still on .4. I plan on downloading the .5 beta this weekend sometime.
Given @ASentientBot 's excellent work on Tesla kexts before, I am confident an update is coming soon!
[doublepost=1554473919][/doublepost]
Phew! multiple CoreImages would have been bad.
A "High Mojave" without acceleration is a non-starter for me. I agree, I don't (yet) see any game changing features on the horizon for 10.15. I'm still crossing my fingers they don't cripple OpenGL even further, but the signs are not good. Geez Nvidia still hasn't delivered Mojave drivers yet, after almost a year! Not a good sign...
A Dot 4 Success! iMac 11,2 everything works - camera, mic, video accel, did OTA update from .3 on APFS HDD (the original). Had to zap NVRAM to get to option-key selections, rebooted into dosdude1 installer, applied appropriate patches, reboot. Patch updater ran after MRT was done, some patches over-written, reinstalled, reboot. Very nice. EXCEPT!!! The News app which crashes reliably, every time. (The News app in .3 was rock solid.) So far - no random KPs this Mac model. Mini3,1s are mad-bombers in .4.
Ok for Flurry there is a call to OpenGL, but I can assure that it works even without Acceleration, with basic GPU kext loaded.
I already sent OpenGL .5 through pm, since very small can upload the entire .5 frameworks, they still have the original apple "touch" so are "touch" free, I always prefer to keep either kext, framework and binaries with their original modified date.
I am back on 10.14.2 I found an old Mojave patcher 14.0.14 installed it then install the public beta on my iMac 9,1 the updated to 14.0.21 then 10.14.2 it hung at boot up but I had went back to High Sierra created a new High Sierra patcher with dosdude's new updated patcher then applied the post install patches it rebooted once then I was in 10.14.2
I am wondering if Flurry Screensaver and Siri's soundwave are having something in common? Both are working on my 10.14.3 installation and both are not working on my 10.14.4 installation.
Folks, the behaviour of flurry (working without OpenGL but not with it) is exactly the same as I described earlier for the Siri notification "window". After my patching Siri functionality, I noted that on machines without OpenGL the oscilloscope-like sound animation (wave) is displayed, with OpenGL its just a grey rectangle (but both with the response movie bubble).
Seems a common thing to look for...
AVZ was faster. ;-)
Yes I forgot you did. Thanks. I will have fun disassembling .5 OpenGL this weekend, can't wait to see what they've changed (again!) I should have time to download a full .5 beta 1 install too. I'm just limited by the number of machines I can play with.
I skimmed through the Flurry code and only see openGL context calls. No guarantees that this old github project (last update 2014) is current though. Maybe the latest code leverages some other (more cpu intensive) acceleration. Anyway, I am only interested in this screensaver as far as our OpenGL compatibility issues go - maybe some additional clues to what is going on.
You mentioned installing .5 beta1 without using dude's patcher utilities: "...I started from a clean 10.14.5 beta1 with stock Extensions and stock Frameworks...." Is that really the case? You patched the clean image yourself ?
[doublepost=1554488476][/doublepost]
Flurry is doing something special the other savers (like "arabesque" and "shell") don't need. OpenGL programs setup their context to leverage different capabilities, the grey screen just translates to "I can't set my self up correctly on your card" Lots to play with...
I am afraid it poses more questions than answers. I believe that Siri's sound wave on 10.14.3 started working only after I "enabled" the clamshell mode(the way ASentientBot and others did it). I am guessing that those who don't have clamshell mode on their 10.14.3 don't have Siri's sound wave either.
Thanks all of you for the assessment of 10.14.4 and the suggestions.
I use a MBP5,2 17", APFS ROM patch applied. 10.14.4 installed with dosdude's patcher on an external SSD with APFS, Patch Updater fixes installed.
1 - I followed the suggestion to delete the Safari settings. First I did: defaults read com.apple.Safari and was surprised by the amount of settings, then deleted them. Good riddance!
And afterwards: Safari works, doesn't provoke KPs anymore. Using it while writing this post. Just before the delete, I verified that Safari did still make KPs.
2 - Tried to switch from the Nvidia 9600M GT GPU, which I used the last days and now again, to the 9400M. Trying that from system settings + logout/login may have worked but resulted in a black screen, with display backlight on. Even with 10.14.3 it was like this. Then forced 9400M by resetting the NVRAM.
10.14.4 did KP soon after reboot in 9400M mode. After second boot I had enough time to switch to 9600M GT with system settings +logout/login, this time no black screen.
9400M related KPs were only experienced on MBP5,2 I think, not on 5,3.
With the cleaned Safari settings, and 9600M GT, 10.14.4 seems good as default for my work (SSD connected to SATA then). Will report observations of unnormal behaviour, and look forward to 10.14.5 and more...
EDIT: after two days of working with 10.4.4 I got a KP when starting Safari, and another one. I'll continue with .4 but refrain from Safari usage (removed it from the dock). Firefox is good enough for me. Curious to see what else may go wrong and keep me from working with .4 on my MBP5,2.
Last edited:
I am back on 10.14.2 I found an old Mojave patcher 14.0.14 installed it then install the public beta on my iMac 9,1 the updated to 14.0.21 then 10.14.2 it hung at boot up but I had went back to High Sierra created a new High Sierra patcher with dosdude's new updated patcher then applied the post install patches it rebooted once then I was in 10.14.2
10.14.2 even better than 10.14.3 , requires less RAM and probably faster than high sierra.
[doublepost=1554493412][/doublepost]
It worked w/o clamshell, but when you enabled clamshell, do you have still OpenGL Acceleration and transparencies ?
[doublepost=1554493825][/doublepost]
You did disassembled also OpenGL .5 it had SimCity code and others big vendors.
Installing .5 beta1 over a dosdude1 patched Mojave makes it clean in some way, even if I noticed placed some additional kext on /L/E/ so had to remove legacyUSBinject that my machines not needed.
Anyway for my tests I cloned my supported Metal Mac 10.14.5 beta1 and manually patched, and I used the best cloning software IMHO, DiskUtility from a Recovery Environment.
To patch yourself you have to take a copy of any prelinkedkernel from 10.14 , because you need that to enter in single user mode with keyboard and recreate the new kextcache, I also "mv" from there the frameworks.
Last edited:
No. I compared OpenGL 18E226 (.4) with 18D109 (.3). I must have misspoke in a previous reply. I'll check out OpenGL .5 next.
I guess the key to bring back OpenGL acceleration on 10.14.5 is between IOGraphicsFamily.kext, IONDRVSupport.kext for Teslas and IOAcceleratorFamily2.ext for IntelHDs together with AppleGraphicsControl.kext, this last one is a very tricky kext but responsible of everything I guess.
Other tests this time about using a patched Mojave on Metal GPU, considered that a 10.14.3 patched Mojave had Metal acceleration feature, I have observed this:
Replacing GPUWrangler.framework or OpenGL.framework with a previous version, does allow booting from non-Metal GPU Mac but cuts off the Metal acceleration (and OpenGL too for legacy machines), so a Metal GPU will have only frame buffer as a OpenGL GPU.
GPUSupport.framework only is needed to allow Safari to render websites, so is very useful too.
For further tests I think I'll wait for .5 beta2.
I was trying to say that I had to enable clamshell mode first in order to see Siri's soundwave on 10.14.3. Yes, acceleration and transparencies remained intact after enabling clamshell. My understanding is that you absolutely must have clamshell mode working in order to see Siri's soundwave.
Absence of the Siri's soundwave is actually the common issue between 10.14.3 and 10.14.4. I got it fixed on 10.14.3 by enabling clamshell mode. Enabling clamshell mode on 10.14.4 did not return the same result, something about the 10.14.4 that breaks Flurry screensaver and Siri's soundwave.