Mac Pro 5.1 should run catalina it out of the box if you set boot-args="-no_compat_check" in Terminal
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.
macOS 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Wonderful! This solves the only issue I had with my MB 5,1. Thank you very much.
Hello there. I have a Macbook4.1. Can I install 10.15? or to which version can I install?
system:
10.7.2 Lion
MacBook4,1
Intel Core 2 Duo
2,4 GHz
2 GB
800 MHz
GMA X3100
MB41.00C1.B00
system:
10.7.2 Lion
MacBook4,1
Intel Core 2 Duo
2,4 GHz
2 GB
800 MHz
GMA X3100
MB41.00C1.B00
macOS Cataina 10.15.2 DP1 runs properly on a non-support hack MacBook Laptop Medion,
as a hackintosh machine. Also transparency and WLAN everything ok.
as a hackintosh machine. Also transparency and WLAN everything ok.
Duet causes USB 3 problems on a Mac Pro 5,1.
After running into issues with enabling SideCar I bought Duet and installed the app on Catalina 10.15.1 with the SideCar patch removed. It turns out not to work properly only showing the Mirrored Display mode.
Worse it disables all USB 3 hubs even if they are connected via USB 2. This happens within a minute of loading the app.
This took a few painful hours of debugging.
--> According to the Duet team, you need to downgrade to Sierra on earlier models. Getting a refund.
After running into issues with enabling SideCar I bought Duet and installed the app on Catalina 10.15.1 with the SideCar patch removed. It turns out not to work properly only showing the Mirrored Display mode.
Worse it disables all USB 3 hubs even if they are connected via USB 2. This happens within a minute of loading the app.
This took a few painful hours of debugging.
--> According to the Duet team, you need to downgrade to Sierra on earlier models. Getting a refund.
Last edited:
Thanks for the mention... I appreciate it.
I don’t believe it would relate to having the AAAmouSSE emulation kext (SSE4.2 patch)
look for a panic dump (not in the system log file)
Had EXACTLY same experience on MP3,1 with nVidia GTX680 and NOT installing the AAAmouSSE emulation kext solved it.
Similar experience with a MacPro 3,1. Upgrading to 10.15.1 worked finally with a USB Drive after failure reboot to 10.15 and not the new system) with "Install to this machine "and also install via a USB key. I didn't had the possibility of unchecking the AAA emulation option (I'm also on Nvidia 680) as post-install options didn't appear after rebooting successfully on 10.15.1. Every thing looks OK so I did not know if missing the post-install options is a problem or not ??????
MBP5,2 updated to release 10.15.1 via USB installer drive. Easy and completely automatic.
Thanks!
The Photos app shows the following wrong behaviour.
(1) when exporting photos in sequence, the chronological order is not preserved. This also happens on a supported machine and is reported elsewhere. Probably a bug, and Apple will likely fix it in a future release.
Workaround is to generate a slide show and export this. Not the same thing of course.
[(2) exporting to the internal SSD fails with one Photos error message per photo. Works with supported machine, as it does when exporting to an external drive (apart from the problem (1)). Will diagnose further.]
Edit: couldn't reproduce the problem (2) anymore - forget it...
Thanks!
The Photos app shows the following wrong behaviour.
(1) when exporting photos in sequence, the chronological order is not preserved. This also happens on a supported machine and is reported elsewhere. Probably a bug, and Apple will likely fix it in a future release.
Workaround is to generate a slide show and export this. Not the same thing of course.
[(2) exporting to the internal SSD fails with one Photos error message per photo. Works with supported machine, as it does when exporting to an external drive (apart from the problem (1)). Will diagnose further.]
Edit: couldn't reproduce the problem (2) anymore - forget it...
Last edited:
MouSSE was designed to be passive, so on systems without AMD cards (and not playing WoW), it should just sit there quietly. However, I've received a few reports of odd behavior that seems to be cleared up by uninstalling MouSSE, so there's apparently an issue that I don't yet understand. For now, if you don't have a Metal AMD card installed, you should not be running MouSSE. This post shows how to uninstall MouSSE. dr.chaos reports that Patch Updater does not notice that MouSSE is gone, so you shouldn't get nagged about reinstalling it. @dosdude1, maybe add a question to the patcher (including "don't install this if you don't have a Metal AMD card"), making MouSSE installation optional?
To date, the problems seem to occur only on systems without Metal AMD cards. If you do have a Metal AMD card installed and are experiencing similar weirdness, please let me know. Thus far, I haven't been able to collect enough data to diagnose this, and staring at the code has gotten me nowhere.
better go back to Final Cut Pro X 10.4.4 which is 100% OpenGL compatible
[automerge]1573650844[/automerge]
better go back to Final Cut Pro X 10.4.4 which is 100% OpenGL compatible
MacOS Catalina 10.15.2 second beta has been released by Apple.
Hi, I’ve been having two issues with Catalina.
1) My E2011 MBP has never been able to wake up from standby (from a dead battery); it just crashes. It worked fine on Mojave patched. How can I diagnose this? Crash reports are sometimes inconsistent.
2) Most recent video patch can’t be installed, it crashes every time I try.
1) My E2011 MBP has never been able to wake up from standby (from a dead battery); it just crashes. It worked fine on Mojave patched. How can I diagnose this? Crash reports are sometimes inconsistent.
2) Most recent video patch can’t be installed, it crashes every time I try.
I have the safe sleep issue too. I spent ages trying to debug this but all I could figure out is that the problem lies in creating the hibernation file, not the wake process. Also pmset doesn't report our Macs as being supported by some hibernation-related stuff.
I assume that it's a matter of compatibility checking/model ID matching with features somewhere, but I couldn't track down where. I'll take another stab at it someday because this bothers me too.
As for the video patch, that sounds like an issue with the patcher rather than the patch.
@early2008macbookpro Man, you made my day week and present time! Thanks alot for helping me out. Great Tip! WOOHOO Works perfectly!
Thanks, you beat me to testing this time
I can't see any evidence of Mojave Patcher and no further Video Patcher update I am assuming that all should be ok i will try it later
You cannot upgrade to any later macOS version (at least if you want to have accelerated graphics, and macOS is unusable without). If you want to upgrade your old Macbook to a modern OS with the latest security fixes, just install Windows 10 or Linux. Both run great on your MacBook if you upgrade the RAM to 4 or 6 GB (and they will also work with 2GB, if you want to try it before buying the memory upgrade.)
Of course, you will have to pay for a Windows license. If you want to try Linux with 2GB RAM first, you can download a compatible Linux Mint ISO image from https://linuxmint.com/edition.php?id=270 . Just burn the image to a DVD and boot your Macbook from the DVD (hold down the option key during startup and choose the DVD in the menu that appears).
APFS Boot
Ever since I installed Catalina on an old iMac 7,1, on which the APFS bootrom had been previously installed, the boot has been verbose, and yesterday I noticed System Preferences has an APFS Boot panel. I think I have two APFS boot solutions in place. If so, how do I get rid of that verbose boot screen and how do I get rid of that APFS Boot panel? Or should I leave it just as it is?
Ever since I installed Catalina on an old iMac 7,1, on which the APFS bootrom had been previously installed, the boot has been verbose, and yesterday I noticed System Preferences has an APFS Boot panel. I think I have two APFS boot solutions in place. If so, how do I get rid of that verbose boot screen and how do I get rid of that APFS Boot panel? Or should I leave it just as it is?