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 am using a Mac Pro 5,1 with updated BLE/WiFi and video.
I only use boot-args -no_compat_check
SIP is enabled in recovery and shows up as enabled under Mojave. It used to shows up as enabled.
In 10.14.6 I get:
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
I reinstalled from DosDude patched stick to make sure that APFS and Patches are not enabled.

Does anybody else see the same?
 
@dosdude1 , @0403979 and/or whoever would know. I have a development question. I'm aware of the lack of metal-enabled drivers for AMD HD 5xxx and 6xxx series that causes all of us with late 2011 macbooks to have to sacrifice GPU acceleration in order to install Catalina. What I don't understand is the reason. Is it because it's a complex task and there hasn't been enough developer bandwith to implement it? Or is there a hardware limitation that makes it impossible to create such drivers? I ask because I think there are older/weaker GPUs with working unofficial drivers.
 
Last edited:
  • Like
Reactions: K two
Came here JUST to report this exact same issue. Fairly recent development:

MacBook Pro 5.1, running 10.15.5 (19F101). Chrome 85.0.4183.83.

Upon an initial boot, clicking Chrome will cause it to look like it's going to open for about 15-20 seconds, and then quit unexpectedly. Subsequent opening of the program works, but is slow.

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1

Full log here: https://pastebin.com/raw/v64vp5W7


or the one remaining search machine with the same symptoms would have given you even a wider variety of links to get help from.

reinstalling the apps or code sign seems to be a solution
 
MacBook Pro 5.1, running 10.15.5 (19F101). I tried installing and using the Zoom app, but applications won't show up under the proper Camera and Microphone sections to use them.

After extensive searching, apparently SIP MUST be enabled in order to work properly. Per:

I attempted to boot up in Recovery Mode and then use Terminal to 'csrutil enable' SIP mode, but it came back with an error saying that it's current state is unknown and can only do that from Recovery (which I was already under).

I now have to somehow turn SIP back on in order to urgently use Zoom. How am I able to do this?
 
Attempting to install Catalina on 5,1 MacPro, currently running latest Mojave, no issues, other than the NVIDIA graphics card (Quadro K5000) insisting on a CUDA driver update that can never happen. Running the Catalina Patcher, I'm encountering "Error Saving BaseSystem Image"...."ensure there is at least 10GB of free space on your startup disk...."

Have tried this on a few computers now, with multiple external drives (USB, Conventional, SSD - all well in excess if that 10GB free space, all empty, properly formatted), as well as the method of direct install - always the same result. Viewing the error log shows that hdiutil: couldn't unmount "diskXX" - Resource Busy, that disk being the Catalina Base Image. 🤫

O.K. - got it working. I won't claim to know why, but running the entire process in Safe Mode allowed the complaint-free creation of the USB installer.

Everything seems to work very well. One minor thing - the DVD tray will occasionally eject itself on bootup. Seems to do it more often if the power has been off on the machine for an extended period of time. It does not do it on restarts, just power off to on bootups.

The major problem - the machine no longer comes out of sleep mode, or rather, it refuses to send a video signal (I'd imagine it is actually coming out of sleep). Also IF I power off the monitor, and then power back up, no video signal. This issue must be conquered or else I'll be forced back into Mojave.

Any suggestions???
 
@dosdude1 Can anyone help? I have a early 2009 MacBook Pro 17” the MacBook5,2. Upgraded to 8Gb RAM and 500Gb SSD. I followed all of the instructions for the patcher and loaded from the drive and begin the install and then about 15 minutes into the install, it said that it could not be installed and gave me the option to restart and when I clicked restart it booted to a gray screen with a circle in a line through it. I have tried using all of the different command key presses and none of them are yielding any results. The highest version of OS I had before was v10.11.6... if I have to go back to the old operating system that’s fine but I really would like to be able to upgrade to Catalina (or at least Mojave) since I can’t update any of my applications otherwise, but I have 10 years worth of irreplaceable files and photos on the drive that I desperately need to make sure I don’t lose. I just saw something about APFS to install for High Sierra or something, but I went straight from El Capitan to Mojave. Please help. My back up apparently hasn’t been backing up for several months so I feel like an idiot. Thanks 🙏🏼
 
Last edited:
Hi!
I'm currently running High Sierra on a 27" iMac (Late 2009). I use this iMac as an external monitor fairly frequently with a Mini DisplayPort cable, and I'm hoping to upgrade to Catalina (unsupported officially) using the Catalina Patch for unsupported devices.

I've seen mixed results posted about this, so I wanted to ask here -- has anyone gotten Target Display mode / external monitor mode working successfully with an iMac (2009) using Mini DisplayPort and Patched Catalina? I've heard that Thunderbolt 2 works on Catalina on 2011-2012 devices, but what about Mini DisplayPort with iMacs from 2009?
 
I can't get built in audio operating. All that shows is "Digital Out" and "iMac/Display Port". Any ideas?

Details: iMac 27" Mid 2011, 3.4 GHz Quad-Core i7, GeForce GTX 765M flashed with Nick(D)vB. Original WiFi/BT chip, may upgrade eventually. Upgraded to 10.15.6 using the latest DosDude1's Catalina patcher after earlier attempt with 10.15.4 a month or two back.
Attempted re-running patches including Legacy Audio Patch - re-checked after reboot, unchecked Legacy Audio Patch -re-checked after reboot, re-checked after reboot.
Plenty of NVRAM/PRAM resets already done.
Booting into El Capitan off of a boot drive also shows the same outputs as on Catalina.

Boot chime is loud and clear, and sound works perfectly in BootCamp/Windows 10. Sound In works ok as well, just the sound out doesn't allow the proper choices.
Unfortunately I don't quite understand the details of how the audio patching is supposed to operate so I don't know where to begin with troubleshooting besides what I've mentioned above.
 

Attachments

  • Screen Shot 2020-08-31 at 6.41.58 PM.png
    Screen Shot 2020-08-31 at 6.41.58 PM.png
    829.6 KB · Views: 286
@dosdude1 Can anyone help? I have a early 2009 MacBook Pro 17” the MacBook5,2. Upgraded to 8Gb RAM and 500Gb SSD. I followed all of the instructions for the patcher and loaded from the drive and begin the install and then about 15 minutes into the install, it said that it could not be installed and gave me the option to restart and when I clicked restart it booted to a gray screen with a circle in a line through it. I have tried using all of the different command key presses and none of them are yielding any results. The highest version of OS I had before was v10.11.6... if I have to go back to the old operating system that’s fine but I really would like to be able to upgrade to Catalina (or at least Mojave) since I can’t update any of my applications otherwise, but I have 10 years worth of irreplaceable files and photos on the drive that I desperately need to make sure I don’t lose. I just saw something about APFS to install for High Sierra or something, but I went straight from El Capitan to Mojave. Please help. My back up apparently hasn’t been backing up for several months so I feel like an idiot. Thanks 🙏🏼
To save all your files (which you should do, before doing anything more with the operating system), try booting your MacBook from a Linux (like Ubuntu or so) live boot disk, either a DVD or USB flash drive.
https://linuxnewbieguide.org/how-to-mount-macos-apfs-disk-volumes-in-linux/
That article shows how to mount an APFS volume in Linux. If your disk is still as an HFS+ volume, though, then Linux will be able to access it natively.
Hope that helps.
 
@dosdude1 Can anyone help? I have a early 2009 MacBook Pro 17” the MacBook5,2. Upgraded to 8Gb RAM and 500Gb SSD. I followed all of the instructions for the patcher and loaded from the drive and begin the install and then about 15 minutes into the install, it said that it could not be installed and gave me the option to restart and when I clicked restart it booted to a gray screen with a circle in a line through it. I have tried using all of the different command key presses and none of them are yielding any results. The highest version of OS I had before was v10.11.6... if I have to go back to the old operating system that’s fine but I really would like to be able to upgrade to Catalina (or at least Mojave) since I can’t update any of my applications otherwise, but I have 10 years worth of irreplaceable files and photos on the drive that I desperately need to make sure I don’t lose. I just saw something about APFS to install for High Sierra or something, but I went straight from El Capitan to Mojave. Please help. My back up apparently hasn’t been backing up for several months so I feel like an idiot. Thanks 🙏🏼
 
Last edited:
Not sure if this was reported already but I have a weird bug with patched Catalina on my MBP5,5 and MB5,1.

Chrome 84 often won't launch initially after a reboot. Or else it may be launching but won't bounce in the dock so I don't know it's launching.
Came here JUST to report this exact same issue. Fairly recent development:

MacBook Pro 5.1, running 10.15.5 (19F101). Chrome 85.0.4183.83.

Upon an initial boot, clicking Chrome will cause it to look like it's going to open for about 15-20 seconds, and then quit unexpectedly. Subsequent opening of the program works, but is slow.

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1

Full log here: https://pastebin.com/raw/v64vp5W7
The workaround that works for me is to add Chrome to the login items. It loads automatically at launch, but does not crash.

BTW, this exposed another small bug for me. When I added Chrome to the login items, it didn't show up there. I added it again, and it still didn't show up. No error message was generated though. So I logged out and logged back in, and it was there.



or the one remaining search machine with the same symptoms would have given you even a wider variety of links to get help from.

reinstalling the apps or code sign seems to be a solution
Interesting. AFAIK, this only seems to happen on first launch though, but not if the first launch is automatic via the login items. I wonder why that would be.

Is this crash behaviour with unsigned apps new to Catalina, and does it happen in Big Sur? FWIW, it doesn't happen to me on my supported Catalina and Big Sur machines.
 
Last edited:
I have Catalina up and running on my MacBook Pro 5,5. No major issues, it seems to run serviceably well.

However, does anyone have recommendations on background processes to quit etc. to lighten the operating system slightly? El Capitan ran supremely well on this MBP, and I suspect Sierra or High Sierra would run about the same, but Catalina seems to have my CPU idling closer to 30-40% and about 7-10 degrees (celcius) hotter than El Cap.

Otherwise everything seemingly works well. :) Feels like an official install.
 
dada
I have Catalina up and running on my MacBook Pro 5,5. No major issues, it seems to run serviceably well.

However, does anyone have recommendations on background processes to quit etc. to lighten the operating system slightly? El Capitan ran supremely well on this MBP, and I suspect Sierra or High Sierra would run about the same, but Catalina seems to have my CPU idling closer to 30-40% and about 7-10 degrees (celcius) hotter than El Cap.

Otherwise everything seemingly works well. :) Feels like an official install.
this is probably only spotlight doing it‘s initial indexing tour through your hard disk. This may take a while depending on the amount of data you installed back via time machine restore...
 
I have Catalina up and running on my MacBook Pro 5,5. No major issues, it seems to run serviceably well.

However, does anyone have recommendations on background processes to quit etc. to lighten the operating system slightly? El Capitan ran supremely well on this MBP, and I suspect Sierra or High Sierra would run about the same, but Catalina seems to have my CPU idling closer to 30-40% and about 7-10 degrees (celcius) hotter than El Cap.

Otherwise everything seemingly works well. :) Feels like an official install.
this is probably only spotlight doing it‘s initial indexing tour through your hard disk. This may take a while depending on the amount of data you installed back via time machine restore...
Yup.

2.26 GHz MacBookPro5,5:

MBP55-Catalina-CPUusage2.png
 
@dosdude1

Fresh install of Catalina 10.15.6 with your patcher. Performed the post-install patches.
Entire OS works fine but get a black screen on ZOOM when the camera is on.
AMD RADEON HD 6970M 1GB

Running Zoom 5.2.2 (very latest build).
Have tried both of these:
zoomnonmetal.command
zoomnonmetal.sh

neither fixes the zoom camera...

Any ideas? does the patch need updating?

THANK YOU!!
.
 
  • Like
Reactions: Pinarek
Hello @RollingRocker are the colors of your Radeon in Catlina and mojave right? I have the 6770 M Radeon with 512Mb graphics memory and everything else just works with the wrong colors.
How can I solve the problem ? I haven't tested the camera yet.
 
Hello @RollingRocker are the colors of your Radeon in Catlina and mojave right? I have the 6770 M Radeon with 512Mb graphics memory and everything else just works with the wrong colors.
How can I solve the problem ? I haven't tested the camera yet.

All the colors in the OSX are perfect. Everything works EXCEPT the camera in ZOOM.
If I bring up the PHOTO BOOTH, the camera works perfectly.
 
  • Like
Reactions: Pinarek
@RollingRocker .. can you please write how you proceeded with catalina installation
and that the colors are right for you. Should this also work with my Radeon 6770M?

downloaded DOSDUDE1's catalina patcher
ran it
allowed it to download a fresh copy of catalina
plugged in a 16gb flash drive
allowed the patcher to fully patch the OS and build a USB installer
when done-
reboot Mac
hold OPTION
selected the catalina installer
phase 1 of install completes and mac reboots
phase 2 continues ~15 min on my iMac
when it reboots that time, hold R and boot to USB drive again
run POST-INSTALLER patches and took all defaults
this reboots the mac again
boots into catalina and go through the regular catalina install wizard

Zero issues at all in the OS -- EXCEPT I can't use the built-in camera for Zoom - which is a dealbreaker for me because I teach using it...

tried running both zoom patches - neither worked.
 
Hello ... is there a solution for an iMac 12.2 with an AMD Radeon 6.xxx graphics card 512 MB,
for catalina for graphics support?
and Mojave, how does it work there?
Radeon 6xxx not supported in patcher. Read first post
[automerge]1599068975[/automerge]
@dosdude1

Fresh install of Catalina 10.15.6 with your patcher. Performed the post-install patches.
Entire OS works fine but get a black screen on ZOOM when the camera is on.
AMD RADEON HD 6970M 1GB

Running Zoom 5.2.2 (very latest build).
Have tried both of these:
zoomnonmetal.command
zoomnonmetal.sh

neither fixes the zoom camera...

Any ideas? does the patch need updating?

THANK YOU!!
.
Radeon 6xxx not supported in patcher. Read first post
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.