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
Yes, the rounding should be fixed for the X5690. Just to clarify the rationale for rebooting: CPUFrequency does vary boot by boot, although not enough to affect the rounding in your case.
Hi all,
Apologies if this has been covered already, but can anyone elaborate on how to access the System Extensions folder in Big Sur?
I want to try to 'force' my rather expensive PCIe audio interface (no longer supported) to run by moving a pref pane and kext into place, but I can't access the Extensions folder.
SIP is still disabled as it was in Mojave, and I tried to run csrutil disable again as well as csrutil authenticaed-root disable in recovery terminal and get the following screen.
Big Sur 11.2.2 and Martin Lo config 0.6.7.
Thanks for any advice you can give!
Ed
Apologies if this has been covered already, but can anyone elaborate on how to access the System Extensions folder in Big Sur?
I want to try to 'force' my rather expensive PCIe audio interface (no longer supported) to run by moving a pref pane and kext into place, but I can't access the Extensions folder.
SIP is still disabled as it was in Mojave, and I tried to run csrutil disable again as well as csrutil authenticaed-root disable in recovery terminal and get the following screen.
Big Sur 11.2.2 and Martin Lo config 0.6.7.
Thanks for any advice you can give!
Ed
Yes, install the debug version. You'll find it next to the release version on GitHub. Then look for Target in you config and change 0 to 65. The log file will be written to your EFI volume.
The fix will officially come with version 0.6.8.
The easiest way is to use Hackintool to install the kext. Remember BS system is sealed it will only load the kext after a reboot.
System extensions should be and with Hackintool will be added to "library\extensions". Use Hackintool as suggested. If you need help using get back at me. Keep SIP disabled.
The short version: my 5,1 using Martin's directions takes a long time to boot. 40 seconds to the picker screen, 1:30 to the desktop.
The long version:
Mid 2012, 3.33 6 core, 32GB RAM, Radeon R9 280X 3GB, 500GB 860 EVO, few other backup data drives.
I dove into this project Saturday and it's been fun and at times frustrating. When I started I just followed all the instructions from Martin's method. I was able to boot into a 2nd drive, download Big Sur and then...DAMMIT...that 2nd drive wasn't APFS. Start over by erasing the 2nd drive and formatting it to APFS, then cloning my boot drive with Mojave to drive 2 with CCC. (I wanted a bootable backup of where I started for an escape route) Followed the directions again and I think I installed OC too many places, rebooting became a real adventure - half installed big sur that got porked during a reboot, blank screen, black screen, slash, different boot pickers, a real mess. Took a break, removed all drives except a clean, cloned Mojave. Followed directions again and nailed it first try. Upgraded to Big Sur , added wifi (BCM43xx) and everything seems stable after a day's use. I'm going to reinstall extra drives one by one just to make sure they don't cause issues. The boot up time though, just seems like it takes a very long time vs previous Mojave boot times. This machine usually doesn't get shut down more than once a month so it's now a huge issue. I'd like to know if it's a sign of impending doom.
And thank you Martin for sharing your talent and knowledge, it's appreciated!
I did not realize when hitting the link in post 1 that it was taking me to completely different thread. So maybe this was answered earlier, sorry haven't had a chance to read through the 300 pages here.
The long version:
Mid 2012, 3.33 6 core, 32GB RAM, Radeon R9 280X 3GB, 500GB 860 EVO, few other backup data drives.
I dove into this project Saturday and it's been fun and at times frustrating. When I started I just followed all the instructions from Martin's method. I was able to boot into a 2nd drive, download Big Sur and then...DAMMIT...that 2nd drive wasn't APFS. Start over by erasing the 2nd drive and formatting it to APFS, then cloning my boot drive with Mojave to drive 2 with CCC. (I wanted a bootable backup of where I started for an escape route) Followed the directions again and I think I installed OC too many places, rebooting became a real adventure - half installed big sur that got porked during a reboot, blank screen, black screen, slash, different boot pickers, a real mess. Took a break, removed all drives except a clean, cloned Mojave. Followed directions again and nailed it first try. Upgraded to Big Sur , added wifi (BCM43xx) and everything seems stable after a day's use. I'm going to reinstall extra drives one by one just to make sure they don't cause issues. The boot up time though, just seems like it takes a very long time vs previous Mojave boot times. This machine usually doesn't get shut down more than once a month so it's now a huge issue. I'd like to know if it's a sign of impending doom.
And thank you Martin for sharing your talent and knowledge, it's appreciated!
I did not realize when hitting the link in post 1 that it was taking me to completely different thread. So maybe this was answered earlier, sorry haven't had a chance to read through the 300 pages here.
Info reported. Thanks! (Actually, the recent fix for the X5690 should work with this as well.)
Last edited:
Using OC 0.6.7 on a Mac Pro 4,1>5,1 with a Sapphire Radeon 11265-05-20G Pulse RX 580 8GB and Big Sur + OpenCore on a PCIe NVMe, 2 standard SATA drives (one with Mojave), and another PCIe + SSD running Windows 10, I noticed that I can't get to the graphical boot picker when connected to my LG 29EB93 via DisplayPort. When I connect it via HDMI cable, I can access the menu every time without issue. I'm not sure if this was reported before. If so, my apologies. If not, is there a more formal way to report this?
you have to set the layout-id and create a dev entry for your audio device. reading the alcid from the boot-args and setting the alc-layout-id is broken
[EDIT: solved, see below]
1. Once the update gets downloaded, the Software Update control panel does it's things (gradually lowering the waiting time from 15 minutes to zero) and then displays a notification about imminent reboot.
2. If I then press "Update Now" within the SU panel, it starts downloading the update again.
3. If I press "Reboot" on the notification, it displays a black screen with Apple logo and a progress bar, after the progress bar goes to about ⅓, it reboots.
4. Once rebooted, the OC bootpicker shows two "Macintosh HD" volumes to boot from. One of them is the actual system (in that case it's only possible to go back to #1 above), so I pick the other one.
5. The other "Macintosh HD" is the update installer, which only progresses to about ⅕ and then reboots, which means I'm back to #4. Tried booting "the other" like 7 times now, makes no difference.
Oddly enough, the original Apple boot selector (I use a dual-ROM GPU, one ROM is Mac flashed and broken in Windows, the other is stock unflashed and works great with OC so I use this one as my daily driver for OS switching convenience) shows a "MacOS installer" instead of "the other Macintosh HD". It does not boot without OC, obviously.
Also, my actual "Macintosh HD" drive has grown a system snapshot, which I didn't see before attempting the upgrade (see pic). I assumed this to be the update volume, however it shows "Mac OS 11.2.2" in Disk Utility, so perhaps it's not the case?
Any ideas on how to proceed with the update to come through?
[EDIT: solved] I solved the problem by:
1. setting the VMM flags in config.plist and rebooting
2. redownloading the update
So - at least for me on a genuine 5.1 with two X5690, if it makes any difference - the hybridization alone, WITHOUT VMM flags set to ON does not allow for seamless updating.
The update shows up on my 5.1 with vanilla OC 0.6.7, however I'm stuck in an install loop.
1. Once the update gets downloaded, the Software Update control panel does it's things (gradually lowering the waiting time from 15 minutes to zero) and then displays a notification about imminent reboot.
2. If I then press "Update Now" within the SU panel, it starts downloading the update again.
3. If I press "Reboot" on the notification, it displays a black screen with Apple logo and a progress bar, after the progress bar goes to about ⅓, it reboots.
4. Once rebooted, the OC bootpicker shows two "Macintosh HD" volumes to boot from. One of them is the actual system (in that case it's only possible to go back to #1 above), so I pick the other one.
5. The other "Macintosh HD" is the update installer, which only progresses to about ⅕ and then reboots, which means I'm back to #4. Tried booting "the other" like 7 times now, makes no difference.
Oddly enough, the original Apple boot selector (I use a dual-ROM GPU, one ROM is Mac flashed and broken in Windows, the other is stock unflashed and works great with OC so I use this one as my daily driver for OS switching convenience) shows a "MacOS installer" instead of "the other Macintosh HD". It does not boot without OC, obviously.
Also, my actual "Macintosh HD" drive has grown a system snapshot, which I didn't see before attempting the upgrade (see pic). I assumed this to be the update volume, however it shows "Mac OS 11.2.2" in Disk Utility, so perhaps it's not the case?
Any ideas on how to proceed with the update to come through?
[EDIT: solved] I solved the problem by:
1. setting the VMM flags in config.plist and rebooting
2. redownloading the update
So - at least for me on a genuine 5.1 with two X5690, if it makes any difference - the hybridization alone, WITHOUT VMM flags set to ON does not allow for seamless updating.
Last edited:
Please excuse my ignorance, but can I use Preferences > Startup Disk to reboot my cMP into Windows 10? Will it cause any irreversible damage to OC or the BootROM?