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
That's what I was thinking. It did fix the DPI so it's much clearer but it's not shrinking down the image. Right now I have is set to 4K I believe,
<key>UIScale</key>
<data>
Ag==
</data>
This look right? Got this from another response from h9826790 I believe.
[automerge]1583023717[/automerge]
2 more questions.
1. Does using this boot loader improve the performance of the GPU in Windows? I remember that the only way to get the full speed of the PCIe port in Windows was to get a flashed card. Is this still the case?
2. Booting from NVMe drive, I notice now that there is a delay when loading the OS. The progress bar starts very quickly and then slows. Boot time is around 30 seconds-1 minute. Why is this so slow? Is there anyway to speed this up?
No, Apple enabled PCIe 2.0 for all devices since 138.0.0.0.0.
Time to POST and boot is related to the quantity of RAM, more RAM/more time, and PCIe enumeration - NVMe drives take longer to be ready when used in a MP5,1.
Post time is longer if you have multiple MemoryConfig entries inside the NVRAM, but even with a totally clean NVRAM, POST/boot time with a MP5,1 is very long when compared with recent Macs/PCs with UEFI fast boot.
Change that to
AQ== if you want normal 1:1 display (non HiDPI, or non Retina, or 1x scale)Hi everyone, I updated to 0.5.6 here. This is my configuration file, with AMD hardware acceleration and bootpicker.
What is needed to get the bootpicker to work? Currently just some flash ups of the 4K display and then nothing.
If this is successful, is it safe to boot via bootpicker from uefi usb win10 install media to install it?
Currently on 0.5.6 + latest working config from @h9826790 from the "AMD hardware acceleration thread" and everything else (NVME as internal, hw decoding, etc.) seems to work.
System: OC from USB 2.0 lower front panel; Radeon VII, 4K Samsung + Cinema Display 24 + BenQ Full HD all via DP
If this is successful, is it safe to boot via bootpicker from uefi usb win10 install media to install it?
Currently on 0.5.6 + latest working config from @h9826790 from the "AMD hardware acceleration thread" and everything else (NVME as internal, hw decoding, etc.) seems to work.
System: OC from USB 2.0 lower front panel; Radeon VII, 4K Samsung + Cinema Display 24 + BenQ Full HD all via DP
Hop back a couple of pages to my earlier post. The answer is yes, but you must chainload rEFInd to handle it.
You can use the "bridge boot" method, not supported, but tests showed can work
OpenCore on the Mac Pro
Ok. So here is a short tutorial on how to get a full blown boot picker through refind from OC boot picker. 1. Download the "Next loader" fork of Refind. 2. Attach a USB drive to the machine. 3. Open Terminal and type : sudo -s 4. Drag and drop the "install.sh" from...
forums.macrumors.com
Ok. This is weird. I downloaded Catalina and I'm getting ready to install it to a new NVMe drive I installed. I'm getting greyed out boxes for all my drives? When I click on the new APFS volume I created it says, system requires a firmware update. Select Mac OS Extended (Journaled) drive instead. Any ideas? I'm pretty sure I'm on 144.0.0.0.0 VMM mask is on. I don't remember reading anything in this thread about this?
@h9826790 - do we need to fake that we have the latest bootrom version for the iMacPro as we are using the iMacPro board ID to bypass that? ... i.e. is the installer seeing 144.0.0.0 as being lower version of firmware compared to what the iMacPro has?
VMM flag is on. Could it be they changed something in the 10.15.3 release? It's definitely weird.
Do you mean booting directly into a Windows UEFI install? Yes, I wrote one up earlier in this thread, but I really would advise against it. To the best of my knowledge a UEFI installation of Windows offers no advantages on a system with firmware 144.0.0.0 and endangers your BootROM through corruption by installing multiple certificates.
What NVMe M.2 blade? This firmware update message is usually a signal that the NVMe blade is incompatible with macOS, several incompatible blades do that like WD Blue SN550.
Just install OC on a USB drive. When you are in OSX remove the USB drive and select Windows in the startup disk as usual. If you want to use the OC again plug in the drive.
Again OC officially does not support Windows in legacy mode nor is it recommending it. @vit9696 created specific to the cMP changes to OC so booting Windows through OC in UEFI is safe.
Sorry, crossing streams with the AMD acceleration thread.
But even there i guess you are just using "BoardProduct" vs Board-ID