Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Thanks for this. I was unsuccessful in editing the right plist, so I plugged my harddrive into a windows machine, and used some software to delete the EFI folders in the partition to disable OpenCore.

I'm now trying to install Mojave on a secondary drive so that I can try again, but I'm getting the message that my firmware needs to be updated in order to install. I am already running Mojave on my main drive, and already ran the firmware update to do this. Do I need to run it again?

(EDIT: changed clover to OpenCore)
If with my package, you have to do this to disable SMBIOS spoofing in order to install Mojave / Catalina.

That firmware update is not for cMP.
 
Full HWAccel achieved now!
View attachment 892675

Everything are covered in the OpenCore threads. The step by step tutorial is at here, but I strongly recommend you go through the whole thread before you do anything.


The same method works in both Mojave and Catalina. HOWEVER, for dual processor cMP user, please stick with Mojave at this moment. (Update: please stick to Mojave for ALL who want HWAccel. CMMChris advised Apple removed HEVC HWAccel for all Polaris GPU in the latest Catalina beta. Which means you may not upgrade the OS to get any security fix, unless this is an error in beta. Stay with Mojave, get HWAccel, and keep your OS up to date seems will be a better choice at this moment)
View attachment 897287

Sidecar (and AirPlay Display) should also work, but I have no iPad to test it yet. The latest config.plist in post #594 and #1314 will now keep the cMP ident as 5,1. Therefore, will NOT activate Sidecar by default now.

------ The procedure below is depreciated, just keep in this post as a record (but I will still maintain the FAQ section to keep that up to date. Please read through the FAQ before you ask anything. Any question that already covered in FAQ won't be answered by me.). For those who don't need HEVC hardware encode, and prefer not to install OpenCore. You may still follow the procedure below to activate HWAccel ------

10.14.5 is now official. And I can confirm that AMD card users (Polaris or above) can enjoy H264 hardware encode / H264 hardware decode / and HEVC hardware decode.
View attachment 836830

The procedure is as follow: (please read through the entire Q&A section BEFORE you do anything. You should know how to recover, or may need to use alternate procedure, etc)

1) Keep SIP disabled

2) Download Lilu.kext

3) Download WhateverGreen.kext

4) open Lilu.kext (right click -> show package contents)

5) enter Contents

6) create folder "Plugins" (N.B. This folder is INSIDE Contents, please do NOT miss step 5)
View attachment 836833

7) Copy the WhateverGreen.kext into Plugins

8) Copy the whole modded Lilu kext to /Library⁩/Extensions/

9) Open terminal

10) Enter
Code:
sudo chmod -R 755 /Library/Extensions/Lilu.kext

11) Enter
Code:
sudo chown -R root:wheel /Library/Extensions/Lilu.kext

12) Enter
Code:
sudo touch /Library/Extensions

13) Enter
Code:
sudo kextcache -update-volume /
(you may get some strange return with this command, don't worry about it)

14) Enter
Code:
sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"
For Catalina, you may need to enter the no compat check boot argument as well, otherwise, you may stuck at the no boot situation until you fix the boot argument in recovery partition.

15) Reboot


FAQ, please read through this section BEFORE you ask. I won’t answer anything that already covered in this section.

Q1: Is this safe?
A: Tested since 10.14.5 beta 4, so far, no system damaged by this mod. (Update: OpenCore may write something into the cMP's firmware. So, if you want to stay safe, avoid OpenCore. And only use Lilu + WhareverGreen, or hex edit method)

Q2: Is there any down side?
A: Yes, for Lilu or hex edit method, iTunes, TV+, and Safari Netflix DRM streaming may not work, but fully download DRM movie should not be affected. And Netflix on Chromium base browsers (Chrome, Brave, Edge, etc) are OK.

DRM streaming can work flawlessly with the OpenCore method.

Q3: Any other known issue?
A: Photos app crash if HDMIAudio.kext is also installed. Besides, few more users reported system freeze. It seems only Polaris GPU is affected e.g. RX580. So far, all freeze only occur in Apple apps. e.g. FCPX, Photos, Compressor, etc. 3rd party apps such as PP, DV, VideoProc are not affected. However, Polaris GPU hwaccel seems perfectly stable in 10.14.6 beta by hex editing the AppleGVA file. Beside, Adobe Media Encoder seems will cause the video engine stall. Not system freeze / crash, but the video engine simply like stop working, perform extremely bad. Normal performance can only recover by reboot. (Update: 10.14.6 official release seems fixed most of these issue. At least, I have no way to reproduce any freeze with my RX580)

Q4: If my system crash after the mod, how to fix it?
A: For Lilu / OpenCore 0.5.5 method, NVRAM reset will remove the boot argument, and disable the kexts / OpenCore. So, will effective revert your system back to the original state. Once your system boot again, you can remove the kext / OpenCore.

For Hex edit method, I ran lots of tests, no way to crash the system. But if there is any instability, please restore the original file from your backup.

For OpenCore 0.5.6, you have to re-mount the EFI partition -> remove the BOOT and OC folder -> reset NVRAM

Q5: What's the benefit?
A: Able to play some very demanding HEVC video (e.g. this one)
https://4kmedia.org/sony-swordsmith-hdr-uhd-4k-demo/

This is how my cMP can play this video now. Smooth playback with very low CPU usage (please use a browser that support VP9 to watch all the following Youtube videos in 4k, otherwise, you may not able to read the details)

Able to edit H264 directly smoothly, no need to transcode to ProRes anymore, greatly reduce the storage speed and capacity requirement. Most likely can improve productivity as well

Able to edit HEVC directly smoothly, no need to transcode to ProRes anymore, greatly reduce the storage speed and capacity requirement. Most likely can improve productivity as well

Can greatly improve H264 export speed with low CPU usage (depends on your CPU / GPU spec)

Able to record the screen at 4k smoothly. As you can see from the above link. My cMP now can do those stuff and still record the screen smoothly at the same time.

Able to play VP9 video smoothly. My cMP now can play this 8K 24FPS youtube video with zero frame drop. (VP9 hardware decode is NOT supported at all in macOS)

Q6: Can this work in 10.14.4 or before?
A: One user reported that latest 10.13.6 with Vega also work with Lilu mehtod. But RX580 will cause GPURestart fault, which freeze the display and make the OS unusable. (update: users reported hardware decode works, but H264 hardware encode will cause the crash)

Q7: Can this work in 10.15?
A: Not as good as 10.14. Only Lilu method, or OpenCore method work. Also, in 10.15.2, Polaris (e.g. RX580) HEVC HWAccel support is removed by Apple (WhateverGreen should fix this Polaris supportability issue. But I haven’t test it personally)

Q8: Can this work for Nvidia GPU?
A: NO

Q9: Can this work for flashed 7950 etc?
A: I don't know. Please test it for me. (Update: The answer is NO, thanks bazza5938 to perform the test)

Q10: Which software can benefit from this mod?
A: This will provide hardware acceleration at system level. So far, all my tested software works (e.g. FCPX, iMovie, Handbrake, Compressor, VideoProc, DVDFab, DV, AE, PP, FFMpeg, QuickTime Player, VLC, IINA......)

Q11: If I do a NVRAM reset due to other reason, how to regain these functions?
A: For Lilu method, repeat step 14 and reboot.

Hex edit method / OpenCore 0.5.6 (post #1314) is not affected.

For OpenCore 0.5.5 (in post #594), depends on your setup, you may need to re-bless to boot via OpenCore again.

Q12: What's the recommended GPU?
A: RX560, RX580, Vega 56, Vega 64, Vega FE. As long as that card can work on cMP, brand / model doesn’t really matter (Update: for this particular purpose, Vega is definitely better than Polaris card. There is zero crash / freeze report from Vega users yet).

Q13: Why not recommend the Radeon VII or RX570, etc.
A: AFAIK, all Polaris, Vega, Navi GPU works, I just not sure how mature the overall support is. (Update: I upgraded my GPU to Radeon VII, perfectly stable, and hardware encoding is about 100% faster than RX580. Navi's HWAccel also confirmed can be activated.)

Q14: Is this QuickSync?
A: NO, QuickSync is the hardware acceleration for Intel iGPU, not the generic term for GPU video hardware acceleration. AMD GPU use UVD (Unified Video Decoder) for decoding, and VCE (Video Coding Engine) for encoding. All this will be controlled by VideoToolBox automatically in macOS, virtually transparent to users. It's the same concept as QuickSync, but not QuickSync.

Q15: I can see that my GPU is working in Compressor before this mod (on a cMP). Is that mean I already have hardware acceleration?
A: NO, we are talking about H264 / HEVC hardware acceleration here. Not the general compute hardware acceleration. They are completely different.

Q16: How's the quality of the hardware encoded video?
A: Not as good as software encoder in general. But if at high bitrate, the difference isn't that noticeable.

Q17: When will we able to get HEVC encoding as well?
A: I don't know. But you can always boot to Windows and use HEVC hardware encode. (Update: FULL HWAccel including HEVC encoding can also be achieved by using OpenCore. Not sure how safe, but it works stably on my cMP)

Q18: How much improvement can I expect?
A: Well, depends on usage. But a quick iMovie 4K H264 export test shows a Vega 64 can reduce the export time from 6:19 to 1:25, which means reduced the export time by ~77% (on a dual X5680 cMP).

Q19: Why VideoProc shows no HEVC decode after the mod?
A: I don't know why, but this is normal in this case. My recommendation is to download demo HEVC video from the above link, and play it via QuickTime (or simply via Finder preview). As long as the CPU usage only stay around 20% (but not 800%), that means HEVC decoding is working properly.

For those who use OpenCore method, you should able to see HEVC HWAccel avail. If not there, please click the little reload icon.

Q20: Should I install the newer version of Lilu and WhateverGreen?
A: NO. Despite the newer version can work, but provide no extra function in this case, and I have no idea if the newer one has poorer stability. If I found a better way / kext to use. I will update the post accordingly. (Update: For Catalina, please install Lilu 1.4.0 and WhateverGreen 1.3.5. And so far, all newer Lilu and WEG only provide better result due to bug fix. Users should be OK to install the latest version)

Q21: I experienced system freeze, Console log shows "GPU Restart" event, what should I do?
A: PRAM reset will bring your system back to normal. If you are with Polaris GPU (RX560, RX570, RX580, etc), it seems some people are affected by this bug. What I found is an alternate method by directly hex edit the AppleGVA file seems more stable for these GPUs. Initial test shows very safe to do so, even I completely destroy the AppleGVA file, the OS can still boot to desktop. If you prefer to go this route, please make sure you know how to restore the file (or even completely recover from an unbootable OS). The info is at post #205. (update: 10.14.6 shows extremely good stability, highly recommended for RX580 users)

Q22: How do I know if hardware acceleration is really working?
A: My suggestion is by using Terminal. Detail info in post #273. You may also use OpenGL Driver Monitor to observe the UVD / VCE activities (link).

Q23: Can I use this mod with MVC flashed RX580?
A: I can't test it, and no report yet, but should work. Since this mod won't touch the ROM, safe to try anyway.

Q24: Is it possible to turn OFF hwaccel without reboot. So that I can enjoy DRM streaming anytime?
A: Only the alternate method allow ON/OFF on the fly. If you don't want to use terminal / Finder to do that every time, you can make two simple apps to do that, procedures at here. (Update: My OpenCore package should allow you to play DRM streaming video by default)

Q25: Does background rendering still works in FCPX?
A: Background rendering still works for both methods. This is completely independent to hwaccel. I turned that off in the above demo is just to illustrate the real time timeline editing performance. Not because of it can't work.

Q26: I tried the hex edit method many many times, it doesn't work, but I am sure I did everything right. What should I do?
A: May be you should try open a new user profile, and see if it help (reference link)

Q27: Why the "Graphics" in VideoProc HWAccel page shows N/A?
A: No idea, but it's just a cosmetic error in this case. (Update: It seems VideoProc looking for the key word "AMD". e.g. If the card ident as AMD Radeon VII, VideoProc can show it properly. But if the card ident as Radeon VII, then VideoProc can't show its name)

Q28: Why VideoProc shows that I am use "Intel "HWAccel when converting videos?
A: Also no idea, but again, it's just a cosmetic error in this case.

Q29: Why VideoProc shows nothing activated but everything seems working as expected?
A: As long as you can see this tick, which mean HWAccel is activated. From my observation, this tick always change automatically.
View attachment 891504

For the Hardware Info Detected page, please click the little reload icon in order to let VideoProc to show you the latest status.
View attachment 891505
Will this work on a Mac Pro 6,1?
 
Will this work on a Mac Pro 6,1?
No.

Requirement for hardware acceleration is an AMD GPU from RX 460/480 or newer. MP6,1 GPUs don't have the ASIC that supports VideoToolBox GPU hardware acceleration, MP6,1 GPUs are equivalent to:

D300 = HD 7870/R9 270
D500 = HD 7950/R9 280
D700 = HD 7970/R9 280X

@h9826790 since this question is common, you should add it to the first post.
 
No.

Requirement for hardware acceleration is an AMD GPU from RX 460/480 or newer. MP6,1 GPUs don't have the ASIC that supports VideoToolBox GPU hardware acceleration, MP6,1 GPUs are equivalent to:

D300 = HD 7870/R9 270
D500 = HD 7950/R9 280
D700 = HD 7970/R9 280X

@h9826790 since this question is common, you should add it to the first post.
Thanks. Very sad that this Mac that was supposed to be powerful have this limit.
 
If with my package, you have to do this to disable SMBIOS spoofing in order to install Mojave / Catalina.

That firmware update is not for cMP.

Okay, so. Firstly, thanks for all your advice, and for compiling this package.

I wanna pop my journey into a single message for anyone else with a similar issue, and because I think the replies here have been a little off-axis, although inadvertently helpful:

I installed the OpenCore package a few days ago on an SSD running Mojave in a Sonnet Tempo PCIE drive. I have no interest in upgrading to Catalina, but wanted a boot picker to work with my Radeon vii for easy switching between OS into Windows on another drive, and for HW Accel.

I thought I had another copy of Mojave OS installed on another drive at the time of installing, but turned out I didn't. The OpenCore package ran just great, and I even got the boot picker, but trying to boot into my Mojave drive just gave me a grey screen with the Apple logo and nothing else. The tips from the initial post (reset NVRAM, and try resetting NVRAM with the OS HD pulled) didn't resolve the issue, and I was completely prevented from booting into my OS.

I figured I'd boot up my secondary drive running Mojave, but at that point realised that it didn't exist, and I must have formatted it some time ago and just forgotten about it.

Without a secondary drive running Mojave without OpenCore, I was stuck with an inoperable computer as nothing was allowing me to boot into OSX. So, I took out my Mojave SSD, plugged it into a windows machine I have using an external adapter, and deleted OpenCore from the EFI partition using some AFPS filebrowser I found online. This got rid of the boot picker, and let me log back in.

I decided to install OSX on a secondary drive and try running OpenCore from there to see what would happen, in light of a comment from H9826790 about the Sonnet Tempo not playing nicely with OpenCore. When I tried to install the OS onto this second drive, I got the same 'you must update your firmware' message that I got when I initially upgraded to Mojave over a year ago. I was hesitant to do this firmware update (shut down, turn back on holding the power button until blinking light and long tone) as I'd already done it, but I gave it a go and...lo and behold, my OSX installer worked again! I installed Mojave onto my secondary drive, booted in, ran your OpenCore script, Turned OFF SMBIOS spoofing, turned ON the VMM Flag, and...wonder of wonders...I now have the boot picker and the ability to upgrade to Catalina on this second drive.

In order to boot back into my original (primary) hard drive, I have to choose it as the startup disk from the new drive, then reboot whilst doing a PRAM reset.

It's clunky, but for the moment it works.

My next steps:

I have an NVME drive and PCIE adapter arriving this weekend. I'll copy my current primary OS onto that drive, and hopefully be able to install OpenCore.
If that's successful, I'll wipe my current primary drive in the Sonnet Tempo and put my windows install there.
It seems like the Sonnet Tempo might be what causes my boot fail?

So yeah, hope that's helpful. Don't be running this Open Core package if you're using a Sonnet Tempo. And if you do, make sure you check your secondary drive to be sure there's an OS installed first. 🙃
 
Okay, so. Firstly, thanks for all your advice, and for compiling this package.

I wanna pop my journey into a single message for anyone else with a similar issue, and because I think the replies here have been a little off-axis, although inadvertently helpful:

I installed the OpenCore package a few days ago on an SSD running Mojave in a Sonnet Tempo PCIE drive. I have no interest in upgrading to Catalina, but wanted a boot picker to work with my Radeon vii for easy switching between OS into Windows on another drive, and for HW Accel.

I thought I had another copy of Mojave OS installed on another drive at the time of installing, but turned out I didn't. The OpenCore package ran just great, and I even got the boot picker, but trying to boot into my Mojave drive just gave me a grey screen with the Apple logo and nothing else. The tips from the initial post (reset NVRAM, and try resetting NVRAM with the OS HD pulled) didn't resolve the issue, and I was completely prevented from booting into my OS.

I figured I'd boot up my secondary drive running Mojave, but at that point realised that it didn't exist, and I must have formatted it some time ago and just forgotten about it.

Without a secondary drive running Mojave without OpenCore, I was stuck with an inoperable computer as nothing was allowing me to boot into OSX. So, I took out my Mojave SSD, plugged it into a windows machine I have using an external adapter, and deleted OpenCore from the EFI partition using some AFPS filebrowser I found online. This got rid of the boot picker, and let me log back in.

I decided to install OSX on a secondary drive and try running OpenCore from there to see what would happen, in light of a comment from H9826790 about the Sonnet Tempo not playing nicely with OpenCore. When I tried to install the OS onto this second drive, I got the same 'you must update your firmware' message that I got when I initially upgraded to Mojave over a year ago. I was hesitant to do this firmware update (shut down, turn back on holding the power button until blinking light and long tone) as I'd already done it, but I gave it a go and...lo and behold, my OSX installer worked again! I installed Mojave onto my secondary drive, booted in, ran your OpenCore script, Turned OFF SMBIOS spoofing, turned ON the VMM Flag, and...wonder of wonders...I now have the boot picker and the ability to upgrade to Catalina on this second drive.

In order to boot back into my original (primary) hard drive, I have to choose it as the startup disk from the new drive, then reboot whilst doing a PRAM reset.

It's clunky, but for the moment it works.

My next steps:

I have an NVME drive and PCIE adapter arriving this weekend. I'll copy my current primary OS onto that drive, and hopefully be able to install OpenCore.
If that's successful, I'll wipe my current primary drive in the Sonnet Tempo and put my windows install there.
It seems like the Sonnet Tempo might be what causes my boot fail?

So yeah, hope that's helpful. Don't be running this Open Core package if you're using a Sonnet Tempo. And if you do, make sure you check your secondary drive to be sure there's an OS installed first. 🙃
OpenCore is fine with TempoSSD, it’s the native Apple boot manager may not work when there is ANY bootable drive on the TempoSSD.
 
Just tried a new merged version of 0.5.7 with the Bootpicker GUI, Titan Ridge TB3 and Hardware Accelleration for h264/h265... and EVERYTHING WORKS (well I haven't flashed the Titan Ridge card yet, but supposedly it'll work)!

I saw a boot selection screen for the first time using my Radeon VIIs! This is terrific.

I can now add another NVME SSD for a Windows install (and get the benefit of the dual Radeon VIIs for some gaming grunt)! Thank you Martin, and this whole wonderful community for making this stuff possible for dumb dumbs like me.
 
Just tried a new merged version of 0.5.7 with the Bootpicker GUI, Titan Ridge TB3 and Hardware Accelleration for h264/h265... and EVERYTHING WORKS (well I haven't flashed the Titan Ridge card yet, but supposedly it'll work)!

I saw a boot selection screen for the first time using my Radeon VIIs! This is terrific.

I can now add another NVME SSD for a Windows install (and get the benefit of the dual Radeon VIIs for some gaming grunt)! Thank you Martin, and this whole wonderful community for making this stuff possible for dumb dumbs like me.
You are welcome, anyway, Radeon VII does not support Crossfire. Even we can still activate it, but it seems can only work properly in limited games.
 
You are welcome, anyway, Radeon VII does not support Crossfire. Even we can still activate it, but it seems can only work properly in limited games.

That's a shame. Still, simply being able to access Windows again, opens up a lot of entertainment options (much needed in this COVID isolation situation). Which games do you know of that will support the dual Radeon VIIs?
 
That's a shame. Still, simply being able to access Windows again, opens up a lot of entertainment options (much needed in this COVID isolation situation). Which games do you know of that will support the dual Radeon VIIs?
Basically only works in DirectX12. So something like Gears of War 5, or Shadow of Tomb Raider should able to benefit from dual Radeon VII.
 
  • Like
Reactions: eksu and pierrox
Basically only works in DirectX12. So something like Gears of War 5, or Shadow of Tomb Raider should able to benefit from dual Radeon VII.

Good to know, thanks! I've actually just finished Tomb Raider and Rise of the Tomb Raider on Mac (two of the few good games actually available on OSX) and Shadow of the Tomb Raider is literally next on the list! So I'll try it out on Windows and see how things compare.

To be fair, I've been playing the first two games basically maxed out (everything except Anti-Aliasing) at 4k using a single Radeon VII on OSX, and they've been shockingly smooth (given it's a 10 year old computer).
 
Is there no Reset NVRAM option in this solution?
I can put it back, but due to the native Apple boot manager has no such option, and no native icon for that one, so I removed it for those who want the boot picker as close to the native one as possible.

I'd vote for reset too, I find it pretty useful to have that just a click away.
Did you publish a final version of your 0.5.7 package @h9826790?
 
I'd vote for reset too, I find it pretty useful to have that just a click away.
Did you publish a final version of your 0.5.7 package @h9826790?
Which icon you want for that? A or B

A)
func_resetnvram.png

B)
os_unknown.png
 
  • Like
Reactions: eksu and pierrox
For Catalina installation, you have to turn on the VMM flag and turn off SMBIOS spoofing.

Also, please make sure you don’t have another copy of Lilu or WEG installed.

Option boot often won’t work with TempoSSD card

I have Mojave installed on an NMVE, and Catalina installed on a separate NVME from a clean install on a MBP and the no_compat_check boot-args. Mojave boots fine from OC (0.5.7), but Catalina hangs at the Apple load screen with no boot progress bar. Could Lilu+Innie installed on Catalina cause this hanged boot phenomena from OC?
 
I have Mojave installed on an NMVE, and Catalina installed on a separate NVME from a clean install on a MBP and the no_compat_check boot-args. Mojave boots fine from OC (0.5.7), but Catalina hangs at the Apple load screen with no boot progress bar. Could Lilu+Innie installed on Catalina cause this hanged boot phenomena from OC?
Yes, please remove them, my OC package already has Lilu included.
 
Yes, please remove them, my OC package already has Lilu included.

I'd been really struggling w/this one. I'd gotten OC installed on a USB EFI, and Mojave booted fine, but Catalina would hang. This particular system is a bit of a PIA because it is a headless/inputless media server that I admin through Remote Desktop, so in order to disable SIP or reset NVRAM I have to pull extended USB & HDMI cables for physical inputs and video.

Well I did that this AM, removed Lilu/Innie from the Catalina /Library/Extensions and rebuilt the kextcache. Reformatted the USB and put OC (0.5.7) on its EFI and blessed it using the tool. On reboot, both Mojave & Catalina properly loaded from the picker. So I dropped the picker timeout to 5 sec., and set Catalina as the default. Rebooted a couple of times to make sure it acted as intended, and now its good to go. Instead of Innie in the Lilu.kext, I set the NVME drives as internal w/the Device Properties setting in OC. I also created a secondary config.plist to have VMM flag ready for updates so now I just have to rename the plists as necessary and reboot in order to apply Catalina updates.

Thanks to all the members of this group for helping me work through these issues.

There is one recurring issue (unrelated to OC) that I have. I have a persistent share set on my media server to a folder on my Workstation so I can move music and video. Often if I have to reboot the workstation and break the share (whether or not I drop the share in the media server beforehand) I will get an error on the media server that the share cannot be found. The only way I have found to fix it is reboot the media server. Is there a way to fix this short of rebooting?
 
  • Like
Reactions: zoltm and h9826790
Firstly, thank you to h9826790 for all of your hard work on this thread. I've semi-successfully installed your latest oc package in my 5,1 cmp. Boot screen, bootpicker, innie and hardware h265 acceleration and Radeonboost are all present and working.

However, when I boot the machine things often go a bit wrong. I choose the OS drive in the boot picker (or allow it to be chosen by default) and the progress bar moves about 10% of the way but then the screen turns black for about 30 seconds, the startup chime starts and the boot picker reappears. (i.e., presumably the machine reboots).

When the default OS is chosen a second time, the machine will display the multi-language, "Your computer restarted because of a problem..." screen and then usually (but not always) boot properly. After logging in to the MacOS desktop, the error dialogue "You shut down your computer because of a problem - click open to reopen apps" appears.

So it seems that the machine fails to boot properly the first time, but then is able to boot the second time. Once booted, the machine is rock solid for days under load.

The problem seems to happen 100% of the time after a cold boot and about 60% of the time after a warm restart. It's driving me crazy because everything else is working so well! Any ideas what might be causing this?

Specs are:
Mac Pro 5,1 (2010)
MacOS Mojave 10.14.6
Dual 3.46 X5690 cpus
96Gb 1333Ghz DDR3
Radeon VII (powered via Pixlas mod) in slot 1
OWC Accelsior 4M2 NVME PCIE card in slot 2 via a PCIE extension cable and populated with:
2Tb Samsung 970 EVO plus boot drive (AFP)
2Tb Samsung 970 EVO plus time machine drive (AFP)
2x 1Tb OWC Aura P12 in RAID 0 (HFS+)
Together with 4x Samsung 860 EVO 4Tb SATA disks in RAID 4
[RAID handled by Softraid 5.8.3]
2x USB 3.2 gen 2 cards in slots 3 and 4
 
  • Like
Reactions: zoltm
Firstly, thank you to h9826790 for all of your hard work on this thread. I've semi-successfully installed your latest oc package in my 5,1 cmp. Boot screen, bootpicker, innie and hardware h265 acceleration and Radeonboost are all present and working.

However, when I boot the machine things often go a bit wrong. I choose the OS drive in the boot picker (or allow it to be chosen by default) and the progress bar moves about 10% of the way but then the screen turns black for about 30 seconds, the startup chime starts and the boot picker reappears. (i.e., presumably the machine reboots).

When the default OS is chosen a second time, the machine will display the multi-language, "Your computer restarted because of a problem..." screen and then usually (but not always) boot properly. After logging in to the MacOS desktop, the error dialogue "You shut down your computer because of a problem - click open to reopen apps" appears.

So it seems that the machine fails to boot properly the first time, but then is able to boot the second time. Once booted, the machine is rock solid for days under load.

The problem seems to happen 100% of the time after a cold boot and about 60% of the time after a warm restart. It's driving me crazy because everything else is working so well! Any ideas what might be causing this?

Specs are:
Mac Pro 5,1 (2010)
MacOS Mojave 10.14.6
Dual 3.46 X5690 cpus
96Gb 1333Ghz DDR3
Radeon VII (powered via Pixlas mod) in slot 1
OWC Accelsior 4M2 NVME PCIE card in slot 2 via a PCIE extension cable and populated with:
2Tb Samsung 970 EVO plus boot drive (AFP)
2Tb Samsung 970 EVO plus time machine drive (AFP)
2x 1Tb OWC Aura P12 in RAID 0 (HFS+)
Together with 4x Samsung 860 EVO 4Tb SATA disks in RAID 4
[RAID handled by Softraid 5.8.3]
2x USB 3.2 gen 2 cards in slots 3 and 4
Remove Lilu in Library/Extensions if any (you should have that installed with innie). Lilu is already included in my package, double Lilu installation can cause issue)
 
Remove Lilu in Library/Extensions if any (you should have that installed with innie). Lilu is already included in my package, double Lilu installation can cause issue)
Thanks for the feedback! To be more clear, I never installed innie separately - I’m just receiving the benefit of NVME drives showing as internal that comes from your oc package.

Unfortunately, there’s no lilu in library/extensions (or, so far as I can tell, anywhere else except the EFI partition on the OS boot disk per your package).
Any other suggestions would be gratefully receivedo- could it possibly be an incompatibility with Softraid?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.