@KingCachapa, perhaps I have misunderstood your post, but there is no need to install another instance of OpenCore on your Windows drive. If you already installed OpenCore (on whichever drive), it will take care of everything. It should automatically detect the Windows bootx64.efi and proceed to (safely) boot Windows. Also, ExitBootServicesDelay is in milliseconds. So, for example, you should set it to 3000 for 3 seconds. Note that the utility of this quirk for us remains to be determined.
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
@cdf well, I am following this guide @roobarb! made
and it involves removing all drives, and at one point the only drive in there is Windows to continue the installation. Part of that guide has me putting OC on Windows drive specifically, so it doesn't boot without it.FINAL UPDATE: SUCESS!! I will do an outline soon of what ended up working for me, maybe it'll help others.
---------------
What do you think? Should I attempt this process without the removing drives shenanigans and just one instance of OC the whole time?
edit: I was also wondering why that guide, if successful, eventually yes would leave me with 2 instances of OC (one on Bay 1 Mojave EFI, and one on Windows destination drive EFI). I understand why I only need it once under normal circumstances.
Thanks for the milliseconds tip, duly noted.
Update: @cdf for testing, I tried via pre-formatting as NTFS on Mojave(I use Paragon) as well, instead of removing all partitions from the installer and letting Windows do its thing. Even with ExitBootServicesDelay at 3secs (in millisecs), either way I end up with:
- if the Windows drive is the only one in the machine, OC loads fine but there's nothing to choose in the BootPicker (if USB installer is still in, it's the only thing that shows, and if I click it of course it just restarts the installation process).
- if the Mojave drive is in Bay 1, and windows drive is in as well (nvme pcie btw), then it does show everything in the OC BootPicker, however the Windows one does not launch it just comes back to OS Bootpicker.
I wonder if could having OC on two EFI volumes on different drives, creates some conflict that prevents this launch. But then again, shouldn't the new windows drive to continue installation, show up, regardless of other drives being present?
(no fatal errors or problems confirmed, just trying to accomplish Windows 10 install safely)
Thanks!
Last edited:
To disable internal slot with 2 cards setup I used:
Unfortunately on a triple video card setup with 2 Polaris and one NVIDIA Kepler GT-640 card, the NVIDIA took over the outputs and the Polaris cards could not connect to the screens. You can connect with VNC, but the screen is disconnected. The above code could not disable my NVIDIA card, but the code below worked:
Of course this is for Kepler card disabling NDRV graphics drivers. For unsupported NVIDIA cards if they are using different driver the first method may work.
So you can have a Kepler card with EFI Vbios to use at boot for the bootpicker. Kepler card gets disabled 2/3 way during the boot stage with the Apple logo.
Code:
<dict>
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>IOName</key>
<string>#display</string>
<key>class-code</key>
<data>
/////w==
</data>
<key>name</key>
<data>
I2Rpc3BsYXk=
</data>
<key>rebuild-device-tree</key>
<data>
AA==
</data>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<array>
<string>name</string>
<string>IOName</string>
<string>class-code</string>
</array>
</dict>
</dict>
</dict>
Code:
<dict>
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>AAPL,ndrv-dev</key>
<false/>
<key>agdpmod</key>
<data>
cGlrZXJhAA==
</data>
<key>rebuild-device-tree</key>
<data>
AA==
</data>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)</key>
<array>
<string>AAPL,ndrv-dev</string>
</array>
</dict>
</dict>
</dict>So you can have a Kepler card with EFI Vbios to use at boot for the bootpicker. Kepler card gets disabled 2/3 way during the boot stage with the Apple logo.
Last edited:
Yes. You just have to be extra careful when formatting.
By installing a second instance of OpenCore, you overwrote the Windows bootx64.efi. Consequently, the second OC shows no Windows entry, and the original OC shows Windows, but this is actually the second OC, which in turn gives you the boot picker.
Hi everyone,
I've been using the info on this site for the last few weeks to get my Titan Ridge card to boot natively on my 2009 Mac Pro 5,1. It was a success, but now that I have OpenCore on my Mac, I'm wondering what else (If anything) I could do to help it operate more efficiently. So I decided to sign up for the forum and dive on in! I've seen talk about Hardware Acceleration but from the posts that I've seen. it only seems beneficial for those doing graphics work. I have a recording studio so most of my work is done with Pro Tools/Logic Pro X. Any suggestions as to where I should head next?
I've been using the info on this site for the last few weeks to get my Titan Ridge card to boot natively on my 2009 Mac Pro 5,1. It was a success, but now that I have OpenCore on my Mac, I'm wondering what else (If anything) I could do to help it operate more efficiently. So I decided to sign up for the forum and dive on in! I've seen talk about Hardware Acceleration but from the posts that I've seen. it only seems beneficial for those doing graphics work. I have a recording studio so most of my work is done with Pro Tools/Logic Pro X. Any suggestions as to where I should head next?
Oh wow, OpenCore inception, I see. Thanks for the explanation (=and everyone for their help. I've updated the post, and I'll do a guide that might help others, because I ended up having to mix a couple other guides.
Managed to install it! My problem was I had no way to access the internet, which is what I was trying to get around, but my MBPro was kind enough to lend big daddy cMP some ethernet and fully installed with Brigadier.
I have learned that Brigadier's network / download package features are critical for it to work.
I was attempting to work around this by downloading the package on one machine, and trying to trigger the install with Brigadier on another machine.
Question-
(
I'd like to know specifically if for the WikiGuide on this thread, the hybridization part where we add the graphics card to the DeviceProperties, is that a recommendation for Catalina users only or will this help in Mojave too? That's the only part I don't seem to have in my config yet.
Thanks a million
Last edited:
While in Windows, rename your Local Disk C: to Windows, like I did. It will show Windows in your Mac.
Thanks man! Hope this helps others, but I ended up working around it and it solved itself (the "no name" issue)
Last edited:
How did you fix it? Curious
I did not do any of this, or fiddled with disks and hardware on my Mac. From Catalina, I installed VirtualBox with EFI enabled and mounted the NVMe drive as virtual disk, then installed Windows on it normally. When it rebooted, I just shut down the VM and continued the install through Bootpicker, it saw the Windows disk automatically.
Last edited:
How did you fix it? Curious
Well, it's taken a few tries over days to finally get this working. Each time I tried, depending on the "recipe" sometimes the result was a drive with "No Name". Sometimes, the result was proper Windows naming.
In the end, I just confirmed that it shows as "Windows" in the OC boot picker, so it I chanted victory before the battle was over. It looks like "No Name" in this case is what I ended up with again haha! Not for much longer
thanks. I'll do a walkthrough with my findings soon, I'm exhausted of restarting the beast.-- As for installing via VM, no real reason, but I did see that guide too. Just winged it and decided to follow this path instead of VM method, especially after I started having issues, I wanted to figure out a non-VM way of doing this. We have time, so I'm learning and testing different approaches.
Last edited:
Just rename the Local Disk C: to Windows. I know is not fancy but it works. If you format the disk in advance as exFat, then yes, you can name it any way you like in macOS. But I want to have NTFS.
Just rename the Local Disk C: to Windows. I know is not fancy but it works
Got it, yes haha agreed papi. Did you see my comments above about having issues re:Brigadier and trying to install the iMacPro1,1 bootcamp?
I don't use BootCamp, I only used the iMacPro1,1 brigadier to fix the Bluetooth (Broadcom BCM943602CDPAX upgrade) and Magic Keyboard/Mouse unknown drivers. I even fixed the mouse to scroll the natural way, like in Mac, it was driving me crazy to upside-down way Windows does. As you can see, the Windows partition shows on my Mac and I can copy files from it. I don't care the Mac drives do not show in Windows, I don't even know this is the right behavior.
If you want to know what I did, I did not installed any exe files. Instead, I went to Device Manager and updated the drivers for all unknown devices directly, while pointing manually the location to Brigadier directory. To fix the mouse scrolling, I went to "/$WinPEDriver$/AppleWirelessMouse" directory and right clicked on the .inf file, then selected "Install driver."
I would appreciate a lot more if we have HWAccel in Windows, like we have now in OpenCore Catalina.
Last edited:
Right. That's encouraging to read. You installed directly with Brigadier while in the target Windows OS right?
if I understand how it works.The difference for me is that when I started Windows10 successfully, I have only ethernet showing, no WiFi, and physically because of where I am, I can't connect my cMP. So used Brigadier on diff. PC only to download the BootCamp package, and brought it over offline to the target Windows OS.
When I launch the installer in Windows by itself, it gives me that error. I guess I need to figure out a way for Brigadier to do it on the target OS completely with network connection, but I have no network connection because Wifi isn't coming up :/
I wonder if I should install 5,1 BootCamp so it doesn't give me the error, and then use Brigadier again once I have connections to now install the iMacPro1,1 package.
Update: well that didn't work, when I try to install 5,1 BootCamp from the raw package, it tells me I need to be on Windows 7 lol. D'oh!
Last edited:
No. I did not ran any exe install on Windows, nor I installed anything on my Mac. Running "brigadier -m iMacPro1,1" on Windows simply downloads the drivers for you and extracts them with 7zip, nothing else. The command does not install anything, which is perfect because I do not want to have anything installed on Windows.
I had to install again Windows because I Installed some RX580 drivers from AMD site hoping I will get HWAccel. But I did not. I had the extracted Brigadier files on a thumb drive to avoid the download and all I did is to manually update the drivers in Device Manager. When I booted back in Catalina, the Windows share was showing on Finder.
Last edited:
Oh right, I just realized there's an additional --install command is what pushes through the full install, and not just putting the model. Thanks! Question for you. After you downloaded the drivers this way, did you install one by one, when you say you did it manually? I don't seem to find a way to tell windows to look and update all drivers in X folder and subfolders, except individually.
As for the AMD drivers I'm taking a chance with the bootcampdrivers.com 2020 updates and so far works great. Making progress, appreciate the help.
I managed to get ethernet fed through from my macbook pro haha, so now with Brigadier, what I did was let the iMacPro1,1 install run through like you said, but with the additionall --install command. I don't mind the Bootcamp option for an easy startup disk pick.
By the way, when I go to startup disk in Windows, it shows my Mojave installation on Bay 1, but not the main Mojave installation i use which is on PCIe nVME. Not a huge deal, but wondering what's up with that. (It all shows up OK on the MacOS side).
Another thing I'm trying to figure out with OC at the moment, despite everything working great so far, is why sometimes my nVME Mojave install does not show up on the OC boot picker? I have to do a NVRAM reset and only then it shows up. The moment I do a restart or shut down, it goes away again. What's up with that?
Last edited:
I'm experiencing something similar with an Apple AHCI drive, which requires a restart after a cold boot to be seen by OpenCore. Perhaps BlessOverride could help...
hi
Since i update SMBIOS to iMac Pro, My Mac says I'm using Core i3. lol
Could anyone know how to change back to Xeon?
By the way i'm using E5620.
thank you.
Since i update SMBIOS to iMac Pro, My Mac says I'm using Core i3. lol
Could anyone know how to change back to Xeon?
By the way i'm using E5620.
thank you.
It is several days ago that I installed an open core for the first time.
It was 0.5.8 and I downloaded config.plist at the same time.
Interesting. I had thought it was an issue I only had.
I had noted that a reboot cleared the issue and had made a feature request to allow rebooting instead of always using 'Reset NVRAM' which was granted and which appeared in v0.5.8. My ResetSystem is set to 'ColdReset' in my config and labelled 'Reboot Computer'.
As some may know, I chain load via Refind but still have the issue at random. Typically, I get a boot screen 6 secs after the chime and when this issue crops up, there is an extra 30 secs or so before the boot screen. When this happens, I just reboot directly from Refind. This solves it 99% of the time but sometimes, I need a second reboot.
I don't think it is OpenCore Specific as in such instances, the disk is also not available to Refind (need to reconfirm)
APFS disks are always available for rEFInd, when it stops at it's boot picker first before continuing to Opencore. It is the same as holding option key during boot. Since I can't make the Apple boot picker stop at the boot screen automatically I use rEFInd for this purpose.