Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 High Sierra issues using Mojave 144 BootROM

M

MVMNT

macrumors 6502a
Original poster
Apr 28, 2010
535
709
Can anyone help please? I've updated the bootROM using the Mojave installer, but have decided to stay on High Sierra for the time being. If it ain't broke, right?

Well now it is... I'm now getting intermittent crashes to black screen, with a white message screen and hard reset at the end (essentially like a kernal panic) especially when using After Effects.

Any ideas if this is down to using the later bootROM? I'm using an Nvidia GFX card and can't afford the performance hit after seeing how bad it is on a works machine.
 
What NVIDIA web driver version are you on?
What NVIDIA CUDA version are you on?
What EXACT build of High Sierra are you on?
How are you powering your GPU?
What exact version/build of After Effects?
Any specific plugins or effects being used during those crashes?
Do they happen during renders or only while working/preview?
 
  • Like
Reactions: bvhprods
Your problem is not related to the 144.0.0.0.0 version, it works perfectly with High Sierra and NVIDIA GPUs and I have one Mac Pro with this config. Start debugging by cleaning the NVRAM 3 times in sequence, then reinstall the current NVIDIA drivers and then check everything else.
 
  • Like
Reactions: bvhprods and h9826790
bsbeamer said:
What NVIDIA web driver version are you on?

Up to date 387.10.10.10.40.128

What NVIDIA CUDA version are you on?

Up to date 418.163

What EXACT build of High Sierra are you on?

10.13.6 (17G7024)

How are you powering your GPU?

It's a Mac EFi NVIDIA GeForce GTX 680 2048 MB

What exact version/build of After Effects?

Happen with both 2018 and 2019

Any specific plugins or effects being used during those crashes?

Nope

Do they happen during renders or only while working/preview?

Any time. Has notably been a few times with quick view and swapping back in out of app with that open.
Click to expand...
 
  • Like
Reactions: bvhprods

High Sierra build #17G8030 (which is the latest) will also give you the 144.0.0.0.0 boot rom. I tried it recently on my Mac Pro and flashed it. The latest EFI boot rom came with the High Sierra supplemental update. This latest supplemental update did also update my firmware EFI bootrom on my Macbook Air to the same as Mojave would do. Maybe you need to update your High Sierra build to the latest, update your Nvidia driver to match build #17G8030 and perhaps this would solve your problem.

Correct latest Nvidia Driver 40.130 for build #17G8030

https://www.nvidia.com/download/driverResults.aspx/149652/
 
Last edited:
  • Like
Reactions: bvhprods
iluvmacs99 said:
High Sierra build #17G8030 (which is the latest) will also give you the 144.0.0.0.0 boot rom. I tried it recently on my Mac Pro and flashed it. The latest EFI boot rom came with the High Sierra supplemental update. This latest supplemental update did also update my firmware EFI bootrom on my Macbook Air to the same as Mojave would do. Maybe you need to update your High Sierra build to the latest, update your Nvidia driver to match build #17G8030 and perhaps this would solve your problem.

Correct latest Nvidia Driver 40.130 for build #17G8030

https://www.nvidia.com/download/driverResults.aspx/149652/
Click to expand...
This is incorrect, Security Updates can't flash Mac Pro 5,1 BootROM and even the new Recovery Update for 17G8030, who can be used to manually flash a MP51 BootROM, still has MP51.0085.B00.

Screen Shot 2019-09-04 at 01.32.35.png
 
  • Like
Reactions: bvhprods and bsbeamer
tsialex said:
You can only get 144.0.0.0.0 running the full installer for 10.14.5 or 10.14.6.
Click to expand...

I didn't run the Mojave installer? So how did I get the 144.0.0.0.0 . All you did was to say it's impossible, but it's done. I never intended to upgrade the firmware to 144.0.0.0.0 as I didn't want to mess the rom, but was surprised to find m Nvidia driver, same as the OP, WAS INCOMPATIBLE. That's how I knew about the build 17G8030! How else did I know this new driver? I have an Nvidia card running along side RX580.
 
  • Like
Reactions: bvhprods
iluvmacs99 said:
I didn't run the Mojave installer? So how did I get the 144.0.0.0.0 . All you did was to say it's impossible, but it's done. I never intended to upgrade the firmware to 144.0.0.0.0 as I didn't want to mess the rom, but was surprised to find m Nvidia driver, same as the OP, WAS INCOMPATIBLE. That's how I knew about the build 17G8030! How else did I know this new driver?
Click to expand...
You are mistaken, see the screenshot, SecUpd2019-004HighSierra.RecoveryHDUpdate.pkg still has MP51_0085_B00_LOCKED.fd.

There are no other way to update a MP51 BootROM, it's the last Mac that have the manual method of firmware updates.
 
  • Like
Reactions: bvhprods and bsbeamer
General question: do Boot-ROM and OS version have to match up? Asking because I also have a newer ROM (from Mojave 10.14.1) than OS (10.13.6) and have experienced two crashes within 10 months which - going by dmesg output - I attribute to a rare GPU (driver) malfunction.
Is this something a close match between OS and ROM are supposed to prevent?
 
  • Like
Reactions: bvhprods
th0masp said:
General question: do Boot-ROM and OS version have to match up? Asking because I also have a newer ROM (from Mojave 10.14.1) than OS (10.13.6) and have experienced two crashes within 10 months which - going by dmesg output - I attribute to a rare GPU (driver) malfunction.
Is this something a close match between OS and ROM are supposed to prevent?
Click to expand...
No. BootROM only works before, probing and configuring the hardware, and at boot time, loading the OS. After the OS loads, hardware control is transferred to the OS.

Apple policy for all Macs that have automatic firmware updates since Sierra is to have the current BootROM release, every time a new firmware update is available, it will be installed automatically and transparently. The exception to the usage of the current BootROM everywhere is MP5,1, where the firmware updates are still manual.
 
  • Like
Reactions: bvhprods, th0masp, crjackson2134 and 1 other person
Is it possible after Updating to 144. then put back the original ATI 5770 card back in to take advantage of using High Sierra for NVMe boot. Will one also be able to boot Older OS like Mt. Lion since you have the original video card in the machine ? On a separate drive of course.
 
Last edited:
  • Like
Reactions: bvhprods
basslik said:
Is it possible after Updating to 144. then put back the original ATI 5770 card back in to take advantage of using High Sierra for NVMe boot. Will one also be able to boot Older OS like Mt. Lion since you have the original video card in the machine ? On a separate drive of course.
Click to expand...
Anybody Please ?
 
  • Like
Reactions: bvhprods
basslik said:
Is it possible after Updating to 144. then put back the original ATI 5770 card back in to take advantage of using High Sierra for NVMe boot. Will one also be able to boot Older OS like Mt. Lion since you have the original video card in the machine ? On a separate drive of course.
Click to expand...
tsialex said:
- 144.0.0.0.0 and previous macOS releases note:

Yes, BootROM 144.0.0.0.0 can boot even 10.6.4 (10F2521), the first ever macOS release that supports a MP5,1, but you are limited to GPU driver support since you can't boot a macOS version that don't have drivers for your GPU. For example, with AMD RX 4xx/5xx GPUs, you are limited to 10.12.6/10.13/10.14.It's the distribution file inside the macOS installer that defines what Macs are supported. Earlier releases than 10.6.4 (10F2521) don't have MP5,1 support and are not bootable with a MP5,1. Several people on MacRumors checked 10.6.8 and it runs without any problems with 144.0.0.0.0.
Other limitation is NVMe support if you have a NVMe drive, NVMe only works since High Sierra (Sierra for 4KB/sector drives), read the first post of the PCIe SSDs - NVMe & AHCI thread to know more. SATA support is not affected by NVMe support requirements.
Click to expand...
 
  • Like
Reactions: bvhprods, basslik and Macschrauber
Thank you Alex. greatly appreciate all you folks.
Quick reason. Will track in Pro Tools 10 with stable ML via OpenCore. Then mix in Mojave. YAHOO
 
I am running High Sierra macOS 10.13.6 (17G14042) on a Mid 2010 Mac Pro with Boot ROM Version: 144.0.0.0.0, Graphics card ATI Radeon HD 5870. My Mac has been crashing (panic attack?) every week or so. Black screen—then reboots. When I bought the Mac Pro it was running Mojave I believe. What might the problem be?! Thank you all very much!!!
 
bvhprods said:
I am running High Sierra macOS 10.13.6 (17G14042) on a Mid 2010 Mac Pro with Boot ROM Version: 144.0.0.0.0, Graphics card ATI Radeon HD 5870. My Mac has been crashing (panic attack?) every week or so. Black screen—then reboots. When I bought the Mac Pro it was running Mojave I believe. What might the problem be?! Thank you all very much!!!
Click to expand...

Run AHT/ASD and see if you can narrow the problem. Also do a clean install to a spare drive and see if the problem is software wise.
 
  • Like
Reactions: bvhprods
tsialex said:
Run AHT/ASD and see if you can narrow the problem. Also do a clean install to a spare drive and see if the problem is software wise.
Click to expand...
Read over the AHT/ASD pages. Seems a bit much for me to deal with. AHT is not available on my Mac Pro via the D key nor does the Option-D keys. Is there another way to do the AHT? Please advise. Thank you!
 
  • Like
Reactions: bvhprods
tsialex said:
While it's not exactly easy, it's one of the simplest procedures of the whole diagnostic process…



Only works this way if the Mac Pro was never erased from the factory install.



No.
Click to expand...
I gave [it] another read. I think I figured it out—just have to do it now!!! Thanks for pointing me in the right direction. I will report back...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back