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.
PeterHolbrook said:
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).
Click to expand...

course, there is already a thread about that....
 
  • Like
Reactions: PeterHolbrook and TimothyR734
0403979 said:
That warning means nothing. It's completely normal.
Click to expand...
I wasn’t pointing out the warning.

I was pointing out there is an Apple Internal Kext test bed under that directory if you make create it. and they do seem to load from there.

It was showing me the path in the warning message. You can put kext’s in there and its not supposed to authentic them. Dunno how useful it is but it’s another place to test kext’s.
 
  • Like
Reactions: applCore, TimothyR734, Appleak and 1 other person
jackluke said:
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.
Click to expand...
I thought of that but I had yet to try it. After reverting GPUWrangler to stock, acceleration works with no issues. Thanks for you insight.
 
  • Like
Reactions: webg3, TimothyR734 and jackluke
ASentientBot said:
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!! :D

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 like Screen 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 me ;) Speaking 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 time we will be much more likely to get a usable end product.

Goodnight :)
Click to expand...
I am honestly amazed at your determination and skill. This kind of announcement should never have happened. But here you are and you delivered on something thought impossible by many. Congratulations. Between this thread and the Mojave one, you have contributed the most individually and I must say, your contributions are amazing and extremely valuable. I am very fond of your great achievements and respect for everyone on this thread. In my opinion, you have helped the most in getting the vast majority of our devices working. Thank you a lot for your incredible research. You are a valuable asset to this community and we're lucky to have you.

Thanks to you, I was able to capture a screenshot I once thought was impossible. Nine days after the release of the first developer beta of macOS Catalina, the OS is working with no issues whatsoever on an almost nine year old computer. The humble MacBook7,1. Bravo.

Screenshot 2019-06-12 at 18.04.15.png
[doublepost=1560359942][/doublepost]macOS Patcher 3 beta 1 will be released with full support for macOS Catalina and all versions before it dating back to Sierra. This beta will be released as soon as I can get my hands on and implement @dosdude1's installer patch. Big thanks to @ASentientBot for his amazing work on macOS Catalina graphics acceleration.

Note for macOS Patcher 3 and future versions: Starting with macOS Patcher 3, transutil will no longer be included with macOS Patcher. It will be available separately and will support all patchers for Mojave and Catalina. Another utility by the name of apfsutil be made available shortly for switching between APFS volumes for users of the APFS system patch. This utility will support macOS Patcher and support status for other patchers will be announced later. And finally, I will soon start to develop a new utility specifically for macOS Patcher, called, macOS Patcher Subsystem. This utility will also be available separately but for macOS Patcher only. macOS Patcher Subsystem (MPS), will have the ability to detect system updates, system patches that have been overwritten, and will offer updates to patches and to MPS itself. It will also allow the reinstallation of patches (including macOS Patcher Subsystem itself), without the need of the macOS installer drive.

These utilities will not be preinstalled as the aim of macOS Patcher is to give more freedom to the user by expanding their choice of operating systems. And including utilities that a user may not need or want is contradicting that. These utilities will all be open source as is macOS Patcher and will have their own GitHub page and download zips. Install scripts will be available for these utilities and they will be installed with the intent to be easily removable by the user. This can be done either manually or via an uninstall script that will also be there for download.

macOS Patcher 3 will not remove the current utilities by default, instead this will be done via an optional upgrade script that will be released along with macOS Patcher 3. I will also be releasing restore scripts individually for all past versions of macOS Patcher since macOS Patcher 1.0 to allow users to remove patcher files for their specific version of macOS Patcher. These restore scripts will also include the latest improvements in the visual design and code structure of my scripts. Users of the Users of macOS Patcher 1 are encouraged to download the restore script for their version of macOS Patcher, when it is released, and follow the instructions on the RMC website for restoring before they use a newer version of macOS Patcher.

I hope these changes will be beneficial to everyone and I'm excited to provide support for Catalina shortly and make my patcher and its utilities more open and to give more choice to the user about the software they install on their machine.
 
  • Like
Reactions: AndreeOnline, nandor690, startergo and 19 others
roddy20 said:
this one works perfectly
no errors, no questions, installed exactly the same way as original macOS does :)
Thanks again
Click to expand...

That is the method of @ASentientBot so thankfulness to him!

Anyway the other method essentially was very similar, conceptually you have had already expanded the "dmg" content, while with "createinstallmedia" they are kept as "dmg" and mounted during RAMdisk phases for the OSX Installer.

I thought with the method you used was needed a manual adjustment of the Preboot UUID.
 
  • Like
Reactions: Starplayr, roddy20, TimothyR734 and 3 others
ASentientBot said:
/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.
Click to expand...
I tried finding your HiD single user stall patched Kext but could not find it. Can you attach it’s post? Thanks!
[doublepost=1560364335][/doublepost]I don’t have sound yet with AplleHDA installed I am trying some Audio kext’s from Mojave. uSB Audio is find btw
 
  • Like
Reactions: TimothyR734
jackluke said:
That is the method of @ASentientBot so thankfulness to him!

Anyway the other method essentially was very similar, conceptually you have had already expanded the "dmg" content, while with "createinstallmedia" they are kept as "dmg" and mounted during RAMdisk phases for the OSX Installer.

I thought with the method you used was needed a manual adjustment of the Preboot UUID.
Click to expand...

Yes, thanks to @ASentientBot too

I understand. But the second method works, the first one does not, maybe we forgotten some very important file (?)
 
  • Like
Reactions: Starplayr, jackluke and TimothyR734
jackluke said:
That is the method of @ASentientBot so thankfulness to him!

Anyway the other method essentially was very similar, conceptually you have had already expanded the "dmg" content, while with "createinstallmedia" they are kept as "dmg" and mounted during RAMdisk phases for the OSX Installer.

I thought with the method you used was needed a manual adjustment of the Preboot UUID.
Click to expand...


From the recent WWDC, there was an interesting presentation on how filesystems are changing on Catalina that worth taking a look. Video and PDFs are here https://developer.apple.com/videos/play/wwdc2019/710/

After looking through it, it appears that the root volume will be set to read-only in future releases so that may affect how we are able to patch things.
 
  • Like
Reactions: estape11, Starplayr, ASentientBot and 2 others
dlfgma said:
From the recent WWDC, there was an interesting presentation on how filesystems are changing on Catalina that worth taking a look. Video and PDFs are here https://developer.apple.com/videos/play/wwdc2019/710/

After looking through it, it appears that the root volume will be set to read-only in future releases so that may affect how we are able to patch things.
Click to expand...
It will only be read-only when booted. And it can be mounted as read-write anyway. Yes, I watched that session.
 
  • Like
Reactions: Alex-Microsmeta and TimothyR734
roddy20 said:
Yes, thanks to @ASentientBot too

I understand. But the second method works, the first one does not, maybe we forgotten some very important file (?)
Click to expand...

You're right, restoring and booting only the Catalina BaseSystem.dmg does work and the Installer/Recoveries apps are showed, but when copy some custom Packages then at next reboot it will show "The installer resources were not found", however if you click on the invisible "upper part" it unveils the Finder top menu, from where you can find and use the Terminal, DiskUtility, but you can't install Catalina since throws that message.

So should be something else the issue.
 
  • Like
Reactions: roddy20, Starplayr and TimothyR734
0403979 said:
I

Thanks to you, I was able to capture a screenshot I once thought was impossible. Nine days after the release of the first developer beta of macOS Catalina, the OS is working with no issues whatsoever on an almost nine year old computer. The humble MacBook7,1. Bravo.

[[doublepost=1560359942][/doublepost]macOS Patcher 3 beta 1 will be released with full support for macOS Catalina and all versions before it dating back to Sierra. This beta will be released as soon as I can get my hands on and implement @dosdude1's installer patch. Big thanks to @ASentientBot for his amazing work on macOS Catalina graphics acceleration.
Click to expand...

I beleived you guys and you proved you are code magicians :) Thanks a lot. looking forward.
 
  • Like
Reactions: TimothyR734
hey guys, I'm trying to run the server manager application for my Xserve running server 10.5

I want to run it on here, how do I run an app from that long ago(it says it requires a OS from 10.6)
 
QUOTE="freqrider, post: 27455738, member: 1165754"]Just don’t forget us 3,1 guys mkay? ;)[/QUOTE]

I have everything working on MP3,1 except for the HD Audio.

I tried IOAudioFamily.kext but it seems to keep load Cat's one, probably from the Prelinked kernel. Have not tried Prelinking the kernel from outside the OS.

USB Audio is fine.
jowaju said:
Figured out a reproduce-able method for creating an image of Catalina dual mode APFS containers to make it easier to move installations quickly. If this guide isn't clear enough let me know and I'll clean it up :

Used Clonezilla Live newest version – filename was clonezilla-live-20190420-disco-amd64.iso. Copied to bootable USB with Etcher / Rufus (make sure it’s GPT partitioned).


1. Clonezilla Live 1024*768, press Enter

2. Start CloneZilla, press Enter

3. Device-image, press Enter

4. Local_dev, press Enter

5. Insert USB to save image to (must be HFS or Xfat, cannot be APFS) wait 5 seconds, press enter

6. If your USB shows on the list, press Ctrl + C to go to the next step

7. Choose your USB drive and partition to save the image to and then press Enter

8. If your drive is HFS, you will get a warning, press Y to continue

9. Choose the folder on the drive to save the image to and press Enter

10. Arrow down to saveparts, then press Enter

11. Choose a new name for the image file or press enter to keep the defaults

12. Choose the source partition (your APFS container that is currently working)

13. Press Enter to choose default priority mode for cloning

14. Press Enter to choose Default Advanced Parameters

15. Arrow down to –Z0 for No Compression and press Enter

16. Add 10 zeros to make sure the file is not split during cloning, then press Enter

17. Press Enter to Skip Source File System Checking

18. Arrow down once to Skip checking the saved image then press Enter

19. Press Enter to not encrypt the image

20. Press Enter to choose shutdown options after cloning

21. You will get a warning about Volume size limit and list of the exact command to run, press Enter

22. Confirm the image information and press Y to continue

23. The Cloning Process will begin, this step took exactly 5 minutes on my machine

24. After cloning a summary will be displayed, press Enter

25. Arrow down to reboot, press Enter

26. Hold the Left Alt key down while rebooting and choose a working Catalina boot device

27. Once booted, find the image file folder you specified in Clonezilla

28. Sort by File Size, the biggest file in the folder should end with img.uncomp.aa

29. Rename the file by removing the uncomp.aa and changing it to .img

30. Now double clicking on the .img file will open it as a usable image in Disk Utility

31. You can now restore to any size drive natively using Disk Utility, all the way down to the size of the used space in the 2 APFS containers that show up, mine was ~ 14.7GB so it fits perfectly on a 16GB USB drive.

32. If you run through the process once more after restoring to a smaller drive you will have a permanent copy shrunk to ~14.7GB

33. When you use Disk Utility to restore the APFS container, it will put both images back correctly and re-enumerate the UUID correctly

34. Confirmed clone ability to External USB drives (multiple) as well as to Internal SSD / Hard drive on any Mac that will boot the Catalina Recovery drive.


Caveats – I had to disable SIP to make all this work, everything worked fine and a reset the PRAM to remove the Verbose boot which turned SIP back on and I had TONS of issues. Turning it back off fixed them instantly.


Also the only Disk Utility that seems to handle Catalina APFS containers is the Catalina version itself. High Sierra did NOT work. I have not tried Mojave yet but plan to test it ASAP.
Click to expand...

That’s a lot of work. You can use diskutil and dd and do this in three lines of code. Both are command line utilities and can be run from an MacOS Installer disk, another system install, or a restore disk. You can also make disk images with dd.

While I value what you did, your volume of steps is a barrier to entry.
 
  • Like
Reactions: webg3, freqrider, ASentientBot and 2 others
Hoping to god this works on my Late 2009 MacBook, MacBook 6,1. If it works fine with Mid 2010 MacBook, 7,1, Hopefully it can work with the first Unibody model that I’ve had since 2009.

I’ve been using @dosdude1 ’s Mojave patcher for my Late 2009, does this mean he will be releasing his version of the Catalina patcher ?
 
  • Like
Reactions: webg3 and TimothyR734
Can some post the HID kext that fixes the Busy Timeout 60 seconds. It runs three times on my system and would like to nix it. Thx!
 
  • Like
Reactions: TimothyR734
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