macOS 10.14 Mojave on Unsupported Macs Thread

[mashersaurus]

Thanks for the suggestion of using Res Xtreme, @saudor. I've just downloaded it, and as you can see from the screenshot below, it lists two profiles for each resolution - one at 4 bit depth, one at 8. I double clicked the 4 bit depth setting, and my display went back to normal! It remains to be seen if this will stick after a reboot, but I reboot so infrequently that I'm happy to just keep the app hanging around in case I need to reset the setting. Thanks so much!

@timthomason - give Res Xtreme a try, it sounds like we've got the same problem. Literally, just download it from this URL, run the app, and double click on the line for whichever resolution you are using and which lists the Depth as 4.

http://resxtreme.com

 

[saudor]

Thanks for the suggestion of using Res Xtreme, @saudor. I've just downloaded it, and as you can see from the screenshot below, it lists two profiles for each resolution - one at 4 bit depth, one at 8. I double clicked the 4 bit depth setting, and my display went back to normal! It remains to be seen if this will stick after a reboot, but I reboot so infrequently that I'm happy to just keep the app hanging around in case I need to reset the setting. Thanks so much!

@timthomason - give Res Xtreme a try, it sounds like we've got the same problem. Literally, just download it from this URL, run the app, and double click on the line for whichever resolution you are using and which lists the Depth as 4.

http://resxtreme.com


View attachment 775920

Awesome. And yep it sticks after reboot. Some of the older radeons started having this issue since High Sierra. Dont really know why but dropping the depth from 8 to 4 fixes it. (Your system profiler will drop from 32 bit color to 24 bit color but as far as i know.. can't tell any difference!)

 

[mashersaurus]

Awesome. And yep it sticks after reboot. Some of the older radeons started having this issue since High Sierra. Dont really know why but dropping the depth from 8 to 4 fixes it. (Your system profiler will drop from 32 bit color to 24 bit color but as far as i know.. can't tell any difference!)

You're right, my System Information now shows the display as 24-bit, but I can't tell any difference either! That's great that it will stick after a reboot. I really wish I could upgrade this iMac but I just can't justify the cost right now. Thanks to this tool and the help of the members of this forum I'm squeezing a bit more life out of this machine!

 

[Vyzantion]

The Dosdude1 patch does not change the kernel, right? I have SSE 4.1, not SSE 4.2 . I was able to boot the installer without the patch from the pen drive, but not to finish install. So the CPU is still vanilla and my SSE 4.1 CPU is running the unmodified Mojave kernel, even with the patch?

 

[0403979]

The Dosdude1 patch does not change the kernel, right? I have SSE 4.1, not SSE 4.2 . I was able to boot the installer without the patch from the pen drive, but not to finish install. So the CPU is still vanilla and my SSE 4.1 CPU is running the unmodified Mojave kernel, even with the patch?

Yes, the kernal is unmodified no matter what patches you select.

 

[pkouame]

It is not just the Clover boot loader, but also the FakeSMC kext, that is essential for Hackintoshing today (unlike some years ago). FakeSMC configures SMC in a way so that macOS can boot on non-Apple hardware or unsupported Macs. Prior to Clover, the widespread boatloader was Chameleon (still used by some), that needs legacy (BIOS) to work, to emulate Apple UEFI, standard UEFI had be avoided altogether. FakeSMC existed since Chameleon times, but it works better with Clover, that works differently. Clover emulates an Apple UEFI environment, for legacy (BIOS) machine, but also for non-Apple UEFI machines. It descends from the Duet boot loader, used to emulate general UEFI for general BIOS machines. FakeSMC still remains yet an essential component of booting in Hackintosh. Running Mojave on an unsupported Mac is, in a way at least, a form of Hackintosh. Clover+FakeSMC works differently then Dosdude1 patch, but, in certain situations, like my own, those two can work together, but you need to know what to do. Perhaps fusing those two methods can create something better both for unsupported Macs and Hackintoshes alike.
I am waiting for public beta, for legal reasons. No DPs for me. What do you mean by registry? Windows has registries, macOS, Linux and other Unixes do not. You mean something analogous to Windows registry or something else altogether?

Thanks for the insights. Appreciate it - it is definitely piquing my interest in hacks! Yes macOs doesn't have a windoze style central registry. I'm just wondering why you can't run ioreg at the command line. Maybe related to FakeSMC, but I'm a neo-phyte

Public betas are already out there, or maybe you meant GM release version? A reason to at least try a system update now would be to set your expectations and gain some experience (you don't have to actually download anything) Getting a new OS on your machine is one thing, the ease of following Apple updates (which come fast and furious now) is a concern of mine. How is this handle in hack world?

Given the entire 2018 mbpro debacle I am seriously considering a super charged core i9 windows laptop that I can hack into my favorite mac.

I agree with you that there is lots to learn from both our communities (hacks and unmacs)
[doublepost=1534258023][/doublepost]

Ahh well umpteenth time of trying to get the Public Beta update via System Preferences and still no go, here's my install log.

Thanks. Your log also indicates beaucoup AssertionMgr "BadgingCount" count issues before it stalls. Seems like a common error for all of us struggling with this. It also may be a side effect from another error as I am noticing many sandbox Policy errors in the main console log (filter for "softwareupdate").softwareupdate_notify plists are sandboxed and mdwrite complains. Curious: are you APFS or HFS+?. One of @TimothyR734 's machines which is on APFS shows no such errors and he runs updates smoothly.

 

[Badruzeus]

I just tried w/o installing any BetaUtility from a Clean installed 1st DP Beta 1 then updating it upto Beta 6, seems get no issue with later releases via Software Update.app. Now going to update to Beta 7.

Spoiler

Uhmmb, I'm still curious with weird Apple Menu using LightMode on my (sorry) Fermi graphics, even strange is.. if this issue also occurred on GT 650M (Kepler)? << with all stock vanilla NVDAGF* NVDAGK* kexts on SLE though. Ha haa, it seems Apple was joking -_- bit difficult to solve, since this issue has been there from the very beginning of Mojave.. at least, if we do binaries comparison.

#EDIT: It was yesterday screenshot my bad.

 

[pkouame]

I just tried recently, w/o installing any BetaUtility from a Clean installed 1st DP Beta 1 then updating it upto Beta 6, seems get no issue with later releases via Software Update.app. Now going to update to Beta 7.

Spoiler

Uhmmb, I'm still curious with weird Apple Menu using LightMode on my (sorry) Fermi graphics, even strange is.. if this issue also occurred on GT 650M (Kepler)? << with all stock vanilla NVDAGF* NVDAGK* kexts on SLE though. Ha haa, it seems Apple was joking -_- bit difficult to solve, since this issue has been there from the very beginning of Mojave.. at least, if we do binaries comparison.

That's the way it should work. Congrats. I didn't go as far as re-installing dp1, but re-installed a clean dp6 with the patcher before attempting dp7. What machine are you on? APFS or HFS+?

 

[Olivia88]

Thanks for the insights. Appreciate it - it is definitely piquing my interest in hacks! Yes macOs doesn't have a windoze style central registry. I'm just wondering why you can't run ioreg at the command line. Maybe related to FakeSMC, but I'm a neo-phyte

Public betas are already out there, or maybe you meant GM release version? A reason to at least try a system update now would be to set your expectations and gain some experience (you don't have to actually download anything) Getting a new OS on your machine is one thing, the ease of following Apple updates (which come fast and furious now) is a concern of mine. How is this handle in hack world?

Given the entire 2018 mbpro debacle I am seriously considering a super charged core i9 windows laptop that I can hack into my favorite mac.

I agree with you that there is lots to learn from both our communities (hacks and unmacs)
[doublepost=1534258023][/doublepost]
Thanks. Your log also indicates beaucoup AssertionMgr "BadgingCount" count issues before it stalls. Seems like a common error for all of us struggling with this. It also may be a side effect from another error as I am noticing many sandbox Policy errors in the main console log (filter for "softwareupdate").softwareupdate_notify plists are sandboxed and mdwrite complains. Curious: are you APFS or HFS+?. One of @TimothyR734 's machines which is on APFS shows no such errors and he runs updates smoothly.

I have the hfs+ on a crucial mx200. I'll try installing with apfs and see if that makes a difference.

 

[L Caputo]

Thanks for the insights. Appreciate it - it is definitely piquing my interest in hacks! Yes macOs doesn't have a windoze style central registry. I'm just wondering why you can't run ioreg at the command line. Maybe related to FakeSMC, but I'm a neo-phyte

Public betas are already out there, or maybe you meant GM release version? A reason to at least try a system update now would be to set your expectations and gain some experience (you don't have to actually download anything) Getting a new OS on your machine is one thing, the ease of following Apple updates (which come fast and furious now) is a concern of mine. How is this handle in hack world?

Given the entire 2018 mbpro debacle I am seriously considering a super charged core i9 windows laptop that I can hack into my favorite mac.

I agree with you that there is lots to learn from both our communities (hacks and unmacs)
[doublepost=1534258023][/doublepost]
Thanks. Your log also indicates beaucoup AssertionMgr "BadgingCount" count issues before it stalls. Seems like a common error for all of us struggling with this. It also may be a side effect from another error as I am noticing many sandbox Policy errors in the main console log (filter for "softwareupdate").softwareupdate_notify plists are sandboxed and mdwrite complains. Curious: are you APFS or HFS+?. One of @TimothyR734 's machines which is on APFS shows no such errors and he runs updates smoothly.

Hi thanks for taking the time to look at the install log, the Mac is a MacPro 3.1 all disks are spinners and all HFS+

 

[Badruzeus]

That's the way it should work. Congrats. I didn't go as far as re-installing dp1, but re-installed a clean dp6 with the patcher before attempting dp7. What machine are you on? APFS or HFS+?

The last one from my signature, sorry.. since there's no real mac with Fermi graphics, so.. you know what I mean. There's no different with APFS or HFS+ on my case, I've reinstalled Mojave more than 10 times w/o issue when updating.

 

[ASentientBot]

It is not just the Clover boot loader, but also the FakeSMC kext, that is essential for Hackintoshing today (unlike some years ago). FakeSMC configures SMC in a way so that macOS can boot on non-Apple hardware or unsupported Macs. Prior to Clover, the widespread boatloader was Chameleon (still used by some), that needs legacy (BIOS) to work, to emulate Apple UEFI, standard UEFI had be avoided altogether. FakeSMC existed since Chameleon times, but it works better with Clover, that works differently. Clover emulates an Apple UEFI environment, for legacy (BIOS) machine, but also for non-Apple UEFI machines. It descends from the Duet boot loader, used to emulate general UEFI for general BIOS machines. FakeSMC still remains yet an essential component of booting in Hackintosh. Running Mojave on an unsupported Mac is, in a way at least, a form of Hackintosh. Clover+FakeSMC works differently then Dosdude1 patch, but, in certain situations, like my own, those two can work together, but you need to know what to do. Perhaps fusing those two methods can create something better both for unsupported Macs and Hackintoshes alike.
I am waiting for public beta, for legal reasons. No DPs for me. What do you mean by registry? Windows has registries, macOS, Linux and other Unixes do not. You mean something analogous to Windows registry or something else altogether?

Registry as in IOKit registry. I don't know the details but it's more like a device tree than the Windows registry. It most certainly still exists on a Hackintosh. If you run ioreg -l and search the output for "class IOPlatformExpertDevice", there should be some information below there including the model, board ID, etc. The other command you were given is supposed to just extract the board ID automatically.

There's already a public beta released. No need to wait for it. Unless you mean a GM.

 

[videotape74]

I've installed DP7 using the latest patcher from @dosdude1 and all installs fine but when I go into System Preferences and click on the TrackPad option to adjust the settings, it just closes. Any ideas? I'm on a MBP 5,4 and using HFS+...thanks!

 

[pkouame]

I have the hfs+ on a crucial mx200. I'll try installing with apfs and see if that makes a difference.

I'm just tallying differences between our machines at this point. So the APFS thing isn't even a strong hunch. But it would be interesting to see if you have time. I'm not sure how you revert "easily" from APFS, so be advised and proceed with caution if you decide to do so. Thanks!

 

[0403979]

I've installed DP7 using the latest patcher from @dosdude1 and all installs fine but when I go into System Preferences and click on the TrackPad option to adjust the settings, it just closes. Any ideas? I'm on a MacBook 5,4 and using HFS+...thanks!

Do you mean MacBook5,2?

 

[pkouame]

The last one from my signature, sorry.. since there's no real mac with Fermi graphics, so.. you know what I mean. There's no different with APFS or HFS+ on my case, I've reinstalled Mojave more than 10 times w/o issue when updating.

@Olivia88 - looks like he confirms success either way. So no need to try an APFS system update.
[doublepost=1534260521][/doublepost]

The Dosdude1 patch does not change the kernel, right? I have SSE 4.1, not SSE 4.2 . I was able to boot the installer without the patch from the pen drive, but not to finish install. So the CPU is still vanilla and my SSE 4.1 CPU is running the unmodified Mojave kernel, even with the patch?

Do you mean you installed from an original "clean" Mojave Installer on a stick? How?

 

[Olivia88]

@Olivia88 - looks like he confirms success either way. So no need to try an APFS system update.

The dock was white in light mode in dp7 and it annoyed me, so I'll downgrade to dp6 and see what that does anyway, + I'm curious to see if there are any other differences with apfs.

 

[pkouame]

Hi thanks for taking the time to look at the install log, the Mac is a MacPro 3.1 all disks are spinners and all HFS+

I have the same model. Coincidence?

EDIT: I also noticed your system (like mine) tags a Gatekeeper Configuration Data 151 update

 

[redheeler]

Spoiler

Uhmmb, I'm still curious with weird Apple Menu using LightMode on my (sorry) Fermi graphics, even strange is.. if this issue also occurred on GT 650M (Kepler)? << with all stock vanilla NVDAGF* NVDAGK* kexts on SLE though. Ha haa, it seems Apple was joking -_- bit difficult to solve, since this issue has been there from the very beginning of Mojave.. at least, if we do binaries comparison.

You mean the darker color of the menus and sidebars in light mode? That's not present on my 2012 rMBP with GeForce GT 650M, but the 650M does support Metal so the issue only seems to be present with OpenGL rendering.

 

[videotape74]

Do you mean MacBook5,2?

No sorry MBP 5,4

 

[TimothyR734]

in the thread Is Developer Beta .. Is it out yet fisherrman tried software update on a HFS drive no luck, rebooted into a APFS and it found the PB6 I asked if he was on a supported Mac waiting for his reply so maybe this might be happening to those on supported Macs as well

 

[arqueox]

You mean the darker color of the menus and sidebars in light mode? That's not present on my 2012 rMBP with GeForce GT 650M, but the 650M does support Metal so the issue only seems to be present with OpenGL rendering.

Totally OpenGL issue... It must be something about metal support.

 

[pkouame]

in the thread Is Developer Beta .. Is it out yet fisherrman tried software update on a HFS drive no luck, rebooted into a APFS and it found the PB6 I asked if he was on a supported Mac waiting for his reply so maybe this might be happening to those on supported Macs as well

Good find. We may be on to something...

 

[TimothyR734]

Good find. We may be on to something...

he did provide a link to download PB6 the download is 2.7 GB but the standard installation is 7.91 GB

 

[hvds]

View attachment 774456

In this thread, advancements in running macOS 10.14 Mojave on unsupported systems will be discussed.
​

Links:

• macOS Mojave
• macOS Mojave Patcher
• macOS Mojave Patcher Demo Video
• Apple Beta Software Program

Current Hardware Support Status:

• Machine Support
  • Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
    • MacPro3,1
    • MacPro4,1
    • iMac8,1
    • iMac9,1
    • iMac10,x
    • iMac11,x
    • iMac12,x
    • MacBookPro4,1
    • MacBookPro5,x
    • MacBookPro6,x
    • MacBookPro7,1
    • MacBookPro8,x
  • Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
    • MacBookAir2,1
    • MacBookAir3,x
    • MacBookAir4,x
    • MacBook5,1
  • Early-2009 or newer Mac Mini or white MacBook:
    • Macmini3,1
    • Macmini4,1
    • Macmini5,x
    • MacBook5,2
    • MacBook6,1
    • MacBook7,1
  • Early-2008 or newer Xserve:
    • Xserve2,1
    • Xserve3,1

• Video Card Support
  • Pre-Metal AMD video cards (Radeon HD 6xxx series and older)
  • Pre-Metal nVidia video cards (GeForce 5xx series and older)
  • Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)

Current Issues

• Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, however, these anomalies are not present. A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display. This is not a fix, this is a workaround. A solution for this issue is currently being investigated.
• AMD Radeon HD 5xxx/6xxx series GPU acceleration: Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series GPU. This includes 2010 and 2011 iMacs and 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these MacBook Pro systems, you'll need to disable the AMD GPU.
• Early-2008 Mac Pro (MacPro3,1) GPU support: When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-comptible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are nVidia cards, which work perfectly fine.
• Built-in iSight cameras: Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
• Trackpad (MacBook5,2 affected only). The trackpad in the MacBook5,2 isn't fully supported in Mojave. While it works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
• Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running Mojave. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.
• App Store Crashing: Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround.

Current Issues by Model

• Graphics anomalies:
  • All machines
• AMD GPU acceleration:
  • All machines with a Radeon HD 5xxx or 6xxx series GPU
• GPU support:
  • MacPro3,1
• Built-in iSight cameras:
  • All machines, hit or miss
• Trackpad:
  • MacBook5,2
• Unsupported WiFi modules:
  • All machines that use the Broadcom BCM4321 WiFi module
• App Store Crashing:
  • Machines with accelerated pre-metal Radeon HD GPUs (like Radeon HD 4xxx series GPUs)

Installing for Testing:
To install on your machine, you can download and run my macOS Mojave Patcher application, which will let you download a copy of the latest Developer Preview from Apple, and create a bootable USB installer for use on unsupported systems. It contains all the patches necessary to achieve the hardware support listed above. At this point, it is recommended that you install Mojave on one of these unsupported systems for testing only, and NOT as your main/daily use OS. Older versions of the patcher can be found here, the changelog here, and the official installation guide here.

Video Demo:
A video demo of Mojave running on various unsupported Macs can be found here.

Mojave Builds and Installer Versions (Developer Preview, Public Beta):
2018/06/04 DP1, build 18A293u, installer 14.0.08
2018/06/19 DP2, build 18A314h, installer 14.0.11
2018/06/26 PB1, build 18A314k, installer 14.0.11
2018/07/03 DP3, build 18A326g, installer 14.0.12
2018/07/06 PB2, build 18A326h, installer 14.0.12
2018/07/16 DP4, 2018/07/17 PB3, build 18A336e, installer 14.0.14
2018/07/30 DP5, 2018/07/31 PB4, build 18A347e, installer 14.0.15
2018/08/06 DP6, 2018/08/06 PB5, build 18A353d, installer 14.0.15
2018/08/13 DP7, 2018/08/13 PB6, build 18A365a, installer 14.0.15

Special Thanks:
@Badruzeus - Discovered that 10.12 OpenGL drivers work in 10.14.
@ASentientBot - Fixed nVidia kernel panic, Core 2 Duo kernel panic, and iSight.
@jackluke - Narrowed down cause of Core 2 Duo kernel panic to the telemetry plugin, noticed that IOAccelerator framework from 10.14 beta 1 fixes some nVidia glitches.
@dosdude1 - Develops macOS Mojave Patcher.

Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.