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.
Thanks @jackluke

Now I am able to login to my beta 10.14.4 MBAir, 2011 by renaming the bundle file.

View attachment 819607

You also mentioned "without acceleration". How can I verify or test the effects of "no acceleration"?

A couple of observations:
  1. Verified that I do not have acceleration.
  2. Running @dosdude1's patch updater reset or setup the HD3000 GL Graphics bundle again. Thus failed to boot. Renamed the bundle folder again and now boots.
You guys think that on the next beta (2) that these anomalies will be fixed? Thanks.
 
Last edited:
Hi,
on my MBP early 2011 on 10.14.3, I have this issue that if photos or goofy message (facebook - message) is running, the mac is lacking and is practically unusable. I have read in this forum that it is related to Intel HD Graphics 3000. I have tried what was sugested here, but did not find a solution. What to do?
 
  • Like
Reactions: TimothyR734
Has anyone else experienced problems waking from sleep? On my 2008 MacPro 3,1 - If the computer goes to sleep, and I wake it up later the screen just stays black and I have to hard restart it. If I put it to sleep, and wake it up a few seconds later SOMETIMES it wakes up, but usually it is the same affect.
Its running a macvidcards GTX 780 Ti, so that should rule out any graphic driver issues. The event log shows a million crashes at the same time as I wake it up. I don't have it in front of me so I don't know what exactly is crashing. I think login UI. This has happened ever since I put mojave on it, but has gotten way worse after 10.14.3.

I have a similar but not identical problem. Sometimes, when my 2008 MBP4,1 (Mojave 10.14.3) goes to sleep, the WiFi needs to be restarted. The frustrating thing is that this is not every time... sometimes, even when it's gone to sleep for 10 hours, no problem; other times, a mere 2 hours and the WiFi, even though it shows 'connected', has to be turned off and on before it resumes functioning. The WiFi card is a BCM94322MC, purchased some 3 years ago. The problem started with Mojave. It is merely frustrating for me, since everything else works. I have googled the problem without success. Perhaps I am asking the wrong questions. Any suggestion/solution will be much appreciated.
 
  • Like
Reactions: TimothyR734
10.14.4 Beta 1 is funny #LoL
(Sorry, on a hack mach --the only one in my hand #atm that having IntelHD 1st Gen / Arrandale gfx).

My PC BIOS has "Display Setting: Auto & LCD Only"). Using exactly same config, AppleIntelHDGraphics* etc as 10.14.3, with LCD Only = Stuck on "IOLock blah blah (not remember exactly)", it never reach LoginUI. With "Display: Auto" it reaches LoginUI - Desktop, but having WhiteScreen (I'm pretty sure gfx / igpu is working, system is up & running, Brightness Fn+Keys, Volume keys are also working with notif sound heard).

Prematurely assummed but it seems, the issue is related to Display (or screen, LinkWidth, or Framebuffer) and not OpenGL related to gfx accel as my prev. report, it's still working on NVDA Fermi. I've tried various AppleIntelHDGraphics* from 10.12 upto 10.13 with similar results.

Using SkyLight, CoreDisplay, CoreGraphics, DisplayServices, IOAccel, OpenCL/GL frameworks from 10.14.3.. dependencies are satisfied on my case, but still.. it's still unable to reach LoginUI #LoL.. will try again with diff. methods. Oh ya, my mach (though it' s h*tosh) is using vanilla system files on LE/SLE except AppleIntelHDGraphics since they're missing from 10.14).

I'd not so much sure that Nvidia Fermi is totally an OpenGL API GPU, it's reported as the natural Nvidia Tesla successor and more over supports the latest Microsoft's "API Direct3D 12" that should be a primeval Metal API:
https://en.wikipedia.org/wiki/Fermi_(microarchitecture)

That said as you well know it's more possible that apple stops the old macs supporting patches than ha**osh scene since can count on Clover almost daily compiled and updated so harder to be stopped.
[doublepost=1549195988][/doublepost]
A couple of observations:
  1. Verified that I do not have acceleration.
  2. Running @dosdude1's patch updater reset or setup the HD3000 GL Graphics bundle again. Thus failed to boot. Renamed the bundle folder again and now boots.
You guys think that on the next beta (2) that these anomalies will be fixed? Thanks.

We will see, @ASentientBot has quickly discovered a good workaround excluding the OpenGL kext, so even if less usable w/o acceleration at least Mojave still boots on 10.14.4.
 
@dosdude1 thank you very much for this Mojave patcher and the APFS ROM patcher. Both are excellent and truly a great contribution to the Mac community.

I’ve patched the ROM on my MacBookPro5,1 (Late 2008) and can now boot APFS Mojave 10.14.3 without the APFS patch and with TRIM working perfectly. Really impressive.

The only bug I’ve encountered so far is that the TrackPad seems to only be detected as a mouse and I cannot modify any system preferences for it.
You mentioned the issue for the MacBook5,2 but this is also present on the MacBookPro5,1 it would seem.

Otherwise it works beautifully. Far better than High Sierra in fact.
Thank you.

One last thing, when using the APFS ROM patcher I had to choose a different EEPROM to the one suggested but it worked fine once I opened up the case and found what it was. See attached images.

IMG_0507.jpeg

IMG_0509.jpg
 
Last edited:
I'd not so much sure that Nvidia Fermi is totally an OpenGL API GPU, it's reported as the natural Nvidia Tesla successor and more over supports the latest Microsoft's "API Direct3D 12" that should be a primeval Metal API:
https://en.wikipedia.org/wiki/Fermi_(microarchitecture)

That said as you well know it's more possible that apple stops the old macs supporting patches than ha**osh scene since can count on Clover almost daily compiled and updated so harder to be stopped.

Yeah, Fermi is bit complicated GPU; Apple's SysInfo said it's Metal Supported one; but OpenGL Extensions Viewer (among many other apps) on the contrary said it doesn't. I'm pretty sure it doesn't.. at least from this MetalInfo.app test.

Anyway, as a workarround for dependencies problem ["Too many corpses being created blah blah blah.."] using diff. frameworks from another macOS version (can't quarantee this will work on your case):
Code:
// Boot Single User: Cmd+S (or RecoveryHD's $ chroot /Volumes/Macintosh\ HD)
// Replace the framework
#root: rm /S*/L*/PrelinkedKernels/prelinkedkernel
#root: rm /S*/L*/Caches/com.apple.kext.caches/Startup/kernelcache
#root: touch /S*/L*/E*
#root: kextcache -q -update-volume /
#root: kextcache -system-caches
#root: update_dyld_shared_cache

Oh hi, my last test using 10.13's AppleIntelHDGraphics* (@dosdude1 Patcher.app uses this version, right?) it stucked on BlackScreen; what interesting is the verbose logs appeared are similar to Clamshell mode did when (for example) Display is connected through VGA Port, while Internal Display (LCD) is closed. A same problem with 10.12's kext (any of 10.14.4 user tried these with IntelHD 1st Gen?), but it leads me to WhiteScreen. #OMG, looks like the only thing that I don't test yet is.. replacing "/S*/L*/Kernels/kernel" from 10.14.3 #LoL :D
[doublepost=1549205096][/doublepost]


You may try /S*/L*/PreferencePanes/Trackpad.prefPane from 10.11.x..???
 

Attachments

  • Screenshot.png
    Screenshot.png
    91.7 KB · Views: 168
Last edited:
You may try /S*/L*/PreferencePanes/Trackpad.prefPane from 10.11.x..???
Great idea! This resolved my exact same issue. Trackpad on MBP 5,1 was not recognized in Mojave (as either trackpad or mouse in System Preferences), though I had full pointer control (no touch or tap gestures of course). Took your suggestion and copied over the Trackpad.prefpane from my El Capitan partition (I dual boot this machine), logged out and then back in, and voila! Immediately recognized the trackpad and I have full control over it again. Thanks!!
[doublepost=1549210336][/doublepost]
@dosdude1 thank you very much for this Mojave patcher and the APFS ROM patcher. Both are excellent and truly a great contribution to the Mac community.

I’ve patched the ROM on my MacBookPro5,1 (Late 2008) and can now boot APFS Mojave 10.14.3 without the APFS patch and with TRIM working perfectly. Really impressive.
I'd like to also compliment DOSDude1 on his excellent work here. It's really quite amazing what he's done. Although I don't really use either my MacBookPro5,1 or MacMini 3,1 anymore, it's still nice to have to them running current OS for those occasions when these systems can be of some assistance to others. And dare I say it, with 8GB of RAM and an SSD, these systems are actually pretty 'snappy', though by no means are performance kings (CPU throttling on the MBP is actually so bad that the mini beats it speed-wise with no audible fan noise, even though the mini's CPU is clocked to 2GHz and the MBP's to 2.53GHz).

Regarding the mention of the MacBookPro5,1 ROM patch: is that something separate from the excellent work done by DOSDude1? I am a bit confused by your comment there...
 
Last edited:
I'd not so much sure that Nvidia Fermi is totally an OpenGL API GPU, it's reported as the natural Nvidia Tesla successor and more over supports the latest Microsoft's "API Direct3D 12" that should be a primeval Metal API:
https://en.wikipedia.org/wiki/Fermi_(microarchitecture)

That said as you well know it's more possible that apple stops the old macs supporting patches than ha**osh scene since can count on Clover almost daily compiled and updated so harder to be stopped.
[doublepost=1549195988][/doublepost]

We will see, @ASentientBot has quickly discovered a good workaround excluding the OpenGL kext, so even if less usable w/o acceleration at least Mojave still boots on 10.14.4.

Thank you @ASentientBot and @jackluke. Please share the workaround excluding the OpenGL kext at your convenience.
 
Thank you @ASentientBot and @jackluke. Please share the workaround excluding the OpenGL kext at your convenience.

I meant ASentientBot already found the workaround disabling the OpenGL feature, so it's possible to boot 10.14.4 beta dropping the OpenGL kext/bundle, then no acceleration available yet, unless another gift with "10.14.4 final full release" but for it we need to wait a while.
 
Great idea! This resolved my exact same issue.

Good to know. The only issue (if I still remember) is; this old prefPane will remain in Light even with DarkMode enabled.. that's if you care about UI than functionalities #LoL

Another workarround is just keep vanilla 10.14.3 Trackpad.prefPane, then replace only Base.lproj located on:
Code:
/System/Library/PreferencePanes/Trackpad.prefPane/Contents/Resources

// Not really sure it'll work on 10.13 or later, I found this issue for the last time with MBP5,2 was on 10.12.
 

Attachments

  • Base.lproj.zip
    61.8 KB · Views: 146
No problems with the 14.3.2 full installer of macOS 10.14.3 as patched by Mojave Patcher 1.2.3 when installing on a Macpro 3,1 with GTX-680.


I just recently put up Mojave 10.14.3 on my Mac Pro 3,1 with an EVGA Nvidia GTX-680 2MB.

But, for whatever reason, I can't get both displays to come up.

During boot, the boot sequence starts on one display (24" Acer), then switches over to the 30" Apple Cinema display. But, when everything is done, only the 30" display is operational. The 24" display never comes up again.

Both monitors are connected to the DVI ports on the card. The 24" has a DVI to VGA adapter on it.

I used the latest version of @dosdude1 Mojave patcher.

I may connect a DVI cable to the 24" display and try that tomorrow.

Any thoughts, suggestions, or ideas? Mojave performance is great with the GTX-680, but I'd like to have both displays operational.

Shawn
 
  • 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!
 
  • Like
Reactions: TimothyR734
Whoa, great work!! This looks like the first real progress on those old cards. @dosdude1 @parrotgeek1

Any more progress here? Im on an iMac mid2011 with 5xxx card and realised in the autumn this wont be easy so i kinda gave up. Been checking in here now and then to see if something changed and it looks so?

@Scrotorr what do you mean with "Mojave Patcher that gimped the 5770 almost completely" ? That its like supported or totaly unsupported?

Wonder if we can hope for a fully functional 10.14 with these machines/gfx cards?
 
  • Like
Reactions: TimothyR734
I just recently put up Mojave 10.14.3 on my Mac Pro 3,1 with an EVGA Nvidia GTX-680 2MB.

But, for whatever reason, I can't get both displays to come up.

During boot, the boot sequence starts on one display (24" Acer), then switches over to the 30" Apple Cinema display. But, when everything is done, only the 30" display is operational. The 24" display never comes up again.

Both monitors are connected to the DVI ports on the card. The 24" has a DVI to VGA adapter on it.

I used the latest version of @dosdude1 Mojave patcher.

I may connect a DVI cable to the 24" display and try that tomorrow.

Any thoughts, suggestions, or ideas? Mojave performance is great with the GTX-680, but I'd like to have both displays operational.

Shawn
Some things to look at. Did you use the legacy video patch? As you have a GTX680 this is not recommended as it can affect the native Mojave drivers for your card.

Which DVI output have you got the DVI to VGA adapter on? It is recommended that this adapter is only used on the DVI-I output not the DVI-D one.

However, I think it is more likely that you have discovered that Mojave does not always play straight with GTX680 cards that have had the efi rom flashed for the Mac as apposed to the specific Mac edition card. Other users have reported that they lost one of the video outputs like you are experiencing. The solution was to use one of the other outputs. The HDMI output may be worth a try. I have no problem using the display port but do not use multiple monitors.
 
Phew. Just installed 10.14.4 beta 2, and it was MUCH less problematic than the first beta. Everything appears to be working smoothly on my 2011 Mac Mini without having to replace any frameworks or kernel extensions.

The mac mini 2011 should have dual graphics, ATI/AMD HD 6xxx and Intel HD 3000, ATI/AMD HD 5xxx/6xxx series have OpenGL disabled by default on their target machines in this thread, could you confirm that using only Intel HD 3000 with OpenGL you still can boot 10.14.4 beta2 with UI transparencies and smooth animations?
 
The mac mini 2011 should have dual graphics, ATI/AMD HD 6xxx and Intel HD 3000, ATI/AMD HD 5xxx/6xxx series have OpenGL disabled by default on their target machines in this thread, could you confirm that using only Intel HD 3000 with OpenGL you still can boot 10.14.4 beta2 with UI transparencies and smooth animations?

I'll dig into that later today, I should have been more precise in my posting: I did not have to do any modifications beyond the original patches that installing 10.14.0 required... presumably all of the framework replacements I had to do to even get 10.14.4 beta 1 working were overwritten by this new build.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.