Benches Mac desktops

9

2006 Mac Pro & EFI Firmware Update 1.2

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Wondering if anyone has any thoughts on this...

Just upgraded to Snow Leopard and was prompted to apply the EFI Firmware Update 1.2... so I did as requested... MP shuts down and I hold down the power button until I see the power light pulse rapidly... I see what looks like the start of an update (w/ the progress bar) but then the MP immediately reboots, returning to the Update application...

I should mention I tried holding down the power button through the tone as well, to no avail...

My Boot ROM Version: MP11.005C.B00

Thanks!

9 replies

Sign in or join Beachball Help to reply.

  1. 0

    The hatter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Mac Pro EFI Firmware Update 1.2

    Post Date: September 27, 2007

    http://support.apple.com/downloads/MacPro_EFI_Firmware_Update_12

    After the firmware is successfully applied to your computer, your BootROM Version will be either:

    MP11.005C.B08 or MP21.007F.B06

    To complete the firmware update process, *please follow the instructions in the updater applicatio*n (/Applications/Utilities/Mac Pro EFI Firmware Update.app). The updater will launch automatically when the Installer closes.

    For more information about firmware updates for Intel-based Macs,

    please visit:

    http://docs.info.apple.com/article.html?artnum=303364

  2. 0

    Justin Surpless

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yup... already seen those instructions... for some reason, it starts to apply the update (I see the progress bar) but then it reboots (as if it's decided it's not valid or whatever...

  3. 0

    The hatter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It came out TWO years ago.

    Seems odd you would just be seeing it.

    There are/were some restrictions, I think, like not being running or booting off RAID volume.

  4. 0

    Justin Surpless

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, I saw Update 1.1 for some time but never installed it... was satisfied as to how my machine ran so I saw no reason to do so...

  5. 0

    jaimeandalex

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just bought SL and because EFI only 32 on mac pro 2006 can not load 64 kernal. Anyone have any info if this can be changed.

  6. 0

    The hatter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    There are hundreds of threads and posts, and some serious articles. It is a non-issue. You aren'lt losing and there isn't a benefit to having a 64-bit kernel loaded.

  7. 0

    Justin Surpless

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you saying that the EFI Update 1.2 is 64-bit and that's why I am unable to load it?

  8. 0

    The hatter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I wasn't replying to you, but someone else that jumped into your thread.

    A good starter on Snow Leopard:

    http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars

    ----

    Created the emergency EFI CD yet? There was also an SMC firmware update around the same time (Aug-Sept '07)

  9. 0

    The hatter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Some tests of Leopard vs Snow Leopard and 32-bit vs 64-bit

    http://macperformanceguide.com/SnowLeopard-Performance.html

    Snow Leopard is faster than Leopard regardless of 32/64-bit issue. Tests were of course done on a 2009 and using 4-drive stripe (to reduce impact of disk I/O from tests).

    OpenCL synthetic tests (there aren't any apps that tap into this technology)

    http://www.barefeats.com/opencl.html

    Reasons why you may not want the slight advantage 64-bit mode offers (from PerformanceGuide):

    *Sonnet Tempo E4P* Sonnet suggest that there will be some issues with 64-bit mode, but should be resolved quickly. Running in 32-bit mode should be fine. Be sure to update to driver version 2.1.9 (or later if there is one).