I’m not sure why providing flashing capabilities to non efi gpu would imply that they have no plans to add functionality to non efi cards. If anything I think its the exact opposite they just added functionality to non efi cards! Why would they go through the trouble of releasing an efi that ads non efi gpu flashing and 5GT support if their goal isn’t full support. Adding a bootscreen probably does’t require a lot more work. I mean they could have easily dropped mac pro 5.1 support for mojave and not have to do any of this. I think this one is in the bag people...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I’m not sure why providing flashing capabilities to non efi gpu would imply that they have no plans to add functionality to non efi cards. If anything I think its the exact opposite they just added functionality to non efi cards! Why would they go through the trouble of releasing an efi that ads non efi gpu flashing and 5GT support if their goal isn’t full support. Adding a bootscreen probably does’t require a lot more work. I mean they could have easily dropped mac pro 5.1 support for mojave and not have to do any of this. I think this one is in the bag people...
In my case, this black box bug only happen when I use my own colour profile. If I use the monitor’s (CHG90) default colour profile, then it won’t happen (with my 1080Ti).
Is there any issue before? I never try Win 7 UEFI, but very sure Win 8 and Win 10 can install in UEFI mode without problem.
I think someone mentioned in "Supported Mojave Video Card Thread" that Apple has a lot of the 5,1 machines in use internally due to their modularity and the fact that employees can "rent out" the machines as need be. This gives me hope that additional support (bootscreens, NVME, etc.) for the cMP is coming at least until the 7,1 arrives.
Then again, no way of knowing if that is the truth, or if Apple would release anything they use internally to us consumers.
Then again, no way of knowing if that is the truth, or if Apple would release anything they use internally to us consumers.
Wow, every month a new security issue with Intel https://newsroom.intel.com/editorials/protecting-our-customers-through-lifecycle-security-threats/
Honeslty I think you can find security flaws in any hardware as long as you look. As intel has a majority of the market share in servers and pcs their hardware is being scrutinized a lot more than amd or others... The question is do these security flaws really represent a danger for the home user?
Happy to report that with the genius and help of @tsialex, my cMP is restored and working perfectly with Boot Rom version 138.0.0.0.0 with NVMe boot support. All user/machine data is back in place and serialized properly.
My machine boots faster now and is in good health.
Thanks so much to @tsialex for all of his hard work and generous contributions. I appreciate this more than you might imagine.
btw, I actually did the last flash from my NVMe drive, and booted directly back into my NVMe drive.
My machine boots faster now and is in good health.
Thanks so much to @tsialex for all of his hard work and generous contributions. I appreciate this more than you might imagine.
btw, I actually did the last flash from my NVMe drive, and booted directly back into my NVMe drive.
Could you explain the steps you went through?Happy to report that with the genius and help of @tsialex, my cMP is restored and working perfectly with Boot Rom version 138.0.0.0.0 with NVMe boot support. All user/machine data is back in place and serialized properly.
My machine boots faster now and is in good health.
Thanks so much to @tsialex for all of his hard work and generous contributions. I appreciate this more than you might imagine.
btw, I actually did the last flash from my NVMe drive, and booted directly back into my NVMe drive.
I am now out of town, can’t test the latest beta, but the hardware encoding in last beta still broken.
I tested FaceTime and iMessage. They work fine so I assume iCloud is fine.
@Pavo I'll make a detailed instruction on how to reconstruct/personalize the BootROM, but since to do that involves heavy hexediting, please wait until done.
If we start to post about this, people will begin testing without the means to restore a corrupt SPI-flash.
I'm being cautious here, I corrupted my own Mac testing it. It's not a problem for me, but for some will be a costly one.
Last edited:
Happy to report that with the genius and help of @tsialex, my cMP is restored and working perfectly with Boot Rom version 138.0.0.0.0 with NVMe boot support. All user/machine data is back in place and serialized properly.
My machine boots faster now and is in good health.
Thanks so much to @tsialex for all of his hard work and generous contributions. I appreciate this more than you might imagine.
btw, I actually did the last flash from my NVMe drive, and booted directly back into my NVMe drive.
How about writing up a how-to document? It would be a great way to preserve / share the info you learned from @tsialex .
I wouldn't mind doing that, but I'll wait until @tsialex has a chance to document the process from his perspective. He actually did the grunt work, I was mostly a passenger.
At least on my 4,1 flashed to 5,1 and GeForce 1060, installing win10 in UEFI mode disabled the built-in sound and led to a lot of weird desktop compositing issues (laggy app windows when not running a full screen game, laggy playback in apps that had embedded video players, that sort of thing). This was running the latest version of win10 education (basically enterprise) and the latest NVIDIA drivers.
Following up to conversations with @tsialex...
DP 7 refuses to install from a full download on a RX470. It errors out from a normal or startosinstall install with:
The support document mentioned is not live: https://support.apple.com/kb/HT208898
DP 7 refuses to install from a full download on a RX470. It errors out from a normal or startosinstall install with:
Error: Installation cannot proceed because a Metal compatible graphics card is required.
It looks like Apple is locking down installation to compatible hardware. Hopefully they won't look at the SMC revision to lock out 4,1's flashed as 5,1's.
The support document mentioned is not live: https://support.apple.com/kb/HT208898
Last edited:
Then I am pretty sure that’s not normal. My flashed 5,1 can run Windows 10 in UEFI mode with 1080Ti or RX580 flawlessly.
[doublepost=1534352377][/doublepost]
It was OK to install 10.14 beta with just the RX470 before DP7?
interesting I suspect this may be a bug in the installer, Apple must be wondering why the sudden influx of MP5,1 bug reports
as Apples requirements are just a Video card that does Metal, with the RX 580 and RX 560 being the recommended ones
my AMD Radeon HD 7950 does not give me such an error when I launch the installer app.
I can't tell exactly when this changed, but I have all the previous full installers here and I'll check when Apple changed this.
[doublepost=1534352755][/doublepost]
Not only RX470, but on other topic @Squuiid reported the same, with unflashed GTX1080.interesting I suspect this may be a bug in the installer, Apple must be wondering why the sudden influx of MP5,1 bug reports
as Apples requirements are just a Video card that does Metal, with the RX 580 and RX 560 being the recommended ones
my AMD Radeon HD 7950 does not give me such an error when I launch the installer app.
also where are you running the full installer from? in your System profiler shot it looks like your in Mojave already
the installer may only be setup to properly check for metal video cards when run in 10.13.6.
in-fact one of the known issues in the DP7 release is (I wonder if that bug report number matches anyones bug report here? )
the installer may only be setup to properly check for metal video cards when run in 10.13.6.
in-fact one of the known issues in the DP7 release is (I wonder if that bug report number matches anyones bug report here?
)
Handoff has stopped working. I've went through the process of re-enabling everything again and I've been waiting for it to provision, but so far no go. I used the terminal CLI to enable, then when that didn't work, I tried CAT.
I ran the CAT tool diagnostic, it reports my WiFi card wrong and won't work. I know this to be false, as it was upgraded, and has handoff has been working trouble free through several clean installs, and even in a new Mojave install. I'm hoping it's just a waiting game.
Do you have another disk with Sierra/ElCap to check if you can activate? I've noticed Apple changed some AirPort Extreme ids recently, that BrcmNIC that CAT is telling you, but did not investigate further.