How come? I didn't say that if an RX580 doesn't have an "Apple" boot screen it won't have a Boot Picker screen. I said that it could happen. And it's absolutely true. It's happened to me. You are wrong.
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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
No, I just tested three such cards. A fourth one is on its way; this one will probably work flawlessly, as it has been flashed by Macvids cards.
There are some RX580 shipped with broken UEFI GOP actually. But most of them are dual ROM card, and one of the ROM doesn't have UEFI GOP. However, for most cases, simply boot from another ROM will allow that RX580 to show boot picker via OpenCore.
There is definitely a small amount of RX580 (single ROM), and can't show boot picker, even with unmodded factory. But from my observation, that's just a small number, definitely not a significant large amount.
Most of the RX580 can't show boot picker, simply because the user modded the ROM which breaks the UEFI GOP. So, user error, not the card's fault.
And lots of the cMP users bought those modded cards, then complain their RX580 can't show boot picker. I believe PeterHolbrook incorrectly ident those modded card as "factory unmodded RX580".
So, after all, I WASN'T wrong, was I? Thanks for admitting so much (without saying so). I never used the expression "factory unmoved RX580", so don't misquote me! I couldn't possibly have misidentified anything when I didn't say anything about what you WRONGLY imagined.
I presume you bought these new in the box and that's how you are 100% certain of their pedigree.
Of course you can have a few RX580 that can't show boot picker.
Anything could happen, but the point is "UEFI GOP boot picker" and "Mac EFI UGA boot screen" are totally unrelated.
We better not to mislead the others.
If any RX580 can't show boot picker in OpenCore, it's the UEFI GOP's issue. Nothing about the boot screen ability (Mac EFI UGA's issue).
You didn't say the card need to have boot screen to show boot picker, but you said "If it doesn't have one, chances are the OpenCore Boot Picker won't work with your GPU either". This sentence can easily mislead the others to believe that they need a card which can display boot screen (e.g. flashed card) in order to show boot picker via OpenCore.
That's fine, you are right, I am wrong.
The point is to make it clear to everyone. So that the other won't go into the wrong direction.
If I can misunderstand your post. Any other could also misunderstand your post.
That is exactly what you said. You should have said:
If it doesn't have one, chances are the OpenCore Boot Picker will work with your GPU.
Beside this I think we should stop here and I beleive the moderator will delete all these posts as "debate" (and he should)
I think it's OK for us to debate and clarify the exact condition to make boot picker works via OpenCore.
So far, we are still mainly focus on the technical stuff, not personal attack.
We quote the others, but that's required for the debate. Not for attacking.
My understanding, we need "CPU + logicboard + DIMM + firmware + OS" support to make the memory run at above 1333MHz.
I really doubt it anything can be done if the CPU can't go above 1333.
We can install faster RAM, we can mod the logic board, let's say OpenCore allow us to overcome the limitation in firmware and OS. But the CPU still can only populate at 1333MHz.
You are right about that too. We might have reached the limitations/end there for our beloved MacPro. But that's already that. Unless someone has a better idea, what else really can we expect from this machine?
I only bought one of them in a regular shop in Madrid and returned it, because it never worked, not even with UgaPassThrought set to true. The other two were loaned to me. As I said, one of them was a Macvids card, and worked fine on its first ROM. I don't know whether the Nitro was modified in any way.
This is what I said, and it is ABSOLUTELY CORRECT: "If it doesn't have one, chances are the OpenCore Boot Picker won't work with your GPU either." "Chances are" doesn't mean "it's certain that the OpenCore Boot Picker won't work". It means that it's possible (but not certain) it won't work. As I said, I know first-hand this is so. And you are wrong. That's too bad. I suggest you change the subject. You can't win this one.
I have just installed Open Core on two 5,1 with rx580. I just followed the instructions on page 1 here.
Yes it worked, got boot screen, gpu accel, nvme as internal .. but system updates are not working (i did the vmm flag stuff). Is it because my Catalina was installed with dosdude patcher ?
Which version of Catalina are you running? Version 10.15.7 is the latest one for now.
Please try to boot to recovery partition, and see if you can install a vanilla Catalina at there (this should effectively unpatch the macOS as well). As long as you don't erase anything, your user data should be safe.
Next would be trying these... https://www.newegg.com/v-color-64gb...AP49399-_-Product&nspcid=178497&nspgid=178498
Should also work for a total of 512GB 😅
A GPU with GOP UEFI driver might not load the driver on older EFI. Perhaps some RX580 do and some others do not. To test this:
Grab the rom of the card. You can use the following commands on EFI Shell on a computer that has boot screen:
Boot macOS, mount the partition where you saved the romhex.txt. Use a script to convert the hex to a binary.
Then back in EFI Shell:
If there's no new handle for the rom.bin image with DriverBinding protocol, then it means it did not load. In that case, loadpcirom should output an error.
I have an Nvidia Titan X (Maxwell) which won't load it's rom on my MacPro3,1 (having EFI v1.1) because it expects UEFI v2.10 (use the
I got the version it expected by using loadpcirom in the built-in EFI Shell of a Parallels VM which uses UEFI v2.70.
"SupportedEfiSpecVersion 0x0002000A" means it requires UEVI v2.10.
I have a W5700 who's rom does load (DriverBinding protocol is added) on my MacPro3,1 but I did not install the card to see if it will also add the GOP protocol.
Grab the rom of the card. You can use the following commands on EFI Shell on a computer that has boot screen:
dh to find the handle for the GPU device.dh -d -v handle (where handle is the handle number in hex) to get the start address and size of the PCI option rom.fs0: where 0 is the file system number of a EFI or FAT partition where you have write access from EFI Shell (use map to see a list of file systems).dmem start size > romhex.txt (where start and size are the start and size in hex) to get the hex of the rom.Boot macOS, mount the partition where you saved the romhex.txt. Use a script to convert the hex to a binary.
diskutil mount disk0s1 to mount the EFI Partition (change 0 if it's on a different disk)iconv -f UCS-2 -t UTF-8 romhex.txt | sed -nE "/^[ 0-9A-F]+:([-0-9A-F ]+).*/s//\1/p" | xxd -p -r > rom.bin to conver dmem output to binary file.Then back in EFI Shell:
loadpcirom rom.bin will output an error or a handle for the EFI driver that is in the rom.If there's no new handle for the rom.bin image with DriverBinding protocol, then it means it did not load. In that case, loadpcirom should output an error.
I have an Nvidia Titan X (Maxwell) which won't load it's rom on my MacPro3,1 (having EFI v1.1) because it expects UEFI v2.10 (use the
ver command to get the version of your EFI - it should match the revision of the System Table shown by dmem by itself).I got the version it expected by using loadpcirom in the built-in EFI Shell of a Parallels VM which uses UEFI v2.70.
"SupportedEfiSpecVersion 0x0002000A" means it requires UEVI v2.10.
dh to see the handle that was loaded by loadpcirom (it should be at the end of the list.dh -d -v handle to see driver and protocol related info (in this case, the handle is B1):
Code:
B1: SupportedEfiSpecVersion(7CB1C848) 0x0002000A ComponentName2(7CB1C7B8) DriverBinding(7CB1CCE0) ImageDevicePath(7DC86618) FS0:\roms\titanx.rom[1] LoadedImage(7DA70CC0) Revision......: 0x00001000
ParentHandle..: 7DC3A518
SystemTable...: 7E9E8018
DeviceHandle..: 0
FilePath......: nvgop-gm2xx
PdbFileName...: <null string>
OptionsSize...: 0
LoadOptions...: 0
ImageBase.....: 7CB1B000
ImageSize.....: 21480
CodeType......: EfiBootServicesCode
DataType......: EfiBootServicesData
Unload........: 7CB1DDB4
Driver Name [B1] : NVIDIA GPU UEFI Driver
Driver Image Name : nvgop-gm2xx
Driver Version : 00020011
Driver Type : <Unknown>
Configuration : NO
Diagnostics : NO
Managing : NoneI have a W5700 who's rom does load (DriverBinding protocol is added) on my MacPro3,1 but I did not install the card to see if it will also add the GOP protocol.
Even though I highly doubt if it can work, but it will be good to know if that 288GB (from the Xeon) is a hard limit.
We will soon know, I am getting 512GB 8x64GB I think that we cannot go pass that has DDR3 highest stick you can get is 64GB - I do not think we can get a 96GB Stick, but I may be wrong one more time.
I have 10.15.5 and with recovery partition it goes straight back to the boot screen
Hmm. I'm not sure whether dosdude1's Catalina Patcher will hamper the creation of a Catalina Recovery partition. If you don't have such a partition or if it is damaged, I suggest you do the following:I have 10.15.5 and with recovery partition it goes straight back to the boot screen
1. Create a full backup of your system, just in case something goes wrong.
2. Using dosdude1's Catalina Patcher, download the latest Catalina installer, but don't modify it. I assume you'll download it to ~/Downloads
3. Download the attached zip file and uncompress it.
4. You'll see a "Catalina Recovery HD partition" app, plus basic instructions that aren't really necessary (I think).
5. Run said application
6. You'll need to say where your Catalina installer is. The rest should be automatic. At the end of the process, you'll have a valid Recovery Partition.
Hey All,
Coming to you again looking for a bit of assistance. Weeks ago I went through the guide in #1 up to installing Windows and everything was great. Yesterday I decided to get the Windows install done, everything appeared to be going well up to the "prepare the installer" step and things started to fall apart for me... I think. End result was my receiving error messages entering the terminal like commands on the Windows setup page.
Since things seemed to not be working as intended I X'd the windows installation Mac restarted failed to boot and turned itself off. Disk A (from the guide, where I had OC and Catalina installed) was the issue so after a safe mode boot and scrub of that disk I am at least back to square one (phew).
I will now get back to the point of the install where I was yesterday (up to tackling the Windows Install section of the guide). What I could use some help with is knowing where I went wrong.
I have added to photos I took of the Windows install and the error messages I received. Please be aware my pre boot screens have that issue where the colours are crazy so the text is a little tough to read but possible.
I am also very happy to to post that part of the guide (where it all went wrong for me) with notes on exactly what I did for each step if that helps you tell me where I went wrong.
Thanks in advance for any help you can provide
Coming to you again looking for a bit of assistance. Weeks ago I went through the guide in #1 up to installing Windows and everything was great. Yesterday I decided to get the Windows install done, everything appeared to be going well up to the "prepare the installer" step and things started to fall apart for me... I think. End result was my receiving error messages entering the terminal like commands on the Windows setup page.
Since things seemed to not be working as intended I X'd the windows installation Mac restarted failed to boot and turned itself off. Disk A (from the guide, where I had OC and Catalina installed) was the issue so after a safe mode boot and scrub of that disk I am at least back to square one (phew).
I will now get back to the point of the install where I was yesterday (up to tackling the Windows Install section of the guide). What I could use some help with is knowing where I went wrong.
I have added to photos I took of the Windows install and the error messages I received. Please be aware my pre boot screens have that issue where the colours are crazy so the text is a little tough to read but possible.
I am also very happy to to post that part of the guide (where it all went wrong for me) with notes on exactly what I did for each step if that helps you tell me where I went wrong.
Thanks in advance for any help you can provide