MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[tsialex]

10.14.4 DP5 didn't bring a new BootROM for MP5,1, still 142.0.0.0.0:

$IBIOSI$ MP51.88Z.F000.B00.1902142049
‰Apple ROM Version
  Model:        MP51
  EFI Version:  142.0.0.0.0
  Date:         Thu Feb 14 20:43:08 2019
  Build Type:   Release

No changes for MP6,1 too:

$IBIOSI$ MP61.88Z.F000.B00.1902141849
Copyright (c) 2005-2019 Apple Inc.  All rights reserved.
Apple ROM Version
  Model:        MP61
  EFI Version:  129.0.0.0.0
  Built by:     root@saumon
  Date:         Thu Feb 14 18:49:50 PST 2019
  Revision:     129 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, Release
  Compiler:     Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)

 

[bsbeamer]

10.14.4 DP5 still have 142.0.0.0.0

Thanks for the quick report. Assume we'll see at least DP6/DP7 before release on this one.

 

[trifero]

My god, new changes??

 

[tsialex]

If anyone here works for a certain fruit company from Cupertino, what the helll is AMD Caesar IV+?

BTW, TSNBCRB1,1 is the model name for some old prototype?

 

[bsbeamer]

https://www.tonymacx86.com/threads/solution-for-intel3000-maybe-test-required.44586/

FYI, TSNBCRB1,1 shows up here from 2012 Hackintosh.

 

[MisterAndrew]

I think TSNBCRB1,1 has to do with the Intel HD 3000. It's located in the AppleIntelSNBVA.bundle. It's a Mac Debug code? I don't know why that would be in a Mac Pro firmware.

Source: https://www.tonymacx86.com/threads/solution-for-intel3000-maybe-test-required.44586/

 

[tsialex]

I think TSNBCRB1,1 has to do with the Intel HD 3000. It's located in the AppleIntelSNBVA.bundle. It's a Mac Debug code? I don't know why that would be in a Mac Pro firmware.

Source: https://www.tonymacx86.com/threads/solution-for-intel3000-maybe-test-required.44586/

Seems to be related to an old prototype.

I even tried to find what was the Transition Development Kit model, but it’s too early to be it and TDK didn’t had a EFI Firmware, so can’t be it.

 

[vrds]

what the helll is AMD Caesar IV+?

Ongoing AMD Zen 2 server CPUs have codename "Rome". Caesar? Rome?

 

[Spacedust]

So still bricking W3xx Xeons.

 

[mikeboss]

what the helll is AMD Caesar IV+?

taken from the LB 820-3298 Schematic Diagram

 

[tsialex]

taken from the LB 820-3298 Schematic Diagram


View attachment 826063

Thx!

Interesting, if is the same thing, why this hardware descriptor is stored into MP51 BootROM?!?

 

[mikeboss]

Thx!

Interesting, if is the same thing, why this hardware descriptor is stored into MP51 BootROM?!?

 

[LightBulbFun]

If anyone here works for a certain fruit company from Cupertino, what the helll is AMD Caesar IV+?

BTW, TSNBCRB1,1 is the model name for some old prototype?

im thinking Tylersburg Customer reference board?

I know CRB is what intel calls there reference boards and the MacPro4,1/5,1 and Xserve3,1 are based on the Tylersburg chipset (I know RB is reference board, but im not 100% sure on what C stands for)

(its like how GPU makers have reference cards, intel will have a reference mobo for specific platforms but you dont often see them)


but if it was also found in HD3000 kext, then it might be SND for sandy bridge

 

[tsialex]

Today I inspected another Mac Pro with a full NVRAM - so many trash, PanicLogs and multiple repeated memory configuration blocks that I was surprised that it still boots.

I don't know if this was caused by Clover or a messed up Netkas upgrade, but for sure this Mac Pro is begging for a clean-up.

 

[Macschrauber]

tsialex, can you please post a binwalk of such a messed up rom ? Just to learn when to pay attention

 

[tsialex]

tsialex, can you please post a binwalk of such a messed up rom ? Just to learn when to pay attention

Binwalk is useless to detect this type of thing, since it’s not a XML, log or anything that it detects, unfortunately.

 

[Macschrauber]

ahw ok

 

[star-affinity]

Today I inspected another Mac Pro with a full NVRAM - so many trash, PanicLogs and multiple repeated memory configuration blocks that I was surprised that it still boots.

I don't know if this was caused by Clover or a messed up Netkas upgrade, but for sure this Mac Pro is begging for a clean-up.

And I take it these things don't go away by performing a NVRAM reset?

I'm wondering if my Mac Pro has some dodgy things in NVRAM – despite a reset of it I can't seem to get Windows 10 (installed as legacy boot) to change my startup disk to MacOS from within the Boot Camp control panel installed via the Boot Camp drivers for iMacPro1,1. It's supposed to work I hear. My Mac Pro only ”listens” to what startup drive I set in Startup Disk in MacOS. If I set it to Windows there it stays that way until I go back to Startup Disk in MacOS and change to MacOS – what I do in Windows is ignored.

 

[tsialex]

And I take it these things don't go away by performing a NVRAM reset?

I'm wondering if my Mac Pro has some dodgy things in NVRAM – despite a reset of it I can't seem to get Windows 10 (installed as legacy boot) to change my startup disk to MacOS from within the Boot Camp control panel installed via the Boot Camp drivers for iMacPro1,1. It's supposed to work I hear. My Mac Pro only ”listens” to what startup drive I set in Startup Disk in MacOS. If I set it to Windows there it stays that way until I go back to Startup Disk in MacOS and change to MacOS – what I do in Windows is ignored.

Do a BootROM dump, sent instructions by PM. I'll check it when I have free time.

 

[Nabru50]

And I take it these things don't go away by performing a NVRAM reset?

I'm wondering if my Mac Pro has some dodgy things in NVRAM – despite a reset of it I can't seem to get Windows 10 (installed as legacy boot) to change my startup disk to MacOS from within the Boot Camp control panel installed via the Boot Camp drivers for iMacPro1,1. It's supposed to work I hear. My Mac Pro only ”listens” to what startup drive I set in Startup Disk in MacOS. If I set it to Windows there it stays that way until I go back to Startup Disk in MacOS and change to MacOS – what I do in Windows is ignored.

I have an RX 480 without boot screens and once in a while, I have the same problem. Choosing the Startup Disk in settings will basically permanently change it until I do an NVRAM reset, and the Boot Camp software in Windows won't work. However, when I use this program to switch back and forth, I can then switch back to MacOS from Boot Camp in Windows no problem. You just need to make sure you disable SIP, and then again after any NVRAM reset.

 

[bsbeamer]

Has everyone with recent NVRAM issues replaced the battery on the board? The OEM BR2032 battery has a 5-7 year life at maximum. These machines are well beyond that. Some people should be nearing at least their second battery replacement. It won't magically fix issues that already exist, but may help to prevent future issues.

 

[TheIguana]

Has everyone with recent NVRAM issues replaced the battery on the board? The OEM BR2032 battery has a 5-7 year life at maximum. These machines are well beyond that. Some people should be nearing at least their second battery replacement. It won't magically fix issues that already exist, but may help to prevent future issues.

Tsialex spoke to the BR2032 on page 57 (Oct 4, 2018). The NVRAM is not reliant on it as the role of the battery is to keep the clock going. Apple built the EFI and NVRAM quite differently from traditional PCs on these Mac Pros.

 

[bsbeamer]

How does Windows use impact this, especially people who install Windows incorrectly? Is that a possible source of the corruption? It does appear those people are the ones with the most common corruption issues. For less than $5, don't see why anyone wouldn't just change the battery if they never have...

 

[tsialex]

Has everyone with recent NVRAM issues replaced the battery on the board? The OEM BR2032 battery has a 5-7 year life at maximum. These machines are well beyond that. Some people should be nearing at least their second battery replacement. It won't magically fix issues that already exist, but may help to prevent future issues.

NVRAM is a volume stored into the main SPI flash memory, the same that stores the BootROM.

Mac Pro NVRAM is not battery backed, last Mac that had some sort of PRAM was MP3,1. NVRAM battery backed was common with PC BIOS era, UEFI PCs are exactly like Macs now.

The clock circuit has a little SRAM that stores the time and seconds since boot, just 56 bytes. No parameters or configuration are battery backed, just the clock like @TheIguana said.

Since a bad battery will mess with the clock and time since boot, you have to replace it, but it’s not the cause for NVRAM volume issues.

 

[Slash-2CPU]

NVRAM = Non-Volatile Random Access Memory.

Non-Volatile. As in not dependent on power to maintain data retention.

It’s flash, and can be thought of as being like an SSD.