hi, what exactly did you do that it boots and installs with you?
I have a MP 5.1 with 12 cores, 64GB Ram, AMD Radeon HD 7950 with 3GB
please tell me exactly what you did
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
hi, what exactly did you do that it boots and installs with you?
I have a MP 5.1 with 12 cores, 64GB Ram, AMD Radeon HD 7950 with 3GB
please tell me exactly what you did
I don't what is it and what exactly do i change inside of it?
I see thanks. once I get in I should be able help figuring out acceleration.
Does anyone know if replacing the AppleIntelHDGraphics*.kext from an earlier release, such as Sierra, would result in graphics acceleration for Intel iGPUs on Catalina? I remember @Badruzeus relaying the info to @dosdude1 early on in the Mojave patching last year. IIRC, Intel's GPUs were the first and easiest to get working so hopefully history will repeat itself.
As far as dosdude1 talked in the latest MacYak show, cataline will proberly never work well with non metal cards.
Api calls found in windowserver are all no longer having opengl backends.
As far as i understand..
He also said catalina could be made work well on unsupported macs, like a Macpro’s with metal gpu’s , iMac’s with upgraded gpu’.
But i doubt any non metal Macbook’s will ever work..
@ASentientBot I guess I have figured out the brightness backlight control on MacBook7,1 and it consists in:
- leaving the stock Catalina /S/L/E/ AppleGraphicsControl.kext and AppleBacklight*.kext
- Just replace (keeping a backup copy of it) in /System/Library/PrivateFramewors/GPUWrangler.framework
with a GPUWrangler or from HighSierra 10.13.6 or from Mojave 10.14.3
The GPUWrangler.framework replacement must be done or from single user mode or booting from another partition/volume (either APFS or HFS) macOS higher than Sierra (to support RW on an APFS volume).
doing this will bring the full backlight F1-F2 control to MacBook7,1 and probably to any other singleGPU machine equipped with a Nvidia Tesla.
Even if this worked I ask you when you'll do your OpenGL fixes test, to prefer use the GPUWrangler.framework from Catalina, because I don't know if this has a binding effect on Catalina OpenGL.framework, but I don't think since I did replaced it always on all my Mojaves and OpenGL acceleration was still there.
-----------------------------------------------------------
While about a MacBookPro6,2 Arrandale with dualGPUs Nvidia Tesla GT 330M and IntelHD (The arrandale one but maybe this will work also with the SandyBridge one IntelHD3000) these are the steps in order to make working the DualGPUs dynamic/manual switching on Catalina:
- Replace from Catalina /S/L/E/ the AppleGraphicsControl.kext, AppleGraphicsPowerManagement.kext, AppleMCCSControl.kext and from /S/L/PrivateFrameworks/ GPUWrangler.framework
All these must be taken or from HighSierra 10.13.6 or from Mojave 10.14.3 (maybe prefer the Mojave ones since should be more closer to a Catalina kernel).
------------------------------------------------------------
@testheit , I did noticed too that replacing the "IOAcceleratorFamily2.kext" cut the "Metal acceleration" to Mojave supported Mac, and I'll try to explain why:
It's a main "graphics kext" shared among many GPUs (I'd exclude the Nvidia Tesla since they should rely on IONDRVSupport.kext), and in particular for IntelHD* series, for example the barely supported Metal 2012 Mac has an IntelHD4000 and of course swapping the "IOAcceleratorFamily2.kext" with a legacy kext will "broke" the Metal acceleration to that card.
I guess not only that will cut the "Metal acceleration" but also downgrading the OpenGL, GPUSupport and CoreDisplay frameworks had that side effect on Metal GPUs.
Meanwhile reading also your post about the "GLContext crashing" when zooming with Catalina Maps.app , well in my case it doesn't crash at all, instead even if very slowly it allows me to zoom -/+ without any issues, I attach pictures.
And a funny thing also for @ASentientBot , using a reddit script thanks and credit to u/dotmax does "enable" the Sidecar prefpane also on Macbook7,1 , I just copy/pasted the reddit script into a Terminal window.
But of course as very well explained by @tsialex , that Sidecar (essentially an improved "Airplay mirroring") feature to mirror screen to an IPadOS requires an HEVC full capable GPU, unless someone will find a patch to allow earlier "Airplay mirroring" GPUs as for example the IntelHD3000-4000-5000 to force the Sidecar using a lower quality encoder/decoder.
- leaving the stock Catalina /S/L/E/ AppleGraphicsControl.kext and AppleBacklight*.kext
- Just replace (keeping a backup copy of it) in /System/Library/PrivateFramewors/GPUWrangler.framework
with a GPUWrangler or from HighSierra 10.13.6 or from Mojave 10.14.3
The GPUWrangler.framework replacement must be done or from single user mode or booting from another partition/volume (either APFS or HFS) macOS higher than Sierra (to support RW on an APFS volume).
doing this will bring the full backlight F1-F2 control to MacBook7,1 and probably to any other singleGPU machine equipped with a Nvidia Tesla.
Even if this worked I ask you when you'll do your OpenGL fixes test, to prefer use the GPUWrangler.framework from Catalina, because I don't know if this has a binding effect on Catalina OpenGL.framework, but I don't think since I did replaced it always on all my Mojaves and OpenGL acceleration was still there.
-----------------------------------------------------------
While about a MacBookPro6,2 Arrandale with dualGPUs Nvidia Tesla GT 330M and IntelHD (The arrandale one but maybe this will work also with the SandyBridge one IntelHD3000) these are the steps in order to make working the DualGPUs dynamic/manual switching on Catalina:
- Replace from Catalina /S/L/E/ the AppleGraphicsControl.kext, AppleGraphicsPowerManagement.kext, AppleMCCSControl.kext and from /S/L/PrivateFrameworks/ GPUWrangler.framework
All these must be taken or from HighSierra 10.13.6 or from Mojave 10.14.3 (maybe prefer the Mojave ones since should be more closer to a Catalina kernel).
------------------------------------------------------------
@testheit , I did noticed too that replacing the "IOAcceleratorFamily2.kext" cut the "Metal acceleration" to Mojave supported Mac, and I'll try to explain why:
It's a main "graphics kext" shared among many GPUs (I'd exclude the Nvidia Tesla since they should rely on IONDRVSupport.kext), and in particular for IntelHD* series, for example the barely supported Metal 2012 Mac has an IntelHD4000 and of course swapping the "IOAcceleratorFamily2.kext" with a legacy kext will "broke" the Metal acceleration to that card.
I guess not only that will cut the "Metal acceleration" but also downgrading the OpenGL, GPUSupport and CoreDisplay frameworks had that side effect on Metal GPUs.
Meanwhile reading also your post about the "GLContext crashing" when zooming with Catalina Maps.app , well in my case it doesn't crash at all, instead even if very slowly it allows me to zoom -/+ without any issues, I attach pictures.
And a funny thing also for @ASentientBot , using a reddit script thanks and credit to u/dotmax does "enable" the Sidecar prefpane also on Macbook7,1 , I just copy/pasted the reddit script into a Terminal window.
But of course as very well explained by @tsialex , that Sidecar (essentially an improved "Airplay mirroring") feature to mirror screen to an IPadOS requires an HEVC full capable GPU, unless someone will find a patch to allow earlier "Airplay mirroring" GPUs as for example the IntelHD3000-4000-5000 to force the Sidecar using a lower quality encoder/decoder.
Attachments
Last edited:
Just to keep people here that have MP4,1>5,1 and MP5,1 informed, I did a non patched install of Catalina on a MP5,1 using rawdisk and VMWare Fusion on the thread What you need to do to make Catalina work with MacPro5,1.
I'll do a step by step post this weekend but there are enough info from the post #107 to reproduce it already.
I'll do a step by step post this weekend but there are enough info from the post #107 to reproduce it already.
What I've found so far about Cataline issue related to OpenGL is different with Mojave. I recently tried lot of kexts & frameworks from 10.13.6 up to 10.14.6Beta but found no solution yet. However, after WindowServer crash on my Nvidia Fermi what I got from logs is this:
`CoreDisplay: Can not create Metal Device for accelerator` blah blah blah.
But on my case, blocking or removing GeForce.kext still loads CoreImaging (CI) only with no stuck on blackscreen with console logs, nor with QuartzExtreme (QE) < CI uses NVDAGF100Hal, ~Resman for sure.
Last edited:
@ASentientBot , not sure if done exactly as you well explained how to, but following your tip, I successfully binary patched IOHIDDevice unix, now finally no more "kextd_stall IOHID timeout" with zero delay booting. In few "words" I've swapped that entire "pseudo-function" leaving only "return". Thanks.
Attachments
If you succeed to OTA update or clone a Catalina beta installation, it's a bit tricky and can broke your current Mojave installation (unless you install Catalina on an external USB hard disk as I did), since my IntelHD (Arrandale) thanks to @ASentientBot IOSurface patch now is correctly detected with Video Framebuffer, almost surely the same method will work for IntelHD3000 too. But still not Acceleration.
What size of USB External Hard do you can handle Catalinia
this my MacBook air configuration:
MacBook Air (13-inch, Mid 2011)
1.8 GHz Intel Core i7
4 GB 1333 MHz DDR3
Intel HD Graphics 3000 384 MB
I have Mojave running on my Mid 2011 MacBook Air
I think I might do the USB external hard seems saver, instead of mess up my laptop.
I reserved 50 gb for Catalina, but don't know it happened during Mojave OTA updates that were required at least 23 GB for a Mojave version update, so if you don't plan to install Xcode or other big apps, they should be suffice, otherwise reserve for Catalina at least 80-100 gb.
Wait now I'm checking the exact size. I confirm, I have an almost clean Catalina APFS Container on a 50 gb partition with 25 gb available space (and I have also dozens of small third party apps installed).
edit: forgot to say, I have done that with a Mojave installation, then OTA upgraded to Catalina, I haven't used or created any Catalina USB Installer, since for an unsupported Mac I don't exactly how to create it, I just restored a Catalina BaseSystem.dmg to a spare partition, and it does reach the Installer GUI, but patching the Core.pkg or Installer sub-checks is not my stuff.
Last edited:
soooo @dosdude1 you've been quiet, any news?
So did you copy you mojave over to you external hard drive then install Catalinia on, Or did you just formatted the external hard drive to APFS and then installed Catalinia?
The first part, as I edited my previous I don't know how to create a valid Catalina installer for unsupported Mac, while for Catalina supported Mac is of course much more easier: https://support.apple.com/en-us/HT201372
So if you follow my path, you should start from a clean Mojave 10.14.5 APFS installation, or better, wait for @dosdude1 or @0403979 Catalina beta USB Installer.
That is what a did with Mojave I used @dosdude1 Mojave Patcher. I just hope that Catalinia Patcher will be available soon
Actually, the Catalina usb installer doesn't work. The data volume is not properly created by the package install or the patched installer method and the system won't boot.
Patched PC Version. I am using a NIB Galaxy 2GB GTX 680 Card. Works really well.
I also have an unpatched 6GB Kepler Titan, but I am leaving it offline for now as I am switching Startup Disk a good bit.
Once you have some type of networking working. I am using Ethernet or Firewire to another box because I don't want to mess with patches until I get a good clone. Carbon Copy Cloner has a beta for Catalina!
Off topic: I used to have a Darwin based cloning tool called CloneTool that I developed for Hackintoshes. It cloned Macs as well. CCC is a good solution.
Yeah, it's tricky. The only way I got it to install (I don't have access to a supported Mac):
- use createinstallmedia to make a bootable disk/partition
- convert InstallESD.dmg (on that disk) to read/write and patch OSInstall.mpkg (the usual Distribution edits caused an error with signing, so I ended up replacing with the one from High Sierra in the end... need a better fix, though... anyone know how @dosdude1 does this?)
- set -no_compat_check in NVRAM (or you can edit com.apple.Boot plist files, but there are a few in different folders... plus, the installer will partially complete, then reboot to another (\) and require another edit to a file on the target volume's Preboot)
- install to APFS using the bootable installer
Edit: more details added.
Last edited:
Beyond pat
Beyond patching OSInstall.mpkg/Distro... file. What else needs to be patched to make a full installer that can run. When I open the 10.15 installer app it gets stuck on, you cannot install 10.15 on this mac, so there is a check that I am missing or something in NVRAM that I can edit? If I can get that to work, I am can help MP 3,1 and 5,1 out a bit more.
[doublepost=1559917973][/doublepost]
That's a good Machine.
Here is my rundown.
I was not able to patch the 10.15 installer to work natively. I will detail what I did.
1. from Mojave with SIP off I ran:
sudo nvram boot-args="-no_compat_check"
2. Take a drive out off your MP3,1 MP4,1 or MP5,1
3. Using an external case, connect the drive to a supported mac.
4. Format drive APFS
5. Install Catalina
6. After install, close the Welcome Screen
7. It will as you to shutdown
8. Insert drive on your MP.
9. Boot up to Mojave. If on MP3,1 remove Telemetry.plugin (it's in the User something Plugins folder)
10. Boot up Catalina
11. Be very patient and wait. It will be very slow the first time without Networking.
12. After 10 min. Catalina should be booted. It will get faster.
13. Firewire and Ethernet network work. So I connected an old box (2006 Mac Mini and shared it's WiFi)
14. WiFi may not work out of the box. I am avoiding it til a how-to is out.
15. Sound may not work. I am using a USB sound adapter. Works fine. will patch it with a how-to for sound is out.
16. Bluetooth works but bluetooth input devices may not work when in Safe Mode. (Word to the wise here).
17. One you get networking working! Ethernet, Firewire or you got luckly with WiFi, the boot will be blazing fast. I think the betas are phoning home to the AppleStore. I've even different messages in verbose mode about it and it barfs when networking out off. When on, all the lag in starting up goes away.
With some creativity with Ethernet or Firewire Networking for Internet and USB Sound, I am running Catalina with Metal on a MP 3,1 and only have removed Telemetry. It's not perfect, but it's as plain vanilla as I could get and with this setup, updates should be easier.
I will be cloning this setup to try to get WiFi and Sound working. I am sure you guys have figured that out. Also want to get a full installer working for the MPs. Those are my goals in the meantime.
Hope this helps.
If I can get assistance an bypassing things to allow a full installer to run, I may try to help further an maybe have a post installer script that helps MacPro 3,1 and 5,1 users. I got the OSInstaller patched, but am missing something the app UI that has another blocker.
Beyond patching OSInstall.mpkg/Distro... file. What else needs to be patched to make a full installer that can run. When I open the 10.15 installer app it gets stuck on, you cannot install 10.15 on this mac, so there is a check that I am missing or something in NVRAM that I can edit? If I can get that to work, I am can help MP 3,1 and 5,1 out a bit more.
[doublepost=1559917973][/doublepost]
That's a good Machine.
Here is my rundown.
I was not able to patch the 10.15 installer to work natively. I will detail what I did.
1. from Mojave with SIP off I ran:
sudo nvram boot-args="-no_compat_check"
2. Take a drive out off your MP3,1 MP4,1 or MP5,1
3. Using an external case, connect the drive to a supported mac.
4. Format drive APFS
5. Install Catalina
6. After install, close the Welcome Screen
7. It will as you to shutdown
8. Insert drive on your MP.
9. Boot up to Mojave. If on MP3,1 remove Telemetry.plugin (it's in the User something Plugins folder)
10. Boot up Catalina
11. Be very patient and wait. It will be very slow the first time without Networking.
12. After 10 min. Catalina should be booted. It will get faster.
13. Firewire and Ethernet network work. So I connected an old box (2006 Mac Mini and shared it's WiFi)
14. WiFi may not work out of the box. I am avoiding it til a how-to is out.
15. Sound may not work. I am using a USB sound adapter. Works fine. will patch it with a how-to for sound is out.
16. Bluetooth works but bluetooth input devices may not work when in Safe Mode. (Word to the wise here).
17. One you get networking working! Ethernet, Firewire or you got luckly with WiFi, the boot will be blazing fast. I think the betas are phoning home to the AppleStore. I've even different messages in verbose mode about it and it barfs when networking out off. When on, all the lag in starting up goes away.
With some creativity with Ethernet or Firewire Networking for Internet and USB Sound, I am running Catalina with Metal on a MP 3,1 and only have removed Telemetry. It's not perfect, but it's as plain vanilla as I could get and with this setup, updates should be easier.
I will be cloning this setup to try to get WiFi and Sound working. I am sure you guys have figured that out. Also want to get a full installer working for the MPs. Those are my goals in the meantime.
Hope this helps.
If I can get assistance an bypassing things to allow a full installer to run, I may try to help further an maybe have a post installer script that helps MacPro 3,1 and 5,1 users. I got the OSInstaller patched, but am missing something the app UI that has another blocker.
Last edited:
Barebones Catalina up and running on mbp 5,3 (dual nvidia gpu)
- initial install on a supported Mac to an external USB stick formatted as APFS (GUID of course)
- Only needed:
- LegacyUSBInjector.kext in S/L/E -> regenerated a prelinkedkernel on a supported Catalina Mac with SIP disabled
- removal of telemetry of course
- nvram boot-args="-no_compat_check -v" (opted out of -x)
- no other framework patches (yet)
- no other kext patches (yet)
- no acceleration (yet)
- keyboard - mouse - bluetooth work (how I transferred the screenshot below)
- sound - video - wifi - brightness control still inoperative since I haven't applied kexts that address those yet
- takes a while to start to get to initial setup and login UI
- Here's a screenshot
If we can get acceleration working, yes. Right now, it boots but isn't really usable.
We've done this three times, though (10.14.0, 10.14.4, 10.14.5), so I'm confident that we can get those annoying Tesla/OpenGL bundles up and running again, sooner or later...
where can i find what my usb hard drive name is so i can change the MyVolume name in a command?