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.
Installed DP3/PB2 on my 6,1. @dosdude1's patcher V 1.0b6 worked like a charm. The OS is a bit slower this time around compared to DP2/PB1, But it's much more stable. Something to do with Catalina, not the hardware. We'll see how the OS runs in DP4/PB3. I can send iMessages and do FaceTime pretty well on here. Regardless, considering this is only 4gb of RAM, I'm amazed how well it runs nearly 10 years later. I got SideCar working in system preferences. Now I have to figure out AirDrop and NightShift and anything else that I'm missing.
 

Attachments

  • Screen Shot 2019-07-03 at 10.31.43 AM.jpeg
    Screen Shot 2019-07-03 at 10.31.43 AM.jpeg
    215.6 KB · Views: 310
Hey guys, im running this on a mac pro 5,1. I am having issues getting anything to come out of non-legacy graphics cards. I have tried with AMD 560 and NvidiaK4000, the K4000 works with my Imac 2012 ( that's another story of how I did that) but when in the 5,1 nothing comes out. Shows up in the System information and everything. The AMD 560 on the other hand shows nothing, just a "display" in system information. Thanks in advance.
 
  • Like
Reactions: TimothyR734
How exactly do you try to install it? There are many methods floating around. I suggest dosdude's USB installer.
I did both, first I ran through with the nvram reset. After I couldn't get that running I did dosdudes, but still no avail.
[doublepost=1562177865][/doublepost]
I did both, first I ran through with the nvram reset. After I couldn't get that running I did dosdudes, but still no avail.
Heres the big kicker. It runs on the 2011 imac with the K4000, (dual External screening actually). On the mac pro 5,1 it also shows up under system information. This in theory should mean it is displaying, but I cant get anything through it and no displays come up as attached.
 
  • Like
Reactions: TimothyR734
The NVRAM reset would clear the no_compat_check boot option, so you need to manually reset it through the recovery volume. The USB installer on the other hand has that integrated so it applies it during installation. Did you run any patches or only the USB installer?
 
  • Like
Reactions: TimothyR734
The NVRAM reset would clear the no_compat_check boot option, so you need to manually reset it through the recovery volume. The USB installer on the other hand has that integrated so it applies it during installation. Did you run any patches or only the USB installer?
just the usb install and the after install ospatcher.
 
  • Like
Reactions: TimothyR734
I used Dosdude1’s nvram gpu disabling method(the old one)...can I still use the thunderbolt output?
It is on MacBook Pro early 2011 8,2
 
Beta 3 supports Watch Unlock on Mac Pro with updated WiFi/BLE cards after updating the plist in the IOBlueTooth framework.
sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"
Crashing on wake - oops.
 
Last edited:
  • Like
Reactions: macinfo
Run this command first then trimforce enable, it run normally and restart automatically, but after bootup , Trim still not enable , I am running M.2 SATA SSD , it work at Mojave before.

And Command +R can’t boot to recovery mode, or is there any other way to do it, want to disable SIP ..

Thanks
Reboot to the dosdude installer disk. If you have that you don't need recovery mode.

I've run ssd's with or without trim and I haven't seen a noticeable difference in performance or longevity. I currently have 4 SSDs in two hardware RAIDs (2 ssd's each) and they are seen as rotational. Been running those for over a year and I am not able to set trim (though it might be doing it internally on the hardware side). I have other SSDs and I've ran them both with and without trim. Many of these the SSDs are just used for testing and are not used much.

Note: APFS does share bits when files are copied on the same volume, and that can actually help save an SSD.

I know trim does save on writes too by erasing and copying only what it needs to, but I would not sweat it if you can't get trim to work. I'd enable it when you can.

One thing that may be bad is DD'ing an entire SSD with zeros.

I heard that messages were getting the metal treatment I didn't think it would be this soon :(
Must be for Animoji's, Stickers and more advancements.
 
Last edited:
Try the installer without the patches.
Hey, thanks for the help. I tried again and failed. This time I just yanked the harddrive out of the 2011 imac and threw it in the 5,1. Then it booted like a champ and ran fine. Thanks for all the help! have we figured out how updates are going to work? or is that up in the air
 
  • Like
Reactions: TimothyR734
Are you know patching the installed SystemVersion.plist on both System and Recovery to eliminate the need for bootargs?

I guess no, the "-no_compat_check" is a kernel xnu flag, and maybe it's related in some way also to the apple boot.efi , so I guess only if the boot.efi would binary patched you could avoid the boot-args .
 
  • Like
Reactions: TimothyR734
I used Dosdude1’s nvram gpu disabling method(the old one)...can I still use the thunderbolt output?
It is on MacBook Pro early 2011 8,2
As far as I know the Thunderbolt port is directly wired to the Discrete AMD GPU. With the NVRAM flag used to disable the discrete GPU this will in term disable the use of the Thunderbolt port. OS X will still detect it as its still got power as the NVRAM flag does not Turn Off the discrete AMD GPU but just disables it.
 
I guess this time for Photos.app since from Catalina is fully Metal, we need to use a third party Photo app, Timothy for NightShift you can use this one temporary pre-patched from Catalina beta2. It goes in /S/L/PrivateFrameworks/
I can't use this in dev beta 3 I can read only can't rename it to replace this with the original so they are fighting the noose on us I go it figured out night shift is working again :)
 
Last edited:
You have to modify the support plist to get it working on the MB4,1.


Hi, Julian, I'v successfully installed Catalina on my MB 4.1, but nothing happened when I type "patch" in terminal after installation and reboot. There are some warnings appeared when I created the install disk, don't know why. Here is the log, could you have a check? Thanks a lot!

+ Mounted installer disk images.
+ Checked installer version.
+ Installer support check passed.
/ What volume would you like to use?
/ Input a volume name.
/ BOOTCAMP
/ Insta
/ MOJAVE
/ SIERRA
/ Insta
+ Unmounted installer disk images.
> Creating installer disk.
> Created installer disk.
+ Renamed installer volume.
+ Mounting BaseSystem disk image.
+ Patched installer files.
+ Patched input drivers.
+ Patched platform support check.
+ Patched kernel cache.
+ Patched System Integrity Protection.
> Copying patcher utilities.
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/CursorAsset: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/CursorAsset_base: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/SkyLightShaders.air64.metallib: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/WindowServer: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/SkyLight: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/SkyLightOriginal: No space left on device
cp: /tmp/Base System/usr/patch/startup.nsh: No space left on device
cp: /tmp/Base System/usr/patch/SUVMMFaker.dylib: No space left on device
cp: /tmp/Base System/usr/bin/patch: No space left on device
+ Copied patcher utilities.
+ Unmounted BaseSystem disk image.
+ Converted BaseSystem disk image.
+ Mounted InstallESD disk image.
+ Patched installer package.
+ Unmounted InstallESD disk image.
+ Converting InstallESD disk image.
+ Removed temporary files.
/ Thank you for using macOS Patcher.
 
Anyone that was able to successfully update to Beta 3 on an unsupported device, have the "Automatic" on System Preferences | Desktop & Screen Saver | Desktop got it to work?

Thanks.
 
  • Like
Reactions: TimothyR734
Hi, Julian, I'v successfully installed Catalina on my MB 4.1, but nothing happened when I type "patch" in terminal after installation and reboot. There are some warnings appeared when I created the install disk, don't know why. Here is the log, could you have a check? Thanks a lot!

+ Mounted installer disk images.
+ Checked installer version.
+ Installer support check passed.
/ What volume would you like to use?
/ Input a volume name.
/ BOOTCAMP
/ Insta
/ MOJAVE
/ SIERRA
/ Insta
+ Unmounted installer disk images.
> Creating installer disk.
> Created installer disk.
+ Renamed installer volume.
+ Mounting BaseSystem disk image.
+ Patched installer files.
+ Patched input drivers.
+ Patched platform support check.
+ Patched kernel cache.
+ Patched System Integrity Protection.
> Copying patcher utilities.
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/CursorAsset: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/CursorAsset_base: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/SkyLightShaders.air64.metallib: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/Resources/WindowServer: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/SkyLight: No space left on device
cp: /tmp/Base System/usr/patch/SkyLight.framework/Versions/Current/SkyLightOriginal: No space left on device
cp: /tmp/Base System/usr/patch/startup.nsh: No space left on device
cp: /tmp/Base System/usr/patch/SUVMMFaker.dylib: No space left on device
cp: /tmp/Base System/usr/bin/patch: No space left on device
+ Copied patcher utilities.
+ Unmounted BaseSystem disk image.
+ Converted BaseSystem disk image.
+ Mounted InstallESD disk image.
+ Patched installer package.
+ Unmounted InstallESD disk image.
+ Converting InstallESD disk image.
+ Removed temporary files.
/ Thank you for using macOS Patcher.
Seems like you need a larger usb or something.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.