MP 1,1-5,1 MP5,1: BootROM thread | 144.0.0.0.0 is a pre-requisite to disable Hyper-threading

Discussion in 'Mac Pro' started by tsialex, Aug 13, 2018.

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

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1226
    You are totally missing the point of my original post, read it. A 3rd party boot loader showing boot picker is within reach, but do you think that anyone but Apple will change the MP51 firmware to use UEFI?
     
  2. Roadmap123 macrumors newbie

    Roadmap123

    Joined:
    Sep 25, 2018
    Location:
    Germany
    #1227
    So I have now Mojave running on my 4,1->5,1 with RX580 onto Bootrom 138.0.0.0.0

    Everything works fine, as far as I see now.

    Now my question:

    I read nearly every post on the 50 pages, but didn't see a success story of injecting the EFI Patch for NVME with boot support into Mojave system.

    So how to so this now on my system, same like the previous instruction for HS?
     
  3. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1228
    Yep.
     
  4. Roadmap123 macrumors newbie

    Roadmap123

    Joined:
    Sep 25, 2018
    Location:
    Germany
    #1229
    Thanks for fast response. As far as I understand the injection for nvme, it can stop working with every minor MacOS Update? So using it means, not really update just right away??
     
  5. bookemdano macrumors 65816

    Joined:
    Jul 29, 2011
    #1230
    I read your post--there is no reason to be rude. The post of yours I responded to was trying to make a distinction between the 3,1 and 4,1 and I'm saying that distinction doesn't matter in this context. Apple isn't going to add UEFI to either machine, but boot screens (which is all anyone really cares about when speaking about EFI/UEFI) were achieved on the 3,1.

    And honestly, I and many others here thought there was a possibility Apple would do it, simply because I didn't think they would officially support the crippled state the cMP ends up in without pre-boot graphics output. When they started adding microcodes and other improvements to the firmware I was even more encouraged, because obviously they set aside $$ and time for their engineers to bring the cMP up to snuff.

    The fix we did get (5GT/s) is pretty arbitrary in my opinion. Why fix that but not HDMI audio (which is so trivial)? Almost like they ran out of $$ in their budget after having to re-do the microcode additions three times and basically said "well, this is all they're going to get".

    My biggest qualm is that Apple is not adequately explaining the functionality cMP users will lose as soon as they buy a "recommended" GPU (whether they end up upgrading to Mojave or not). FileVault is not a trivial feature, especially in this day and age--not to mention being able to use verbose mode to troubleshoot issues.
     
  6. h9826790 macrumors G5

    h9826790

    Joined:
    Apr 3, 2014
    Location:
    Hong Kong
    #1231
    IMO, no one talk about it because nothing changed.
    --- Post Merged, Sep 25, 2018 ---
    Incorrect.

    That's firmware level NVMe support, OS version independent.
     
  7. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1232
    Only with BootROM updates, so no.
     
  8. flowrider macrumors 603

    flowrider

    Joined:
    Nov 23, 2012
    #1233
    Of all the members, the one I consider the be the most helpful and the least rude is tsialex. Rethink your comment
    image.png



    Lou
     
  9. Roadmap123 macrumors newbie

    Roadmap123

    Joined:
    Sep 25, 2018
    Location:
    Germany
    #1234
    OK. Point for you ;-)

    Means as long as I don't update any Firmware of my cMP or be forced to do this by a future Update, it will just work?
     
  10. bookemdano macrumors 65816

    Joined:
    Jul 29, 2011
    #1235
    Thanks for your helpful addition to this thread. I don't appreciate being accused of not reading a post I clearly read, by you or anyone else. tsialex is indeed one of the most helpful members here--doesn't mean he can't err.
     
  11. h9826790 macrumors G5

    h9826790

    Joined:
    Apr 3, 2014
    Location:
    Hong Kong
    #1236
    Correct.
     
  12. tsialex, Sep 25, 2018
    Last edited: Sep 25, 2018

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1237
    I wasn't being rude, sorry about that. I'm not a native english speaker, I was being direct.

    MP3,1 and MP5,1 hardware and firmware are totally different beasts. MP5,1 firmware are a lot more similar with a iMac11,1 than with a MP3,1. Comparison between MP3,1 and MP5,1 are almost useless since you can't transplant things from one to the other. I tried that and got two bricks already.

    The firmware are structured differently internally, EFI modules are similar and most can be interchangeable within processor support limitations, but stops there. Not even the way checksums are made are the same.
     
  13. star-affinity macrumors 6502a

    star-affinity

    Joined:
    Nov 14, 2007
    #1238
    You mean a cheap Mac EFI Kepler card?

    Because I have a ”non-Mac” GTX 1070 that should support Mojave when (if…) Nvidia releases their drivers for it.
     
  14. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1239
    Yep.

    You can't debug/troubleshoot or do a clean install of Mojave, unless you use startosinstall --installpackage with a modified NVIDIA web driver.
    --- Post Merged, Sep 25, 2018 ---
    Mojave and NVIDIA Maxwell/Pascal cards will be really difficult to install without using a supported card.
     
  15. Roadmap123 macrumors newbie

    Roadmap123

    Joined:
    Sep 25, 2018
    Location:
    Germany
    #1240
    Did everything as described in the Google Docs Document, only thing I miss: Can I reenable SIP after flashing the injected Rom??!
     
  16. h9826790 macrumors G5

    h9826790

    Joined:
    Apr 3, 2014
    Location:
    Hong Kong
    #1241
    Yes, that SIP disabled is only for firmware flashing. Once finished that part, you can re-enable it.
     
  17. tsialex, Sep 25, 2018
    Last edited: Sep 25, 2018

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1242
    Apple released 10.14.1beta1, build 18B45d.

    --- Post Merged, Sep 25, 2018 ---
    Welcome 139.0.0.0.0

    Screen Shot 2018-09-25 at 17.56.27.png
    --- Post Merged, Sep 25, 2018 ---
    139.0.0.0.0 - still no NVMe EFI module for Mac Pro. I'll check the rest ASAP.
    --- Post Merged, Sep 25, 2018 ---
    Code:
    $IBIOSI$ MP51.88Z.F000.B00.1808171030
    Apple ROM Version
      Model:        MP51
      EFI Version:  139.0.0.0.0
      Date:         Fri Aug 17 10:24:21 2018
      Build Type:   Release
    
     
  18. TheIguana macrumors 6502a

    TheIguana

    Joined:
    Sep 26, 2004
    Location:
    Canada
    #1243
    Cool, so perhaps Apple's team just ran out of time for work on the firmware before the ship date on the GM this month!
     
  19. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1244
    I'll reconstruct my Mac Pro BootROM to test 139.0.0.0.0.
    --- Post Merged, Sep 25, 2018 ---
    Screen Shot 2018-09-25 at 18.30.33.png
    --- Post Merged, Sep 25, 2018 ---
    Screen Shot 2018-09-25 at 18.32.37.png
    --- Post Merged, Sep 25, 2018 ---
    Nothing different on System Information. Seems snappy.
     
  20. MIKX macrumors 6502a

    MIKX

    Joined:
    Dec 16, 2004
    Location:
    Japan
    #1245
    I would pay good money for a mechanical switch ( like those dual bios switches on AMD GPUs ) that would enable me to ( prior to cold boot ) switch from MP51.0089.B00 & 139.0.0.0 - and I am not joking.

    tsialex .. the cMP world awaits your talents.

    :)
     
  21. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1246
    Start saving;)
     
  22. MIKX macrumors 6502a

    MIKX

    Joined:
    Dec 16, 2004
    Location:
    Japan
  23. tsialex, Sep 25, 2018
    Last edited: Sep 25, 2018

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1248
    Flashed my vanilla reconstructed one, everything worked here. Now I’m gonna flash the NVMe v124 one.
    --- Post Merged, Sep 25, 2018 ---
    Booting Recovery with the NVMe BootROM to disable SIP. Seems to be working too.
    --- Post Merged, Sep 25, 2018 ---
    Double boot, yet… :mad:
    --- Post Merged, Sep 25, 2018 ---
    Screen Shot 2018-09-25 at 15.14.15.png
    --- Post Merged, Sep 25, 2018 ---
    Lot’s of restarts, 10.14b1 update seems interminable.
    --- Post Merged, Sep 25, 2018 ---
    Screen Shot 2018-09-25 at 15.29.25.png
    --- Post Merged, Sep 25, 2018 ---
    Reconstructed @h9826790 and @Matty_TypeR BootROMs with 139.0.0.0.0, to get more people testing/searching. @crjackson2134 did it himself :p

    No changes here:
    Screen Shot 2018-09-25 at 19.52.22.png
     
  24. tsialex, Sep 25, 2018
    Last edited: Sep 25, 2018

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #1249
    No FileVault2 yet…
    Screen Shot 2018-09-25 at 15.59.19.png

    Same microcodes:

    Screen Shot 2018-09-25 at 16.03.55.png
     
  25. fhturner macrumors 6502

    fhturner

    Joined:
    Nov 7, 2007
    Location:
    Birmingham, AL & Atlanta, GA
    #1250
    Being a point-release instead of full beta, are you still able to download a full installer in order to apply the firmware? Or is it being applied by the updater now? Sorry to be dense...I'm usually on top of this, but sometimes get confused!
     
Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page