Probably also need rolling back CoreGraphics binary from 10.14.3 as well?
Code:
/System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
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.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Probably also need rolling back CoreGraphics binary from 10.14.3 as well?
Wait a sec, your APFS Recovery's com.apple.Boot.plist is wrong, root.dmg doesn't exist and "-no_compat_check" must be inserted only after BaseSystem.dmg:
replace
root.dmg -no_compat_check=file:///
with
root-dmg=file:///
and CMD+R should give some response now.
Everything works after using your steps AND booting Recovery FROM REFIND. It’s only when I boot it with CMD + R that I need an NVRAM variable and the kernel cache doesn’t work.
[doublepost=1548777424][/doublepost]
I’ve since fixed this issue. It was an issue with the script. My newer post was made after this fix.
No, and it might be an advantage of Teleport tool instead of sharing screens. Much lower bitrates needed for that alternative.
Anybody get 10.14.4 DP1 working yet?
I installed it on my MacBook7,1 but couldn't get to the desktop. It'd just show the Apple logo for a second and then go back to the console, and repeat that forever. A dmesg log confirmed that it's WindowServer crashing (error message of "too many corpses being created").
I could only solve that by disabling the OpenGL driver. After that it works fine, but no acceleration of course.
I don't have time to test more now, but I'm worried that Apple's somehow broken the OpenGL fallback mode. Any ideas? (Replacing the WindowServer/SkyLight has never worked for me, it's too version dependent.)
I installed it on my MacBook7,1 but couldn't get to the desktop. It'd just show the Apple logo for a second and then go back to the console, and repeat that forever. A dmesg log confirmed that it's WindowServer crashing (error message of "too many corpses being created").
I could only solve that by disabling the OpenGL driver. After that it works fine, but no acceleration of course.
I don't have time to test more now, but I'm worried that Apple's somehow broken the OpenGL fallback mode. Any ideas? (Replacing the WindowServer/SkyLight has never worked for me, it's too version dependent.)
I have the same problem on the MacBook Pro 7,1 and a MacMini 3,1. I am hoping @dosdude1 has a fix working.
Can you tell me the steps to disable the OpenGL driver please? Thanks.
I assume this is a reference to using the legacy video patches on non-Metal video cards, no? If so, you will be left with non-accelerated video on such hardware. Glad I upgraded my MacPro 3,1 to a Metal compatible GTX-680.
Is this using untouched System's Frameworks (vanilla)? Interesting! If so, I guess something was really wrong with this Beta (which actually is aimed for dev & tester #LoL) that caused dependency problem.
Yeah, sure.. CoreDisplay, IOAccelerator* are not loaded on VESA mode (or disabled nvAccelerator: if "sudo nvram nv_disable=1" with Nvidia gfx being used). SafeMode on Nvidia is still using CoreImaging (CI / Draw), NVDA~HAL*.kext is still loaded so, this still loads CoreDisplay (IOAccelerator && GeForce are for QuartzExtreme / QE / 3D).
OpenGL is still there, at least my NVDA Fermi (that's not Metal-capable) is still alive with full gfx accel. Seems like a bug with WindowServer itself, but these are my inspections when booting 10.14.4 Beta 1 (not sure what will we do with these? #LoL.. you may try replacing only CoreDisplay and DisplayServices from 10.14.3; and keep SkyLight, WindowServer, CoreGraphics vanilla from 10.14.4).
#EDIT: As we could see, WindowServer needs _dyld to be rebuilt so... replacing only is not enough w/o:
sudo update_dyld_shared_cache -force
Last edited:
I may have misunderstood the requirement (disabling OpenGL driver). My unsupported MBAir4,2 has Intel HD 3000 graphics. All I wanted to test is 10.14.4 beta installed on this sandbox device. And I thought doing so can finish the boot without WindowServer crashing as I experienced previously.
Holding down "SHIFT" key once Apple logo appears on StartUp will boot into SafeMode, right?
I have my MacPro 3,1 running Mojave using dosdude's post install APFS patch.
It starts and runs good and the boot time is livable (33sec.), I've just now discoverd what could become a major
problem, I cannot get into single user mode (cmd+S) at startup also no verbose startup.
No matter which keys I press on power on it always goes to the APFS preboot scrolling text screen
Anyone figured out a fix for this.
It starts and runs good and the boot time is livable (33sec.), I've just now discoverd what could become a major
problem, I cannot get into single user mode (cmd+S) at startup also no verbose startup.
No matter which keys I press on power on it always goes to the APFS preboot scrolling text screen
Anyone figured out a fix for this.
Not sure what system you're on, but with nVidia Tesla, just move /S*/L*/E*/GeForceTeslaGLDriver.bundle. But the system will be barely usable. I'd just stick with 10.14.3 for now if I were you.
No modifications to frameworks whatsoever, just the basic patches for the machine.
Good point -- safe mode is a smart way to test without moving files around.
That is fantastic news that it still works on some GPUs at least. I'm still worried that they won't fix the WindowServer since no supported Macs render the UI with OpenGL anymore, but I'm glad they didn't remove the OpenGL fallback altogether. I'll try that! Though I might just wait until the final 10.14.4 release instead of wasting time on betas.
Thanks for the tips!
Hold it down immediately, not after the Apple logo. It's interpreted by the firmware and passed to the kernel at the very beginning of the boot process, I think.
You just have to hold the keys WHILE the APFS boot script is running, then it'll process your key command as soon as the OS starts loading.
Thanks for the quick response.
I tried it and it works just as you say, thanks, now everything is as it should be.
Now I can run my favorite old app, "Applejack" which still works just fine in Mojave, just skip step 2 (Repair Permissions).
I tried it and it works just as you say, thanks, now everything is as it should be.
Now I can run my favorite old app, "Applejack" which still works just fine in Mojave, just skip step 2 (Repair Permissions).
I will just wait for the next beta release (2). Hopefully it can or will bypass the installation glitch on beta 1 for unsupported MBPs and MBAs.
Thank you.
I appreciate everyone looking out for my computer's best interest. I fully understand the consequences of trying to patch the bootrom. So does anyone know how to try and solve the error?
Does anyone know how to take a screenshot or a screen recording in the installer envoirment?
So you understand to enable updates the hard drive has to be formatted in the new hard drive standard format to update via software update
Try replacing /S/L/PrivateFramework/IOAccelerator.framework and or its plugin inside /S/L/E/ with previous Mojave 10.14.3 , it's involved too in graphics acceleration at loginUI and WindowServer.
[doublepost=1548836603][/doublepost]
I know well these kext family when I played with their VRAM, for IntelHD3000 the OpenGL driver is simply this: /System/Library/Extensions/AppleIntelHD3000GraphicsGLDriver.kext
So just rename it to something else (ex. A*.kext2) or move out from its folder or delete directly and an automatic kextcache schedule will occur at your next reboot and as @ASentientBot stated without OpenGL you should be able to pass the LoginWindow with the current 10.14.4 beta.
If for some reason you still can't reach the LoginUI then repeat the same steps even for its Framebuffer: /System/Library/Extensions/AppleIntelSNBGraphicsFB.kext
Removing this last one is equivalent to a holding-SHIFT-safe mode.
[doublepost=1548838477][/doublepost]
There is something much better, the "Installer Log" (cmd⌘+L during the Installer) you can customize it with "Show All Logs" and you can export the log text file wherever you want.
Otherwise use a virtual machine shooting screencaps.
Last edited:
If I were you I would do a fresh start. I would clean install the 10.14.3 on APFS formated drive, making sure it is the only partition on the drive. And then go from here. After you run the tool you might get a drop down menu with multiple definitions for your EEPROM. And here can get very tricky as you must select the correct one(which can involve looking up the chip on your logic board). If you are not presented with a choice of multiple definitions, the procedure should be straightforward.
Yes, use your iPhone.
I have the same problem on the MacBook Pro 7,1 and a MacMini 3,1. I am hoping @dosdude1 has a fix working.
Sorry, I'm a little late.
You're right.
https://support.apple.com/en-us/HT209057
Apple posted an article on this link, take a look at how the Windows partition affects the conversion of your system to APFS.
Is there no way to take actual screenshots in the installer? I saw @dosdude1 did it on his tutorial page.