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.
I've followed that method with my supported 2012 Macbook Pro configured APFS RAID 0 with latest Macosx Catalina 10.15.1 release today and its working fine, just need to rename bootcaches near the end to complete installation.
View attachment 873477
Unfortunately, The T2 Security chipset prevents booting from RAID 0 in APFS format for me. I was able to setup Raid 0 in APFS and installed Catalina though. I have 2018 Mac Mini. Is there a solution for me? :(
 
  • Like
Reactions: TimothyR734
Unfortunately, Apple deprecated RAID 0 booting as far back as High Sierra. A number of people have tried to get round this and as far as I know have been largely unsuccessful. One reason provided by Apple engineers is that RAID booting is inherently insecure.
Some non-Apple engineers at carbon copy cloner and softraid tried to figure a workaround but gave up.
I have seen some very obscure methods that some people claim to work but it was too much effort for too little reward in my case.
Good luck.

Unfortunately, The T2 Security chipset prevents booting from RAID 0 in APFS format for me. I was able to setup Raid 0 in APFS and installed Catalina though. I have 2018 Mac Mini. Is there a solution for me? :(
 
  • Like
Reactions: TimothyR734
Have not done this for Catalina but this works for Mojave so give it a try. First find the name of your efi partition. In terminal use:

sudo diskutil list

You will be asked for your password then get a full list of all the drives. Find the efi one, for example mine is disk0s1 - yours may be different. Then mount this disk so it appears on your desktop. In terminal use :

sudo diskutil mount disk0s1

You may need to replace my example disk name with yours. After a moment the efi drive should appear on your desktop. You can then use finder to delete the following: apfs.efi, /BOOT/BOOTX64.EFI and startup.nsh.

I have tried this in Catalina and it does bring up the disk onto the desktop. However, I have no files to delete (using APFS ROM) so have not actually deleted anything to see if it works fully. Catalina's system drive is now read only so I do not know if this will effect mounted efi drive. If you find that you are not allowed to delete the files inside the efi drive then try this command first to make the system drive read/write (SIP disabled):

sudo mount -uw /
Thank you, I did it and all is OK now!
 
  • Like
Reactions: TimothyR734
Hi Guys, Can anyone tell me if Sidecar works on my MP 3.1 running Catalina ? I see it in system preferences and I am thinking of getting a 2018 iPad which is 6th generation and Sidecar supported.
 
  • Like
Reactions: TimothyR734
Hi Guys, Can anyone tell me if Sidecar works on my MP 3.1 running Catalina ? I see it in system preferences and I am thinking of getting a 2018 iPad which is 6th generation and Sidecar supported.
Sidecar will only work if you have HEVC encode/decode. Unfortunately the cMP3.1 is unable to do this. Need an upto date Intel CPU with QuickSync or T2 chip. Work is presently being done by members to get a cMP5.1 with appropriate graphics card (like RX580) to have HEVC encoding/decoding but it is proving a challenge. They have a solution but it is undergoing evaluation as we speak. Maybe the cMP3.1 may benefit from this work but at the moment the answer is no for Sidecar.
 
Sidecar will only work if you have HEVC encode/decode. Unfortunately the cMP3.1 is unable to do this. Need an upto date Intel CPU with QuickSync or T2 chip. Work is presently being done by members to get a cMP5.1 with appropriate graphics card (like RX580) to have HEVC encoding/decoding but it is proving a challenge. They have a solution but it is undergoing evaluation as we speak. Maybe the cMP3.1 may benefit from this work but at the moment the answer is no for Sidecar.

I am using a GTX 680 2GB card
 
  • Like
Reactions: TimothyR734
To those who use iMovie and already noticed that recently apple switched to a Metal version, the majority of weblink you can find on internet (even claiming to redirect to an older app version) will point instead to this version: https://apps.apple.com/us/app/imovie/id408981434?mt=8

That is the 10.1.13 and if read the AppStore description it requires 10.14.6 or later.

So here is a direct link to an older version iMovie10112.pkg that I've tested and it works on 10.14.3 (the latest stock Mojave OpenGL with all the other stock frameworks), on 10.15.0 (full "non-metal patched" through Mojave frameworks thanks to @ASentientBot) and even on 10.13.6 (after moving the iMovie.app there).

edit:
Since this iMovie.app (version 10.1.12) works correctly also on HighSierra, it should not present any Metal glitches on Catalina, but in case you may consider to replace the AppleGVA.framework in /System/Library/PrivateFrameworks , this during Mojave fixed framerate dropping in some h264 / 1080p videos.
 

Attachments

  • Screenshot 2019-11-01 at 12.23.20.png
    Screenshot 2019-11-01 at 12.23.20.png
    930.6 KB · Views: 283
Last edited:
Unfortunately, Apple deprecated RAID 0 booting as far back as High Sierra. A number of people have tried to get round this and as far as I know have been largely unsuccessful. One reason provided by Apple engineers is that RAID booting is inherently insecure.
Some non-Apple engineers at carbon copy cloner and softraid tried to figure a workaround but gave up.
I have seen some very obscure methods that some people claim to work but it was too much effort for too little reward in my case.
Good luck.

Raid 0 works only through Terminal, through command lines, and works very well in HFS, in High Sierra you can later convert to APFS (but without updates). On case Mojave/Catalina works (APFS) with updates and it's not as difficult as you are. You mentioned, you just need to rename bootcaches.plist to bootcaches.bak, there's nothing else here.
 
Last edited:
  • Like
Reactions: TimothyR734
On this thread: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-27924041

Using the OpenCore bootloader and its config file with some kind of "on-the-fly EFI patches", seems unlocked HEVC encoding/decoding on target Metal GPUs (and similar method also should allow "Software Update" on Catalina unsupported machines).
Yes, but as far as I know the Kepler core does not contain any HEVC hardware so it will not benefit from any EFI patches etc. It is a card from 2012 so has done very well in its time but nVidia themselves say it is unable to encode/decode HEVC.
 
Yes, but as far as I know the Kepler core does not contain any HEVC hardware so it will not benefit from any EFI patches etc. It is a card from 2012 so has done very well in its time but nVidia themselves say it is unable to encode/decode HEVC.

I read from that thread that spoofed the MacPro as an iMac (with HEVC support GPU), I thought any Metal GPU were capable of HEVC, however just to clarify the credit for that discovery belongs to this post: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-27921590
 
  • Like
Reactions: TimothyR734
Which of these is the proper installation method for 10.15.1?
  1. Make a new USB patcher and then reinstall over current OS. OR
  2. Install from Software update and then apply the post-install patches?
 
Crashing a lot on 10.15.1 with this:

Process: UserNotificationCenter [9359]
Path: /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter
Identifier: UserNotificationCenter
Version: ???
Build Info: UserNotificationCenter-51000000000000~12
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: UserNotificationCenter [9359]
User ID: 501

Date/Time: 2019-11-01 06:27:33.135 -0700
OS Version: Mac OS X 10.15.1 (19B88)
Report Version: 12


Time Awake Since Boot: 110000 seconds

System Integrity Protection: disabled

Crashed Thread: Unknown

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: DYLD, [0x4] Symbol missing

Dyld Error Message:
symbol '_OBJC_CLASS_$_SLSecureCursorAssertion' not found, expected in '/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight', needed by '/System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter'

Binary images description not available
 
I read from that thread that spoofed the MacPro as an iMac (with HEVC support GPU), I thought any Metal GPU were capable of HEVC, however just to clarify the credit for that discovery belongs to this post: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-27921590
Yes this is looking promising if you have a graphics card that supports HEVC such as the AMD RX580. Cards like the GTX680 are metal enabled but lack the physical hardware for HEVC. So not all metal cards are capable of HEVC.
Here is a link that helps. Basically none of the Kepler series can do HEVC.
 
Hello!

Just finished update from 10.15.0 to 10.15.1 with latest @dosdude1 patcher v 1.2.1, downloaded yesterday and Catalina downloaded within the patcher, also yesterday. My Mac still says he's enrolled in the Apple Beta Software Programme...
Is this normal?
Will this cause me problems in the future?

Thanks!
 

Attachments

  • Screenshot 2019-11-01 at 14.20.26.png
    Screenshot 2019-11-01 at 14.20.26.png
    148.4 KB · Views: 208
  • Like
Reactions: MacClueless
Which of these is the proper installation method for 10.15.1?
  1. Make a new USB patcher and then reinstall over current OS. OR
  2. Install from Software update and then apply the post-install patches?
Number 1. Software update in preferences not working yet.
You'd could also try "Install to this Machine" but having a USB patcher is useful for emergencies!
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.