macOS 10.14 Mojave on Unsupported Macs Thread

[testheit]

Don't know why I didn't think of this earlier, but listing the dependencies for GeForceTeslaGLDriver.bundle shows some possible areas of focus:

OpenGL.framework
IOSurface.framework
GPUSupport.framework

Maybe OpenGL.framework since the last entries right before the KP in the DYLD-log-file are pointing to this framework...

 

[0403979]

I formatted my internal to apfs it works fine the only 2 post install patches I left unchecked were the legacy graphic and legacy wifi patches during install but make sure you choose your model for example 7.1 and you will see the ones that need to be installed checked when I installed on my internal I unplugged my external hard drive only left my keyboard and mouse plugged in just to be safe until I got up and running

Good that you have it working now.
[doublepost=1531257685][/doublepost]

Maybe OpenGL.framework since the last entries right before the KP in the DYLD-log-file are pointing to this framework...

It should be replaced with the equivalent from High Sierra if one exists. Some try this.

 

[jackluke]

Don't know why I didn't think of this earlier, but listing the dependencies for GeForceTeslaGLDriver.bundle shows some possible areas of focus:

OpenGL.framework
IOSurface.framework
GPUSupport.framework

I have read your suggestion and tried swapping them one by one with relative HS frameworks:

IOSurface.framework generates a verbose roundup of pids crashes so avoid and leave the Mojave one

OpenGL.framework and GPUSupport.framework, both or individually give the same KP after LoginUI like the Mojave ones.


But everyone feel free to test them again, I used the 10.13.6 ones, maybe trying some from Sierra.


I would focus on PrivateFramework IOAccelerator taken from High Sierra but can't figure out those missing symbols or references to others HS frameworks.

 

[gugadj]

Hello everyone even scoring [macbook 8.2] in the patch the system does not load my Intel HD 3000 graphics card, but when I change HD and I enter the High Sierra it is loaded @ASentientBot sorry for disturbing

 

[jackluke]

Here are the dependencies I found on IOAccelerator from HS:

otool -L ~/D*/IOAccelerator.framework/*/*/IOAccelerator*
/Users/macbook/Downloads/IOAccelerator.framework/Versions/A/IOAccelerator:
    /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libDiagnosticMessagesClient.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 58286.70.4)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1454.90.0)
    /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1454.90.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4)
/Users/macbook/Downloads/IOAccelerator.framework/Versions/Current/IOAccelerator:
    /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libDiagnosticMessagesClient.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 58286.70.4)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1454.90.0)
    /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1454.90.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4)

They seems too sensitive frameworks, here again IOSurface, Security and so on.

 

[Starplayr]

New NVIDiA web drivers are already out for 10.13.6. I will be testing those out today on Mojave and see if there is any progress. Most likely a lot of us will be watching for the official release and new NVIDiA web drivers. I’m not Even gonna attempt my AMD Radeon 7970 anymore. It works great in El Cap and I got the artifacts to go away in High Sierra but the 3D timing is off on HS and does not list a metal family. My Titan X is what I really want on Mojave. The Radeon is good enough to keep for my Windows 10 Mac. Nice to have extra cheap hardware laying around.

 

[TimothyR734]

New NVIDiA web drivers are already out for 10.13.6. I will be testing those out today on Mojave and see if there is any progress. Most likely a lot of us will be watching for the official release and new NVIDiA web drivers. I’m not Even gonna attempt my AMD Radeon 7970 anymore. It works great in El Cap and I got the artifacts to go away in High Sierra but the 3D timing is off on HS and does not list a metal family. My Titan X is what I really want on Mojave. The Radeon is good enough to keep for my Windows 10 Mac. Nice to have extra cheap hardware laying around.

I already tried the new NVidia webdrivers no go the one the change I did notice no option to show package contents in Mojave

 

[DaniloGeekDude]

Just for posterity and for the good of this thread, if you have any kind of booting-related issue, like hanging on apple logo, no progress bar, or anything before the GUI loads, please please please try booting with Command-V and taking a picture of that instead. The verbose error is much more helpful than another picture of the same Apple Logo and progress bar which have already been posted hundreds of times. I never like being harsh or mean, and I don't mean it at all that way, but having the error already captured on the first post will streamline the debugging process for the dev's and the rest of us, who have straightforward access to the error.
[doublepost=1531240280][/doublepost]
Oh good, we have a panic log... maybe I missed it if someone already had one from a Tesla GPU. This is probably a binpatch waiting to happen, while I don't know how to do them I do know that its probably just patching a check in GeForceTesla

I have verbose mode (nvram boot-args="-v") as a default on my mb air. Is there a way to capture the messages into a log that I could review later? It scrolls by so fast in the screen. BTW, I currently have no issues (finger's crossed) with @dosdude1's amazing 1.b4 mojave patch app.

Regards.

 

[lefruitix]

No problem. I'm not writing this again though 😉

Patch the installer
1. Get a copy of the install app and open Contents/SharedSupport/InstallESD.dmg
2. Copy the folder Packages somewhere you can edit
3. cd to the folder and pkgutil --expand OSInstall.mpkg Expanded
4. Open the folder Expanded and open Distribution in a text editor
5. Find the function installationCheck() and put return true; at the very beginning
6. Remove the text installsOS=true from the same file
7. pkgutil --flatten Expanded Patched.mpkg
You will now have an install file "Patched.mpkg" that you can double-click and install to a HFS+ partition.

Patch the installed system to boot
1. On the partition, copy boot.efi from /usr/standalone/i386/ to /System/Library/CoreServices
2. Open /Library/Preferences/SystemConfiguration/com.apple.Boot.plist in a text editor
3. Make Kernel Flags as <string>-v -no_compat_check keepsyms=1</string>
This will make the disk bootable, bypass the prohibitory symbol (\) and show symbols in kernel panic logs (If it panics, let it reboot and pick your High Sierra partition; it should automatically show the log in "your computer was restarted because of a problem" dialog once it boots.)

Fix the kernel panic on Penryn systems
Replace from High Sierra:
/System/Library/UserEventPlugins/com.apple.telemetry.plugin

Patch USB
Replace from High Sierra:
/System/Library/Extensions/IOUSBHostFamily.kext

Patch audio
Replace from High Sierra:
/System/Library/Extensions/AppleHDA.kext

Recognize the Tesla GPU
Copy from High Sierra:
NVDANV50HalTesla.kext
NVDAResmanTesla.kext
IONDRVSupport.kext
IOGraphicsFamily.kext
This allows changing the brightness and shows the correct display in About This Mac

Enable the framebuffer
Copy from High Sierra:
GeForceTesla.kext
GeForceGA.kext
Partial acceleration.

Enable full acceleration
Copy from High Sierra
GeForceTeslaGLDriver.bundle
GeForceTeslaVADriver.bundle
Right now, this causes a kernel panic on login.

Fix kext permissions
sudo chmod -R 755 /Volumes/Mojave/System/Library/Extensions
sudo chown -R root /Volumes/Mojave/System/Library/Extensions
Replacing "Mojave" with the name of your partition. This'll allow the system to automatically rebuild the prelinkedkernel when you boot from the Mojave volume (it'll reboot after doing so).


That took longer to write than I expected, haha. Hope that helps. It's good to have a consolidated list of patches so far anyways, I've been meaning to make a post like this for a bit.

Edit: Does someone want to link this on the wikipost or something? Maybe decrease the amount of redundant questions so we can focus on moving forward 🙂

Edit 2: This is only for MacBook6,1 and MacBook7,1 systems.

Why couldn't it work with MB5,1?

 

[Starplayr]

I already tried the new NVidia webdrivers no go the one the change I did notice no option to show package contents in Mojave

Most of us have different video cards. More attempts the better.

 

[lefruitix]

No problem. I'm not writing this again though 😉

Patch the installer
1. Get a copy of the install app and open Contents/SharedSupport/InstallESD.dmg
2. Copy the folder Packages somewhere you can edit
3. cd to the folder and pkgutil --expand OSInstall.mpkg Expanded
4. Open the folder Expanded and open Distribution in a text editor
5. Find the function installationCheck() and put return true; at the very beginning
6. Remove the text installsOS=true from the same file
7. pkgutil --flatten Expanded Patched.mpkg
You will now have an install file "Patched.mpkg" that you can double-click and install to a HFS+ partition.

Patch the installed system to boot
1. On the partition, copy boot.efi from /usr/standalone/i386/ to /System/Library/CoreServices
2. Open /Library/Preferences/SystemConfiguration/com.apple.Boot.plist in a text editor
3. Make Kernel Flags as <string>-v -no_compat_check keepsyms=1</string>
This will make the disk bootable, bypass the prohibitory symbol (\) and show symbols in kernel panic logs (If it panics, let it reboot and pick your High Sierra partition; it should automatically show the log in "your computer was restarted because of a problem" dialog once it boots.)

Fix the kernel panic on Penryn systems
Replace from High Sierra:
/System/Library/UserEventPlugins/com.apple.telemetry.plugin

Patch USB
Replace from High Sierra:
/System/Library/Extensions/IOUSBHostFamily.kext

Patch audio
Replace from High Sierra:
/System/Library/Extensions/AppleHDA.kext

Recognize the Tesla GPU
Copy from High Sierra:
NVDANV50HalTesla.kext
NVDAResmanTesla.kext
IONDRVSupport.kext
IOGraphicsFamily.kext
This allows changing the brightness and shows the correct display in About This Mac

Enable the framebuffer
Copy from High Sierra:
GeForceTesla.kext
GeForceGA.kext
Partial acceleration.

Enable full acceleration
Copy from High Sierra
GeForceTeslaGLDriver.bundle
GeForceTeslaVADriver.bundle
Right now, this causes a kernel panic on login.

Fix kext permissions
sudo chmod -R 755 /Volumes/Mojave/System/Library/Extensions
sudo chown -R root /Volumes/Mojave/System/Library/Extensions
Replacing "Mojave" with the name of your partition. This'll allow the system to automatically rebuild the prelinkedkernel when you boot from the Mojave volume (it'll reboot after doing so).


That took longer to write than I expected, haha. Hope that helps. It's good to have a consolidated list of patches so far anyways, I've been meaning to make a post like this for a bit.

Edit: Does someone want to link this on the wikipost or something? Maybe decrease the amount of redundant questions so we can focus on moving forward 🙂

Edit 2: This is only for MacBook6,1 and MacBook7,1 systems.

And also I didn't get where to put those words. Here?

 

[ASentientBot]

I have verbose mode (nvram boot-args="-v") as a default on my mb air. Is there a way to capture the messages into a log that I could review later? It scrolls by so fast in the screen. BTW, I currently have no issues (finger's crossed) with @dosdude1's amazing 1.b4 mojave patch app.

Regards.

I wrote a few very simple scripts that I use for debugging boot messages. I'll attach them here. For verbose mode logs, dmesg works best. Edit: You can even just use sudo dmesg immediately after booting to see the most recent messages, but the buffer is pretty small. Edit: if you're encountering panics, adding keepsyms=1 to your boot args makes the panic logs a bit less cryptic.
[doublepost=1531266900][/doublepost]

And also I didn't get where to put those words. Here?View attachment 769978

No, further down it should say:
function installationCheck() {
... some code ...

Edit it like
function installationCheck() {return true;
... code ...

 

[nekton1]

As a hardware workaround for iMacs with AMD HD cards, has anyone tried replacing the MXM card with something like a Dell laptop PC MXM GTX 680M from nVidia? These cards are around although not very cheap yet. I suppose it would require the card to be flashed to a Mac efi but it might be doable for hardware nerds.

 

[netsrot39]

I've just tried the Beta 3 of Mojave on my MacBook 7,1. Installation and patching worked like a charm but I noticed upon login that the UI is rendering slowly. I've read the last pages of this thread and noticed that there is no real graphics acceleration as of now. I applied the legacy graphics patch and ended up with a kernel panic so my installation is stuck now (but maybe a PRAM reset and reapplying the other kexts could restore a functioning system without acceleration?) Hopefully there is a fix for this in the future. And again great work from you all 🙂 Thanks!!! 🙂

BTW: How far do you go back when it comes to trying out kexts? (El Capitan?)

 

[ASentientBot]

I've just tried the Beta 3 of Mojave on my MacBook 7,1. Installation and patching worked like a charm but I noticed upon login that the UI is rendering slowly. I've read the last pages of this thread and noticed that there is no real graphics acceleration as of now. I applied the legacy graphics patch and ended up with a kernel panic so my installation is stuck now (but maybe a PRAM reset and reapplying the other kexts could restore a functioning system without acceleration?) Hopefully there is a fix for this in the future. And again great work from you all 🙂 Thanks!!! 🙂

BTW: How far do you go back when it comes to trying out kexts? (El Capitan?)

Yep, that's to be expected. If you follow the kext list in my tutorial post (a page or two back, plus I believe @0403979 linked it on the wikipost) you can get framebuffer acceleration which is not much but it makes it semi-usable.

No need to reset PRAM, just delete the file
/System/Library/Extensions/GeForceTeslaGLDriver.bundle
and it should rebuild prelinkedkernel on reboot and no longer panic.

Edit: I believe Sierra and High Sierra have been tested. It wouldn't hurt to try El Capitan ones if you feel like it.

 

[Loyd-01a]

Yep, that's to be expected. If you follow the kext list in my tutorial post (a page or two back, plus I believe @0403979 linked it on the wikipost) you can get framebuffer acceleration which is not much but it makes it semi-usable.

No need to reset PRAM, just delete the file
/System/Library/Extensions/GeForceTeslaGLDriver.bundle
and it should rebuild prelinkedkernel on reboot and no longer panic.

Edit: I believe Sierra and High Sierra have been tested. It wouldn't hurt to try El Capitan ones if you feel like it.

Hi,

How do you manage high temperature and fan speed under Mojave for your macbook7,1.

From my hackintosh experience I know that if sleep doesn't work it means that power managment is not efficient. So I suspect that right know as long as sleep doesn't work under macbook7,1, temperature will still not correctly controlled by macOS.
But I wonder if you use a software to reduce high temperature and fan speed (be it for Mojave or even for High Sierra) ?

Another time congratulation for your discovery of what causes KP for MB7,1 and thank you for your efforts !

 

[dosdude1]

Hi,

How do you manage high temperature and fan speed under Mojave for your macbook7,1.

From my hackintosh experience I know that if sleep doesn't work it means that power managment is not efficient. So I suspect that right know as long as sleep doesn't work under macbook7,1, temperature will still not correctly controlled by macOS.
But I wonder if you use a software to reduce high temperature and fan speed (be it for Mojave or even for High Sierra) ?

Another time congratulation for your discovery of what causes KP for MB7,1 and thank you for your efforts !

Sleep will not work without proper graphics acceleration.

 

[Loyd-01a]

Sleep will not work without proper graphics acceleration.

Good to know !
Thanks

 

[DaniloGeekDude]

I wrote a few very simple scripts that I use for debugging boot messages. I'll attach them here. For verbose mode logs, dmesg works best. Edit: You can even just use sudo dmesg immediately after booting to see the most recent messages, but the buffer is pretty small. Edit: if you're encountering panics, adding keepsyms=1 to your boot args makes the panic logs a bit less cryptic.
[doublepost=1531266900][/doublepost]

No, further down it should say:
function installationCheck() {
... some code ...

Edit it like
function installationCheck() {return true;
... code ...

Thank You for the script and your link on the OP.

 

[Luckygreek]

You’re welcome. If you have a problem mention me and I’ll do my best to help you.

This is as far as I can get, any suggestions? The drive has been erased as APFS & connected via firewire, I did end up with a "BaseSystem.dmg"? Attached is a screenshot of error from the patch. The Mojave install is 5.63GB, v.14.0.12.

 

[dosdude1]

This is as far as I can get, any suggestions? The drive has been erased as APFS & connected via firewire, I did end up with a "BaseSystem.dmg"? Attached is a screenshot of error from the patch. The Mojave install is 5.63GB, v.14.0.12.

Check Disk Utility, and make sure InstallESD is not mounted. Then, run the tool again. Also, the tool is NOT installing the OS, it is creating a bootable installer (which you should be using an external USB drive for), which you then boot from and install the OS.

 

[ASentientBot]

Sleep will not work without proper graphics acceleration.

It actually seems to work with just the first two sets of kexts for recognizing the GPU and enabling the framebuffer. The *GLDriver* and *VADriver* bundles don't seem necessary.

@Loyd-01a

 

[Luckygreek]

Check Disk Utility, and make sure InstallESD is not mounted. Then, run the tool again. Also, the tool is NOT installing the OS, it is creating a bootable installer (which you should be using an external USB drive for), which you then boot from and install the OS.

thanks, dosdude1, it was mounted, unmount & moving forward, I do have a USB 32GB, that iMac has USB 2.0, figured it would go faster with Firewire. Will give the USB a try.. Thanks again for all the hard work you've put into "patcher" along with some many others.

 

[Loyd-01a]

It actually seems to work with just the first two sets of kexts for recognizing the GPU and enabling the framebuffer. The *GLDriver* and *VADriver* bundles don't seem necessary.

@Loyd-01a

Thank you
You mean installing GeForceTesla.kext and GeForceGA.kext from High Sierra ?
If it's the cas, I will use Kextutility for that...
Am I in the right direction ?

 

[ASentientBot]

Just figured out a workaround for the nVidia Tesla QE/CI crash!

The keyword here is workaround, while it may seem like a fix this is a dumb-as-heck solution. In the panic log, there's a function clientClose, or something. I basically just opened up GeForceTesla in Hopper Disassembler and NOP'ed that entire function. Yep, I just deleted the code that is causing the kernel panic. So you can see why this might not be a great solution...

Anyways, if you still want to try it (because it does work!)...

Install the previously kernel panicky bundle files...
Replace the GeForceTesla.kext's main executable with the one I attached here...
Fix permissions, rebuild kext cache etc...
And boot!

It's been working well enough for me to seriously consider making this my primary system, it feels 10x more responsive, I just played 10 minutes of Half-Life 2, etc. But who knows how stable it will be.

😀

Edit: better workaround later in the thread. This one causes the occasional extreme lag as apps start to fail to use OpenGL.