Not to my knowledge, no. When I first tried installing BS, OC was already blessed and in release mode.
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
Actually, best to set verbose mode in OC instead of RP since test is for OC.
Add "-v" to the boot-args in OC.
No camera?
Before 11.2.1 (or, at least, in the days of 11.1), my Apple LED Cinema Display camera was working just fine. I've just discovered that the camera no longer works, or Big Sur says it doesn't. I discovered this when I tried to run Face time. I received this message: "FaceTime has not received any video from the connected camera". I tried rebooting to no avail. I haven't checked other operating systems, but my hunch is that the camera itself is just fine. Are there any camera issues related to OC 0.6.6 and/or Big Sur 11.2.1?
EDIT: I've just fixed it. Perhaps the solution is only temporary, but it might be permanent. I simply ran, from Terminal,
sudo killall AppleCameraAssistant
The camera has started working flawlessly.
Before 11.2.1 (or, at least, in the days of 11.1), my Apple LED Cinema Display camera was working just fine. I've just discovered that the camera no longer works, or Big Sur says it doesn't. I discovered this when I tried to run Face time. I received this message: "FaceTime has not received any video from the connected camera". I tried rebooting to no avail. I haven't checked other operating systems, but my hunch is that the camera itself is just fine. Are there any camera issues related to OC 0.6.6 and/or Big Sur 11.2.1?
EDIT: I've just fixed it. Perhaps the solution is only temporary, but it might be permanent. I simply ran, from Terminal,
sudo killall AppleCameraAssistant
The camera has started working flawlessly.
Last edited:
Sorry to be another new poster who left it too long before asking for help but after years of lurking I've hit my limit and thought it best to ask before I brick something permanently so here goes.
I've been tinkering with my cMP4,1 over the last few months (probably years) and kept hitting wall after wall which I managed to recover from / upgrade / repair with the info on this forum. To cut a long nightmare short I started with wanting a new GPU and ended up doing a dual CPU upgrade for the cMP 4,1 due to the Nehalem / Mojave CPU code audio stutter issue.
Somewhere before realising I needed to change the CPU's I started down the OpenCore road. I went with the chainloaded MyBootManager (excellent work and many thanks to the creator) and I kept it blessed to rEFIndPlus while shifting to my focus on getting Mojave working via the CPU upgrade and once that finally worked I did a clean install which blessed the Mojave SSD which also happened again after the recent security update. At some point the EFI (which I now know shouldn't have been on APFS) couldn't be mounted due to corruption.
Sorry for rambling but I'm not sure exactly which upgrade or mod was the problem or if it was a standard corrupt APFS volume but after trying to recover from the clean install boot coup the Mac Pro would go into the black screen update for a while installing Mojave and the disc drives would pop out like when I flashed it up to 144.0.0.0.0 (even a USB BD drive which may have ejected normally but I unplugged it). When I looked at the EFI the first time I installed OC via MyBootManager it ended up in a folder called APPLE which I heard isn't uncommon but it was actually a firmware folder with a file named 'firmware 5,1 something .scap' which I guess was leftover from the first upgrade to the boot rom I did using the Mojave installer which I quit before actually installing the OS due to GPU being an MVC NVIDIA 980 Ti (now using a Radeon Pro WX 4100 which was surprisingly pleasant to install but I lost boot screen hence OC).
I copied then deleted the folder incase it was from OC and may try install it due to spoofing etc. Then somewhere along the line a second file titled firmware.scap appeared in APPLE/EXTENSIONS. This drive wasn't in Mojave use although it was in an internal bay with the Mojave SSD I did a second Mojave install to PCIe SSD from so unsure why it may have been used for any firmware storage.
Then a second boot coup happened due to the Mojave security update which blessed itself again but this caused me to see the EFI was now unable to mount. I decided to start over with a clean install to NVMe, reformatted the corrupt APFS drive using HFS and reinstalled MyBootManager to the EFI properly (I now know why APFS isn't advised) but still got some strange issues (could be using NVMe for first time) which caused me to come here and ask for advice.
Am I right in thinking the firmware file was written by the Mojave install and then possibly written a second time possibly via the security update which corrupted or fill the EFI? The ejecting discs and black screen stalls got me really worried and maybe I have too many things in the air at once while tinkering with OC/rEFIndPlus.
I guess I need to backup then check the rom for wear and signs of failure so I've downloaded ROMTool but I am scared to even reboot after coming this far! Can I use the current blessed rEFIndPlus EFI boot to toggle SIP before running the tool or is that going to push the limits of the NVRAM further or add stuff to the results? Sorry for my rambling and likely bad grammar etc as typing isn't easy for me to communicate so I get jumbled and add too much info. I guess my main issue is backup boot rom and then maybe help understanding what happened with this firmware / EFI folder corruption and probably a million other issues eventually.
I've been tinkering with my cMP4,1 over the last few months (probably years) and kept hitting wall after wall which I managed to recover from / upgrade / repair with the info on this forum. To cut a long nightmare short I started with wanting a new GPU and ended up doing a dual CPU upgrade for the cMP 4,1 due to the Nehalem / Mojave CPU code audio stutter issue.
Somewhere before realising I needed to change the CPU's I started down the OpenCore road. I went with the chainloaded MyBootManager (excellent work and many thanks to the creator) and I kept it blessed to rEFIndPlus while shifting to my focus on getting Mojave working via the CPU upgrade and once that finally worked I did a clean install which blessed the Mojave SSD which also happened again after the recent security update. At some point the EFI (which I now know shouldn't have been on APFS) couldn't be mounted due to corruption.
Sorry for rambling but I'm not sure exactly which upgrade or mod was the problem or if it was a standard corrupt APFS volume but after trying to recover from the clean install boot coup the Mac Pro would go into the black screen update for a while installing Mojave and the disc drives would pop out like when I flashed it up to 144.0.0.0.0 (even a USB BD drive which may have ejected normally but I unplugged it). When I looked at the EFI the first time I installed OC via MyBootManager it ended up in a folder called APPLE which I heard isn't uncommon but it was actually a firmware folder with a file named 'firmware 5,1 something .scap' which I guess was leftover from the first upgrade to the boot rom I did using the Mojave installer which I quit before actually installing the OS due to GPU being an MVC NVIDIA 980 Ti (now using a Radeon Pro WX 4100 which was surprisingly pleasant to install but I lost boot screen hence OC).
I copied then deleted the folder incase it was from OC and may try install it due to spoofing etc. Then somewhere along the line a second file titled firmware.scap appeared in APPLE/EXTENSIONS. This drive wasn't in Mojave use although it was in an internal bay with the Mojave SSD I did a second Mojave install to PCIe SSD from so unsure why it may have been used for any firmware storage.
Then a second boot coup happened due to the Mojave security update which blessed itself again but this caused me to see the EFI was now unable to mount. I decided to start over with a clean install to NVMe, reformatted the corrupt APFS drive using HFS and reinstalled MyBootManager to the EFI properly (I now know why APFS isn't advised) but still got some strange issues (could be using NVMe for first time) which caused me to come here and ask for advice.
Am I right in thinking the firmware file was written by the Mojave install and then possibly written a second time possibly via the security update which corrupted or fill the EFI? The ejecting discs and black screen stalls got me really worried and maybe I have too many things in the air at once while tinkering with OC/rEFIndPlus.
I guess I need to backup then check the rom for wear and signs of failure so I've downloaded ROMTool but I am scared to even reboot after coming this far! Can I use the current blessed rEFIndPlus EFI boot to toggle SIP before running the tool or is that going to push the limits of the NVRAM further or add stuff to the results? Sorry for my rambling and likely bad grammar etc as typing isn't easy for me to communicate so I get jumbled and add too much info. I guess my main issue is backup boot rom and then maybe help understanding what happened with this firmware / EFI folder corruption and probably a million other issues eventually.
Last edited:
Despite from the lacking USB-Drivers for my M-Audio Oxygen 8 in Catalina
(maybe this will help somebody: https://sourceforge.net/projects/midisport-macos/files/)
, I am in more serious trouble now: while booting in Recovery Mode, because its the first option in my boot-picker that will run automatically if you do nothing, I stupidly made a hard reset (pushing the OFF Button) to prevent going in the whole procedure. The "benefit" was: the system won't boot entirely, only to about 90% and then shut down to boot again. I tried recovering Catalina from the boot menu: same outcome. I reapplied OC to the EFI of the Catalina partition from a Mojave system I have on my old HDD: same. I repaired the Catalina NVME volume with the DiskManager in recovery mode: same. Strange thing is: I can only start the installation in recovery mode; when I try it in directly from Mojave it will say, that I have to upgrade to Catalina to install it on that drive. Should I apply the OC EFI changes to my Mojave EFI as well? Will it make any difference? Any suggestions welcome!
(maybe this will help somebody: https://sourceforge.net/projects/midisport-macos/files/)
, I am in more serious trouble now: while booting in Recovery Mode, because its the first option in my boot-picker that will run automatically if you do nothing, I stupidly made a hard reset (pushing the OFF Button) to prevent going in the whole procedure. The "benefit" was: the system won't boot entirely, only to about 90% and then shut down to boot again. I tried recovering Catalina from the boot menu: same outcome. I reapplied OC to the EFI of the Catalina partition from a Mojave system I have on my old HDD: same. I repaired the Catalina NVME volume with the DiskManager in recovery mode: same. Strange thing is: I can only start the installation in recovery mode; when I try it in directly from Mojave it will say, that I have to upgrade to Catalina to install it on that drive. Should I apply the OC EFI changes to my Mojave EFI as well? Will it make any difference? Any suggestions welcome!
There are two
boot-args entries in config.plist. I assume the key should be modified as such: <key>boot-args-v</key>?Here:
What about
<string>boot-args</string> here:
There is only one boot argument injected. The 2nd one is to tell OpenCore to block the original boot argument.
If you want to add the
-v, you can add that after unfairgva=1
Last edited:
Ok, did that and now I get verbose output during 1st stage of the boot loader.
EDIT: forgot to attach logs.
Last edited:
Ya'll - First off, amazing work on the OpenCore project - Big Sur's smooth sailing along blissfully and lightning quick on my 5,1 and it's simply amazing.
However Software Update via System Preferences doesn't work - at all. It's "stuck" at 11.2 - doesn't see the latest 11.2.1, driving me crazy. Need to have the latest installed and have the know that it's doable regardless.
Any help on this? I know others have experienced this with their Hackintoshes but on a real Mac SIP enabled plus rebuild of Kext cache should totally do it right?
SIP is enabled
VMM flag is enabled AFAIK per the guide and whatnot - it matches 1:1 for the flag etc.
- Did the PRAM reset like, 5 times, not consecutively but that should've cleared any blockages, no?
Any help would be *awesome*
Thanks
However Software Update via System Preferences doesn't work - at all. It's "stuck" at 11.2 - doesn't see the latest 11.2.1, driving me crazy. Need to have the latest installed and have the know that it's doable regardless.
Any help on this? I know others have experienced this with their Hackintoshes but on a real Mac SIP enabled plus rebuild of Kext cache should totally do it right?
SIP is enabled
VMM flag is enabled AFAIK per the guide and whatnot - it matches 1:1 for the flag etc.
- Did the PRAM reset like, 5 times, not consecutively but that should've cleared any blockages, no?
Any help would be *awesome*
Thanks
@cdf @h9826790 @startergoOk, did that and now I get verbose output during 1st stage of the boot loader.
EDIT: forgot to attach logs.
Just having a closer look at my logs, and these entries stand out. Not knowing enough about OC to determine what's happening, could these possibly indicate to you why I'm not getting the 1st stage boot screen on my Mac EFI flashed 7950?
@cdf any changes improvements to the Windows10 install procedure? I did not booted for a while into Windows, this afternoon when I selected the Windows disk, I was presented with the blue Windows logo, frozen. as it happened many times before. There is nothing I can do, except the shut down the Mac.
Also, I cannot set anymore Windows as Startup disk:
Also, I cannot set anymore Windows as Startup disk:
We've confirmed that text works but not graphics. Perhaps try enabling ProvideConsoleGop.
The only one that's perhaps significant is the ASCII Output not being found.
This is the text renderer which only works on GOP Units. Might be that it impacts the Stage 1 screen but not sure as it should have been the same with RP if so as it uses the same protocols.
Might be that UGA units do not show this in OC. Perhaps someone can confirm this.
Ultimately, I think you need to raise an issue on the project.
Not for me, it boots into Big Sur as it remains selected into OpenCanopy.
Should I re-install Windows again?
NVRAM reset fixed the absent boot screen (i'll keep that in mind). however following the instructions again gave me the same error in Windows setup. i get through Cortana, set up keyboard and network, system restarts once (select Windows from OC boot picker) then i get stop code:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDwhat failed: bcmwl63a.sys
Last edited:
Which Windows iso version? Is it the latest? Did you do local or network account?
most recent Win10 Home iso. i didn't get to make an account yet. it restarted once before i got that stop code.