Just tweaked my OSInstall and its installing ontop of my mbp 5,2 10.14.5. Did you try applying post-install or are you taking another route?
What all did you have to modify in order to get the installer to boot?
Just tweaked my OSInstall and its installing ontop of my mbp 5,2 10.14.5. Did you try applying post-install or are you taking another route?
that's not the point. The point is that we already have extensive patching and documentation on running 10.12-10.14 on macbooks as old as the *late* 2008 5,1 with GeForce 9400M. The GMA GPU's are a nightmare and have nothing to build off of when it comes to OpenGL support in Metal-macOS. It'd require a massive amount of work to effectively restart on this macbook because of it's GPU. The best move if OP is looking for a development device is to sell this one for a full 5,2 or grab a 2009 5,2 board to put in his 4,1 case at a discount.
EDIT: and there was an error in my previous post, I have yet to see a successful install of anything past 10.11 on the 4,1, and 10.13 has zero documented support patched or otherwise.
What did you use to do that? just stock patcher?I've got 10.14.5 installed and running on my 4,1. It runs no better or worse than 10.11.6.
Just the standard InstallESD->OSInstall.mpkg->Distribution overrides (InstallationCheck and InstallsOS) will enable the installer.What all did you have to modify in order to get the installer to boot?
Just the standard InstallESD->OSInstall.mpkg->Distribution overrides (InstallationCheck and InstallsOS) will enable the installer.
But I'm getting errors so there may be more to it...
Hey Collin are you doing getting Catalina for the unsupported MacBook ?I had intended to make this thread once the OS name was officially announced. Now that it's been done earlier than I intended, please change the title accordingly.
Not there yet. Stuck on "The Installation Failed" panel from a patched OSInstall. After about an hour (sigh). The error seems familiar but I don't remember which step I missed. Any clues?Anybody figure out the HID timeout during boot? I can't get to the desktop yet. Going to try some IOUSB* replacements...
I guess not this time. My goal is to get it running as soon as I can and I could certainly use the help of people more or even less experienced than me. And thanks to @dosdude1 and @Larsvonhier, I now have my own MacBook4,1 to use for testing unsupported macOS on. As I'm currently the only developer who is developing a patcher tool that supports the MacBook4,1, this is very useful for me. Thanks a lot to both of them.
What did you use to do that? just stock patcher?
Rebuilding the prelinkedkernel from Mojave isn't possible. It needs to be the same major version. So only Catalina can rebuild Catalina prelinkedkernels.I'm still not sure how you guys -- @swamprock and @jackluke -- have gotten this working. I got a copy of the OS installed, but it always hangs on this IOHIDFamily timeout if I try to boot without safe mode (-x). Replacing that kext gets me to the desktop, but I can't move the mouse (because a ton of USB/HID kexts fail to link).
But now, the super weird part: I discovered that, booting in single-user mode, I can consistently avoid this hang. Is it the typing at that prompt? Something different in the way it loads drivers? Something behaving differently in single-user mode? (There are several checks for that in IOHIDFamily for single-user mode, but even if I patch them as true, it does not work any better.)
Also, I've been unable to kextcache -i / from the root prompt on Catalina -- it just spits out a "security framework error", whatever that is. I've been forced to rebuild from Mojave with -prelinked-kernel -kernel /Volumes/Catalina...Kernel /Volumes/Catalina...Extensions. Anybody have some insight on that?
I've also noticed phrases about validating image4 files (which I thought was just an iOS thing) and some sort of kext whitelist that gets regenerated at boot? We are dealing with weird stuff.
I've got to sleep. Good luck everyone!
I don't think so. If you specify a -kernel argument, you can link with Catalina's kernel.Rebuilding the prelinkedkernel from Mojave isn't possible. It needs to be the same major version. So only Catalina can rebuild Catalina prelinkedkernels.
Huh, I didn't know about that option. That's actually quite useful. I'll use that in future. That should mean that we don't need a supported mac for anything then!I don't think so. If you specify a -kernel argument, you can link with Catalina's kernel.
I haven't even installed it yet cause I had to sleep. But I'm currently doing so. Then I'll modify macOS Patcher version checks and some paths for the "read-only" stuff and then try that on my 7,1.My desire to get this working got the better of my desire to sleep
Where are you guys at? Were you even getting this IOHIDLib issue or is this just a "me" problem?
In any case, I patched it.
I got it fully booting and working on a 2011 MacBookPro8,3. Attempting to get graphics acceleration working, however, is a different story.My desire to get this working got the better of my desire to sleep
Where are you guys at? Were you even getting this IOHIDLib issue or is this just a "me" problem?
In any case, I patched it.
Great work. More details please! What files are you currently replacing? Did you run into this HID issue at all? If so, what'd you do about it?I got it fully booting and working on a 2011 MacBookPro8,3. Attempting to get graphics acceleration working, however, is a different story.
They replaced bash with zsh?Great work. More details please! What files are you currently replacing? Did you run into this HID issue at all? If so, what'd you do about it?
I've just gotten that fixed (assembler patch in IOHIDFamily.kext) and wifi (IO80211Family.kext) working so far (MacBook7,1). Would love to hear what you're doing to prevent doing the same stuff twice
Edit: oh, and also deleting the telemetry plugin is required as always.
Edit 2: also, what is up with replacing bash with zsh?
Just for a user's default shell.probably new at the kernel level
could you replace AppKit and CoreDisplay from 10.14.6 beta 1Just for a user's default shell.
[doublepost=1559627501][/doublepost]Also -- we can't be replacing CoreDisplay anymore. It prevents AppKit from loading, which is, well, quite bad.