What is @ASentientBot's fix and how does it help with OpenGL acceleration? would this help me get GPU acceleration back on my 2011 8,1 MBP running Mojave via @dosdude1's patcher??
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
What is @ASentientBot's fix and how does it help with OpenGL acceleration? would this help me get GPU acceleration back on my 2011 8,1 MBP running Mojave via @dosdude1's patcher??
Oh hey -- you're the user who PMed me on reddit, right?
The MacBookPro8,1 has an Intel HD 3000 (not a GeForce as I incorrectly told you before -- sorry about that) so my nVidia Tesla patch (linked on the wikipost) is irrelevant. As for the .5b2 patch I found a couple days ago, it's just an updated version of dosdude1's .4 patch, which allows acceleration on these recent builds. None of this applies to 10.14.3 or earlier.
One thing I'm unclear about is whether you have no acceleration/OpenGL system-wide, or is this an Adobe-specific issue? Please provide more details and we'll be happy to help!
Yeah that's me! :-D I've actually created a thread about my issue here (we can continue discussion there if it's easier), but the gist of it is that yes, my 8,1 Macbook Pro 2011 has an Intel HD 3000 and I'm not sure about whether I have no acceleration system-wide... Graphics all look fine, no weird colours or artifacts, but in Adobe Premiere it definitely says 'Mercury Playback Engine Software Only' with the selection box greyed out, whereas before I updated to Mojave I THINK it was doing some kind of OpenCL or CUDA acceleration, though annoyingly I can't remember 100%.....!! Video playback in Premiere is certainly more choppy now than I remember it before I updated to Mojave, but I don't want to go through all the hassle of downgrading back to High Sierra (if that's even possible without losing all my files as I don't currently have a Time Machine backup of HS) only to find I was mistaken and I didn't even have hardware acceleration back then either....!
So any advice you could give would be much appreciated.
Your fix indeed is relevant also for IntelHD3000, cause they share the same yours IOGraphicsFamily.kext and CoreDisplay.framework to fix OpenGL acceleration on .5 beta2.
The only difference is that for IntelHD3000 are required in addition IOAcceleratorFamily2.kext and IOAccelerator2D.plugin , and of course the IntelHD3000 kexts but from Sierra (it was an earlier Badruzeus post), however dosdude1 in his Mojave Patcher fixed the HighSierra ones so they work both.
Moreover I can assure that using your new 10.14.5accel fix is totally safe also for non-NvidiaTesla machines.
[doublepost=1555439584][/doublepost]
If you own a 13" MBP 8,1 you can surely achieve OpenGL acceleration with IntelHD3000 , CUDA is only for Nvidia.
If you own a 15" or 17" MBP 2011, I cannot help you.
Which Mojave version do you have installed 10.14.3 or .4 ?
Check in your /S/L/E/ if you have these:
AppleIntelHD3000Graphics.kext
AppleIntelHD3000GraphicsGA.plugin
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext
AppleIntelSNBVA.bundle
AppleIntelHD3000GraphicsGA.plugin
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext
AppleIntelSNBVA.bundle
The easiest way either if you have .3 or .4 just use the dosdude1's Post Install "Video Patch" from Mojave Patcher version 1.3.0 .
Last edited:
Hello everyone,
Is there anyone else for whom after getting transparency and vibrancy (with hybrid mode update) for both modes have lost the transparency of the menu bar as well as all the drop-down menus?
If you want top and context menu transparencies (only dark mode) you should use the stock HIToolBox .
But you can use pkouame Hybrid patch also partially, for example replacing only CoreUI.
Last edited:
First of all I need you to confirm that there is OpenGL acceleration on your system. Check transparency of your Dock, menubar, notifications pane and Finder sidebars. If those are transparent, then acceleration is working. If not, this is a system-wide problem (in other words, the legacy video patch is not working). Otherwise this is a Premiere-specific compatibility problem.
The majority of patches just involve bringing over old frameworks, so I don't see why that'd break just Premiere. I can investigate that further if it's the case, though.
Thanks for all the tips! I do indeed own the 13" version, so thanks for confirming that I should have (and have obviously somehow lost) the ability to achieve OpenGL with my IntelHD3000. I can also confirm that I'm running 10.14.4 and I have all of those kets/bundles in my /S/L/E/, and I have also applied @dosdude1's Post Install 'Video Patch' 1.3.0 but even after doing so, STILL no OpenGL in Adobe Premiere....
I had real problems updating from 10.14.3 to 10.14.4 as I didn't read that I had to update the patcher first so I couldn't boot for a while, but then got it fixed somehow.... So I wonder if that hiccup has somehow caused the loss of hardware acceleration within Premiere???
[doublepost=1555442780][/doublepost]
Ah I think this has highlighted a big issue - I have no transparency!! So I'm guessing that means that, for some reason, despite running @dosdude1's video patch, I still don't have OpenGL acceleration running properly on my system....!
Any ideas how to get that working, apart from, you know, running the video patch again (which I have done multiple times as I thought there was something not right....!)
I guess your OpenGL issue occurred when you updated from 10.14.3 to .4 , something mismatched, but @ASentientBot is right, so to try fixing "transparencies" if you have done all the steps, try this as last attempt open Terminal and type or copy-paste one line at once:
sudo chown -R 0:0 /S*/L*/E*/
sudo chmod -R 755 /S*/L*/E*/
sudo kextcache -i /
(this will take a while)
sudo reboot
reboot and maybe this time you'll have UI transparencies that is a OpenGL ready proof.
Last edited:
Thanks so much for the advice; unfortunately after running all that successfully and rebooting, still no system transparencies... What could I have done wrong as far as the video patch tool in the patcher that hasn't worked? I updated it to the latest version....but then I don't know if/how it has updated in my EFI or whatever.....?? Maybe that bit didn't take properly? Maybe the only way is to try re-install Mojave with the latest version of @dosdude1's post-install tool?? Can I do that without erasing my hard drive though??
Last edited:
It's not EFI issue, and apparently you have done all the right attempts to fix that, yes you can re-install Mojave over your current volume without losing datas, then re-apply the Post-Install patches for your machine.
Ok thanks, I guess I'll try that, it'll be good to make sure it's all installed correctly after my slightly tricky failed update last time...!
So further update, I reinstalled Mojave one more time with the latest version of @dosdude1’s patcher and STILL have no System transparencies and therefore I’m guessing no OpenGL hardware acceleration… I ran the post install tools and applied patches, including the video patch, but still nothing… Any ideas how to work out why this is happening/get my hardware acceleration working again?
That's weird, it appears you followed the correct route, one other attempt I guess is a PRAM reset, try after power-on chime to hold ALT+CMD+P+R for about 5 seconds. Then boot again Mojave and check.
Do you have brightness control F1/F2 working ? If so, it means framebuffer SNB is correctly loaded, if not I guess you are in safe mode.
By all accounts, your system is supported here and should accelerate, this is puzzling. If you haven't already, I would completely reinstall Mojave from a 10.14.3 (most reliable) patcher stick. Sometimes we muck around with our systems so much that a re-baseline is in order. If you do, make sure you backup your stuff of course...
EDIT: by completely I mean wipe your disk and install clean. Vestiges of the old OS sometimes remain even if you install on top of it. I do this from time to time to reboot from a clean slate.
Thanks for the suggestion! Yep I have brightness and everything else working. I reset PRAM but still nothing :-/
Hmm I was hoping I wouldn't have to do a format/reinstall as I'm away from home and don't have an easy way to back up all my files.....
I did have 10.14.3 running fine before all this. How easy is it to downgrade from my current .4 back to .3 though? What would it require? How would I make sure .3 was installed on my patcher stick rather than .4?? I really appreciate your help by the way!
EDIT: Ok, I didn't realise this but somehow re-installing Mojave from the stick I had it has gone back to 10.14.3......!! But still no transparency.... So I'm REALLY confused now....! :-D
Did you possibly run an rm command to delete a graphics kext that was preventing booting? This could cause a loss of acceleration, although I would expect that a reinstall of the OS and the legacy graphics patch would fix this.
I'd suggest that posting the output of kextstat might help see if those drivers are even loading. However, I am not super familiar with the Intel HD side of things. I've only got the one nVidia-based MacBook for comparison. But another user might be able to help more.
I second @pkouame's opinion that a wipe and reinstall might be the best option at this point though. If you don't have another drive to backup to, you might make a second partition and store files there temporarily. If you take this route though, be very careful. And setup a backup system soon -- it'll save your ass eventually.
Good luck.
Have the updates been released? And do these bring back acceleration in 10.14.5? Thanks.
@dosdude1 @ASentientBot @jackluke @pkouame.
For my early 2011 MBP 8.1 13" with Intel3000 I have absolutely same story as @peanutismint.
After updating to 10.14.4 from .3 using @dosdude1's patcher 1.3.0 I have no system transparency, Siri wave, Chess and a couple side apps that use OpenGL rendering such as Jump Desktop etc.
I've even tried fresh install .4 on new unused before ssd no luck with above problem. Now I'll going to try to up for .5b2 with @ASentientBot finding of .3 CoreDisplay.framework, and if it fail I'd to go back for .3.
For my early 2011 MBP 8.1 13" with Intel3000 I have absolutely same story as @peanutismint.
After updating to 10.14.4 from .3 using @dosdude1's patcher 1.3.0 I have no system transparency, Siri wave, Chess and a couple side apps that use OpenGL rendering such as Jump Desktop etc.
I've even tried fresh install .4 on new unused before ssd no luck with above problem. Now I'll going to try to up for .5b2 with @ASentientBot finding of .3 CoreDisplay.framework, and if it fail I'd to go back for .3.
I think I am zeroing in on the major differences between the .3 and (.4/.5) graphics subsystem (especially CoreDisplay)
Some very interesting things:
1. CoreDisplay .3 only has a 64 code (yes no 32 bit support). I have no idea...load it in Hopper and you'll see
2. CoreDisplay .5b+ (and probably .4) has both a 32 and 64 bit "universal" structure AND introduces a whole bunch of support for virtual "plug" and "play" screens and displays. This is major and very consistent with all that Apple is doing in this area. I think the home page even has a new article about 10.15 rumors along these lines.
I noted a while ago that .4 OpenGL+ implements new pixel format and virtual screen processing. Now we know why, having almost decommissioned OpenGL, Apple would only touch this framework if it was forced too.
One last thing, while we were all searching for an acceleration solution, I GL profiled the screensavers that worked versus our old finicky friend Flurry. Both Arabesque and Shell implement a more compatible way of setting pixel formats and leveraging offline renderers, hence no problem working on .4 and .5b+. Flurry did (does) not - this sort of may explain why it doesn't work well on our old systems. I used OpenGL Monitor + trace to capture the GL calls while the screensavers were running (blank or black screen is still a running screensaver)
So all of this is starting to make sense : why OpenGL, GPuSupport and CoreDisplay have to form a whole matching set. There are possibly some other dependencies that we haven't stumbled on yet. What's clear is that none of these new features will support our old hardware very well (if at all).
[doublepost=1555510339][/doublepost]
Looks like a trend. Anyone else with an mbp 8.1 having the same issues?
[doublepost=1555511103][/doublepost]
Yes, you can pretty much "a la carte" my patches to your tastes. Some prefer a normal (albeit solid) looking menubar instead of the grey "broken" one in Light Mode. Loss of menubar transparency is not an oversight or preference, just a nut I haven't able to crack elegantly yet. If found, enhancements will be rolled out in the future.
I have a MacBook Pro 8,1 and don’t have these issues. The only thing I’m missing is the Siri sound wave (which doesn’t bother me).
Cool. I you have time, elaborate a little on your installation or upgrade experience. It may help @peanutismint and @MelkorMorgoth . Thanks.