I wouldn't quite give up on acceleration yet it may happen
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
Dont get me wrong: It won‘t happen on MB4,1.I wouldn't quite give up on acceleration yet it may happen
I also hope it can be done for all other unsupported machines
Not likely. Since Mavericks we've been unable to get a patched OpenGL Framework to even make it through WindowServer. I do still have the beta ones that MLforAll gave us back then if you want to take a crack at it.I wouldn't quite give up on acceleration yet it may happen
Looking at the contents of OSInstall.mpkg from the developer seed, I see a updated NVDAGK100Hal (which I assume contains the GTX-680 drivers). The Mojave copy is 12.0.23 but the Catalina copy is 14.0.24.
I was able to install it on my MacBook Pro 2018. I would like to clone the system.
What method have you folks used?
What method have you folks used?
Does not automatically handle the two volumes. Will try doing it "manually."
The system volume content is not visible under Mojave, only the top directories.
Last edited:
@pkouame I was looking at the Catalina Carbon's HIToolBox and noticed the half sized binary 4.7 MB (Catalina) vs 10 MB (the HS/Mojave one), then I remembered why, of course it's halved, it's fork'ed of 32 bit coding by apple, so I thought, since our HighSierra/Mojave frameworks binaries are mostly still 32+64 bit (@ASentientBot found also some 64bit Haswell iirc), maybe this could cause some side effects on Catalina booting on unsupported Mac ?
I mean if Catalina kernel found a 32 bit coding into a framework binary to execute could this lead to a side effect or even unexpected kernelpanic ?
Then I remember another thing, if I don't get wrong, the HighSierra and Mojave "BaseSystem.dmg" should contain all frameworks with 64 bit coding only, so in case it's not needed a disassembly to cut the 32 bit coding.
Don't know maybe this is unrelated, but I'd start to try using the frameworks binaries for patching purposes only with 64 bit for our Catalina unsupported Mac.
I mean if Catalina kernel found a 32 bit coding into a framework binary to execute could this lead to a side effect or even unexpected kernelpanic ?
Then I remember another thing, if I don't get wrong, the HighSierra and Mojave "BaseSystem.dmg" should contain all frameworks with 64 bit coding only, so in case it's not needed a disassembly to cut the 32 bit coding.
Don't know maybe this is unrelated, but I'd start to try using the frameworks binaries for patching purposes only with 64 bit for our Catalina unsupported Mac.
Last edited:
I could successfully boot into Catalina on my MBP5,1 after including LegacyUSBInjector to prelinkedkernel and deleting telemetry. Everything else unchanged at the moment
Last edited:
Just did the "usual" way on a Mac Pro 5.1, took apart installESD and patched Distribution File to wipe unsupported MacPro5,1 and added its Board ID.
Run osinstall.mpkg in High Sierra. I was a hero and took an empty HFS plus Spinner. It wrote all the folders but refused to boot. Does not show in Boot Picker nor in Startup Disk.
Run osinstall.mpkg in High Sierra. I was a hero and took an empty HFS plus Spinner. It wrote all the folders but refused to boot. Does not show in Boot Picker nor in Startup Disk.
Yes there are some Haswell forks out there also.
"Fat" binaries should (normally) not cause any side effects. It should be just "bloat" in Catalina (remember the old PowerPC/Intel days...)
The system loads what it needs. I test my hybrid patches in "thin" 64 bit first for speed and convenience, then lipo the two patched and code-signed architectures together.
If you want to strip some binaries lipo -remove or lipo -thin should still work.
[doublepost=1559686784][/doublepost]
screenshot please
Yes there are some Haswell forks out there also.
"Fat" binaries should (normally) not cause any side effects. It should be just "bloat" in Catalina (remember the old PowerPC/Intel days...)
The system loads what it needs. I test my hybrid patches in "thin" 64 bit first for speed and convenience, then lipo the two patched and code-signed architectures together.
If you want to strip some binaries lipo -remove or lipo -thin should still work.
[doublepost=1559686784][/doublepost]
screenshot please
Agreed, I edited my post I meant only frameworks, since all the kext unix binaries I guess from HighSierra are all 64 bit only, but I remembered when you did your hybrid patch using the "BaseSystem.dmg" HIToolBox binary framework and it was only 64 bit and caused some side effects to 32 bit apps. But yes probably it's unrelated and just ignored by Catalina kernel.
[doublepost=1559687209][/doublepost]
Do you encountered any delay in verbose booting with kext_stall or busy_timeout 60s on HIDDevice ?
[doublepost=1559687564][/doublepost]
Before acceleration I guess we need first a Framebuffer video driver loaded, and @ASentientBot I guess has almost found a solution to that binary patching IOSurface.kext that caused a kernel panic just before the stage2 apple logo, when prelinked together with IOAccel*.kext, IOGraphicsFamily and IONDRSupport kext (taken from HighSierra to support older non-metal graphics).
Last edited:
Something is very odd with this installer. I did a fresh install off a thumb drive onto an external hard drive via a supported system (2012 Mac Mini) and after the first reboot it showed the progress bar then went to a prohibited sign. I had to force the machine off and select the Install drive from the boot selector for it to go back into install mode.
I was doing all this to test my MacPro4,1->5,1 which I haven't gotten to yet. Curious, are you getting the EFI screen when booting? Because I will sometimes get the EFI if I power cycle my monitor at the right time with my 380X card. I'm just afraid of setting the Catalina test volume as the primary boot drive and having to reinstall my 5870 to get the system to show EFI if it fails.
screenshot please
Sorry for the bad picture.
[doublepost=1559688073][/doublepost]
Yes, exactly as you described earlier. Also no delay in safe mode.
But maybe it has to do with some missing kexts. As Brightness control, WiFi, maybe audio, ... (didn’t looked deeper at the Moment) aren’t working for now. But these things also didn’t work on Mojave out of the box, so patching is also necessary on Catalina I think.
Bro the tech news websites are giving mixed info on it, some say that it's been dropped CNET, TechRepublic, Tech radar etc., while Macworld says they will be supported with a Metal GPU inside.
The Package is still on my Downloads Backend. You can extract it with Pacifist.Thank you
OpenGL Beta Mod (10.9 - 10.12).pkg
(NOT FOR THIS VERSION OF MACOS)
Yes, had a GT120 in for this, to see verbose mode, but that never happened. Tried other things, apfs drive, even to install over high sierra, was all refused or the installer showed no drive. Error message was somelike can only install on the drive the installer is. Wtf...
Btw same procedure worked last year with 1st Mojave beta, even on a 3.1 - so I know the basic steps...
On the missing Dashboard - in another life way back in the day, I found an iPad Dashboard look a like on github. In fact it was so good Apple denied the developer (an ex-Apple employee) AppStore rights.
You would have to brush up on your Obj-C but it's a full implementation with downloadable widgets and all. I think it should be easily transferable to macOS. Especially with all the Marzipan/Catalyst/SwiftUI stuff happening...Interested? Check it out here : https://github.com/hongrich/Dashboard. Sounds like a nice Summer project
Let me say this:
1) remember, the developers said they're building OpenCore with real Macs in mind - so this is not just an effort for the Hackintosh world @pkouame.
2) I've found that some things like Lilu and WhateverGreen can save the day with real Macs when it comes to video cards having quirks with Mojave. The Hackintosh devs, especially these incredibly talented ones, are saving the day for everyone while Apple is worried about its bottom line coming from mobile devices.
have you tried installing it with parallel desktop software it might be a way to test for now somewhat. Iam going to try it that right now to see what happens