Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
@DaniloGeekDude 10.14.4beta2 is out, could you do an attempt to update your MBA re-renaming the IntelHD3000 OpenGL bundle2 to bundle and checking if you can reach the desktop with acceleration (transparencies and so on)?

OTA update went fine.

Screen Shot 2019-02-04 at 3.18.08 PM.png

But with the IntelHD3000 OpenGL renamed to original bundle folder name, it failed to boot again. Renamed bundle to backup folder name. Rebooted Fine after. I guess still no acceleration at this beta 2.

Please let me know if you have any other suggestions to have the acceleration enabled.

Thank You.
 
Where is the link to the combo. I would try it with my MacBook Pro 7,1 or my Macmini 3,1 if there were a chance it would work.

Uhmmb.. Forum rules / OP don't allow me providing any link into it.
But this tool will help you building it, your self. Sorry.. it' s for HFS+ only, #AFAICT.
Once you fetched xxx-xxxxx.English.dist, there will be "update-catalogs" file located on "/tmp".
Open it with text editor and Cmd+F for "macOSUpdCombo10.14.4".
So yes, UpdCombo is there even with Beta.
On my case is bit easier with DualBoot, I could run the *.pkg when running 10.11.6 then choose 10.14.x as TargetPartition, that is. DWYOR.
 
Last edited:
OTA update went fine.

View attachment 819918

But with the IntelHD3000 OpenGL renamed to original bundle folder name, it failed to boot again. Renamed bundle to backup folder name. Rebooted Fine after. I guess still no acceleration at this beta 2.

Please let me know if you have any other suggestions to have the acceleration enabled.

Thank You.
You need to re-apply the entire Legacy Video Card Patch... The OTA update overwrites the IOAccelerator bundles.
 
You need to re-apply the entire Legacy Video Card Patch... The OTA update overwrites the IOAccelerator bundles.

..and I guess, PlatformSupport.plist on /S*/L*/CoreServices/ also overrided with new one so.. will also need rolling back from Patcher.app, if we wanna boot on unSupported mach.
 
  • Like
Reactions: TimothyR734
You need to re-apply the entire Legacy Video Card Patch... The OTA update overwrites the IOAccelerator bundles.

Actually, that's what I did (re-ran Patch Updater), which "restored" the IntelHD3000 OpenGL to it's bundle file name. Subsequently, it did not reboot as before. So I had to delete the same bundle file again in-order be able to reboot.

Thanks @dosdude1.
 
You need to re-apply the entire Legacy Video Card Patch... The OTA update overwrites the IOAccelerator bundles.
It's more than that. The WindowServer crashes if it's rendering with OpenGL, confirmed on nVidia Tesla and it seems Intel HD 3000 too. The only way I've found to boot the system is to delete the /S*/L*/E*/*GLDriver.bundle for that GPU. (I just confirmed that all of this is the same on DP2.)

Replacing SkyLight.framework, OpenGL.framework, and others does not fix the issue. Patches for the *GLDriver.bundle probably isn't the way to go since it's happening on Intel and nVidia cards.

I'll upload the WindowServer crash log here so you guys can take a look at it. @Badruzeus @jackluke @0403979 @dosdude1

Hope that helps clarify things a little. Looking forward to hearing of any progress with this! I'll keep testing things.
 

Attachments

  • apparently you can't upload .crash files.zip
    16.9 KB · Views: 186
It's more than that. The WindowServer crashes if it's rendering with OpenGL, confirmed on nVidia Tesla and it seems Intel HD 3000 too. The only way I've found to boot the system is to delete the /S*/L*/E*/*GLDriver.bundle for that GPU. (I just confirmed that all of this is the same on DP2.)

Replacing SkyLight.framework, OpenGL.framework, and others does not fix the issue. Patches for the *GLDriver.bundle probably isn't the way to go since it's happening on Intel and nVidia cards.

I'll upload the WindowServer crash log here so you guys can take a look at it. @Badruzeus @jackluke @0403979 @dosdude1

Hope that helps clarify things a little. Looking forward to hearing of any progress with this! I'll keep testing things.

Thanks. Weird ughh.. I don't see "com.apple.iokit.IOGraphicsFamily" loaded from your *.crash logs.
But this one (if I still remember) also depends on:
Code:
"/S*/L*/E*/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext

Since I'm on a h*ck mach, I'll try using diff. Fake SMBIOS versions (though I don't see it makes any sense, but who know?). I'll take a look into it, just finished my 10.14.4-b2 update on my mach with Fermi; then need backup-restore to one with 1st Gen IntelHD Graphics, as usual.
 
@ASentientBot and @Badruzeus do you have tried to compare the 10.14.4 OpenGL, OpenCL, QuartzCore and Accelerate frameworks with previous 10.14.3 versions, I mean if they differ in byte size (maybe smaller) why don't try to replace with previous ones then checking the WindowServer behavior. I believe in replacing and supporting them even SkyLight is required.

Not yet with binaries comparison, currently having not enogh time doing it.
Are you running 10.14.4 Beta 2? Try using AppleIntelHDGraphics* from 10.12.6 (Sierra).
For IOAccelerator* IOPCI* IONDRV* AppleGraphics* IOGraphics* are native from 10.14.4 Beta 2.
Then try applying this patch for /S*/L*/E*/IOGraphicsFamily.kext/IOGraphicsFamily:
Code:
Find* [HEX]: 01000075 22
Replace [HEX]: 010000EB 22

Don't forget to resign the binary with Xcode, then rebuild-repair prelinkedkernel && kernelcache, update_dyld_shared_cache as usual, reboot:
Code:
sudo codesign -f -s - /S*/L*/E*/IOGraphicsFamily.kext/IOGraphicsFamily
 
Not yet with binaries comparison, currently having not enogh time doing it.
Are you running 10.14.4 Beta 2? Try using AppleIntelHDGraphics* from 10.12.6 (Sierra).
For IOAccelerator* IOPCI* IONDRV* AppleGraphics* IOGraphics* are native from 10.14.4 Beta 2.
Then try applying this patch for /S*/L*/E*/IOGraphicsFamily.kext/IOGraphicsFamily:
Code:
Find* [HEX]: 01000075 22
Replace [HEX]: 010000EB 22

Don't forget to resign the binary with Xcode, then rebuild-repair prelinkedkernel && kernelcache, update_dyld_shared_cache as usual, reboot:
Code:
sudo codesign -f -s - /S*/L*/E*/IOGraphicsFamily.kext/IOGraphicsFamily
I'll try this when I have time.

Could you explain what the hex patch does?
 
I'll try this when I have time.

Could you explain what the hex patch does?

It' s actually, 2nd boot glitch fix. Ah, I just re-test it with 10.14.4 Beta 2 on 1st Gen IntelHD; still having similar issue.. but now the WhiteScreen is blinking every second.. I didn't make IOGraphicsFamily binary comparison a lot #btw
 
  • Like
Reactions: TimothyR734
Hello, I just installed Mojave 10.14.3 on a macbook pro 5,3.
the problems I have, have been discussed here before. But the thread is sooo long. i cannot find a solution.
Can somebody please help?
a) the brightness slider disappears most of the time. i cannot download the "brightness slider app" from the app store due to my non-american apple-ID.
b) my macbook pro does not wake up after sleeping. the display stays black. i need to reboot.
any ideas to solve the problems?
Thank you!
on a MB Pro 5,3 15" I have no issues like this.
Maybe you need to perform an clean install
 
  • Like
Reactions: TimothyR734
It's more than that. The WindowServer crashes if it's rendering with OpenGL, confirmed on nVidia Tesla and it seems Intel HD 3000 too. The only way I've found to boot the system is to delete the /S*/L*/E*/*GLDriver.bundle for that GPU. (I just confirmed that all of this is the same on DP2.)

Replacing SkyLight.framework, OpenGL.framework, and others does not fix the issue. Patches for the *GLDriver.bundle probably isn't the way to go since it's happening on Intel and nVidia cards.

I'll upload the WindowServer crash log here so you guys can take a look at it. @Badruzeus @jackluke @0403979 @dosdude1

Hope that helps clarify things a little. Looking forward to hearing of any progress with this! I'll keep testing things.
Oh, dang... Apple must have made some significant changes in 10.14.4... I'll do some testing of my own soon, and see if I can pinpoint the issue.
 
I haven't been following for a while because I stopped using my unsupported Macs a while ago, but because of the issues I thought I'd try to update to beta 2 on my mbp 15 2011.

So I installed 14.3 first, and then tried to update to 14.4 beta 2.
It hangs, and when it does, all I get is two lines of momentary flashing text every 30 seconds or so in verbose mode. (See picture)

Unfortunately I think it makes sense that apple would eventually remove OpenGL completely.
But at least we can still use 14.3, and maybe security updates could still work.

Edit: did the heating trick with the Dgpu so I could test it. Without AMDRadeonX3000 loaded it goes to white screen and then turns off, with it loaded it gets stuck on white screen, so neither intelhd3000 or Amd work.
 

Attachments

  • 1.png
    1.png
    390 KB · Views: 138
Last edited:
I haven't been following for a while because I stopped using my unsupported Macs a while ago, but because of the issues I thought I'd try to update to beta 2 on my mbp 15 2011.

So I installed 14.3 first, and then tried to update to 14.4 beta 2.
It hangs, and when it does, all I get is two lines of momentary flashing text every 30 seconds or so in verbose mode. (See picture)

Unfortunately I think it makes sense that apple would eventually remove OpenGL completely.
But at least we can still use 14.3, and maybe security updates could still work.

Edit: did the heating trick with the Dgpu so I could test it. Without AMDRadeonX3000 loaded it goes to white screen and then turns off, with it loaded it gets stuck on white screen, so neither intelhd3000 or Amd work.

It's a known issue, @ASentientBot found a workaround in dropping the OpenGL feature, if you can isolate your Mojave booting only to IntelHD3000 then boot holding CMD+S single user mode and rename the /S*/L*/E*/AppleIntelHD3000GraphicsGLDriver.bundle

into AppleIntelHD3000GraphicsGLDriver.bundle2

In this way at next reboot the OpenGL kext of your GPU won't be loaded in the prelinkedkernel and you can reach the desktop.
[doublepost=1549393692][/doublepost]
Yes I understand that, which is why I asked if there was any chance of a fix for this.

There is, post here the result from your Terminal:

diskutil apfs list
 
Yes, @jackluke posted this a while ago and it was discussed again a couple of pages earlier.

https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-347#post-26622208
[doublepost=1549394033][/doublepost]

Edit: and he already replied

It's ok but I guess I made many other (annoying) posts about that, there is another important step to override the platform support hardware check (typically prohibitory symbol guilty) and needs to edit inside the APFS Recovery the com.apple.Boot.plist
adding next to the "BaseSystem.dmg" string this: "BaseSystem.dmg -no_compat_check -v"

In this way at 99% of the times you can pass the prohibitory CMD+R symbol.
 
APFS Recovery is working great! I used DU and did Time Machine system restore to my MacBook5,1's original 160GB HDD connected externally via SATA to USB adapter. The original 160GB HDD is still going strong after 10 years of use.

I don't understand much about the OpenGL issue but I am wondering if GeForce 9400M is going to have the same issues as IntelHD3000?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.