macOS 10.14 Mojave on Unsupported Macs Thread

[Martyimac]

What you mean by saying "it wont upgrade" ?

Sometimes when a beta is used, my experience has been if one has the GM through the beta program, once the actual GM is released, the system sees you already have the most up to date version and does not do the update. It has been hit or miss which is why I said assuming it wont upgrade. When I used the mojave patcher method before, it did not upgrade, on demand. It said I had the most current version. I had to start from scratch, again, with the dosdude1 patcher program to get the final release.

Make sense?

 

[Starplayr]

While reduceTransparency is a legitimate workaround for the ugly grey menu bar, I find that it has too broad a system impact: effectively zapping transparency all over the place - especially the dock etc. You're left with a dock and notification sidebar panel (for example) that are barely visually functional. At least for my poor eyes...

I found a software switch in HIToolbox that simply turns menu bar transparency OFF. Unfortunately it is not available as a setting, environment variable or default - the equivalent of an HIMenuBarOpaque application plist setting would have been really nice, but Apple doesn't always make this easy.

Anyway, it's a one byte patch that easily (and harmlessly) flattens the menu bar to white or black (Light or Dark mode) but preserves all other functional transparencies. See below:
View attachment 781474 View attachment 781475

PM me if you're interested in the details or want to test the HIToolbox DB11 patch. At least it takes care of the grey menu bar (without affecting general transparency/vibrancy) which in my opinion is the most egregious aspect of the Light mode bug.

As far as AppKit and the ugly sidebars (in Finder and other apps), swapping Light mode processing for Dark mode is still an option (per my previous screenshots) but has some side effects I am not pleased with: dark window bars and obscured function bars in some apps. I've found that these "modes" are not consistently implemented - for example while my "Hybrid" mode looks good for the Finder AppStore and Xcode, News and iTunes look a little quirky. Still work in progress.

Can this menu bar option become a system pref? That would be ideal.

 

[Wooser]

If it's the model with an AMD Radeon HD 6xxx series GPU, sleep mode will not work due to lack of graphics acceleration.
[doublepost=1536896915][/doublepost]
Nah, I'm going to revise the Legacy Video Card Patch in the post-install tool to not install by default on systems with the Radeon HD 5xxx and 6xxx series GPUs. That will make that issue not happen. In fact, I'd highly advise that you DON'T run Mojave on systems with these GPUs, simply due to the extremely poor performance, the system running much hotter than normal, and the lack of features such as sleep mode.

Hi, I registered just to reply and point something out about this. I am on an early 2011 15" MBP with a dead video card since the Sierra days. I have used three different methods to disable the GPU and force the computer to use the Intel HD 3000 graphics instead, including dosdude1's method. His resulted in the lack of sleep and brightness functionality in both High Sierra and Mojave for me, causing a lot of excess heat and poor performance.

This method was made by someone else on the forum, but I can't remember the thread or user. I'm very sorry for the lack of credit, but I believe this will save at least the macs running AMD 6xxx chips from being totally unusable. I cannot say if this works for the 5xxx chips since I don't have a machine with that chip.

I do want to point out that this method makes it so an external display cannot be used and I have found using Photoshop and FCPX for major editing is pretty much impossible. If you're in the same boat as me where the card is completely dead anyway and you still want a laptop for basic things that aren't graphically intense, I'd give this a try before giving up.

Right now on High Sierra my CPU is idling at 61°C and has, so far, been the same in Mojave (installed on a second hard drive) with fully functional backlight adjustment and sleep. It lags a bit at first when, say, clicking the apps folder from the dock for the first time after boot, but it only happens at first.

To enable this fix, install Mojave and run the post install tools as usual including the legacy video card patch. Once rebooted, follow the steps in the attachment. I have found that, unlike High Sierra, Mojave doesn't place the AMDRadeonX3000.kext file back into the extensions folder, so there is no need to re-run the Legacy Video Card Patch or do these steps after every update. You will have to run the "force-iGPU-boot.sh" again in single user mode if your NVRAM or SMC gets reset, but I haven't had any major problems with Mojave since using this fix. I specified Mojave because High Sierra required moving the kext back and re-doing the process after every update.

I really hope this helps and wish everyone the best.

Thank you all for your diligent work and especially dosdude1 who gave me the hope of running Mojave at all.

Edit: Sorry, I forgot to mention that the graphical anomalies are still present in Mojave with this GPU fix, it just fixes the backlight, sleep and heat problems.

 

[Vyzantion]

Re-downloaded the installer app this morning, re-installed the OS, I wanted to get Public Beta 10 as a clean install. This time, I have swtiched from APFS to HFS+ for performance issues. The install worked quite well, the OS was fine, but I was back on PB 9. This time, no update for PB 10 whatsoever. Both the Apple Beta Acces utility and the Dosdude1 app only download the full installer of PB 9. Has PB 10 been pulled out? Was it the GM realsed by mistake as PB 10?

 

[jackluke]

Hi, I registered just to reply and point something out about this. I am on an early 2011 15" MBP with a dead video card since the Sierra days. I have used three different methods to disable the GPU and force the computer to use the Intel HD 3000 graphics instead, including dosdude1's method. His resulted in the lack of sleep and brightness functionality in both High Sierra and Mojave for me, causing a lot of excess heat and poor performance.

This method was made by someone else on the forum, but I can't remember the thread or user. I'm very sorry for the lack of credit, but I believe this will save at least the macs running AMD 6xxx chips from being totally unusable. I cannot say if this works for the 5xxx chips since I don't have a machine with that chip.

I do want to point out that this method makes it so an external display cannot be used and I have found using Photoshop and FCPX for major editing is pretty much impossible. If you're in the same boat as me where the card is completely dead anyway and you still want a laptop for basic things that aren't graphically intense, I'd give this a try before giving up.

Right now on High Sierra my CPU is idling at 61°C and has, so far, been the same in Mojave (installed on a second hard drive) with fully functional backlight adjustment and sleep. It lags a bit at first when, say, clicking the apps folder from the dock for the first time after boot, but it only happens at first.

To enable this fix, install Mojave and run the post install tools as usual including the legacy video card patch. Once rebooted, follow the steps in the attachment. I have found that, unlike High Sierra, Mojave doesn't place the AMDRadeonX3000.kext file back into the extensions folder, so there is no need to re-run the Legacy Video Card Patch or do these steps after every update. You will have to run the "force-iGPU-boot.sh" again in single user mode if your NVRAM or SMC gets reset, but I haven't had any major problems with Mojave since using this fix. I specified Mojave because High Sierra required moving the kext back and re-doing the process after every update.

I really hope this helps and wish everyone the best.

Thank you all for your diligent work and especially dosdude1 who gave me the hope of running Mojave at all.

Edit: Sorry, I forgot to mention that the graphical anomalies are still present with this GPU fix, it just fixes the backlight, sleep and heat problems.

Sorry, I don't have understood one step, if you use the:

sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext

without leaving that kext into the stock Extensions folder, that FrameBuffer kext will be partially loaded and you will have backlight and sleep working on ATI/AMD 6xxx series ?

edit:
Just noticed you wrote about graphics anomalies, so never mind my message.

 

[Wooser]

Sorry, I don't have understood one step, if you use the:

sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext

without leaving that kext into the stock Extensions folder, that FrameBuffer kext will be partially loaded and you will have backlight and sleep working on ATI/AMD 6xxx series ?

From what I understand (I did not make that method) it uses the loginhook at the end of the process to point the system to the moved kext for backlight and sleep functionality but uses the HD 3000 for the graphic acceleration for everything else. Since the kext is no longer in the extensions folder, it doesn't try to load by default, so the loginhook can tell the system how to use it post boot.

 

[TimothyR734]

I applied pkuaome's hybrid patch and jackluke's looks good Thank you

 

[Starplayr]

on pro 3.1 - my mac edition GTX 680 reports 5.0 GT/s in slot 1 with Link Width x8

I’ e read people getting better performance from some cards in slot 2 on 3,1. What is strange i

Sometimes when a beta is used, my experience has been if one has the GM through the beta program, once the actual GM is released, the system sees you already have the most up to date version and does not do the update. It has been hit or miss which is why I said assuming it wont upgrade. When I used the mojave patcher method before, it did not upgrade, on demand. It said I had the most current version. I had to start from scratch, again, with the dosdude1 patcher program to get the final release.

Make sense?

It’s been reported you need to be on APFS for the system pref software Updater to work. Funny thing is I applied the APFS patch for 3,1 but the Dosdude1 installer won’t let me install on an APFS volume. I even tried cloning to an APFS Volume and it won’t bless.

I have gotten APFS to work once the last with Clover. Not advised but I was even able to install from Apple installer directly from High Sierra. Lately, I have been mostly using the Dosdude1 installer and patcher.

 

[pkouame]

Can this menu bar option become a system pref? That would be ideal.

That would be great, but this workaround (patching a data section in a framework) makes it kind of awkward. Still good food for thought.
Fixing the menu bar is just one aspect of this, the application side is another which is still in the works (with varying degrees of success - see previous posts).

The ultimate fix is to rewrite and swizzle out the entire vibrant light code (using vibrant dark as the pattern - since it works), that is a little more involved and I'm waiting for GM to avoid chasing my tail

 

[Martyimac]

I’ e read people getting better performance from some cards in slot 2 on 3,1. What is strange i


It’s been reported you need to be on APFS for the system pref software Updater to work. Funny thing is I applied the APFS patch for 3,1 but the Dosdude1 installer won’t let me install on an APFS volume. I even tried cloning to an APFS Volume and it won’t bless.

I have gotten APFS to work once the last with Clover. Not advised but I was even able to install from Apple installer directly from High Sierra. Lately, I have been mostly using the Dosdude1 installer and patcher.

Hmm, well my mini 5,2 has an SSD with APFS formatting. When used with the dosdude1 patched system, software update did not work, had to start over from scratch to get the most current Mojave version.

 

[pkouame]

I applied pkuaome's hybrid patch and jackluke's looks good Thank you

 

[d4gli]

Downlaoding Mojave via App, will use latest Publicbeta or latest release (from the last 2 days e.g. Beta 11)?

 

[Vyzantion]

Downlaoding Mojave via App, will use latest Publicbeta or latest release (from the last 2 days e.g. Beta 11)?

It seems you can only get PB 9, for now. PB 10 might have been pulled out by Apple. I have reinstalled the OS and could not get PB 10 anymore.

 

[d4gli]

It seems you can only get PB 9, for now. PB 10 might have been pulled out by Apple. I have reinstalled the OS and could not get PB 10 anymore.

Thanks for clarification, would take this weekend to install on my old buddy... So 'Ill take what I get and just start...

 

[TimothyR734]

It seems you can only get PB 9, for now. PB 10 might have been pulled out by Apple. I have reinstalled the OS and could not get PB 10 anymore.

Are you using the newest macOS Mojave Patcher 1.2.0

 

[Vyzantion]

Are you using the newest macOS Mojave Patcher 1.2.0

Yes, downloaded it yesterday night. Perhaps HFS+ may be responsable.
[doublepost=1536940246][/doublepost]

Thanks for clarification, would take this weekend to install on my old buddy... So 'Ill take what I get and just start...

I am not sure, this why I was asking myself this. But this is how it seems from what I have experienced today, for now.

 

[jackluke]

I read many posts regarding issues updating Mojave beta from APFS versus HFS+, I am on Mojave beta 9 and I feel it like a stable GM, checking the calendar, we are really close to the App Store public release, so I am very confident apple (as always) should release any delta/combo update under form of pkg/dmg downloadable through direct link. From then I guess anyone will follow an easier update process, of course with some pre make-up for the HFS+ Mojaves that need to avoid expressly the APFS conversion during a minor next update.

 

[TimothyR734]

I read many posts regarding issues updating Mojave beta from APFS versus HFS+, I am on Mojave beta 9 and I feel it like a stable GM, checking the calendar, we are really close to the App Store public release, so I am very confident apple (as always) should release any delta/combo update under form of pkg/dmg downloadable through direct link. From then I guess anyone will follow an easier update process, of course with some pre make-up for the HFS+ Mojaves that need to avoid expressly the APFS conversion during a minor next update.

I found if you apply your patch but don't quit the terminal your patch keeps active but if you quit the terminal and remove the terminal from the dock then the patch quits and the finder sidebar turns darker grey

 

[jackluke]

I found if you apply your patch but don't quit the terminal your patch keeps active but if you quit the terminal and remove the terminal from the dock then the patch quits and the finder sidebar turns darker grey

It works in both ways, check my previous post I've uploaded a new revision of the script, anyway even with the current you have try launch the mojavehld.command and type (each followed by enter key): 2, 1, 4 and last close the Terminal application or CMD+Q shortcut

If you want to use only the "choice number 1", you have to set first global transparency from Accessibility prefpane disabling the "reduce transparency" checkbox.

edit:
If you used the pkouame HIToolBox I guess you can't use both together, you should restore first your stock HiToolBox.framework, because his patch override an internal framework value, while my patch needs the "light mode grey glitch" untouched, at least I guess they are reversed, my "reduce transparency" matches the pkouame HIToolbox in an "enable transparency".

 

[TimothyR734]

It works in both ways, check my previous post I've uploaded a new revision of the script, anyway even with the current you have try launch the mojavehld.command and type (each followed by enter key): 2, 1, 4 and last close the Terminal application or CMD+Q shortcut

If you want to use only the "choice number 1", you have to set first global transparency from Accessibility prefpane disabling the "reduce transparency" checkbox.

edit:
If you used the pkouame HIToolBox I guess you can't use both together, you should restore first your stock HiToolBox.framework, because his patch override an internal framework value, while my patch needs the "light mode grey glitch" untouched, at least I guess they are reversed, my "reduce transparency" matches the pkouame HIToolbox in an "enable transparency".

I am using pkouame's and yours and they seem to work fine together on my iMac 9,1 I put your script in my login items

 

[jackluke]

I am using pkouame's and yours and they seem to work fine together on my iMac 9,1 I put your script in my login items

I think you use mine to turn "whiter" the "dark grey" Finder "left side-bar windows" (I'd discovered another way to do that), but if I understood you should not use them together, I mean my patch instead of "reduce transparency" will act like "enable transparency" if you use it with the pkouame patch, and viceversa. So that's why you could encounter issues using both simultaneously.

In summary, my patch requires "reduce transparency" feature disabled namely "pure blur transparency", while pkouame patch it's an already "reduced transparency" namely "pure 100% opacity".

 

[Starplayr]

Hmm, well my mini 5,2 has an SSD with APFS formatting. When used with the dosdude1 patched system, software update did not work, had to start over from scratch to get the most current Mojave version.

Could be one of two things, bugs in the software Updater or it may be looking if the machine is supported or not and may just be saying what the well to itself and not updating. Also supported macs a getting new firmware for Mojave as part of the install. That may be part of it.

For being unsupported it’s kind of a blessing in disguise because you ha e total control over the installs and updates. Stuff like this was common in the hackintosh realm. I would be Nike if the Updater worked and in am sure talhatbwill be solved when Mojave is out for real and Apple has more users banging away on it.

My feeling after the Sept.12 event thst Apple is taking a backside with Macs and MacOS. It’s a shame really. It’s their legacy after the Apple I, II, IIgs, and the Lisa.

I know Apple is a consumer company now days but they need to not forget their roots.
[doublepost=1536952771][/doublepost]Finally got Fortnite on the 2008 to play as good at the PC with the same settings. But PC is running the AMD and at 5GT/s. Mac is running NVIDiA at GT/s.

the Mac tends to drop fps a lot. To avoid this I put the FPS at unlimited and turn on V sync and it balances out between 48-75. And it never goes below 48. No lag.

 

[Sevenfeet]

My feeling after the Sept.12 event thst Apple is taking a backside with Macs and MacOS. It’s a shame really. It’s their legacy after the Apple I, II, IIgs, and the Lisa.

Apple almost never does an iOS/tvOS event alongside macOs for years now. There will either be a separate event for macOS in October or there will be an announcements with no event (since sometimes the macOS event is at or around WWDC in June). Since it's the Christmas shopping season, usually you want to set up some buzz for people to buy Macs before then. And finally, iPads get renewed in March. Again, Apple's pretty predictable these days with their product lifecycle.

 

[DuncanGarp]

I applied pkuaome's hybrid patch and jackluke's looks good Thank you

Can you please tell me or point me to @pkouame's hybrid patch or is it similar to @jackluke's post, which I made 2 shell scripts from it. Listed below.


Thanks.

 

[ASentientBot]

Can you please tell me or point me to @pkouame's hybrid patch or is it similar to @jackluke's post, which I made 2 shell scripts from it. Listed below.
View attachment 781796

Thanks.

I don't believe @pkouame has released their patch yet, but it is totally different and more advanced than @jackluke's. But it's a lot more invasive, it involves patching system frameworks rather than a few simple defaults commands. I personally can't wait to see it though!