MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[startergo]

Does OpenCore allows enabling Sidecar without using patchers for that feature?

Sidecar-supported Mac models:
• MacBook introduced in 2016 or later
• MacBook Air introduced in 2018 or later
• MacBook Pro introduced in 2016 or later
• Mac mini introduced in 2018 or later
• iMac introduced in late 2015 or later
• iMac Pro introduced in 2017 or later
• Mac Pro introduced in 2019
What is the common denominator? Intel Quick Sync or T2 chip.
the 2015 MBP model is a supported model and has a discrete GPU, but no T2 chip hence no Sidecar.
In theory if you spoof iMac19,1 which uses Quick Sync partially or fully you can probably do it

Sidecar not working on iGPU-less systems reliably · Issue #1 · AMD-OSX/bugtracker

Description: On macOS 10.15.1 and higher Sidecar is not stable on iGPU-less systems macOS 10.15 betas worked on all supported SMBIOS regardless of iGPU, including iMacPro1,1 and MacPro7,1. Was even...

github.com

 

[cdf]

Hi thanks for the reply, although I am not sure what you mean.... or where I went wrong following your guide.

If it is ok with you I am going to post that part of your guide and what I did so you can quickly see where I screwed up

This clarifies things a bit. The error you are getting seems to indicate a problem with the installer. I suggest recreating the installer. The rsync operation can take some time to complete, so make sure that the prompt is available (indicating that the operation has completed) before exiting Terminal.

 

[johnwillsey]

Big Sur RC installation frustration and victory...
Well, I was going nutz trying to get my big Sur RC install working. kept going to Apple, then freezing after install reboot. then I messed with some settings and it partially finished the post boot install but never finished.

Then I finally removed refind chain loader (I had default with no VMM and alt with VMM setups and alt failsafe config) and sure enough, without refind in the mix, I had no issues getting int installed per the recommendations this week using our favorite Acceleration Master's std 0.63 build. (post #1,314)

UPDATE: @davo let me know that refindplus should work with Big Sur. Looks like I should have updated it. (I didn't. I simply updated the OC within my old refind setup). Will need to try that out...

Thought I'd pass it on....

 

[ber404]

Hi, OC 0.6.3 on cMP 2009 5,1, Catalina 10.15.7, won't shutdown anymore and audio not working, how can I solve this ?
Dosdude post install doesn't fix audio and reset smc+nvram doesn't fix shutdown

 

[johnwillsey]

@davo let me know that refindplus should work with Big Sur. Looks like I should have updated it. (I didn't. I simply updated the OC within my old refind setup). Will need to try that out... (Correcting Post above)

 

[Dayo]

Just wanted to clarify that the issue of what works or not is not the presence or absence of RefindPlus.
Other factors in the OpenCore config are what matter.

 

[startergo]

Hi, OC 0.6.3 on cMP 2009 5,1, Catalina 10.15.7, won't shutdown anymore and audio not working, how can I solve this ?
Dosdude post install doesn't fix audio and reset smc+nvram doesn't fix shutdown

The shutdown file is located in /Library/Logs/DiagnosticReports which you can find by opening a Finder window and selecting "Go" --> "Go to Folder" option in the Finder menubar. You can then type in or copy and paste that directory to find the shutdown stall (the filename will start with "shutdown_stall". When you open it, you will notice it is all a bunch of letters and numbers. You will need to open up terminal and type in , "spindump -i " and notice the space after the "i". You can drag the shutdown log file (from Finder into Terminal) after the space and hit enter. You will get some authentication notice, just hit enter again and the file will be created in the /tmp/spindump.txt directory. If you see any processes that are third party, you can either remove them or make sure they are updated. Otherwise, it's just Catalina being Catalina.

 

[TECK]

With the imminent release of Big Sur, I want to do clean OS install on current Catalina NVMe. Will the USB install work with OC? @cdf this might be something users will want to do, do you think you can update first post to detail an USB install of Catalina/Big Sur?

 

[cdf]

With the imminent release of Big Sur, I want to do clean OS install on current Catalina NVMe. Will the USB install work with OC? @cdf this might be something users will want to do, do you think you can update first post to detail an USB install of Catalina/Big Sur?

A clean install from a USB installer should work. Just select the USB drive from the boot picker. For Catalina, you need to turn on the VMM flag. For Big Sur, you'll want to use hybridization with that firmware-feature bit I identified last week (no need for VMM). See post #4,399.

 

[ber404]

I did that, but I'm not sure how to check and remove stuffs .. can I post the result of spindump here ?

 

[startergo]

I did that, but I'm not sure how to check and remove stuffs .. can I post the result of spindump here ?

PM me.

 

[naerct]

Test

 

[TECK]

Unfortunately, Lilu userspace patching is broken in Big Sur

Do you know if there is an issue open with developer? I don't see anything into bug tracker.

 

[TECK]

reboot to Mojave and correct OC errors without having to open the case.

I never open the case, all I have to do is a hard reset and I'm back on Mojave.

 

[startergo]

Do you know if there is an issue open with developer? I don't see anything into bug tracker.

Kernel extensions are replaced by system extension in BigSur. Lilu+ plugins operated by patching the Kernel and user space, which is no longer patchable. They are fully aware of the situation.

 

[djangovic]

The USB drive originally contained the folder called efi, which made the drive bootable. During the installation, we backed up that folder and replace it with another one that we generated for your Windows drive. This folder contained the Microsoft folder that we needed. After copying the Microsoft folder, we restore the USB drive to its original state in case we want to use it again.



Windows probably activated itself automatically when you connected to the internet. If you've ever had Windows activated on your machine, Microsoft knows it.

hello, i made it trough the whole installation and everything is running perfect, except two things:
1. I can't activate windows with an regular bought license key.
2. I have an built in an wlan adapter and i works with Mojave and windows but not with Catalina.

every help is welcomed!
thanks.

 

[wnlewis]

When I put in -r Volumes/CCCOMA_64/ /Volumes/dev/disk5s1

I get the response

-bash: -r: command not found.

I think I have left something out. What is likely?

Thanks

 

[paalb]

When I put in -r Volumes/CCCOMA_64/ /Volumes/dev/disk5s1

I get the response

-bash: -r: command not found.

I think I have left something out. What is likely?

Thanks

If it is the command that is mentioned on page one under Windows?
rsync is the command that is missing before -r

rsync -r /Volumes/....

 

[jackluke]

Kernel extensions are replaced by system extension in BigSur. Lilu+ plugins operated by patching the Kernel and user space, which is no longer patchable. They are fully aware of the situation.

When BigSur prelinkedkernel worked during early beta Lilu worked too, then after beta4 prelinkedkernel doesn't work more so either on Boot and SystemKernelExtensions (kernelcollections) I guess this is the new user space used for kext injection, from opencore 0.6.3 release note:

• Increased slide allocation reserve to 200 MB for Big Sur beta 10

Then maybe Lilu or other kext need to recompile for newer macOS11 SDK , because with BKE and SKE there is also a kernelcollection UUID matching verification (from kmutil and kcditto), between these:

/Volumes/Preboot/UUID/boot/System/Library/KernelCollections/*.kc

/Volumes/BigSur/System/Library/KernelCollections/*.kc

 

[h9826790]

Big Sur RC installation frustration and victory...
Well, I was going nutz trying to get my big Sur RC install working. kept going to Apple, then freezing after install reboot. then I messed with some settings and it partially finished the post boot install but never finished.

Then I finally removed refind chain loader (I had default with no VMM and alt with VMM setups and alt failsafe config) and sure enough, without refind in the mix, I had no issues getting int installed per the recommendations this week using our favorite Acceleration Master's std 0.63 build. (post #1,314)

Thought I'd pass it on....

All credit goes to cdf, he found the critical firmware feature mask.

 

[wnlewis]

Making a proper USB ISO has eluded me so far.

I download Windows 10 home on my HP desktop.

Should I be downloading the ISO in my cMP?

I have tried that, but since my cMP does not yet have Windows installed I get the Microsoft screen that says, You don't have the right type of computer (not a Windows PC).

The instructions on the OpenCore instructions say to double click the ISO image.

When I double click the ISO on the HP desktop, it just opens, it does not mount. Likewise on the CMP.

The ISO probably won't boot the cMP unless it is mounted.

So how do I get it mounted and how do I get it to be CCCOMA_x64, which I believe is the correct name for the file?

I have made a USB with the Windows tool. When I put it in the cMP it says ESD-ISO. I also tried it with a dual layer DVD. Same results.

 

[Cesar2066]

Finally got OpenCore setup to play nicely as I can now dual boot Catalina and Windows 10 (EFI), both on dedicated NVMe drives, with my recently installed RX 5700 XT Anniversary Edition.

I'm lovin it!

May I ask how? I have Catalina fresh install on nvme and have open core 6.3 and did a fresh install of windows 10 but when I turn on the Mac it boots straight to windows if I remove the windows ssd then I’ll get selector screen...i have an rx 580 is there something I have to do different for windows not to load by default and let me select which drive to boot from?

 

[johnwillsey]

May I ask how? I have Catalina fresh install on nvme and have open core 6.3 and did a fresh install of windows 10 but when I turn on the Mac it boots straight to windows if I remove the windows ssd then I’ll get selector screen...i have an rx 580 is there something I have to do different for windows not to load by default and let me select which drive to boot from?

I wen't crazy with this for a day before I figured it out.. Windows even on my UEFI machine would install fresh but not be a UEFI install. do some googling, but I used the mbr2gpt utility to convert my fresh install to UEFI. Then it finally appeared in Opencore. I just found the instructions again by searching for "convert mbr to efi windows 10"

 

[startergo]

May I ask how? I have Catalina fresh install on nvme and have open core 6.3 and did a fresh install of windows 10 but when I turn on the Mac it boots straight to windows if I remove the windows ssd then I’ll get selector screen...i have an rx 580 is there something I have to do different for windows not to load by default and let me select which drive to boot from?

Remove the EFI\Boot folder from the Windows EFI partition. Then the Mac won't be able to boot Windows without OC.

 

[joevt]

Remove the EFI\Boot folder from the Windows EFI partition. Then the Mac won't be able to boot Windows without OC.

Unless you put NTFS.efi in the ROM or in the Driver#### and DriverOrder nvram variables and have an EFI folder on the Windows NTFS volume... but it's all the same thing - I mean you could put Windows EFI boot loader anywhere on an HFS+ partition and bless it and it could boot Windows. The point is to make sure the Mac can't boot a Windows EFI without going through OpenCore first.