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
You're right. I should be more optimistic about it after watching the break throughs on this fourm!
These frameworks:
/S/L/Frameworks/CoreDisplay.framework
and
/S/L/PrivateFrameworks/SkyLight.framework
must be (mandatory) replaced or from a Recovery Terminal or from single user mode (CMD+S after power-on) or from another macOS installation (bootable partition) but higher than Sierra to support the Catalina APFS container read/write from external.
If you replace them directly from Catalina Finder they will corrupt at 100%.
That's why you can't reach more the loginUI (OSX GUI Mode).
Even if I do this it doesn't work for my HD 3000 (put the frameworks using Mojave 10.14.5 to the Catalina partition)
You replaced correctly the frameworks but for non-metal acceleration, I guess you need these other two kext for IntelHD series from your Mojave 10.14.5 (patched) installation to be put in your Catalina /S/L/E/:
IOAccelerator2D.plugin
IOAcceleratorFamily2.kext
in addition to these that I suppose you already put in your Catalina SLE:
AppleIntelHD3000Graphics.kext
AppleIntelHD3000GraphicsGA.kext
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext
AppleIntelSNBVA.bundle
But the kext must be installed properly it's not only a copy/paste, after copy/paste you need to chown/chmod the kext permissions otherwise they fail to load and in some cases they will produce a KernelPanic.
[doublepost=1560599858][/doublepost]@Rastafabi watch : here
That is a MacBookPro early 2011 13", your method "Catalina loader" has worked also there, so apparently the EFI/SMC or is automatically avoided from Catalina Installer or simply the EFI/SMC package does fail during checksum/EEPROM writing ("the big apple logo with big loading bar" phase) and so it's refused to be upgraded by the machine.
I mean seems your method is working also for other different machines.
Last edited:
Thank you, this helps me alot I was really wondering what kexts I needed and what I didn't so I copied too much over probably... Also didn't know Skylight went into private frameworks xD
Catalina DP1 don't have any BootROM or SMC upgrades at all.
Catalina DP1:
10.14.6 DP2 where all Macs got BootROM updates except MP5,1:
Ah right! That's why many here with "Catalina loader" have escaped from EFI/SMC pkg updates.
But in the root of "Catalina's InstallESD.dmg" I guess there are the *firmware*.pkg updates for 10.14.6 beta 1 , so a bit of risk is lying in wait.
I mean if EFI/SMC update for a spoofed iMac is issued to a MacBookPro, after, there is risk of unstable machine or bricked.
However many here that used "Catalina loader" have encountered at half install the "big apple and big loading bar", then this scenario has failed/interrupted (or powered off the machine), hence they were able to power-on it again and resume the stage2 Catalina installation.
Last edited:
Hello again, so I did what you told me @jackluke , on my mbp it now does a bootloop, but on the iMac I now have my Cinema display detected and the internal one properly, I put the right kexts, but even with the 2 IOAccelerator, still no metal support. (I take photos with my iPhone because i don’t have wifi support on Catalina)
Attachments
For the bootloop machine try this (don't worry is fixable), boot in Catalina single user mode (CMD+S after power-on):
mount -uw /
chown -R 0:0 /System/Library/Extensions/
chmod -R 755 /System/Library/Extensions/
exit
You have to be sure that the IOAccelerator*.kext and IntelHD3000*.kext are taken from the same patched Mojave installation.
But you may try use also the two IOAccelerator*.kext from HighSierra, I am using those from HS and they brought me back acceleration on IntelHD Arrandale (different from IntelHD3000 but similar).
For the non-metal ATI iMac, this was a Mojave patch from dosdude1 that I guess is making also another newer for Catalina, so for now there not yet acceleration.
Last edited:
Where do I get AppleIntelHD3000GraphicsGA.kext, it's not in my Mojave patched version...
AppleIntelHD3000GraphicsGA.plugin
Probably my mistake in typing.
I used similar naming for AppleIntelHDGraphics (Arrandale).
Sometimes I consider plugins and bundles as kext, that's why.
[doublepost=1560609487][/doublepost]@PixelmonGalaxy and @mocteo for Wifi you could use IO80211Family.kext from HighSierra or Mojave, this should enable again the wifi on yours Catalina machine, but when install or overwrite a kext do it carefully, otherwise a wrong way installed kext may produce bootloop or kernelpanic, however fixable in some way.
For those fortunate enough to have a (unsupported) pro with a metal card, I can confirm that Xcode 11 beta on Catalina runs with all the new bells and whistles.
Screenshot from Mac Pro 3,1 + GTX680:
Screenshot from Mac Pro 3,1 + GTX680:
Little by little they are metal-izing everything.
Ok, I think I am not doing something right... It booted as it should but nothing is different can you give me information on where to place and how to run "kextcache" properly and if there is any other permission related things I need to know.
These are directories I get errors for so I am guessing (although the errors might not matter) somewhere in these I place the kexts?
Warning: /Volumes/macOS Catalina/Library/Extensions: No such file or directory
Warning: /Volumes/macOS Catalina/AppleInternal/Library/Extensions: No such file or directory
Warning: /Volumes/macOS Catalina/Library/Apple/System/Library/Extensions: No such file or directory
Currently I have the kexts and bundles in /S*/L*/E*
You have to place them here /Volumes/macOS Catalina/System/Library/Extensions/
Then from a booted Catalina open Terminal and type (copy/paste one line at once) this:
sudo chown -R 0:0 /System/Library/Extensions/
sudo chmod -R 755 /System/Library/Extensions/
sudo kextcache -i /
reboot and should achieve something.
Otherwise as alternative:
If you can't boot to Catalina after replacing kext then boot holding CMD+S after power-on and type from Shell:
mount -uw /
chown -R 0:0 /System/Library/Extensions/
chmod -R 755 /System/Library/Extensions/
exit
You bet (and unfortunately for us) - just check out all the CoreImage metal-sized support in Catalina.
It did achieve something xD
A kernel panic loop, it did boot tho so I did the frameworks correctly as that did boot.
yea, but i found where it uses metal, my question is can there be a workaround
- Semantic highlighting, code completion, live issues, symbol search, and jump-to-definition are now supported for the Metal shading language. (45144204)
and @mocteo almost surely haven't replaced or installed them properly, anyway can you boot in single user mode holding CMD+S after power-on?
If so, then try this from single user mode Shell:
mount -uw /
cd /System/Library/PrelinkedKernels/
cp immutablekernel prelinkedkernel
reboot
That should allow reach again the OSX GUI Mode.
In few words you have to re-use the immutablekernel as a prelinkedkernel I guess apple put it there for this reason, to recover it.
However it's weird, I have interchanged IOAccelerator*.* from HighSierra to Mojave and got no kernel panic or bootloop in any machine. Currently I am using 10.13.6 ones for almost everything.
But wait a second, have you replaced also IOSurface.kext patched from @ASentientBot ?
This is another important Catalina fix needed for Video Framebuffer and OpenGL/non-metal acceleration.
I bet 99% that's why you are getting Catalina kernel panic or bootloop.
Hence try use the file attached.
Last edited:
Do I need, to boot catalina, to just replace the kexts you mention and boot normally or I have to use the patch to install catalina? At this point and replacing the files you mention, it is necessary to use the patch to boot the OS, right?
I mean the @Rastafabi patch... I have a mbp 13" late 2011 with Intel HD 3000
Not strictly necessary, Catalina can boot stock from 2010-2011 machines with only nvram set as "-no_compat_check".
Instead to get audio, wifi:
For audio AppleHDA.kext from HighSierra, Wifi IO80211Family.kext from HighSierra or Mojave.
For gpu framebuffer/acceleration you need all the @ASentientBot Catalina patches: CoreDisplay.framework, SkyLight.framework (PrivateFramework), IOSurface.kext and IOHIDFamily.kext
In addition @dosdude1 non-metal fixes: .3 Mojave OpenGL.framework and GPUSupport.framework (Privateframework)
Then: IOGraphicsFamily.kext, IONDRVSupport.kext, IOAccelerator2D.plugin, IOAcceleratorFamily2.kext all from HighSierra
And last: your GPU kext from HighSierra.
Last edited:
That quote from the release notes actually has to do with better support (semantic highlighting) for the Metal Shading Language itself ( it is like a C++ compiler for metal code - pretty neat) It doesn't necessarily indicate the underlying metal gpu requirement (which was discovered above) Apple is being its usual opaque self...
Another interesting Release Note quote is the Simulator one:
"...When running on earlier versions of macOS or in an environment where Metal is not available, simulators continue to use software rendered OpenGL. If your Mac has multiple GPUs, use the File menu in Simulator to select which GPU to use. If the GPU in use becomes unavailable, any simulators using it automatically shut down. (18430676) "
If I read that correctly, key Xcode tools like the iOS and iPadOS simulators should run under OpenGL (software rendered). Why the nice minimap (a new Xcode 11 feature) now requires Metal is beyond me. If a sophisticated simulator can run under GL - the minimal should also. Maybe a legitimate bug we can file for a possible fix in a later beta...
This seems to be one of the few times Apple is actually explaining why the GL frameworks are still available and have been tweaked since the "official deprecation notices"...