sure I have
[doublepost=1560337799][/doublepost]hdiutil attach -owners on InstallESD.dmg -shadow
replaced pkg from Hierra
hdiutil detach /dev/disk4
hdiutil convert -format UDZO -o InstallESD.NEW.dmg InstallESD.dmg -shadow
is it OK?
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
[doublepost=1560337799][/doublepost]hdiutil attach -owners on InstallESD.dmg -shadow
replaced pkg from Hierra
hdiutil detach /dev/disk4
hdiutil convert -format UDZO -o InstallESD.NEW.dmg InstallESD.dmg -shadow
is it OK?
even using the AGC set from 10.14.3 I can't control the brightness of my display (MBP5,1).
The keys (F1/F2) are recognized and the HUD is shown on the display, but brightness doesn't change...
The keys (F1/F2) are recognized and the HUD is shown on the display, but brightness doesn't change...
Exactly since you need to put it again in read-only for the OSX Installer, so a temporary shadow Volume is good.
[doublepost=1560338558][/doublepost]
You have also to downgrade the privateframework GPUWrangler.framework (only from single user mode) to 10.14.3 or 10.13.6, however it must match with the AGC kext set used, I for example use the HighSierra ones, but they work the same as 10.14.3, since I got working this new fresh @ASentientBot non-metal acceleration even using OpenGL.framework and GPUSupport.framework from HS 10.13.6 .
Note AGC set is: AppleGraphicsControl, AppleGraphicsPowerManagement and AppleMCCSControl kext .
And I'd extend it also to using IOAccelerator2D.plugin, IOAcceleratorFamily2.kext , IOGraphicsFamily and IONDRVSupport (all these strictly from 10.13.6 )
Last edited:
brightness works!! with the new patches from @ASentientBot. so I think CoreDisplay downgrade is necessary for my MBP
Yes, I also as you try sometimes to keep the most updated and downgrade less things possible, but in these cases they are needful especially for older machines, but I can confirm that downgrading the AGC kext set (with GPUWrangler.framework) will help dualGPUs Catalina unsupported Macs and doesn't affect bad the singleGPU Mac, as it was been for Mojave.
I guess @pkouame and you can start to focus on a hybrid Catalina light/dark mode.
I've already tried to use the Mojave HIToolbox and CoreUI but they didn't worked.
Acceleration works with stock IOAccelerator2D.plugin, IOAcceleratorFamily2.kext , IOGraphicsFamily and IONDRVSupport on my MBP5,1. Really impressive work @ASentientBot
For a non-IntelHD GPU mac, probably these: IOAccelerator2D.plugin, IOAcceleratorFamily2.kext are not totally needed.
About these: IOGraphicsFamily and IONDRVSupport , probably you use the NDRVShim from @parrotgeek1 , that I don't used that's why I needed to downgrade more stuffs.
did not finished yet
but this way seems to be working
Install started from USB
Thanks
Yay Indeed! Great work and achievement - you deserve a medal for getting to this point (and alone) - congrats.Hiiiii! Sorry for being so quiet since my post yesterday. I've been busy. I've significantly improved the SkyLight/CoreDisplay patches to a point where I feel they're ready to be tested/improved upon by you guys!
As of yesterday, I had binary patched about 5 different files (including AppKit, yikes) in order to just barely get the system running. Today, I undid that and implemented wrapper binaries for the old frameworks, with stub functions to (mostly) keep things happy -- a much cleaner solution. I just finished doing a full reinstall to re-check everything, and I'm writing this from accelerated Catalina on my 2010 MacBook!
So... on a system with a working framebuffer (which should be achievable by following the same steps as for 10.14.5), you should be able to just replace these two frameworks with the attached copies. No other binary patches needed!!
For convenience I'm also including the fix for the HID timeout, as well as a patched IOSurface.kext that seems to be required to load the nVidia Tesla kexts.
Now for the bad news. Overall, the system is still quite unstable, absolutely not usable as a daily driver yet. For one, most of my rewritten functions are just stubs. So, things likeScreen Time(edit: actually seems to be working!) and automatic light/dark switching, which require functions in the new SkyLight? Not working at all. Not sure if they ever will. There is a bit of other weirdness too, like the way that windows can be extended over the Dock -- my stub SLSGetDockRectWithOrientation currently does nothing. And sometimes, stuff just... crashes, and I don't know why yet.
Anyways, have fun! I'm heading to bed, but I hope some of you guys can try this out. I'm definitely struggling a little here, so hopefully some smarter people can help meSpeaking of which, @pkouame, how are your efforts going? If we can get this working without the SkyLight replacement altogether,
I will have wasted a massive amount of timewe will be much more likely to get a usable end product.
Goodnight
I see that some are testing and verified acceleration. Excellent.
I'm not exactly sure what your approach was but if it involves refactoring old(er) frameworks (in essence retro-patching) and "filling in the blanks" to keep the newer frameworks happy -> the crashes are not surprising at all. Your technique may have to involve doing the same to even more frameworks (as you noticed when you patched 5 of them). That may be unavoidable to get more stability. Using your approach, a simple CoreDisplay "magic bullet" is not possible at all, so you definitely did not waste your time.
As I mentioned before, in Catalina the new Display functionality required a lot of re-architecting on Apple's part. To support the new features (like SideCar) - even new inter-framework/process messages as exhibited by the "new" AppKit and CoreDisplay XPCs. They also retired some critical Mojave GL related functionality ( check the CGXGL... _DEAD symbols in Catalina SkyLight). I know this by static analyzing a lot of the newer frameworks over the past few days.
My track is different and it hinges on starting with and patching the newest frameworks to 1) preserve the essence of Catalina 2) port over what proved to work on Mojave but has been effectively retired (not just deprecated) by Apple. It may be a pipe dream...totally unrealistic and time-consuming
So keep tuning what you have to reduce the crashes. Keep in mind that it may have to involve many other frameworks - no way around that. Again great effort...More power to you.
First of all, Thank you and everyone else who has been working hard to keeping all of our machines updated.
I would like to make a suggestion for the new patcher. As a few other people have requested, it would be great if the could somehow integrate the continuity activation tool into your patcher.
hey guys, off topic but,, can we change the video card support on the tread starter
@ASentientBot, @jackluke, @pkouame PrefPowerService and universalaccessd are permanently crashing (use filter "ReportCrash" in Console to check)
I noticed this too. I think it's because of my stub functions that do nothing, haha. I will try to fix these soon.
PrefPowerService I did noticed some instances during experiments but apparently sleep function and other related to "power settings" work with the @ASentientBot Catalina patches, about the other universalaccessd , I hope it won't affect the new Catalina exclusive accessibility feature that is "Voice control" to use Mac with voice only, not tested yet and not sure if it's already available.
Perhaps it's available: System Pref - Accessibility - Dictation - Enable Voice Control
it's downloading lets check.
Installing.
It does work!
And it seems also available offline after downloaded, as offline dictation.
This is a "show grid" example, but I guess this is a great feature apple added for universal access, if I don't get wrong a similar function was already available in Leopard/SnowLeopard.
Attachments
Last edited:
Unfortunately I can't seem to get this working. I have all 10.14.5 graphics patches (except CoreDisplay is from your patch) and I have the SkyLight patch. Any ideas?Hiiiii! Sorry for being so quiet since my post yesterday. I've been busy. I've significantly improved the SkyLight/CoreDisplay patches to a point where I feel they're ready to be tested/improved upon by you guys!
As of yesterday, I had binary patched about 5 different files (including AppKit, yikes) in order to just barely get the system running. Today, I undid that and implemented wrapper binaries for the old frameworks, with stub functions to (mostly) keep things happy -- a much cleaner solution. I just finished doing a full reinstall to re-check everything, and I'm writing this from accelerated Catalina on my 2010 MacBook!
So... on a system with a working framebuffer (which should be achievable by following the same steps as for 10.14.5), you should be able to just replace these two frameworks with the attached copies. No other binary patches needed!!
For convenience I'm also including the fix for the HID timeout, as well as a patched IOSurface.kext that seems to be required to load the nVidia Tesla kexts.
Now for the bad news. Overall, the system is still quite unstable, absolutely not usable as a daily driver yet. For one, most of my rewritten functions are just stubs. So, things likeScreen Time(edit: actually seems to be working!) and automatic light/dark switching, which require functions in the new SkyLight? Not working at all. Not sure if they ever will. There is a bit of other weirdness too, like the way that windows can be extended over the Dock -- my stub SLSGetDockRectWithOrientation currently does nothing. And sometimes, stuff just... crashes, and I don't know why yet.
Anyways, have fun! I'm heading to bed, but I hope some of you guys can try this out. I'm definitely struggling a little here, so hopefully some smarter people can help meI will have wasted a massive amount of timewe will be much more likely to get a usable end product.
Goodnight
Do you have loaded framebuffer/GeForceTesla kexts?
Yes, I should.
Edit: Verified framebuffer is working and NVDA50HAL loads during verbose boot. Brightness is also working with jackluke's GPUWangler patch. Everything boots and works fine but still no accel.
Edit 2: Same model as you btw. As written in signature.
Last edited:
When trying to update the caches and having problems with prelinked kernel, I can across this"
It appears /AppleInternal/Library/Extensions is used for development, according to the -z flag
-no-authentication (-z): don't authenticate kexts (for use during development)
Might be worth a try putting unsigned kexts or problematic kexts there and see if it builds the prelinked kernel. Just a wild guess.
Code:
Mac-Pro / % sudo kextcache -u / -z -r -caches-only
Warning: /AppleInternal/Library/Extensions: No such file or directoryIt appears /AppleInternal/Library/Extensions is used for development, according to the -z flag
-no-authentication (-z): don't authenticate kexts (for use during development)
Might be worth a try putting unsigned kexts or problematic kexts there and see if it builds the prelinked kernel. Just a wild guess.
/usr/standalone/bootcaches.plist lists the folders for extensions as: /System/Library/Extensions, /Library/Extensions, /AppleInternal/Library/Extensions, /Library/Apple/System/Library/Extensions
I am pretty sure that those folders are all treated equally, though. Putting into the AppleInternal one shouldn't do much differently from putting them anywhere else.
An interesting idea might be to add a folder to the front of that list (assuming that they are linked in the order listed) which would allow overriding system kexts like AppleHDA without deleting them (kind of like Clover does?).
Edit: As for /AppleInternal folder itself, it's just as the name states. I've only come across a few things that install there -- some internal iPhone restore tools, Apple Service Toolkit, etc. Nothing that's really supposed to be publicly available, as far as I know.
Try this, even if the GPUWrangler.framework worked on macbook7,1 is mainly addressed for DualGPUs machines and should be linked to an AGC kext set same version.
So try use the GPUWrangler.framework from Catalina, and be sure of replacing these:
OpenGL.framework (Mojave 10.14.3) this framework if untouched has a typical date of 20 February 2019
GPUSupport.framework (PrivateFramework Mojave 10.14.3) same date 20 February 2019
CoreDisplay and Skylight Privateframeworks the @ASentientBot Catalina patches
Even if OpenCL.framework replaced worked, just use the OpenCL.framework from Catalina.
All the Catalina frameworks and binaries if untouched have a date 31 May 2019.
That's all.
Hiiiii! Sorry for being so quiet since my post yesterday. I've been busy. I've significantly improved the SkyLight/CoreDisplay patches to a point where I feel they're ready to be tested/improved upon by you guys!
As of yesterday, I had binary patched about 5 different files (including AppKit, yikes) in order to just barely get the system running. Today, I undid that and implemented wrapper binaries for the old frameworks, with stub functions to (mostly) keep things happy -- a much cleaner solution. I just finished doing a full reinstall to re-check everything, and I'm writing this from accelerated Catalina on my 2010 MacBook!
So... on a system with a working framebuffer (which should be achievable by following the same steps as for 10.14.5), you should be able to just replace these two frameworks with the attached copies. No other binary patches needed!!
For convenience I'm also including the fix for the HID timeout, as well as a patched IOSurface.kext that seems to be required to load the nVidia Tesla kexts.
Now for the bad news. Overall, the system is still quite unstable, absolutely not usable as a daily driver yet. For one, most of my rewritten functions are just stubs. So, things likeScreen Time(edit: actually seems to be working!) and automatic light/dark switching, which require functions in the new SkyLight? Not working at all. Not sure if they ever will. There is a bit of other weirdness too, like the way that windows can be extended over the Dock -- my stub SLSGetDockRectWithOrientation currently does nothing. And sometimes, stuff just... crashes, and I don't know why yet.
Anyways, have fun! I'm heading to bed, but I hope some of you guys can try this out. I'm definitely struggling a little here, so hopefully some smarter people can help meI will have wasted a massive amount of timewe will be much more likely to get a usable end product.
Goodnight
Hi @ASentientBot thanks for sharing again great infos
What files I need exactly with the file you have post to setup my GT 210 on Catalina 10.15
What files I need exactly with the file you have post to setup my Intel HD 3000 on Catalina 10.15
I have made a test but failed because I am not really sure
thanks for the work
Did I miss something here? is it possible to install on a Hackintosh MacBook Pro 5.2 Catalina?
if so, how should I proceed?
if so, how should I proceed?
I haven't misread, it appears that some significant degree of graphics acceleration has been achieved on non-Metal GPUs in Catalina. I wonder if such an achievement, which can perhaps be improved upon in the near future, can possibly be retrofitted to Mojave on Macs that don't have a Metal GPU, such as a 2011 iMac (not my computer, but one of my son's).