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.
Got it up and running on a 2011 MBP 2.3Ghz 16GB RAM and AMD GPU.

Does it run hotter for anyone? It runs hotter than high sierra, even after disabling transparencies.

I repasted the CPU recently and it was running very cool under High Sierra but Mojave just runs hot.

I assume this is related to the fact that it's still beta?
 
  • Like
Reactions: TimothyR734
Got it up and running on a 2011 MBP 2.3Ghz 16GB RAM and AMD GPU.

Does it run hotter for anyone? It runs hotter than high sierra, even after disabling transparencies.

I repasted the CPU recently and it was running very cool under High Sierra but Mojave just runs hot.

I assume this is related to the fact that it's still beta?
If you have the AMD GPU enabled, then you have no graphics acceleration. That's why it's running hot.
 
If you have the AMD GPU enabled, then you have no graphics acceleration. That's why it's running hot.

Hmm there's no GPU acceleration for Radeon 6750M 1GB?

EDIT: Read your first post. Great work by the way.

Will Radeon 6750M ever be enabled in Mojave?

Could we inject a kext from High Sierra to enable it somehow?
 
  • Like
Reactions: TimothyR734
Don’t know if this relates to the forum, but what does Safari Technology Preview have that Safari doesn’t? Noticed it was a discussion in this forum earlier, tried it, but didn’t find anything worthwhile.
Speed, substantially faster than Safari, at least on this unsupported iMac, initially it was a preview on High Sierra for upcoming Mojave. For me personally there really isn't a comparison, Safari Tech is so much faster than stock version. Again just my perspective.
 
Last edited:
Mine is working great. All the apps are running well, including Adobe illustrator and Photoshop...
No random reboots. Camera working great, you name it.but if you only have one app running, probably there is a problem with your installation... This last beta is pretty "stable" for a beta.

Clean install of the latest beta. Stability sounds about "right" for a 10.x.0 release. Only really missing bigger WiFi woes than the long time it takes to connect (ever since Mavericks, to be fair).
 
Hmm there's no GPU acceleration for Radeon 6750M 1GB?

EDIT: Read your first post. Great work by the way.

Will Radeon 6750M ever be enabled in Mojave?

Could we inject a kext from High Sierra to enable it somehow?

we could load the drivers on first and second rls .. after the third rls apple abolished to load the drivers :( dosdude1 was to fast on rls this bugs.. wait to final and then rls would be all ok ... he say we must upgrade the gpu card , if my broke then buy an nvidia card or he has an surprise and fix that :) *hope*
 
  • Like
Reactions: TimothyR734
Do you know of any scripts to download the install from macOS itself?
Yes, see this post. There's also the DIY (no script required) method that @ASentientBot posted earlier in this thread.
[doublepost=1534141883][/doublepost]
Could we inject a kext from High Sierra to enable it somehow?
It was attempted already. All the needed kexts load fine in Mojave but there is simply still only partial acceleration, no Core Image. No one has been able to figure out why, especially as in the case of the Intel HD Graphics 3000 and legacy Nvidia GPUs, the kexts load and Core Image is enabled without issue.
 
Last edited:
Yes, see this post. There's also the DIY (no script required) method that @ASentientBot posted earlier in this thread.
[doublepost=1534141883][/doublepost]
It was attempted already. All the needed kexts load fine in Mojave but there is simply still only partial acceleration, no Core Image. No one has been able to figure out why, especially as in the case of the Intel HD Graphics 3000 and legacy Nvidia GPUs, the kexts load and Core Image is enabled without issue.

I tried that script recently but it didn’t work for me.
 
  • Like
Reactions: TimothyR734
Yes, see this post. There's also the DIY (no script required) method that @ASentientBot posted earlier in this thread.
[doublepost=1534141883][/doublepost]
It was attempted already. All the needed kexts load fine in Mojave but there is simply still only partial acceleration, no Core Image. No one has been able to figure out why, especially as in the case of the Intel HD Graphics 3000 and legacy Nvidia GPUs, the kexts load and Core Image is enabled without issue.

I have a feeling someone at insanelymac or one of these other Hackintosh forums might be able to figure it out...if they have an incentive...
 
Indeed very cool! Does this also work for a macbook pro 5,3? I'm away and don't remember what my Intel HD GC is. Does this notably improve appearance/performance using the non-accelerated GC?

wait...
a MBP 5.3 has a Intel Graphic Card?
i have a MBP 5.4 an a NVIDIA Card. is there a integrated Card,too?
How to test and use this?
Thank you
 
  • Like
Reactions: TimothyR734
Interesting. By the way, I think hack <-> unmac exchanges are valuable for both our communities. In fact a lot of what we're doing here was inspired by those famous hack forums/boards. I also have a selfish reason: hacks are becoming a real option for me as Apple stumbles badly with their new machines and I don't believe in their mac pro promises any more..

But I'm confused, so some more questions:
- Have you tried a normal system update (from preferences - that's where it's moved to in Mojave)? If so, what happens?
- What is your hack identified as now? I mean model, machine id, etc.? Can you also print out the output from the following:
- sysctl -a | grep machdep.cpu
- system_profiler SPHardwareDataType
- ioreg -l | awk -F\" '/board-id/ { print $4 }'

[doublepost=1534119124][/doublepost]
I think so to. Simply because I got bitten by OWC SSD driver issues...so speaking from painful experience.
The first succesfull install of Mojave was on the current beta build, so I have not tested any upgrade to a new build yet. I was able to update Gatekeeper configuration data via the update command in Terminal, as usual, I so it installed fine in the receipts. We shall see if updating shall be without issues via System Preferences. But I sitll prefer clean installs on beta builds and having the latest beta build on the bootable pen drive, for testing. Perhaps the developers of Clover and FakeSMC shall find a way to run Mojave on older hardware in another way, making the build in Mojave kexts to work. That would make crashing due to system updates less likely.
Currently, Clover selected iMac 10.1, iMac late 2009. The machine is made of two older Asus systems. The ASUS motherboard is from 2008, Intel Core 2 Duo e8500 and an even older Nvidia GPU from 2005 or 2004, GeForce 6200, 256 mb, that was in an older ASUS system, with AMD cpu previously.

- sysctl -a | grep machdep.cpu
- system_profiler SPHardwareDataType
- ioreg -l | awk -F\" '/board-id/ { print $4 }'
Thoose are Terminal command lines, right?
One more thing. The CPU supports Intel on board graphics, the motherboard does not, it seems. I have a suspicion that I actually run Intel HD Graphics, not the Nvidia GPU graphics and the Nvidia graphics card acts just like a connected interface for Intel HD Graphics, its GPU being disabled. I suspect this for a long time. On System Information, if do not select from Multibeast „Inject Nvidia” and let the default „Inject Intel”, System Information gives me ”Unknown Nvidia 6 mb”. I f I select „Inject Nvidia” instead of „Inject Intel”, after a reboot I get ”Unknown Nvidia 256 mb). I have tested and AMD graphics card on the machine on a computer shop last mounth, I have got incomclusive results regarding compatibility, but some suggestes the hypothesis that macOS High Sierra, and later the Dosdude1 patched Mojave actually use Intel HD graphics.
 
Last edited:
  • Like
Reactions: TimothyR734
I don't know why people aren't being helpful. If we help Hackintosh users, then we will get help from them as well and both communities will benefit. There's no need for this slight hostility towards Hackintosh that a lot of people on this forum seem to have.

The Mojave App Store doesn't have an option to download macOS installers. You can use the option Tools --> Download macOS Mojave in @dosdude1's patcher. Alternately, you can use a script like this one or follow my instructions to manually find the download links from the software catalog.

Hope that helps!
I knew that I can use Dosdude1„s tool to download. The issue was a legal one, to have the installer app from a legit Apple source. Downloading on Windows it is probably considered ilegitimate. So, you say Mojave app store does not allow downloading of any installer app? I just had first succesfull install of Mojave on my machine two days ago and I failed to download the app installer for Mojave, when I had tested it.
 
  • Like
Reactions: TimothyR734
I knew that I can use Dosdude1„s tool to download. The issue was a legal one, to have the installer app from a legit Apple source. Downloading on Windows it is probably considered ilegitimate. So, you say Mojave app store does not allow downloading of any installer app? I just had first succesfull install of Mojave on my machine two days ago and I failed to download the app installer for Mojave, when I had tested it.

The download option in the patcher downloads all files from the official Apple server and should be legal, however, using a Hackintosh is not so legal issues with Apple shouldn’t matter to you anyway. In Mojave the App Store no longer allows the download of a macOS installer so you must use dosdude1’s tool or another method.
 
  • Like
Reactions: TimothyR734
The download option in the patcher downloads all files from the official Apple server and should be legal, however, using a Hackintosh is not so legal issues with Apple shouldn’t matter to you anyway. In Mojave the App Store no longer allows the download of a macOS installer so you must use dosdude1’s tool or another method.
So, it seems Mojave App store does not download any macOS installer app. I tought it was due to my system definitions from Clover. A question for thoose Who tried previous public beta builds of Mojave: updating from one build to the next is done via the software update from System Preferences, not by downloading the new build from App Store, right?
Regarding legal issues, the rules from the board Tonymacx86 give the clearest picture about what is it legal and what it is not legal in Hackintoshing, according to EU law.
 
  • Like
Reactions: TimothyR734
So, it seems Mojave App store does not download any macOS installer app. I tought it was due to my system definitions from Clover. A question for thoose Who tried previous public beta builds of Mojave: updating from one build to the next is done via the software update from System Preferences, not by downloading the new build from App Store, right?
Regarding legal issues, the rules from the board Tonymacx86 give the clearest picture about what is it legal and what it is not legal in Hackintoshing, according to EU law.

Yes, updates are supposed to be made from the Software Updates section in System Preferences which will work on unsupported Macs or Hackintoshes if you have installed dosdude1’s software update patch. AFAIK Hackintoshing is not illegal, however, it is against Apple’s terms of service while AFAIK downloading the macOS installer from another client is not against their terms of service unless it is pirated which in this case it isn’t, it’s simply being downloaded from another client but the files are still from Apple’s official server.
 
  • Like
Reactions: TimothyR734
The first succesfull install of Mojave was on the current beta build, so I have not tested any upgrade to a new build yet. I was able to update Gatekeeper configuration data via the update command in Terminal, as usual, I so it installed fine in the receipts. We shall see if updating shall be without issues via System Preferences. But I sitll prefer clean installs on beta builds and having the latest beta build on the bootable pen drive, for testing. Perhaps the developers of Clover and FakeSMC shall find a way to run Mojave on older hardware in another way, making the build in Mojave kexts to work. That would make crashing due to system updates less likely.
Currently, Clover selected iMac 10.1, iMac late 2009. The machine is made of two older Asus systems. The ASUS motherboard is from 2008, Intel Core 2 Duo e8500 and an even older Nvidia GPU from 2005 or 2004, GeForce 6200, 256 mb, that was in an older ASUS system, with AMD cpu previously.

- sysctl -a | grep machdep.cpu
- system_profiler SPHardwareDataType
- ioreg -l | awk -F\" '/board-id/ { print $4 }'
Thoose are Terminal command lines, right?
One more thing. The CPU supports Intel on board graphics, the motherboard does not, it seems. I have a suspicion that I actually run Intel HD Graphics, not the Nvidia GPU graphics and the Nvidia graphics card acts just like a connected interface for Intel HD Graphics, its GPU being disabled. I suspect this for a long time. On System Information, if do not select from Multibeast „Inject Nvidia” and let the default „Inject Intel”, System Information gives me ”Unknown Nvidia 6 mb”. I f I select „Inject Nvidia” instead of „Inject Intel”, after a reboot I get ”Unknown Nvidia 256 mb). I have tested and AMD graphics card on the machine on a computer shop last mounth, I have got incomclusive results regarding compatibility, but some suggestes the hypothesis that macOS High Sierra, and later the Dosdude1 patched Mojave actually use Intel HD graphics.
Yes. Those are terminal commands meant to identify your system. Some are the same commands the system update "process" uses to determine compatibility.
As others have already mentioned, the normal update route in Mojave is to use system update in preferences. Your success may vary. I have an old post (back in dp3 days) showing the screens you get when a system update (from dp3 to dp4) is triggered. Since then, (my) success has been spotty: for some it works, others have to download the full installer and follow procedures to update (either fresh or over a previous install works)
You can of course use dude's patcher to download a fresh copy.
Yes, clean installs on betas is the sane approach. Exercising the system update function is just to get a heads up on future (post-GM) types of issues. Good luck.
 
  • Like
Reactions: TimothyR734
Yes, see this post. There's also the DIY (no script required) method that @ASentientBot posted earlier in this thread.
[doublepost=1534141883][/doublepost]
It was attempted already. All the needed kexts load fine in Mojave but there is simply still only partial acceleration, no Core Image. No one has been able to figure out why, especially as in the case of the Intel HD Graphics 3000 and legacy Nvidia GPUs, the kexts load and Core Image is enabled without issue.

There are some people who know why. They are in Cupertino, and are now laughing at this thread, and our woes.
 
  • Like
Reactions: TimothyR734
Yes. Those are terminal commands meant to identify your system. Some are the same commands the system update "process" uses to determine compatibility.
As others have already mentioned, the normal update route in Mojave is to use system update in preferences. Your success may vary. I have an old post (back in dp3 days) showing the screens you get when a system update (from dp3 to dp4) is triggered. Since then, (my) success has been spotty: for some it works, others have to download the full installer and follow procedures to update (either fresh or over a previous install works)
You can of course use dude's patcher to download a fresh copy.
Yes, clean installs on betas is the sane approach. Exercising the system update function is just to get a heads up on future (post-GM) types of issues. Good luck.
So, when updating from a public beta build to the next, the full installer is downloaded, not just an update pkg file? This seems to be the case.
 
  • Like
Reactions: TimothyR734
@Czo,

I’m having issues getting continuity to work on my 2011 Mac Mini running Mojave patched with @dosdude1 tool. It seems I’m having issues similar to issues seen with High Sierra when it was in beta that you were able to help some people through. I have already used the CAT to activate continuity but it is still not working. I would really appreciate your help....
 
  • Like
Reactions: TimothyR734
I tried that script recently but it didn’t work for me.
Have you also tried the manual / DIY method? It may seem complicated at first, but I was able to confirm it works to produce a functional installer.

Credit to @ASentientBot for posting the step-by-step process. It may be possible to build a normal BASH script to automate it, rather than a Python script like the one linked in the post.
I have a feeling someone at insanelymac or one of these other Hackintosh forums might be able to figure it out...if they have an incentive...
Some older Hackintosh builds I would imagine do have Radeon 5000-series or 6000-series GPUs. But unlike the laptop Macs, they can be upgraded.

So if you have a Mac with a 5000-series or 6000-series, as it stands now you this is what you're left having to do if you want the it to run Mojave:
  • Mac Pro - upgrade it!
  • iMac - also upgrade it. (2011 iMacs are the last generation to have an upgradable GPU, so take advantage of it. However, you will end up losing boot screens and possibly external monitor support, so this isn't a perfect solution.)
  • MacBook Pro - disable the discrete GPU using a non-permanent NVRAM setting. (They are known to be failure-prone anyway.)
eGPU is also an option for 2011 Macs, but unsurprisingly doesn't work for the internal display.
 
So, when updating from a public beta build to the next, the full installer is downloaded, not just an update pkg file? This seems to be the case.
In my case (repeatedly) yes, I can always get the full installer to download (either manually or via beta utility). I got a "real" in-place update once from dp3 to dp4 once. As you said, these are just betas...
 
  • Like
Reactions: TimothyR734
Oh my fault, didn't know sorry.

@arqueox try these steps they 100% work this time to increase from stock 512 MB to 1536 MB VRAM:

cd /S*/L*/Ext*/AppleIntelSNBGraphicsFB.kext/C*/M*

sudo cp AppleIntelSNBGraphicsFB AppleIntelSNBGraphicsFB.backup

sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x20|\xC7\x45\xD0\x00\x00\x00\x60|g' AppleIntelSNBGraphicsFB

sudo touch /S*/L*/Extensions


edit:
thanks to @arqueox for having tested the Info.plist
before reboot/restart you have to edit this file:

/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist

Adding after these strings,
this part:

<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>

<key>VRAMSize</key>
<integer>1536</integer>

after edited the plist from Terminal type:

sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions

sudo kextcache -i /

sudo reboot
I tried your method on my 2011 (still on HS), works great and it seems like the screen flickering it did before has stopped !

I've been looking into increasing the vram on my mbp 15 2010. On a fresh install of snow leopard from the original discs the MacBook came with, I get 288 mb vram for the intel hd no matter what ram combination I put in. I get the same on Mojave and high Sierra.
Apples specs is 256mb. So I conclude that its set in the efi, and I will leave it at that.
 

Attachments

  • 2011.png
    2011.png
    831.2 KB · Views: 303
wait...
a MBP 5.3 has a Intel Graphic Card?
i have a MBP 5.4 an a NVIDIA Card. is there a integrated Card,too?
How to test and use this?
Thank you
old post. no Intel card, my 5,3 has two NVidia GPUs. Sorry for the confusion.
[doublepost=1534175676][/doublepost]
There are some people who know why. They are in Cupertino, and are now laughing at this thread, and our woes.
I doubt it. I think they're busy enough with their own embarrassing issues...;)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.