Sidebar Sidebar
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

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.
sirlindqvist said:
Any more progress here? Im on an iMac mid2011 with 5xxx card and realised in the autumn this wont be easy so i kinda gave up. Been checking in here now and then to see if something changed and it looks so?

@Scrotorr what do you mean with "Mojave Patcher that gimped the 5770 almost completely" ? That its like supported or totaly unsupported?

Wonder if we can hope for a fully functional 10.14 with these machines/gfx cards?
Click to expand...

With the last revision of @dosdude1 Mojave patcher that was still for the original retail release of Mojave my Mac Pro 3,1 units with AMD 5770 cards worked just fine. No inverted color, pretty snappy to use. After that when I tried to update to 10.14.2 or 10.14.3 with the appropriate patchers the Legacy Video Card patch didn't seem to do much. The "inverted color" and no acceleration issue happened and I have no clue what changed. However after copying IOAccelerator2D.plugin and IOAcceleratorFamily2.kext from the "gfxshared" folder and replacing the stock versions in your Extensions folder you will likely have acceleration and a usable card after you do a kext cache clear and reboot.

At least that has been my experience with the late 2009 iMac I'm on right now, and the MacPro 3,1 units I have with AMD 5770.
 
  • Like
Reactions: webg3 and ASentientBot
Scrotorr said:
With the last revision of @dosdude1 Mojave patcher that was still for the original retail release of Mojave my Mac Pro 3,1 units with AMD 5770 cards worked just fine. No inverted color, pretty snappy to use. After that when I tried to update to 10.14.2 or 10.14.3 with the appropriate patchers the Legacy Video Card patch didn't seem to do much. The "inverted color" and no acceleration issue happened and I have no clue what changed. However after copying IOAccelerator2D.plugin and IOAcceleratorFamily2.kext from the "gfxshared" folder and replacing the stock versions in your Extensions folder you will likely have acceleration and a usable card after you do a kext cache clear and reboot.

At least that has been my experience with the late 2009 iMac I'm on right now, and the MacPro 3,1 units I have with AMD 5770.
Click to expand...
There is no possible way to achieve full acceleration with the Radeon HD 5xxx or 6xxx series cards in Mojave, especially on the Mac Pro 3,1, which doesn't support SSE4.2 (and can't even load those AMD drivers). If you don't have full transparency and lag-free animations (especially apparent in LaunchPad), then you do not have full graphics acceleration.
 
  • Like
Reactions: webg3 and ASentientBot
its done.
COMPLETE.
BUT at boot still white and yellow letters on black background.

How to check if apfs rom is available?

boot into dosdudes patcher and remove apfs patch?
 
I checked and verified that copying the IOAccelerator2D.plugin and IOAcceleratorFamily2.kext from the "gfxshared" folder of the patcher does indeed work to get basic acceleration and correct colors with legacy AMD cards (tested 5770 and 6970) on patched 10.14.2 and 10.14.3.

This seemed to work fine with the first installs I did with the initial retail release of Mojave and the appropriate patcher for that - @dosdude1 did something change in a script that no longer installs these kext files when doing the AMD Legacy Patch at install?
[doublepost=1549485281][/doublepost]
dosdude1 said:
There is no possible way to achieve full acceleration with the Radeon HD 5xxx or 6xxx series cards in Mojave, especially on the Mac Pro 3,1, which doesn't support SSE4.2 (and can't even load those AMD drivers). If you don't have full transparency and lag-free animations (especially apparent in LaunchPad), then you do not have full graphics acceleration.
Click to expand...

I totally get that - just that in the recent versions of the patcher it didn't appear to copy over your IOAccelerator2D.plugin and IOAcceleratorFamily2.kext which left the card entirely worthless. Just with doing that I at least have a machine that is usable without window draw artifacts and the color issue (although admittedly, without full acceleration).

And no slight to all the amazing work you do. You've single handedly saved my non-profit thousands of dollars with not having to replace perfectly good machines that didn't meet university OS standards.
 
  • Like
Reactions: ASentientBot
16v said:
its done.
COMPLETE.
BUT at boot still white and yellow letters on black background.

How to check if apfs rom is available?

boot into dosdudes patcher and remove apfs patch?
Click to expand...
If you've finished applying the APFS ROM Patch, then just reboot, and then hold the Option key. If the APFS volume shows, it works as intended. You can boot from this, and then set it as the Startup Disk using System Preferences.
 
  • Like
Reactions: roronl
O.k....
I removed apfs patch in patcher.

Then i read what you wrote...
Apfs volume is shown...

Do i need apfs patch?
And it seems it boots faster.
7260cc570e499bfd5133aef6f0c76aeb.jpg
 
magero said:
Hi i have the same issue, after install patched Mojave on MacPro 3.1, boot stuck on approx. 75%, please how can i logging remotely? I have a Macbook pro also.
Thanks for answer.
Click to expand...

Put the installer back in your macpro, boot into installer, and there will be terminal.
 
  • Like
Reactions: magero
YES!
Thank you very much.

last Question:
Solution for This?
When installing newer Version it says no supported card.

What to do?
 

Attachments

  • Bildschirmfoto 2019-02-06 um 22.22.27.png
    Bildschirmfoto 2019-02-06 um 22.22.27.png
    171.3 KB · Views: 245
16v said:
Solution for This?
When installing newer Version it says no supported card.
Click to expand...

First, check if Cuda Device is found (detected) on your system; for example using Cuda-Z. If not, update Cuda Driver to v8.0.90 < this was the last version that supports NVDA Tesla (and Fermi, though release note said it' s for 10.11.x-10.12.x). Yeah, already tested on 10.14.x and it just works.

If Cuda is recognized, you could ignore those warning. However Cuda.prefPane checks for update on every boot, but you could remove it's LaunchAgents from System (only removing update, not it's support):
Code: 
cd /Library/LaunchAgents && ls
sudo rm com.nvidia.CUDASoftwareUpdate.plist

There's another method; is adding "GPU Driver version (NVDAResman)" on "CUDA.framework's Info.plist" located on: /Library/Frameworks/CUDA.framework/Versions/A/Resources/Info.plist:
Code: 
cd /Library/Frameworks/CUDA.framework/Versions/A/Resources
sudo nano Info.plist
// eg. adding these lines:
<key>NVDAResmanVersions</key>
<dict>
...
<key>310.90.30</key>
<string>310.90.30</string>
...
</dict>

// then:
cd /Library/Frameworks/CUDA.framework/Versions/A/Libraries && ls
sudo cp libcuda_310.42.25_mercury.dylib libcuda_310.90.30_mercury.dylib
sudo update_dyld_shared_cache
reboot

2nd method is no longer working on 10.14.4 Beta 1-2.
Oh ya, as 10.14.4 another issue.. though my NVDA Fermi is still running, I have problem recognizing Cuda device for unsupported / deprecated GPU. Cool..!!!
 
Last edited:
  • Like
Reactions: 16v, webg3, Larsvonhier and 1 other person
Hello everyone - thank you for making this work on my Macbook 5,2. I suddenly have troubles with normal audio output. Headphones work fine, but as soon as I disconnect them, only an optical digital output is shown in System Settings and the sound control buttons don't work (prohibited sign). I already tried reinstalling legacy audio patch and booting to @dosdude1 installer re-applying all patches for my model to no avail. Rebuilt kext cache each time.
Any ideas how to debug this?
(mojave 10.14.3)
 
Teutone said:
Hello everyone - thank you for making this work on my Macbook 5,2. I suddenly have troubles with normal audio output. Headphones work fine, but as soon as I disconnect them, only an optical digital output is shown in System Settings and the sound control buttons don't work (prohibited sign). I already tried reinstalling legacy audio patch and booting to @dosdude1 installer re-applying all patches for my model to no avail. Rebuilt kext cache each time.
Any ideas how to debug this?
(mojave 10.14.3)
Click to expand...
Might be unrelated to Mojave:
- some older MB had this fault even when run with legacy macOS (its a defect in the detection of optical vs analog out)
- check with i.e. (High)Sierra if the bug is still there
- it is not a general problem with MB5,2 and Mojave - I have this setup also and it works fine...
 
New macOS Mojave 10.14.3 Supplemental Update to correct Group FaceTime issue!

Installing macOS Mojave 10.14.3 Supplemental Update on your Mac updates the build number of macOS to 18D109. This build contains the security content described in this article. If you update to macOS Mojave 10.14.3 and your macOS build is not 18D109, make sure you also install the Supplemental Update.
 
  • Like
Reactions: ASentientBot, jackluke, jbarley and 1 other person
oscarodas said:
I'm running Mojave 10.14.1 since it came out.View attachment 791546
[doublepost=1538526169][/doublepost]And again this is the beta 2 which installed without problems, I didn't even had to use the patcherView attachment 791558
Click to expand...

Hello oscarodas

How do you managed running Mojave with AMD Radeon HD 6970M? Are there working drivers in Beta1? Because now with 10.14.2 i had no luck with any AMD Radeon Cards - wired colors an no Hardware-Acelleration. Actually i have a 2011 iMac 27" with SSD and 16 GB RAM and i like to install Mojave with DosDude's Mojave Patcher but he warns about the AMD 5xxx and 6xxx cards that they are unusable - and that what i saw in my own test with another 2011 iMac.

Thanks And
 
visberry said:
New macOS Mojave 10.14.3 Supplemental Update to correct Group FaceTime issue!

Installing macOS Mojave 10.14.3 Supplemental Update on your Mac updates the build number of macOS to 18D109. This build contains the security content described in this article. If you update to macOS Mojave 10.14.3 and your macOS build is not 18D109, make sure you also install the Supplemental Update.
Click to expand...
So the question: is it safe to install the update?

Im on mojave 10.14.3 with mac mini 2010 mid.
[doublepost=1549566423][/doublepost]
magero said:
I have try this, but it say command not found :(
Click to expand...
Are there any way to recreate your installer thumb drive?!
 
How much better or worse runs Mojave on late-2008 aluminum MacBooks, in comparison to El Capitan?
 
iRock1 said:
How much better or worse runs Mojave on late-2008 aluminum MacBooks, in comparison to El Capitan?
Click to expand...

In my experience there is no competition: Mojave wins every time. It just feels much faster. I even for an experiment's sake downgraded the RAM from 8GB to 4GB and it is still just as fast. I am a light user though. Maybe APFS makes a difference.
 
  • Like
Reactions: ASentientBot, jackluke, olad and 1 other person
Flacko said:
Same here. No problems with MB air 4.2 and MacPro 3.1 using preferences. Quite a large update - 762 MB in each case..
Click to expand...
OK after a while I realized that my Bluetooth was not seeing my keyboard. Inserted USB keyboard and all is well, the supplemental works. Now hoping for a way to get the latest beta to work.
 
Last edited:
avz said:
In my experience there is no competition: Mojave wins every time. It just feels much faster. I even for an experiment's sake downgraded the RAM from 8GB to 4GB and it is still just as fast. I am a light user though. Maybe APFS makes a difference.
Click to expand...

Which model do you have? Have you had any glitch or bug?
 
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