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 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Anyone have some reboots when samba transfer?
I use smb with my shared windows 10 HDD.
But for several weeks now, and I don't know why, my cMP 2012 (Catalina) reboot in the middle of transfers.
I tried to use forklift or commander pro... No luck.
For a time, I manually put the boost in IStat Menus at medium (even high sometimes) as TG pro didn't seems to work.
Well it did the trick, but this morning, nothing works... When I transfer a file around 3Go, it freezes and reboot, without saying there's an error, and the mac has to reboot... nothing...
I posted here because, maybe it's related to OpenCore and as I use Martin's mod... But idk.
Hope someone have the same issue
I use smb with my shared windows 10 HDD.
But for several weeks now, and I don't know why, my cMP 2012 (Catalina) reboot in the middle of transfers.
I tried to use forklift or commander pro... No luck.
For a time, I manually put the boost in IStat Menus at medium (even high sometimes) as TG pro didn't seems to work.
Well it did the trick, but this morning, nothing works... When I transfer a file around 3Go, it freezes and reboot, without saying there's an error, and the mac has to reboot... nothing...
I posted here because, maybe it's related to OpenCore and as I use Martin's mod... But idk.
Hope someone have the same issue
Thanks, but i already checked, and the NorthBridge Tdiode never get above 70°C...
I thought also it was a bad cooling from my only processor, but even when the temperature is at 38/40°C, Catalina freeze and reboot, and now during torrents transfer... so it's during heavy use of HDD, i guess...
Also it's not on one same HDD.
Samba transfer has been made on different HDDs for the same error.
Same for torrent, I tried on 2/3 HDDs...
I really don't know from where this freeze/reboot comes from
EDIT : I think it's solved, I forgot to make few rules to apply when temperatures rise in IStat Menus... Now, and since I removed Crossover, I didn't have freeze/reboot with heavy samba transfers, and heavily use of torrent app. Let's see, but it seemed to be a software issue...
Last edited:
I thought to update this past inquiry and issue of mine from this thread. Since then, my disk names never showed up properly in bootscreen and I never got into using the disklabel tool as I found it a bit intimidating 😬 .
But I just updated OC with your 0.6.8 package and all disk names show up properly now! Not sure why, but it is so much better as I have multiple OS drives and it used to be confusing choosing the right one without names. But no more guessing drives now!
Thanks again for keeping this package updated, it is very much appreciated!
I've come late to this party after being away for over a year or so, and now want to finally upgrade my 2012 cMP to Big Sur, which is currently running Mojave installed on an Apricorn Velocity Duo X2 (Windows 10 installed on the other SSD), flashed 280X, and an Apple OEM Broadcom BCM94360CD WiFi/Bluetooth card.
Is this method proposed in this thread the best way to do this? Can I upgrade from the 280X to something newer and faster and still retain the Apple Boot Picker screen, or facsimile thereof?
I first checked the general Big Sur thread and came away to use OCLP. Then I checked here in the Mac Pro thread and came across OpenCore, where some one recommended coming to this thread.
Is this method proposed in this thread the best way to do this? Can I upgrade from the 280X to something newer and faster and still retain the Apple Boot Picker screen, or facsimile thereof?
I first checked the general Big Sur thread and came away to use OCLP. Then I checked here in the Mac Pro thread and came across OpenCore, where some one recommended coming to this thread.
Last edited:
Yes, the latest OC package from post #1314 should enable boot screen for most AMD graphic cards (RX560 or newer).
Here is the demostration
For 280X, pretty much anything from RX570 can be considered as an upgrade.
For Mojave (latest 10.14.6), the highest graphic card can be used is Radeon VII.
If you want to go Big Sur, the latest graphic card now can be used is 5700XT. However, don't expect this card perform much better than Radeon VII. In fact, on average, the Radeon VII still 8% faster than 5700XT.
My package was developed on my cMP with Radeon VII. And since the Radeon VII has no variant but only reference card. Therefore, it's the safest choice. However, this card seems extremely expensive nowadays.
A little heads up for you, the latest Big Sur beta isn't working that good on cMP. If you want to go Big Sur, my personal suggestion is to get the current (11.2.3) official installer ASAP. It may help you to install Big Sur easier later.
Yea, I've been told elsewhere to stick to 11.2.3, though since I'm using a regular SSD on a PCIe card, I could move it to one of the bays and this may allow 11.3/4 to boot...
I perused the videos in post 1314 but I really didn't see anything about upgrading my existing Mojave system.
1) Do I need to start from a wiped system to install OpenCore, then do a migration and start upgrading? It appears I can just install OpenCore on top of my existing Mojave setup.
2) Can I upgrade to Big Sur directly from Mojave, or do I first need to upgrade to Catalina? "Additional Option 3" simply starts with Catalina, enabling it to be upgraded via Apple's update mechanism, including up to Big Sur.
1) Do I need to start from a wiped system to install OpenCore, then do a migration and start upgrading? It appears I can just install OpenCore on top of my existing Mojave setup.
2) Can I upgrade to Big Sur directly from Mojave, or do I first need to upgrade to Catalina? "Additional Option 3" simply starts with Catalina, enabling it to be upgraded via Apple's update mechanism, including up to Big Sur.
The suggested (perhaps required) procedure is to always have a Mojave OS boot drive installed on SATA Bay 1. You will need this in the future when you will perform OC upgrades. And it is absolutely necessary if unexpected issues break your Big Sur boot drive.
When I installed OC and Big Sur, I first cloned my Mojave boot drive and then started up from the cloned drive to install OC and Big Sur. For cloning I use Carbon Copy Cloner but there are alternatives too.
The OC guide in the general cMP OC thread explains in details why it is good practice to have your "vanilla" Mojave drive installed in SATA Bay 1. Worth reading those introductory posts to become familiar with this. The @h9826790 OC package covers a lot but is not really meant to cover all things OC and/or replace the more comprehensive OC guide in the cMP OC thread. Again, this @h9826790 OC package was developed with the aim to activate hardware acceleration.
Lastly, as you move forward with your installs, please note that there is a known (and so far) unresolved bug with Bluetooth not working only after the first boot from Mojave into Big Sur. One subsequent Big Sur reboot will bring back Bluetooth and it will then work properly for all subsequent Big Sur reboots. More on this bug in this thread:
OpenCore Big Sur: Random loss of Bluetooth functionality
This behaviour is experienced also by @startergo. Basically, I lose Bluetooth on random reboots while on OC Big Sur only. Everything works as expected on Mojave and OC Catalina. Update: This issue occurs only when I boot from Mojave to Big Sur. If I reboot again from Big Sur, Bluetooth is...
forums.macrumors.com
Has Anyone managed to update to 11.2.3? I tried to just upgrade but the installer just reboots. I cleared the NVRAM but it still doesn't work. I am thinking of trying the combo update.
I had no issues when updating to 11.2.3. I do remember multiple reboots with relatively long periods of black screen and apparent inactivity. I just waited it out every time and it finally installed it properly. But not sure what your problem might have been, others could chime in or perhaps better, raise the issue in the general cMP OC thread for help.
I'm trying right now with same issue. I choose the installer in OC boot picker but seems to loop again and again with installing on another AFPS formatted HDD, with reboot and reboot to the same state when choosing the BS installer.
I try now to remove Filevault on my main macOS (so Catalina 10.15.7), I'm waiting for now that it'll finish decrypting.
If I tried to use an external USB bootable I made with terminal, it goes to BS recovery, not installer... Dunno why...
EDIT : everything goes fine with a fresh install of everything. Even the freeze/reboot. Big Sur works flawless for me.
I try now to remove Filevault on my main macOS (so Catalina 10.15.7), I'm waiting for now that it'll finish decrypting.
If I tried to use an external USB bootable I made with terminal, it goes to BS recovery, not installer... Dunno why...
EDIT : everything goes fine with a fresh install of everything. Even the freeze/reboot. Big Sur works flawless for me.
Last edited:
Ran into my first issue: following the OpenCore video linked in post 1314 and when I mount my EFI partition, it's an empty volume; no EFI folder exists as shown in the video.
Now, the video is running Catalina, whereas I am running Mojave.
How should I proceed? Do I simply create a new EFI folder or did I run into a problem?
UPDATE: I went through the install steps outlined in the OpenCore thread and it explicitly states that there may or may not be an EFI folder in the EFI partition; if there is, it can be merged with the files provided in post 1314.
So I simply copied the EFI folder over to the partition and rebooted successfully. Didn't notice anything different in any aspect, so now starting the Big Sur install...
SECOND UPDATE: I'm a literal guy; I watch and I follow exactly. Even though I saw the script file, Bless OpenCore, neither the video nor the instructions of post 1314 showed it being ran, so I didn't run it. And "Additional option 3" to install Big Sur indicates with OC 0.6.8, I didn't need to change anything in the config.plist, but my 11.2.3 installer would not allow me to install onto my Mojave drive. So reading the posts afterwards, I noticed someone having problems running the Bless OpenCore script. Curious, I launched the script and it ran with no problems, rebooted, and NOW I noticed a BIG difference at boot as it presented me a black-background Boot Picker, exactly like my 2015 MBP does.
I think the video(s) and instrux need to be corrected to indicate that you MUST run the Bless OpenCore script after copying the EFI contents over.
Big Sur installer can finally select my Mojave SSD (I did modify the config file but will restore settings after upgrade is complete).
THIRD UPDATE: I decided to reinstall my RX 580 before upgrading to Big Sur, and while I was at it, I restored the original config.plist file and Big Sur is still available to be upgraded, which is finally in progress now...
Now, the video is running Catalina, whereas I am running Mojave.
How should I proceed? Do I simply create a new EFI folder or did I run into a problem?
UPDATE: I went through the install steps outlined in the OpenCore thread and it explicitly states that there may or may not be an EFI folder in the EFI partition; if there is, it can be merged with the files provided in post 1314.
So I simply copied the EFI folder over to the partition and rebooted successfully. Didn't notice anything different in any aspect, so now starting the Big Sur install...
SECOND UPDATE: I'm a literal guy; I watch and I follow exactly. Even though I saw the script file, Bless OpenCore, neither the video nor the instructions of post 1314 showed it being ran, so I didn't run it. And "Additional option 3" to install Big Sur indicates with OC 0.6.8, I didn't need to change anything in the config.plist, but my 11.2.3 installer would not allow me to install onto my Mojave drive. So reading the posts afterwards, I noticed someone having problems running the Bless OpenCore script. Curious, I launched the script and it ran with no problems, rebooted, and NOW I noticed a BIG difference at boot as it presented me a black-background Boot Picker, exactly like my 2015 MBP does.
I think the video(s) and instrux need to be corrected to indicate that you MUST run the Bless OpenCore script after copying the EFI contents over.
Big Sur installer can finally select my Mojave SSD (I did modify the config file but will restore settings after upgrade is complete).
THIRD UPDATE: I decided to reinstall my RX 580 before upgrading to Big Sur, and while I was at it, I restored the original config.plist file and Big Sur is still available to be upgraded, which is finally in progress now...
Last edited:
Thanks for your report, those info actually contained in the video's subtitle. Post #1314 updated accordingly.
Great that you were able to solve the issues/confusions. It should all work fine now. One reminder - make sure, once you boot into Big Sur, that in "System Preferences>Software Update>Advanced" you deselect "Install MacOS Updates" and maybe even "Download new updates when available". At least until the 11.3 PCIe issues have been (hopefully) resolved...
Success!
Both my 2012 cMP and 2012 Server cMP now have OpenCore installed, with the former now running smoothly on Big Sur 11.2.3 on an SSD mounted on a Apricorn Velocity Duo X2 with RX 580, and the latter running on Catalina 10.15.7 on an SSD in Bay 1 with a flashed 7970. Big Sur took quite awhile to install but otherwise no hitches. Both have newer Airport cards.
I installed Catalina thinking that 32-bit apps were made to run on it, but I misread the statements in the first post: it's only non-GUI 32-bit apps that was made to work under Catalina. I have an old Real Basic custom app I wrote that is still 32-bit, but now that I've upgraded both machines, it forces me to either rebuild it under Xojo (weeks or months to do) or give it up completely.
Both my 2012 cMP and 2012 Server cMP now have OpenCore installed, with the former now running smoothly on Big Sur 11.2.3 on an SSD mounted on a Apricorn Velocity Duo X2 with RX 580, and the latter running on Catalina 10.15.7 on an SSD in Bay 1 with a flashed 7970. Big Sur took quite awhile to install but otherwise no hitches. Both have newer Airport cards.
I installed Catalina thinking that 32-bit apps were made to run on it, but I misread the statements in the first post: it's only non-GUI 32-bit apps that was made to work under Catalina. I have an old Real Basic custom app I wrote that is still 32-bit, but now that I've upgraded both machines, it forces me to either rebuild it under Xojo (weeks or months to do) or give it up completely.
Follow-up question: Both machines had Windows 10 Pro legacy installed. I've read somewhere that UEFI Windows should be installed. Is this necessary?
The Server can start with a clean Windows 10, which I'm preparing to do, but the other cMP's Windows install had a lot of apps installed and I'd rather not hassle with reinstalling and tweaking them again.
The Server can start with a clean Windows 10, which I'm preparing to do, but the other cMP's Windows install had a lot of apps installed and I'd rather not hassle with reinstalling and tweaking them again.
I can't provide feedback on Windows as I don't have it/use it on cMP. But as far as 32-bit versus 64-bit apps, you can have multiple Mac OS drives and boot accordingly to your needs. I have High Sierra, Mojave, and Big Sur in my cMP.
Yes, that's what I have now: Big Sur, Mojave, High Sierra, Sierra, and El Capitan. Essentially, as I upgrade to major releases, I clone my current system and that clone remains at the OS version before upgrade.
But my 32-bit app runs on a daily basis off-hours, so it's not practical to boot into an older OS so it can run at night. And because it takes a significant amount of time to run, running it virtualized would also not be a practical solution (though it could be a temporary one).
I just have to bite the bullet and rewrite it almost entirely from scratch, which I might as well go XCode since I no longer need cross-platform compatibility.
Lovely! It's a living Mac OS museum!!!
They also act as backups, synchronizing my documents with at least the newest previous OS volume nightly.
Legacy Windows is not mandatory, but highly recommended.
OpenCore only support UEFI OS, legacy Windows won’t boot directly from OC boot picker.
To fix it completely, you can convert the existing legacy Windows to UEFI Windows.
Or further install rEFInd+ to bridge boot legacy Windows.
For clean Windows installation, please read the appendix in post #1 of the sticky OpenCore thread.