Yes you can... That's the whole point of the options in the post-install tool. The Legacy Video Card patch is not installed by default on ANY Mac Pro model.
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
I’m talking about creation of the “USB installer” which is long before having a chance at doing any post-install tool.
[doublepost=1559950931][/doublepost]The prelinked kernelcache in your latest version is like 5MB in size different from the vanilla copy for 10.14.5 IIRC.
My understanding is that the patched installer's running system is very lightly patched and runs unaccelerated graphics during the installation process. And of course this all relies on using a virgin copy of the Mojave installer without any additional modes.
That IS true, but what do you need to have a graphic accelerated installer for, anyway? It is JUST the installer, which won't have acceleration, and not the system installed by that installer. Actually the installer installs a totally non-patched macOS. Therefor you need to run dosdude1's great patcher utility from within the installer to customise the installed system to your needs. While the default settings are valid for most, some cases need user specific adjustments, like yours. So for patching the installed system just unselect the graphics patch for making netkas' patch work afterwards.
I don't think that is quite accurate. During the creation of the usb installer, macOS Mojave Patcher explicitly shows a patching stage in the reporting of its progress. Otherwise, the resulting system couldn't boot on unsupported machines.
Well of course. Otherwise the installer would not boot, just like you say. But the system the installer (NOT the patcher) installs is vanilla Mojave.
The legacy video card drivers are not included in the bootable installer, as they're unnecessary until the OS is completely installed.
I don’t need it accelerated. You’re missing the point I’m trying to make. The installer UI NEVER LOADS for me. It just leaves me at the verbose boot screen complaining about kext version differences.
I’ll have to redo it and take some photos for you all.
hi there I seem to have a issue that when I install macOS Mojave and reboot on my mid 2010 13 inch core 2 duo Mac it runs incredibly slow and will sometimes not boot at all please help I need Xcode 11 for iOS 13 beta but can't because no mojve
Now I get it… Did you try to patch the installer using netkas' method? This might be necessary to avoid SSE4.2 issues in this case (@dosdude1 ?). If so either try this or try booting the installer in safe mode (shift while booting or a -x [nvram] boot-arg). This could help.
You could also try to delete any AMD* file from the installers /System/Extensions/ directory, though this will fail, if you do not have an EFI enabled GPU.
Last edited:
Make sure you are creating the USB installer for installed patched Mojave from a virgin copy of the Mojave installer. You don't want to be layering additional levels of patches onto the installer itself. Just use the Download feature in the patcher to get a fresh copy and recreate the USB installer from that.
So during my install I'm using my GTX 650 since it has been EFI flashed and my RX 580 is for a different machine. If I get this working I'll get another 580 or 570.
I'm using the tool to download a fresh virgin copy.
I just redid this again now.
Made a new installer partition and installed there. Then booted from it.
Here is where it stalls.
[doublepost=1559958960][/doublepost]
I didn't patch for SSE4.2 until after install / update was done. Then rebooted a couple times then I powered off and swapped the 650 with the 580.
I'm using the nvidia card during installer.
But your suggestion was a hint at the answer.
I booted the installer in single user mode remounted read write and moved all the NVDA* out of SLE. then rebooted. Now it instantly went to the installer UI.
Now I'm doing a new clean install.
[doublepost=1559959374][/doublepost]Oh and maybe audio will work this time.
Attachments
Last edited:
The patch for AMD sse4.2 bypass still did not work for my 580 on the clean install. Same window server crash loop as before so I never get to the desktop but I can ssh in.
@netkas You may want to take a look at this.
@dosdude1 If you get a chance to do a video on this it'd be appreciated. I'm stumped with my 3,1 at the moment. got 10.14.5 working thanks to your patcher. but i'm using a HD5770 with it and i've got a couple RX 580s i could try to pop in and test it out. would be sweet to get one or 2 of those working in there.
That´s a good advice on all other unsupported systems, but unfortunately does not work on the MB4,1 due to even older USB / iSight kext dependencies. Perhaps we need to dig in deeper (older) OS X layers for that beast.
Yes, great that dosdude integrated it so quickly into patcher 1.3.3. In my case (MBP5,2 17“) it also brought back DVD Player which had been crashing since quite a while.
Yes it was a clean install of 10.14.5
It was created by dosdude’s patcher with the extra stipulation of removal of Nvidia drivers from the installer to get the installer UI to work with my efi flashed GTX 650 so that I could then install your SSE4.2 emulation bypass and swap cards to the PowerColor red devil RX 580 8Gb card. It has dual bios, I’ve tried using the “silent” and “OC” bios with same results. Does the 580 use the same driver as the 560 that you used? I assume it does.
WindowServer ends up in a crash loop if the AMD drivers are loaded and to fix the loop I just have to go back to the GTX 650 or have both cards and remove the AMD drivers. So I know the OS is ok. And the RX 580 works fine in my C610 chipset “iMacPro1,1” hack so that also tells me the card is also good.
(SSH is up at that point so I can get into the system and make changes if needed)
Screen sharing doesn’t work any different than the direct video output. The cursor shows up for a second or so every few seconds as WindowServer crashes and restarts.
There’s a few more posts about what I’ve seen starting in the middle of page 637 through this post.
I am running Mojave 10.14.5 on a 5.1 2011 Mini with 16GB of RAM and an SSD drive. I use a Logitech bluetooth backlit keyboard and an Apple Mouse gen 1. I mention that because lately bluetooth has been completely disconnecting, to the point that to get them working again I have to press and hold the power button on the Mini to restart the computer because the keyboard and mouse will NOT reconnect whatsoever. This has never been a problem until the last few days where it has happened 3 times. Each time when I am away from the computer for a while with programs open.
Any ideas? Is this a hard ware issue? Software? Unsupported hardware problem? Etc...
Any ideas? Is this a hard ware issue? Software? Unsupported hardware problem? Etc...
Good news from the "doubly-unsupported" MB4,1.
While there still is no solution for the brightness control of the display on this machine, I found a way to get back display backlight power-off while semi-sleeping (utilizing NoSleep in v1.5.1) or when the lid is closed.
Unfortunately, this is a tiny hardware modification that I´ll document later today. It can be done with medium soldering skills and fits nicely into the machine so everything can be assembled back to the original closed state. Total time to do this: Around 1h, with parts costing below €1,-
So here we go with the circuit for the modification.
The BOM consists of
1x 74HCT04 hex inverter logic IC
2x 1kOhm resistors (any wired non-SMT type will do)
The idea behind the circuit is to use the SMC-generated LED PWM signal that ramps from off (floating) to 100% on (3.3V) whenever either the lid is closed, during startup or when macOS tries to enter sleep mode (which is prevented by the NoSleep extension because we could never wake up after that). This signal could be used directly as a driver for the PWM LCD input, only it has a reverse logic for that. Screen backlight is on when the signal is 3.3V and off at 0V.
So we need to invert it at least 1x (but in case of optional additional R-C timing that might have been we do it 3x here).
Pls. excuse the free-hand drawing of the circuit (and Euro style for Rs and IC gates) - I did not like to fire up an ECAD system on my weekend for this li´l circuit ;-)
I skip all steps needed to get to the right place on the PCB, so we dive right in:
1.
2.
3.
4.
5.
6.
7.
While there still is no solution for the brightness control of the display on this machine, I found a way to get back display backlight power-off while semi-sleeping (utilizing NoSleep in v1.5.1) or when the lid is closed.
Unfortunately, this is a tiny hardware modification that I´ll document later today. It can be done with medium soldering skills and fits nicely into the machine so everything can be assembled back to the original closed state. Total time to do this: Around 1h, with parts costing below €1,-
So here we go with the circuit for the modification.
The BOM consists of
1x 74HCT04 hex inverter logic IC
2x 1kOhm resistors (any wired non-SMT type will do)
The idea behind the circuit is to use the SMC-generated LED PWM signal that ramps from off (floating) to 100% on (3.3V) whenever either the lid is closed, during startup or when macOS tries to enter sleep mode (which is prevented by the NoSleep extension because we could never wake up after that). This signal could be used directly as a driver for the PWM LCD input, only it has a reverse logic for that. Screen backlight is on when the signal is 3.3V and off at 0V.
So we need to invert it at least 1x (but in case of optional additional R-C timing that might have been we do it 3x here).
Pls. excuse the free-hand drawing of the circuit (and Euro style for Rs and IC gates) - I did not like to fire up an ECAD system on my weekend for this li´l circuit ;-)
I skip all steps needed to get to the right place on the PCB, so we dive right in:
1.
2.
3.
4.
5.
6.
7.
Last edited: