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, Apr 29, 2019
    Last edited: May 1, 2019

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3326
    Note to mods: Reference info - Please do not delete.


    144.0.0.0.0 released with 10.14.5 DP4:

    Code:
    $IBIOSI$ MP51.88Z.F000.B00.1904121248
    ‰Apple ROM Version
      Model:        MP51
      EFI Version:  144.0.0.0.0
      Date:         Fri Apr 12 12:43:00 2019
      Build Type:   Release
    
    Lots of EFI modules changed:

    • IoTrap
    • UsbBus.dxe, UhciDxe
    • DxeMain, UndiRuntimeDxe
    • HfsPlus.efi, APFSJumpStart, LegacyBootFS.efi
    • PchSerialGpio, PchSmbusDxe, PchSpiRuntime.efi, PchSmiDispatcher
    • SataController
    • SmbiosMisc
    • AppleGraphicsPolicy.efi

    Same microcodes:

    144.0.0.0.0 - microcodes.png


    10.14.5 DP4 updated MP5,1, IM19,1 and MBP11,4 BootROMs, this table does not include BridgeOS Macs:


    Mac:EFI version:
    IM13,1285.0.0.0.0
    IM14,1137.0.0.0.0
    IM14,2137.0.0.0.0
    IM14,3137.0.0.0.0
    IM14,4197.0.0.0.0
    IM15,1228.0.0.0.0
    IM16,1227.0.0.0.0
    IM16,2227.0.0.0.0
    IM17,1166.0.0.0.0
    IM18,1172.0.0.0.0
    IM18,3172.0.0.0.0
    IM19,1220.260.170.0.0
    MB10,1175.0.0.0.0
    MB8,1181.0.0.0.0
    MB9,1181.0.0.0.0
    MBA5,1257.0.0.0.0
    MBA6,1115.0.0.0.0
    MBA7,1186.0.0.0.0
    MBP10,1255.0.0.0.0
    MBP10,2278.0.0.0.0
    MBP11,1153.0.0.0.0
    MBP11,2153.0.0.0.0
    MBP11,4192.0.0.0.0
    MBP12,1184.0.0.0.0
    MBP13,1233.0.0.0.0
    MBP13,2256.0.0.0.0
    MBP13,3256.0.0.0.0
    MBP14,1194.0.0.0.0
    MBP14,2194.0.0.0.0
    MBP14,3194.0.0.0.0
    MBP9,1226.0.0.0.0
    MM6,1278.0.0.0.0
    MM7,1242.0.0.0.0
    MP5,1144.0.0.0.0
    MP6,1130.0.0.0.0
     
  2. LightBulbFun macrumors 68000

    LightBulbFun

    Joined:
    Nov 17, 2013
    Location:
    London UK
    #3327

    cool stuff, that BootROM chart is a handy reference :)

    BTW an interesting thing i noticed is with Security updates for 10.13.6 Apple also updated High sierra supported macs to the new boot rom format

    (or at least the new naming scheme)

    threw me for a loop when I first saw it :)
     
  3. startergo macrumors 6502a

    startergo

    Joined:
    Sep 20, 2018
  4. LightBulbFun macrumors 68000

    LightBulbFun

    Joined:
    Nov 17, 2013
    Location:
    London UK
    #3329
    I suspect it was an internal build, in that they pull 142, start work on 143 pushed to to internal testing, but then realised they still needed to make more improvements/bug fixes so they spun 144 :)
     
  5. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3330
    High Sierra Security Updates carry the current BootROM EFI version format for Macs that have it for a long time, at least 10.13.1.

    Howard Oakley tracks this since last year https://eclecticlight.co/2018/06/27/which-efi-firmware-should-your-mac-be-using-version-2/
     
  6. mrtang42 macrumors member

    Joined:
    Apr 19, 2019
    #3331
    Is there anyway to install 144.0.0.0.0 without fully reinstall the system?
     
  7. Nabru50 macrumors newbie

    Nabru50

    Joined:
    Aug 24, 2017
    Location:
    United States
    #3332
    Check the first post, you don't need to reinstall macOS. Just download installer and let the firmware update without installing macOS.

    Edit: Never mind, not sure about 144.0.0.0.0 myself
     
  8. crjackson2134, Apr 29, 2019
    Last edited: Apr 29, 2019

    crjackson2134 macrumors 601

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #3333
    If you are asking, you shouldn't test beta BootROMs. No one besides those who can reprogram the SPI flash memory or have replacement backplanes should install beta BootROMs.

    All the information you need is in the FIRST POST!

    IL
     
  9. MisterAndrew macrumors 65816

    MisterAndrew

    Joined:
    Sep 15, 2015
    Location:
    Portland, Oregon
    #3334
    Once 10.14.5 final is released you can download the full installer as Nabru50 said. Keep in mind 144.0.0.0.0 is a developer beta and it may not be the firmware released with the 10.14.5 final release. I suggest do not install it and let the beta users test it first who also have the ability to restore their old firmware in case something goes wrong.
     
  10. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3335
    I already extracted 144.0.0.0.0 EFI modules to compare with 141.0.0.0.0 and 142.0.0.0.0 and track what was updated, but I have a deadline for tomorrow and can't analyse it today.

    I'll check 144.0.0.0.0 changes in the holiday.

    BTW, I did not installed it yet and recent history shows no one besides who can recover from a bad firmware should do it.
     
  11. mrtang42, Apr 29, 2019
    Last edited: Apr 29, 2019

    mrtang42 macrumors member

    Joined:
    Apr 19, 2019
    #3336
    I have the SPI programer and know what I am doing. So the answer is no. Public beta only come with update package rather than full OS installer(Looks like this only required by cMP). Thank you for your info.
     
  12. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3337
    If you know what you are doing, why you are asking? :rolleyes:

    No one should install beta BootROMs. Stop asking.

    This thread will need a clean-up today.
     
  13. mrtang42 macrumors member

    Joined:
    Apr 19, 2019
    #3338
    Beta is for people to test, right?
     
  14. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3339
    If Apple wanted that non developers test beta BootROMs, it would be readily available and not hidden.
     
  15. LightBulbFun, Apr 29, 2019
    Last edited: Apr 29, 2019

    LightBulbFun macrumors 68000

    LightBulbFun

    Joined:
    Nov 17, 2013
    Location:
    London UK
    #3340
    Model: IM101
    EFI Version: 214.0.0.0.0
    Date: Wed Dec 19 16:03:38 2018
    Build Type: Release

    clearly they need to update their page as for example here is the latest BootROM for the Late 2009 Core 2 Duo iMac

    I was just noting that I find it most interesting how apple is continuing to update the boot rom of these legacy machines even after dropping OS support for them :)

    (I only found out about this after a friends machine displayed the new BR format, as I only checked for new BootROMs in Mojave which of course dont contain BR updates for any non supported machines, then I remembred sometimes security updates contain BR updates, so I checked the latest 10.13.6 Security update at the time and low and behold, a bunch of new format BootROMs for legacy late 2009-2011 machines)

    edit: I see the source you linked has an updated page themselves https://eclecticlight.co/2018/10/31/which-efi-firmware-should-your-mac-be-using-version-3/
     
  16. mrtang42 macrumors member

    Joined:
    Apr 19, 2019
    #3341
    Actually, it is not hidden. The beta bootrom is also included in the public beta. It is not developer exclusive! All other Macs can receive the update via public beta delta package. It is just the cMP legacy bootrom update mechanism.
     
  17. tsialex, Apr 29, 2019
    Last edited: Apr 29, 2019

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3342
    Please stop, you are being obnoxious.

    I’m not going to post where/how to install it. This thread intentionally don’t have a how to on beta BootROMs to keep people from installing it. Even people who are registered Apple developers bricked MP5,1 recently and Apple gave zero support.

    You are free to do whatever you want with your Mac Pro, but this info will not be posted here, I talked about this numerous times.

    The only thing that you are accomplishing with your posts is a thread clean up.
     
  18. crjackson2134 macrumors 601

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #3343
    Same with W3680 - Just adding a data point.
     
  19. tsialex, May 1, 2019
    Last edited: May 1, 2019

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3344
    Started doing diffs between 142 and 144 and the first thing that I noticed is that 144.0.0.0.0 removed the public keys that 142 added.

    Why?o_O

    Blank_00.JPG Blank_01.JPG Blank_02.JPG Blank_03.JPG Blank_04.JPG Blank_05.JPG Blank_06.JPG Blank_07.JPG Blank_08.JPG Blank_09.JPG
     
  20. tsialex, May 1, 2019
    Last edited: May 1, 2019

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3345
    Post edited to remove any possible confusion about it.

    144.0.0.0.0 diffs from 142.0.0.0.0 with 0 insertions, 8 deletions and 39 modifications.

    One thing that got my attention was the first time Apple updated AppleGraphicsPolicy.efi since I'm tracking the modules differences between BootROM releases.

    Screen Shot 2019-05-01 at 10.08.12.png Screen Shot 2019-05-01 at 10.10.28.png


    Everything that changed between 142.0.0.0.0 and 144.0.0.0.0, sorted by GUID order:

    Code:
    18CEC42B-F0FC-4EFA-84AE-27D2184E873A - ??
    2374EDDF-F203-4FC0-A20E-61BAD73089D6 - IoTrap
    240612B7-A063-11D4-9A3A-0090273FC14D - UsbBus.dxe
    2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7 - UhciDxe
    35B898CA-B6A9-49CE-8C72-904735CC49B7 - DxeMain
    4CF484CD-135F-4FDC-BAFB-1AA104B48D36 - HfsPlus.efi
    4D37DA42-3A0C-4EDA-B9EB-BC0E1DB4713B - PpisNeededByDxeCore.pei
    7EC21E57-CE8A-4FDE-B147-0F7C0959CD3F - ??
    8A107CC5-DCDA-4FB7-A272-4243B41AFBFE - AppleGraphicsPolicy.efi
    8E6BD67D-1872-4932-A39A-FC9DCA4A98CF - ??
    A1F436EA-A127-4EF8-957C-8048606FF670 - UndiRuntimeDxe
    AB8DDBAA-9C47-429B-9D12-326F273D9B88 - ??
    ABBCE13D-E25A-4D9F-A1F9-2F7710786892 -- Platform
    B0D6ED53-B844-43F5-BD2F-61095264E77E - PchSmiDispatcher
    B2CB10B1-714A-4E0C-9ED3-35688B2C99F0 -- public keys
    BB1FBD4F-2E30-4793-9BED-74F672BC8FFE - PchResetRuntime
    BB65942B-521F-4EC3-BAF9-A92540CF60D2 - SataController
    C194C6EA-B68C-4981-B64B-9BD271474B20 - PchSpiRuntime.efi
    C3E36D09-8294-4B97-A857-D5288FE33E28 - BIOS version
    CC582C73-F48F-4B62-83E8-A586B4C88F84 - AppleFirmwareFeatures.efi
    CFFB32F4-C2A8-48BB-A0EB-6C3CCA3FE847 - APFSJumpStart
    DF9A9591-B646-4621-AF0D-18143A73289F - LegacyBootFS.efi
    E052D8A6-224A-4C32-8D37-2E0AE162364D - PchSmbusDxe
    EF0C99B6-B1D3-4025-9405-BF6A560FE0E0 - SmbiosMisc
    FC1B7640-3466-4C06-B1CC-1C935394B5C2 - PchSerialGpio
    
    144.0.0.0.0 have changes on various subsystems and seems a great update without any unintended problems identified until now.
     
  21. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3346
    Updated post #3326 with the info I got from the diff between 142.0.0.0.0 and 144.0.0.0.0. Blank_00.JPG
     
  22. thomasthegps macrumors regular

    Joined:
    Sep 23, 2015
    Location:
    France
    #3347
    Could this be apple adding boot screen support ?
     
  23. tsialex, May 1, 2019
    Last edited: May 1, 2019

    tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3348
    Thanks moderation for the fast clean-up of the thread.
     
  24. phoenix.factory macrumors newbie

    phoenix.factory

    Joined:
    Oct 9, 2018
    Location:
    Switzerland
    #3349
    Any reason why my cMP 2009 shows 141.0.0.0 and cMP 2010 shows 141.0.0.0.0 ?
     
  25. tsialex thread starter macrumors 601

    tsialex

    Joined:
    Jun 13, 2016
    Location:
    Brazil
    #3350
    Sierra/earlier macOS releases vs High Sierra/Mojave.
     
Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page