macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

I tried safe mode and used in the terminal sudo nvram boot args=-x to enable it from the Mojave patcher no luck tried renaming OpenGL, removed GeForceTesla.kext, renamed GeForceTeslaGLDriver nothing from command s

To enter forcing safe-mode you should type booting with CMD+S exactly this (quotes, minus symbols, and underscores included):

nvram boot-args="-no_compat_check -x -v"
reboot
[doublepost=1551906886][/doublepost]

Serious??? This is true?
[

they're my suppositions, but on fall 2019 there will be 10.15 for sure, 50% sure 10.15 will no support more 32 bit apps, 10.15 should introduce the universal Apps with iOS devices, 25% sure that these current fixes will be still valid for 10.15 , 5% sure that 10.15 will still installable on HFS+.

 

[avz]

Thanks to @dosdude1 & all for their work - great place here ! Its working now and thus I share my success and a question here:
> Maybe some SSD Models are not compatible / seen by the EFI Bootloade when they are formatted with APFS?

What I did:

1st try with the macOS Mojave Patcher on MacMini4,1 on a Samsung SSD 850 Evo (2nd Drive with HDD , data only):
- freshly reformatted the SSD with APFS
- installed Mojave and the Patches - didn't boot on it
- freshly reformatted the SSD with HFS+ installed Mojave - worked

The second try after zapping P-RAM, fully partitining / reformatting the SSD again with APFS
- freshly reformatted the SSD with APFS
- installed Mojave and the Patches -> and still the SSD didn't want to boot and didn't show up in the StartUPDisks
- rebotted with USB and the Mojave Patch Tool and applied the APFS Patch (as for MacMini3)
-> now an EFI Volume is seen as a startup Disk, it boots after showing a single screen of text (not scrolling).

From what I read the macMini4,1 should be able to boot APFS without the APFS ROM patch or the APFS Patch from the Mojave Patcher - but it seems this is not always the case?

Looks like for you it is just a matter of upgrading to High Sierra first(this should update your firmware) and then you'll be all set for APFS Mojave install.
[doublepost=1551909694][/doublepost]

There my hope died.. actually thought "non-metal support" meant those cards as well. Don't think we will ever see support. Better to upgrade gpu?

I might be wrong but in your particular case "non-metal" is not an issue you should be worrying about.

 

[DragenFi]

I have an Early 2011 13” MBP 8.1 and after following all the instructions I installed a patched version of Mojave on my system. Unfortunately I have found sleep, screen brightness and volume problems that I cannot fix.

I am up to date with all the patch updates and have reset NVRAM and SMC incase the problems were caused by them but it didn’t work.

Starting with the sleep issues, I have tried different scenarios;

If I close the lid the Sleep Indicator Light appears solidly when the screen gets to about three centimetres from closing but the display stays on yet the keyboard lights shut off.

When I set the display to sleep in Energy Saver when the time comes the keyboard lights go out and the Sleep Indicator Light comes on but that’s as far as it goes, it’s the same if I select sleep from the Apple menu.

The only time the display goes dark when I shut the lid is at the login screen but the system doesn’t sleep it just switches off after 30 odd seconds and I have to press the power button to restart.

Next, the brightness keys do not work, and the visual display doesn’t appear on screen and none of the volume keys work but the visual display appears with a circle with a line through when I press any of the volume keys


Are these common issues that people have found that have a fix or do I try going back and trying the installation again? Any help will be very much appreciated.

 

[batboyaka]

So I'm running into a problem with the patched Mojave, I'm trying to partition the APFS mac but it won't let me change the partition size to anything above 155 MB??? I'm trying to install Windows 10 Bootcamp on my mid 2009, 13" MacBook Pro 5,5. I was successfully able to install Windows 10 on an early 2011 13" MacBook Pro 8,1 (after having installed the Mojave Patched OS and a bit of extra work - making sure to use a burned DVD of Win10 iso, etc). I was looking to replicate the process on my Mac but to no avail.

Any suggestions? It seems the disk is locked and when I try in Disk Utility (and the Mojave Patcher USB version of Disk Utility from booting off it). Is there any way to force this process without deleting data? Opening bootcamp assistant says that the HD needs more free space... and there is more than 500 GB available. Disabling SIP have anything to do with this?

 

[hfogel]

If you have transparency of any kind then acceleration is working. Your issue is probably caused by an old application but not just the app file. There are potentially other files made by the app that are causing the issue. I would suggest to try booting in safe mode by holding the shift key on startup.

Thanks for the suggestion,

The system is working nicely, but there isn't any GPU acceleration at least in terms of transparency. On El Cap, I had the Nvidia drivers, and Preference Pane installed, and kept the drivers up-to-date. So I'm curious if that will have any impact on GPU performance. I use Lightroom Classic, which can take advantage of GPU acceleration, along with CUDA. I'm also not sure if LR can tap into the GPU without Mojave support.

My plan is once the system is working and populated, I'll use Carbon Copy Cloner to clone the internal HD to the faster SSD. ill let you know how it goes. I am curious at the advantages and disadvantages of using the new APFS format instead of GUID for the SSD.

 

[scrub10rd]

So installing this patch will more than likely break your FaceTime/iSight camera right?

I should play the lottery tonight. MacbookPro7,1 I was paid with today for doing some IT work for this nice old lady

 

[ASentientBot]

Well, I need to give a HUGE thanks to @parrotgeek1, who figured out this amazing solution... Broadcom BCM94321 WiFi cards are now WORKING under Mojave! If you'd like to test, just download the attached ZIP, extract it, cd into the extracted directory using Terminal, and then run ./install.sh. This should get WiFi working on ALL machines with BCM94321 WiFi chipsets, including the MacMini3,1, MacBookAir2,1, MacBookPro4,1, iMac8,1, and more. Please post results!

View attachment 825032

Absolute legend.

Edit: Looks like the credits need to be updated with @dosdude1's and @parrotgeek1's recent findings. You guys never cease to impress me.
[doublepost=1551933549][/doublepost]

To enter forcing safe-mode you should type booting with CMD+S exactly this (quotes, minus symbols, and underscores included):

nvram boot-args="-no_compat_check -x -v"
reboot
[doublepost=1551906886][/doublepost]

they're my suppositions, but on fall 2019 there will be 10.15 for sure, 50% sure 10.15 will no support more 32 bit apps, 10.15 should introduce the universal Apps with iOS devices, 25% sure that these current fixes will be still valid for 10.15 , 5% sure that 10.15 will still installable on HFS+.

The beta will almost certainly be June 2019. Apple doesn't officially say when 32-bit support will be phased out, but I'd guess 10.16 at the absolute latest. I'm almost certain that a few more releases will boot on our old Macs; the only thing that could permanently stop us would be making core software require SSE4.2. Graphics patches are going to keep getting harder as they move further away from OpenGL, but in the worst case, we can still boot in software rendering mode.

As for HFS+, I don't see why it'll suddenly stop working. They won't remove the drivers for a long time since many disks are HFS+ formatted, and the EFI will always support it. Updates, Time Machine, recovery mode, etc. may become harder to use, but I bet that it'll still boot. And in the worst case, there are @dosdude1's two APFS patches, as well as third-party bootloaders like Clover.

I can't wait for another round of hacking with you guys

Also, two naming-related predictions:
- 10.15 will be called Joshua Tree (the name of a national park in the Mojave desert and a registered trademark of Apple)
- The first release for ARM-based Macs will be called macOS 11.0
Anyone wanna make bets?

 

[SpyderSoldier]

I have an Early 2011 MBP 8.1 and after following all the instructions I installed a patched version of Mojave on my system. Unfortunately I have found sleep, screen brightness and volume problems that I cannot fix.

I am up to date with all the patch updates and have reset NVRAM and SMC incase the problems were caused by them but it didn’t work.

Starting with the sleep issues, I have tried different scenarios;

If I close the lid the Sleep Indicator Light appears solidly when the screen gets to about three centimetres from closing but the display stays on yet the keyboard lights shut off.

When I set the display to sleep in Energy Saver when the time comes the keyboard lights go out and the Sleep Indicator Light comes on but that’s as far as it goes, it’s the same if I select sleep from the Apple menu.

The only time the display goes dark when I shut the lid is at the login screen but the system doesn’t sleep it just switches off after 30 odd seconds and I have to press the power button to restart.

Next, the brightness keys do not work, and the visual display doesn’t appear on screen and none of the volume keys work but the visual display appears with a circle with a line through when I press any of the volume keys


Are these common issues that people have found that have a fix or do I try going back and trying the installation again? Any help will be very much appreciated.

Yeah, happened to me too. 15 incher here, I completely re installed and omitted the removing graphics driver step. if you search up "disabling dGPU MacBook Pro AMD" they will have something in regards to having you move the AMDRadeonX3000 kext which is the one causing the graphics acceleration problem. if you have more questions just reply to this and ill try to find the step by step thread for you

 

[DragenFi]

Yeah, happened to me too. 15 incher here, I completely re installed and omitted the removing graphics driver step. if you search up "disabling dGPU MacBook Pro AMD" they will have something in regards to having you move the AMDRadeonX3000 kext which is the one causing the graphics acceleration problem. if you have more questions just reply to this and ill try to find the step by step thread for you

Ah I haven’t seen that, did it affect the 13” as well as I remember seeing it affecting the 15” and 17” models? Better edit my above comment as forgot to mention the size I have in my original post.

 

[SpyderSoldier]

Ah I haven’t seen that, did it affect the 13” as well? Better edit my above comment as forgot to mention the size in my original post.

hmm. did you apply the dosdude patch where he uninstalls the AMD drivers? that's what broke sleep/wake and brightness toggles for me.

 

[SpyderSoldier]

Ah I haven’t seen that, did it affect the 13” as well? Better edit my above comment as forgot to mention the size in my original post.

https://forums.macrumors.com/thread...fi-variable-fix.2037591/page-35#post-24956091

that's what I was talking about. lifesaver for me, my MacBook works like brand new on Mojave.

 

[DragenFi]

hmm. did you apply the dosdude patch where he uninstalls the AMD drivers? that's what broke sleep/wake and brightness toggles for me.

If it was part of the post install, or part of any patch update I would have to presume yes. Although I have just checked and the 13” only had Intel HD Graphics 3000 where as the 15” and 17” had that and AMD Radeon HD too.

I’m going to have a look at the patches installed on my system.

 

[SpyderSoldier]

If it was part of the post install, or part of any patch update I would have to presume yes. Although I have just checked and the 13” only had Intel HD Graphics 3000 where as the 15” and 17” had that and AMD Radeon HD too.

I’m going to have a look at the patches installed on my system.

sounds good. I don't think you need to apply dosdude graphics driver uninstaller patch because that was only required for the 15 inch models with dGPUs. so maybe look into that

 

[DragenFi]

sounds good. I don't think you need to apply dosdude graphics driver uninstaller patch because that was only required for the 15 inch models with dGPUs. so maybe look into that

Good call! I’ll start there... Thanks for your help.

 

[jackluke]

Absolute legend.

Edit: Looks like the credits need to be updated with @dosdude1's and @parrotgeek1's recent findings. You guys never cease to impress me.
[doublepost=1551933549][/doublepost]
The beta will almost certainly be June 2019. Apple doesn't officially say when 32-bit support will be phased out, but I'd guess 10.16 at the absolute latest. I'm almost certain that a few more releases will boot on our old Macs; the only thing that could permanently stop us would be making core software require SSE4.2. Graphics patches are going to keep getting harder as they move further away from OpenGL, but in the worst case, we can still boot in software rendering mode.

As for HFS+, I don't see why it'll suddenly stop working. They won't remove the drivers for a long time since many disks are HFS+ formatted, and the EFI will always support it. Updates, Time Machine, recovery mode, etc. may become harder to use, but I bet that it'll still boot. And in the worst case, there are @dosdude1's two APFS patches, as well as third-party bootloaders like Clover.

I can't wait for another round of hacking with you guys

Also, two naming-related predictions:
- 10.15 will be called Joshua Tree (the name of a national park in the Mojave desert and a registered trademark of Apple)
- The first release for ARM-based Macs will be called macOS 11.0
Anyone wanna make bets?

Yes, and June is not so far, I read somewhere blog they registered also these names Sequoia, Sonoma and Ventura, but who knows, the most important thing here is that 10.15 will still keep some OpenGL residual, 32 bit support, and I am pros HFS+ too.
Agree with your observations, and most probably macOS 11.0 will drop Intel cpus.

But many future changes I guess are in the air, for example I was reading that on newer 2018 Macs with T2 chip there is no more single user mode CMD+S but only Recovery: https://support.apple.com/en-us/HT201573

edit:
whoops it's reported here also: https://www.macrumors.com/2018/05/25/macos-10-14-trademark-names/

 

[jhowarth]

Thanks. Ok, a bit of an update. More to come later. After numerous tries, installing Mojave as an update to the existing El Cap system, but ending up with a computer that crashed at startup, and reinstalling, etc. to no avail, I tried a different tack. I installed an empty drive in one of the bays of my MacPro 3,1 formatted and partitioned it, installed Mojave on it. And voila, it booted fine, the Nvidia Quadro Fermi 4000 card worked fine, and all was well. That was until I used Migration Assistant to transfer data, settings, etc.. and upon restart, same error and crash at Startup.

So, I installed again, used Migration Assistant to only transfer settings and users, and all is well. I don't know if there is a way to tell if Graphics Acceleration is working. It seems that the problem is with something in my existing system that is crashing the system. The challenge is how to transfer over data and apps on a selective basis. The moral is, as it always has been, start with a clean install.

It would be interesting to find out if upgrading the El Capitan volume to patched High Sierra shows the same issue for you as patched Mojave.
[doublepost=1551960567][/doublepost]

Yes, and June is not so far, I read somewhere blog they registered also these names Sequoia, Sonoma and Ventura, but who knows, the most important thing here is that 10.15 will still keep some OpenGL residual, 32 bit support, and I am pros HFS+ too.
Agree with your observations, and most probably macOS 11.0 will drop Intel cpus.

But many future changes I guess are in the air, for example I was reading that on newer 2018 Macs with T2 chip there is no more single user mode CMD+S but only Recovery: https://support.apple.com/en-us/HT201573

edit:
whoops it's reported here also: https://www.macrumors.com/2018/05/25/macos-10-14-trademark-names/

I could see them dropping the 32-bit binaries from the next macOS just to clear the decks for arm64 fat binaries.

 

[Pinarek]

big thanks dosdude1 for your good work so that again older nVidia graphics cards with Mojave 10.14.4 Beta4 are running with full graphics acceleration. My Hackbook with MCP79 and nVidia 9100M (512 MB) is very good.

 

[DeGarmo]

Well, I need to give a HUGE thanks to @parrotgeek1, who figured out this amazing solution... Broadcom BCM94321 WiFi cards are now WORKING under Mojave! If you'd like to test, just download the attached ZIP, extract it, cd into the extracted directory using Terminal, and then run ./install.sh. This should get WiFi working on ALL machines with BCM94321 WiFi chipsets, including the MacMini3,1, MacBookAir2,1, MacBookPro4,1, iMac8,1, and more. Please post results!

View attachment 825032

I confirm it WORKS on my Mac Pro 3.1! Many thanks to @parrotgeek1!!!

 

[joelw135]

@dosdude1 Will patcher be able to fix the non metal graphics soon?

 

[Larsvonhier]

@dosdude1 Will patcher be able to fix the non metal graphics soon?

Who knows. Until then read #1 and #497 and hack it yourself.

 

[joelw135]

Who knows. Until then read #1 and #497 and hack it yourself.

Well I have tried many times and have failed. I am not to good with terminal.

 

[Larsvonhier]

Well I have tried many times and have failed. I am not to good with terminal.

perhaps I'm not the only one experiencing that the script does not copy the bundles correctly so had to do it manually - but then it worked (on two machines now, MBAir4,1 and MP5,2).

 

[BuffyzDead]

Well, I need to give a HUGE thanks to @parrotgeek1, who figured out this amazing solution... Broadcom BCM94321 WiFi cards are now WORKING under Mojave! If you'd like to test, just download the attached ZIP, extract it, cd into the extracted directory using Terminal, and then run ./install.sh. This should get WiFi working on ALL machines with BCM94321 WiFi chipsets, including the MacMini3,1, MacBookAir2,1, MacBookPro4,1, iMac8,1, and more. Please post results!

View attachment 825032

Worked Perfectly on my 2008 iMac 8,1
AWESOME !!!

 

[K two]

The Mojave patch updater just now updated the built-in WI-FI on this 3,1 Mini, perfectly. No more need for USB WI-FI.

Much thanks to all involved esp. dosdude1.

 

[hfogel]

It would be interesting to find out if upgrading the El Capitan volume to patched High Sierra shows the same issue for you as patched Mojave.
[doublepost=1551960567][/doublepost]

I might just do that when I have time. Create a High Sierra boot drive and see how things work. I did run the patch for WiFi, worked perfectly! Woot!