macOS 10.14 Mojave on Unsupported Macs Thread

Discussion in 'macOS Mojave (10.14)' started by dosdude1, Jun 4, 2018.

Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
  1. testheit macrumors newbie

    Joined:
    Jun 8, 2018
    #2101
    Maybe OpenGL.framework since the last entries right before the KP in the DYLD-log-file are pointing to this framework...
     
  2. Julian Marius Fairfax macrumors 6502a

    Julian Marius Fairfax

    Joined:
    Jun 11, 2018
    Location:
    Switzerland
    #2102
    Good that you have it working now.
    --- Post Merged, Jul 10, 2018 ---
    It should be replaced with the equivalent from High Sierra if one exists. Some try this.
     
  3. jackluke, Jul 10, 2018
    Last edited: Jul 10, 2018

    jackluke macrumors 6502a

    jackluke

    Joined:
    Jun 15, 2018
    #2103
    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.
     
  4. gugadj, Jul 10, 2018
    Last edited: Jul 10, 2018

    gugadj macrumors member

    Joined:
    Jul 5, 2018
    #2104
    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
     

    Attached Files:

  5. jackluke, Jul 10, 2018
    Last edited: Jul 10, 2018

    jackluke macrumors 6502a

    jackluke

    Joined:
    Jun 15, 2018
    #2105
    Here are the dependencies I found on IOAccelerator from HS:

    Code:
    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.
     
  6. Starplayr macrumors 6502

    Starplayr

    Joined:
    Jun 13, 2018
    Location:
    Charlotte
    #2106
    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.
     
  7. TimothyR734 macrumors 6502a

    TimothyR734

    Joined:
    Apr 10, 2018
    Location:
    Logsden Oregon
    #2107
    I already tried the new NVidia webdrivers no go the one the change I did notice no option to show package contents in Mojave
     
  8. DaniloGeekDude macrumors regular

    DaniloGeekDude

    Joined:
    Jun 17, 2018
    #2108
    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.
     
  9. lefruitix macrumors newbie

    Joined:
    Jul 10, 2018
    #2109
    Why couldn't it work with MB5,1?
     
  10. Starplayr macrumors 6502

    Starplayr

    Joined:
    Jun 13, 2018
    Location:
    Charlotte
    #2110
    Most of us have different video cards. More attempts the better.
     
  11. lefruitix macrumors newbie

    Joined:
    Jul 10, 2018
    #2111
    And also I didn't get where to put those words. Here? upload_2018-7-11_2-36-7.png
     
  12. ASentientBot, Jul 10, 2018
    Last edited: Jul 10, 2018

    ASentientBot macrumors 6502

    ASentientBot

    Joined:
    Jun 27, 2018
    Location:
    the System suitcase
    #2112
    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.
    --- Post Merged, Jul 10, 2018 ---
    No, further down it should say:
    function installationCheck() {
    ... some code ...

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

    Attached Files:

  13. nekton1 macrumors 6502a

    Joined:
    Apr 15, 2010
    Location:
    Asia
    #2113
    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.
     
  14. netsrot39 macrumors member

    Joined:
    Feb 7, 2018
    Location:
    Austria
    #2114
    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?)
     
  15. ASentientBot macrumors 6502

    ASentientBot

    Joined:
    Jun 27, 2018
    Location:
    the System suitcase
    #2115
    Yep, that's to be expected. If you follow the kext list in my tutorial post (a page or two back, plus I believe @Julian Marius Fairfax 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.
     
  16. Loyd-01a macrumors member

    Joined:
    Oct 10, 2014
    #2116
    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 !
     
  17. dosdude1 thread starter macrumors 68000

    dosdude1

    Joined:
    Feb 16, 2012
    #2117
    Sleep will not work without proper graphics acceleration.
     
  18. Loyd-01a macrumors member

    Joined:
    Oct 10, 2014
    #2118
    Good to know !
    Thanks
     
  19. DaniloGeekDude macrumors regular

    DaniloGeekDude

    Joined:
    Jun 17, 2018
    #2119
    Thank You for the script and your link on the OP.
     
  20. Luckygreek macrumors regular

    Luckygreek

    Joined:
    May 14, 2018
    Location:
    Florida
    #2120
    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.
     

    Attached Files:

  21. dosdude1 thread starter macrumors 68000

    dosdude1

    Joined:
    Feb 16, 2012
    #2121
    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.
     
  22. ASentientBot macrumors 6502

    ASentientBot

    Joined:
    Jun 27, 2018
    Location:
    the System suitcase
    #2122
    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
     
  23. Luckygreek macrumors regular

    Luckygreek

    Joined:
    May 14, 2018
    Location:
    Florida
    #2123
    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.
     
  24. Loyd-01a macrumors member

    Joined:
    Oct 10, 2014
    #2124
    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 ?
     
  25. ASentientBot, Jul 10, 2018
    Last edited: Sep 27, 2018

    ASentientBot macrumors 6502

    ASentientBot

    Joined:
    Jun 27, 2018
    Location:
    the System suitcase
    #2125
    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.

    :D

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

    Attached Files:

Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page