Sidebar Sidebar
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

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.
@bmillz for Catarina beta1 to try getting acceleration on an IntelHD3000 you have to use: these

and these from a Mojave Patched:

AppleIntelHD3000Graphics.kext
AppleIntelHD3000GraphicsGA.kext
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext
AppleIntelSNBVA.bundle
 
  • Like
Reactions: hvds and pkouame
dosdude1 said:
Of course, Apple being Apple, the new DP2 installer broke my patches that worked in DP1. I have now updated the tool to beta 6, which fixes those issues.
Click to expand...

I am seeing the installation fail with the 'An error occurred while verifying firmware' on a MacPro 3,1 with the APFS ROM patch applied. At the moment, I doubt anyone will be able to install who isn't on a machine that has APFS support in the official Apple firmware.

Has anyone posted a hack to disable that firmware check?
 
  • Like
Reactions: olad
jhowarth said:
I am seeing the installation fail with the 'An error occurred while verifying firmware' on a MacPro 3,1 with the APFS ROM patch applied. At the moment, I doubt anyone will be able to install who isn't on a machine that has APFS support in the official Apple firmware.

Has anyone posted a hack to disable that firmware check?
Click to expand...
I had that patched out... Guess there's another check I need to patch. I will have it fixed momentarily.
 
  • Like
Reactions: webg3, Appleak and TimothyR734
jackluke said:
Then try this:

from your Catalina Mac, before power-on, plug the USB Mojave Patcher (any version), power-on, hold alt-option key and boot from the USB Mojave Patcher, after loaded, launch the Mojave Post-Install

Don't select your Mac model, target your Catalina Volume and select only these patches:

Legacy USB Injector
USBOHCI Support
SIPDisabler
Legacy Audio
Legacy Platform Compatibility
Legacy Wifi

Select Volume: YourCatalinaLabel

Press Patch button

But Do NOT install/select the "Legacy Video Patch" and do NOT check "force cache rebuild".

Just reboot and unplug the USB Mojave Patcher, and maybe Catalina should boot.
Click to expand...
I tried that this is what I got I even pull the Mojave Patcher out before rebooting after applying the selected patches
 

Attachments

  • IMG_2244.jpeg
    IMG_2244.jpeg
    4.2 MB · Views: 326
ASentientBot said:
Bad news -- Xcode 11 beta crashes on both patched Mojave and Catalina. Looks like some of the core editor functionality uses Metal.

Edit: I (sloppily) fixed it!
Click to expand...

I was pondering on trying your fix, or waiting for beta 2. Well, if anyone else was having issues with Xcode 11 beta 1, try Xcode 11 beta 2 and see if it works. It works for me, where beta 1 would just crash if I did anything other than open it up. Error had something to do with illegal instructions my old processor didn't understand.

Looking forward to trying out some of the new features with it.
 
I have beta 2 downloaded and Catalina Patcher 1.0b6. (may wait for 1.0b7 if need be)
Can I just use separate containers on my internal ssd to do the installs?

MacBookPro8,1 with Intel HD Graphics 3000
Internal SSD
-> container1 - Mojave
-> container2 - Patched Catalina beta 2 installer
-> container3 - (installed) Catalina beta 2

Or, do I need 1 or two external devices?

For Mojave, I have been using an SDXC card in the internal reader.

Thanks for the help.
 
  • Like
Reactions: TimothyR734
dosdude1 said:
Beta 7 of the tool is now available, which fixes the firmware validation error on DP2.
Click to expand...

Is there a check that prevents installation of Catalina on a hard drive? The installer created by Beta 7 from DP2 now passes the firmware check but fails with...

The operation couldn't be completed (com.apple.DiskManagement.disenter error 49168.)

This is a on a MacPro 3,1 with the APFS ROM patch installing on a APFS formatted hard drive.
 
Last edited:
jhowarth said:
Is there a check that prevents installation of Catalina on a hard drive? The installer created by Beta 7 from DP2 now passes the firmware check but fails with...

The operation couldn't be completed (com.apple.DiskManagement.disenter error 49168.)
Click to expand...
No, should install fine on any drive... Is the volume formatted as APFS?
 
  • Like
Reactions: webg3 and Appleak
dosdude1 said:
No, should install fine on any drive... Is the volume formatted as APFS?
Click to expand...

The install volume ends up with a /private/var/log/dm/dm.log with the following contents...

https://pastebin.com/dyQWzgtS

I assume the problem line is...

20190617-18:05:08.33204 [00634:003803] diskmanagementd _DAOperation_callback_ IntErr=1=0x1 Unmount of disk29s2 blocked by dissenter PID=639 (/System/Installation/CDIS/macOS Installer.app/Contents/MacOS/macOS Installer) PPID=625 (/System/Library/CoreServices/Language Chooser.app/Contents/MacOS/Language Chooser) status=0x0000c010 (File system reports this error: Resource busy)
 
  • Like
Reactions: TimothyR734
This is the error message I get trying to partition the drive both with b6-b7 partial installers with Cat beta 1
 

Attachments

  • IMG_2245.jpeg
    IMG_2245.jpeg
    6 MB · Views: 281
TimothyR734 said:
This is the error message I get trying to partition the drive both with b6-b7 partial installers with Cat beta 1
Click to expand...
Erase the container volume as macOS Extended, then erase that volume again as APFS. Then, it should work. Also keep in mind those versions only support Dev Preview 2, and will NOT work correctly with DP1.
 
Last edited:
  • Like
Reactions: Appleak, BuffyzDead, crjackson2134 and 1 other person
Just installed DP2 and experienced the same issue -- hanging on the Apple logo due to repeated loginwindow crashes. I hit it with the ol' stub hammer again and managed to get to the Desktop, but still lack acceleration (framebuffer working though). There are a ton of new symbols in CoreDisplay, which is a bad sign.

I'll report back if I make any progress. @pkouame or @dosdude1 , have you looked into this yet? Anything I should be aware of?

Edit: The stubs were actually all it took, I just somehow messed up my copy of the OpenGL framework while testing. It works now.
 
Last edited:
  • Like
Reactions: Appleak, Badruzeus, estape11 and 3 others
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back