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

[tsialex]

I did all my flashing within 10.13.6.

I do all my flashing from Mojave since at least DP6. I tested every reconstructed BootROM and iCloud obligated password change at least 5 times. Now I just boot my Mojave test SATA SSD without iCloud and do the flashing/test from there. Once tested, I flash again with my own BootROM and go back to 10.13.6/SM951.

 

[RamMac]

Logout from iCloud, reboot, login iCloud first then in iMessage/FaceTime.

If that don’t work, maybe your BootROM is missing the ids.

Thanks tsialex for your endless effort to get folks MacPros run properly. I did not yet try to log out from iCloud. Instead I booted from same MacPro, but from another internal disk the previous version of Mojave Public Beta (18A365a). When running with it, both iMessage and FaceTime are logged with my AppleID and function perfectly. So would it be then something else than BootROM missing the ids?

 

[tsialex]

Thanks tsialex for your endless effort to get folks MacPros run properly. I did not yet try to log out from iCloud. Instead I booted from same MacPro, but from another internal disk the previous version of Mojave Public Beta (18A365a). When running with it, both iMessage and FaceTime are logged with my AppleID and function perfectly. So would it be then something else than BootROM missing the ids?

That’s a weird one. Maybe Apple is checking for more things with the last beta of Mojave?

I can do a quick check to see if you BootROM is correct if you want. Just compress it, the most recent one, and PM me it.

 

[Earl Urley]

If possible, I'd like to take a look on your MP51.0089.B00 BootROM dump. Every dump I looked from people who used MP51.0087.B00 has a quirk.

Ok, I'll get it to you sometime today. You want the non-injected or the injected version?

 

[tsialex]

Ok, I'll get it to you sometime today. You want the non-injected or the injected version?

Send me what you're using now.

 

[zozomester]

Send me what you're using now.

Hi, Can you even inject me?

 

[tsialex]

Hi, Can you even inject me?

You, no!

But I can check and inject NVMe to your MP51 BootROM.

 

[zozomester]

You, no!

But I can check and inject NVMe to your MP51 BootROM.

Thank, where I send it?

 

[tsialex]

Thank, where I send it?

Compress it and PM me here.

 

[zozomester]

OK thanks! I will send tomorrow!

 

[bookemdano]

Hmmm... well earlier today I was thinking about Apple's coding of the check for FV2 being disabled before installing Mojave. I was wondering if they actually prevented it from being turned on after the install is complete. Sure enough, they absolutely do (as of PB6)--both via the GUI (System Preferences>Security & Privacy>FileVault) and via the "diskutil apfs encrypt" terminal command.

If they don't figure out a way to enable boot screens for the 560 & 580 then those blocks are almost 100% going to stay in place for the GM. If so, that will be a real hindrance to people who own a "Mac Edition" 7950 or GTX 680 (or one of the unofficial flashed versions of those cards), in addition to people like myself who paid big bucks for a MVC-flashed Maxwell card. Even though we *will* have boot screens on Mojave, it seems Apple will prevent us from using FileVault2 as well.

Just in case, can someone who is using a 7950 or GTX 680 with Mojave try enabling FileVault (if it even lets you--which I doubt--you can immediately cancel if you don't want to use it) just to make sure that Apple isn't somehow checking the installed GPU? I mean I really doubt they coded the block that specifically, but I am not able to test it since my only EFI card is a 750 Ti and there are no web drivers for Mojave yet.

Assuming users of those cards are also blocked from enabling FV, then I think this is yet another bug that should be reported. Apple should not be restricting that feature from users who have cards perfectly capable of using it.

There may be workarounds (like encrypting the drive on another Mac and then moving it back over to the cMP), but who knows if that could raise other issues as well.

 

[Earl Urley]

Running an OG Mac EFI GTX 680, here's the response I get, same as yours..

 

[crjackson2134]

I just tested with a Genuine Apple EFI Card. Same as @bookemdano and @Earl Urley
No love from Apple on this...

 

[bookemdano]

Running an OG Mac EFI GTX 680, here's the response I get, same as yours..

View attachment 777311

Thanks. So yeah, if you have any interest in FileVault (or even if you don't but feel like helping those of us who do) please report that as a bug using either Feedback Assistant or https://bugreport.apple.com

 

[LightBulbFun]

for anyone having iCloud issues I wonder if this is related (this is in the latest DP8 "Change log" PDF)

 

[tsialex]

View attachment 777339

for anyone having iCloud issues I wonder if this is related (this is in the latest DP8 "Change log" PDF)

I'd like to know if the "might" refers as corrupted identifiers in the BootROM or trash in the private part of the NVRAM, or else.
[doublepost=1534977759][/doublepost]

Ok, I'll get it to you sometime today. You want the non-injected or the injected version?

Did you tried and failed to install macOS? Your MP51.0087.B00 dump has this "InstallPhaseList" plist in the NVRAM.


Not one, but two times…


[doublepost=1534979789][/doublepost]@Earl Urley Has the WEIRDEST CASE UNTIL NOW

Look at this SSN_HWC_SON block from his MP51.0087.B00 dump:




Now look at the same place in his MP51.0089.B00 and 138.0.0.0 dumps:



I couldn't believe and checked 3 times, even downloaded his dumps again, then I asked for a picture of his grey/white label.

MP51.0087.B00 changed the last digit from his serial number and hardware code. That was corrected in MP51.0089.B00 but now his SON was replaced with the SKU for his mid-2012 MacPro.

Maybe a gremlin changed his BootROM between 10.13.4 and 10.13.6…

 

[Squuiid]

I'd like to know if the "might" refers as corrupted identifiers in the BootROM or trash in the private part of the NVRAM, or else.
[doublepost=1534977759][/doublepost]

Did you tried and failed to install macOS? Your MP51.0087.B00 dump has this "InstallPhaseList" plist in the NVRAM.
View attachment 777342

Not one, but two times…

View attachment 777341 View attachment 777343
[doublepost=1534979789][/doublepost]@Earl Urley Has the WEIRDEST CASE UNTIL NOW

Look at this SSN_HWC_SON block from his MP51.0087.B00 dump:

View attachment 777344


Now look at the same place in his MP51.0089.B00 and 138.0.0.0 dumps:

View attachment 777347 View attachment 777345

I couldn't believe and checked 3 times, even downloaded his dumps again, then I asked for a picture of his gray/white label.

MP51.0087.B00 changed the last digit from his serial number and hardware code. That was corrected in MP51.0089.B00 but now his SON was replaced for the SKU for his Mac.

Wow, those that stayed away from 0087 did well to do so it would seem. Horror show of a firmware update.

 

[crjackson2134]

That’s bizarre, as I said, Apple’s flash technique leaves a lot to be desired. I absolutely don’t trust the Apple flash tool.

 

[dgarratt]

Thanks. So yeah, if you have any interest in FileVault (or even if you don't but feel like helping those of us who do) please report that as a bug using either Feedback Assistant or https://bugreport.apple.com

Yeah..really hope this is resolved by Apple.

If not, maybe a workaround will be discovered.

 

[tsialex]

Wow, those that stayed away from 0087 did well to do so it would seem. Horror show of a firmware update.

I still do not believe that changes. WTF?!?

Maybe @Earl Urley changed his logic board for the next one in the production line and forgot to tell me. I need a logic explanation.

 

[handheldgames]

That’s bizarre, as I said, Apple’s flash technique leaves a lot to be desired. I absolutely don’t trust the Apple flash tool.

If it's in the NVRAM block, it's probably not the firmware flash causing the issue. It sounds like an issue with the OS management of the NVRAM space and a lack of code to audit and clean up left over logging info. Writing to the flash ram is akin to saving your place in an old cartridge based console game.

 

[tsialex]

If it's in the NVRAM block, it's probably not the firmware flash causing the issue. It sounds like an issue with the OS management of the NVRAM space and a lack of code to audit and clean up left over logging info.

I'm thinking a long this lines too, I'm finding lots of trash/logs/plists.

I remembered everyone who said to me that zap-PRAM don't do anything…

 

[bookemdano]

Well my interest is definitely piqued. I zipped up my dumps from 0085, 0089 and 138 (I never installed 0087) and am sending to you now tsialex. When and if you get time, I'd love to know how clean it looks.

Thanks!

 

[crjackson2134]

If it's in the NVRAM block, it's probably not the firmware flash causing the issue. It sounds like an issue with the OS management of the NVRAM space and a lack of code to audit and clean up left over logging info. Writing to the flash ram is akin to saving your place in an old cartridge based console game.

That sounds like it should be crafted into a well written bug report.

 

[tsialex]

Well my interest is definitely piqued. I zipped up my dumps from 0085, 0089 and 138 (I never installed 0087) and am sending to you now tsialex. When and if you get time, I'd love to know how clean it looks.

Thanks!

I'll look at yours tomorrow, got them by email.