macOS 10.14 Mojave on Unsupported Macs Thread

[tsialex]

So this patch is only for "pre-Nehalem cpu" with an AMD Metal GPU, right ?

I don't know much, but reading here https://en.wikipedia.org/wiki/Graphics_Core_Next
I understood a bit.

But I still don't understand this sentence: "Since 10.14.5 (or maybe earlier) sse4.2 bits disappearedfrom opengl driver"

The only Mac that the patch is useful is MP3,1, no other Mac can have an AMD GCN GPU with a processor without SSE4.2.

Netkas assumed that Mojave OpenGL driver required SSE4.2, I don't really know if it was needed before.

 

[jackluke]

The only Mac that the patch is useful is MP3,1, no other Mac can have an AMD GCN GPU with a processor without SSE4.2.

Netkas assumed that Mojave OpenGL driver required SSE4.2, I don't really know if it was needed before.

As far I know Mojave OpenGL driver from the beginning worked (after discovered patches) with Penryn CPU (SSE4.1), IntelHD, Nvidia Tesla and ATI 4xxx series, so from what I understand the SSE4.2 is not a requirement for Radeon HD 5xxx and 6xxx cards (since typically they are present on i5/i7 logic boards), but the issue for not loading OpenGL acceleration on those cards should be elsewhere.

 

[alphascorp]

Hello,

Could you share alls screenshots related to "Parametrage ventilateur" in iStatMenus ?
I mean what RPM you choose for others "Moyen", "Elevé", "Haut" and "Maxi" ?
Thank you

Hi @Loyd-01a
Here are the screenshots:

 

[Minh_Ton]

Apple dropping OpenGL supports from macOS... 10.15 will be the next challenge Waiting for the event...

 

[pkouame]

As far I know Mojave OpenGL driver from the beginning worked (after discovered patches) with Penryn CPU (SSE4.1), IntelHD, Nvidia Tesla and ATI 4xxx series, so from what I understand the SSE4.2 is not a requirement for Radeon HD 5xxx and 6xxx cards (since typically they are present on i5/i7 logic boards), but the issue for not loading OpenGL acceleration on those cards should be elsewhere.

Agreed. Never been an issue between OpenGL and sse 4.2 instruction set that I know of. But I think netkas is patching the metal driver itself.

 

[macosdon]

Not sure if you settled the problem in the meantime, but here´s what you essentially need for getting Wifi up and running on your MB4,1 (hopefully you have the same card or at least one of the same sub-group).
Make sure you use the latest Kext Utility (2.6.6?) and most importantly, wait until the pre-linked kernel is re-generated (see folder of the same name, wait for the 0 byte file being replaced). This takes some time more than the kext util suggests...
Also make sure that all three files are included in our post-patch:
IO80211Family.kext v7.0.4
Broadcom43XXFamily.kext and ...Familyrev2.kext (both v3.1.4)

You can also see if kexts are loaded correctly if you do a verbose boot or with "kext wizard", another fine tool.
IO802 reports as version 704.52 then and one of the Broadcom kexts as com.apple.driver.AirPortBrcm43224 v700.36.24

In case you still have no wifi, does it report as missing hardware or just a greyed-out indicator?

Hi, good news! wifi works after I installed the three kexts files with kext wizard and repair the permissions and rebuilt the kernel cache with this wonderful application. Thanks for your great help and my appreciation goes to 0403979 too. Currently, the machine runs smoothly under 10.14.5, only the brightness can't be adjusted and the system sometimes reboots suddenly.

 

[TianjinMBP]

This does sound very strange. Maybe the hard drive/ribbon cable is dying? Have you tried installing on an external HDD/SSD?

The only externals I have are for backups. I was thinking that perhaps my USB ports are wearing out. It is 10 years old and we mac users use our USBs for just about everything (charging iPhones, etc...). I wonder if you can burn Dosdude's output to a file and then burn it to a DVD? No, I think it's too big. just pondering and not really wanting to replace the motherboard for a worn out USB port.

 

[spacec0w]

Just wanted to bring this to the relevant people's attention again. You might be interested in my input because I run a repair shop and have been installing these High Sierra and Mojave patches for quite a long time, and aside from other little issues (the random kernel panics recently for example) that have been fixed along the way this is the only problem I've repeatedly experienced in all the models I've installed it on (which is pretty much all of them by now, perhaps 50+ computers in total).

No one seems to truly look into it or discuss it, and the audio of a computer I generally consider one of it's core functions, so if it doesn't work right someone will be stuck with 10.11. Not a big deal in the scheme of things but it really seems like this deserves some more attention.

At the very least I'd be content to know someone's actually listening and it were listed in dosdude1's list of known issues, as I've been able to replicate it on multiple machines of the same model with fresh installs, applying all available Patch Updater updates. It continues in 10.14.5 by the way.

Hi first of all a huge thanks to everyone who helps make this thing work... I've installed this on multiple machines and almost always with perfect results. But I have a couple iMac 8,1 (both 24") that keep having problems with audio--a near constant clicking. I did a quick search in the thread and found someone else with the same issue, but it doesn't seem like he or she got it solved it in the end. I tried all the same things, reinstalling all patches, running the patch tool again, once rebuilding caches. I have seen a couple of times the message "Legacy Audio driver has been overwritten, reinstall". I reinstall but it happens again.

With the machine I've spent most time with, there are periods where it will work well, but most of the time no. It also happened with High Sierra on the same machine, and earlier versions of Mojave. Now it is at 10.14.4.

Today, before posting, I finally tried a clean install. After first boot, Patch Updater opens to tell me about 4 things to install, volume, brightness, isight and video I think. I apply, restart. Same sound issue. After boot the Patch Updater warns me that the Legacy Audio driver has been overwritten, I reinstall, restart. Same issue. Any ideas here?

 

[pkouame]

The only externals I have are for backups. I was thinking that perhaps my USB ports are wearing out. It is 10 years old and we mac users use our USBs for just about everything (charging iPhones, etc...). I wonder if you can burn Dosdude's output to a file and then burn it to a DVD? No, I think it's too big. just pondering and not really wanting to replace the motherboard for a worn out USB port.

Definitely sounds like some hw issue. Have you tried running full diagnostics on your machine?

 

[TianjinMBP]

Definitely sounds like some hw issue. Have you tried running full diagnostics on your machine?

How can I do that?

 

[Jalu]

Hi, good news! wifi works after I installed the three kexts files with kext wizard and repair the permissions and rebuilt the kernel cache with this wonderful application. Thanks for your great help and my appreciation goes to 0403979 too. Currently, the machine runs smoothly under 10.14.5, only the brightness can't be adjusted and the system sometimes reboots suddenly.

I have just tried the same thing on an old but pristine Macbook4,1 that I have had lying around here for some time. And it is indeed running 10.14.5. Issues are that the trackpad can't be configured, the brightness can't be adjusted and the machine seems to KP when attempting to shutdown or reboot the OS. Other than that, it ís running relatively ok (this old little machine does have 6GB RAM and an SSD).

It wóuld be very nice to regain brightness control one way or the other, because the display is surprisingly bright like this...

 

[pkouame]

How can I do that?

Option-D on startup if you're machine isn't too old. See https://support.apple.com/en-us/HT202731

If it's an older model and you don't have the original disks read this : https://github.com/upekkha/AppleHardwareTest

I've had two hardware related failures on my mbp 5,2 detected by running full diagnostics (had to replace ram and an aging SSD)

Good luck.

 

[flygbuss]

Just wanted to bring this to the relevant people's attention again. You might be interested in my input because I run a repair shop and have been installing these High Sierra and Mojave patches for quite a long time, and aside from other little issues (the random kernel panics recently for example) that have been fixed along the way this is the only problem I've repeatedly experienced in all the models I've installed it on (which is pretty much all of them by now, perhaps 50+ computers in total).

No one seems to truly look into it or discuss it, and the audio of a computer I generally consider one of it's core functions, so if it doesn't work right someone will be stuck with 10.11. Not a big deal in the scheme of things but it really seems like this deserves some more attention.

At the very least I'd be content to know someone's actually listening and it were listed in dosdude1's list of known issues, as I've been able to replicate it on multiple machines of the same model with fresh installs, applying all available Patch Updater updates. It continues in 10.14.5 by the way.

Colud it be related to the CPU?
I know there are some audio issues with the older cMP 4,1 Xeon CPUs (E5...)
Have a look at my earlier post here:
https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-574#post-27284807

More about that issue:
https://forums.macrumors.com/threads/strange-audio-issue-on-mp-4-1-5-1-mojave-10-14-4.2176792/

If I remember correctly the issue doesn't occur with 10.14.3
Can you confirm that?

 

[TianjinMBP]

Option-D on startup if you're machine isn't too old. See https://support.apple.com/en-us/HT202731

If it's an older model and you don't have the original disks read this : https://github.com/upekkha/AppleHardwareTest

I've had two hardware related failures on my mbp 5,2 detected by running full diagnostics (had to replace ram and an aging SSD)

Good luck.

The first option is NULL because I wiped my drive and went APFS and since the repeated attempts at install have screwed my efi boot. The github option is sweet! I'm testing now with a bootable USB. Here in China, I can buy second hand MBP for really cheap and although they might be "altered", I can use this tool for testing. Most come with a 30 day money back garantee.

I'll let you know what I find.

 

[Rand0mUserNam3]

I've seen a report of this crash in the blur filter. Someone claims Option-clicking to open Photos then creating a new library solves it. Not sure if this will do the trick for you. Do you have a complete trace or crash log? Only way to tell if it has anything to do with our patches... What version of macOS are you on?

Hi @pkouame - thanks for your response. It is good to know that someone else has seen related reports to Photos crashing.

I'm running:
Mac OS X 10.14.5 (18F132)

Hardware:
MacBook5,1

Photos:
4.0 (3451.7.120)

I have saved two most recent crash logs, both of which occur together, in the hopes that this is enough information to provide a lead on what's happening, to see if it is related to the Mojave patcher and a solution can be found:

Photos crash:
https://pastebin.com/LzDNpLYj

photolibraryd crash:
https://pastebin.com/RWgLv1rp

Thank you

/cc @dosdude1 @TimothyR734 @ASentientBot

 

[spacec0w]

Thanks for replying Well it seems like it wouldn't have to do with the CPU as I haven't had issues with other 2008 iMacs, the 20" model for example, which just have different clock speeds for what I assume is the same Penryn architecture. In the one computer I have here that I actually work with it did pass through 10.14.3, and it's possible the problem didn't occur during that version as there was a time when it didn't happen. In general I've had this as an intermittent issue in this machine. And every so often Patch Updater will show it's message about an audio or volume patch being overwritten, then maybe it will work for a while or maybe not-- I couldn't find a pattern as to why it stopped working well sometimes.

As for trying 10.14.3, how does one go about downloading an earlier version of Mojave? I keep all the OS versions but never thought to stockpile the minor revisions!

Colud it be related to the CPU?
I know there are some audio issues with the older cMP 4,1 Xeon CPUs (E5...)
Have a look at my earlier post here:
https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-574#post-27284807

More about that issue:
https://forums.macrumors.com/threads/strange-audio-issue-on-mp-4-1-5-1-mojave-10-14-4.2176792/

If I remember correctly the issue doesn't occur with 10.14.3
Can you confirm that?

 

[ASentientBot]

Netkas patched 10.14.5 AMD Metal drivers to work with MP3,1, emulating the SSE4.2 instruction needed by the driver.

http://forum.netkas.org/index.php/topic,13890.0.html

This should be a nice addition for Mojave Patcher cc @dosdude1

Absolute legend.

Sounds like he didn't implement a full kernel-level emulator though, he just patched the driver itself to avoid the use of the instruction? I'm not super clear on how that would be done but it's impressive in any case. Somebody going to test this?

On another note, get ready for 10.15 everybody! Just a couple hours left
[doublepost=1559569035][/doublepost]

Hi @pkouame - thanks for your response. It is good to know that someone else has seen related reports to Photos crashing.

I'm running:
Mac OS X 10.14.5 (18F132)

Hardware:
MacBook5,1

Photos:
4.0 (3451.7.120)

I have saved two most recent crash logs, both of which occur together, in the hopes that this is enough information to provide a lead on what's happening, to see if it is related to the Mojave patcher and a solution can be found:

Photos crash:
https://pastebin.com/LzDNpLYj

photolibraryd crash:
https://pastebin.com/RWgLv1rp

Thank you

/cc @dosdude1 @TimothyR734 @ASentientBot

I just tried Photos, importing a few pictures and such, and it won't crash for me. Can you reliably trigger it with a certain action?
[doublepost=1559569087][/doublepost]

Thanks for replying Well it seems like it wouldn't have to do with the CPU as I haven't had issues with other 2008 iMacs, the 20" model for example, which just have different clock speeds for what I assume is the same Penryn architecture. In the one computer I have here that I actually work with it did pass through 10.14.3, and it's possible the problem didn't occur during that version as there was a time when it didn't happen. In general I've had this as an intermittent issue in this machine. And every so often Patch Updater will show it's message about an audio or volume patch being overwritten, then maybe it will work for a while or maybe not-- I couldn't find a pattern as to why it stopped working well sometimes.

As for trying 10.14.3, how does one go about downloading an earlier version of Mojave? I keep all the OS versions but never thought to stockpile the minor revisions!

I think that @0403979 has a copy uploaded. If not, I can upload mine later today.

 

[vince22]

I have a mid 2010 13 inch MacBook Pro that is running high Sierra on its own without any patch, I am thinking about trying this but want to make sure that my 2010 MacBook Pro will be able to handle it ok first. it has a 256gb SSD and 8gb of ram.

I would not hesitate doing it, its running well. Here's a screenshot between Flat light vs Flat dark mode.

 

[jackluke]

Agreed. Never been an issue between OpenGL and sse 4.2 instruction set that I know of. But I think netkas is patching the metal driver itself.

Yes, it's only for using AMD Metal GPUs as alternative to Nvidia Metal GTX on SSE4.1 cpus, because I guess in Mojave there is no written SSE4.2 mandatory requirement (the minimum one is SSE4.1 since 10.12 Sierra), it's only a requirement for AMD GCN (Metal) GPUs (starting from 7xxx series) that to load the driver need those SIMD answers from the cpu, but I guess this is unrelated to the most machines equipped with AMD 5xxx and 6xxx series that IMHO don't need the SSE4.2 emulation, more over they have it already from their i5/i7 cpus.

 

[avz]

Hi @pkouame - thanks for your response. It is good to know that someone else has seen related reports to Photos crashing.

I'm running:
Mac OS X 10.14.5 (18F132)

Hardware:
MacBook5,1

Photos:
4.0 (3451.7.120)

I have saved two most recent crash logs, both of which occur together, in the hopes that this is enough information to provide a lead on what's happening, to see if it is related to the Mojave patcher and a solution can be found:

Photos crash:
https://pastebin.com/LzDNpLYj

photolibraryd crash:
https://pastebin.com/RWgLv1rp

Thank you

/cc @dosdude1 @TimothyR734 @ASentientBot

I have a MacBook5,1 and would like to replicate the issue. Would you be able to tell me step by step the fastest way to do it? My Photos version is 4.0(3461.7.120) though.

 

[Rand0mUserNam3]

I just tried Photos, importing a few pictures and such, and it won't crash for me. Can you reliably trigger it with a certain action?

The reliable trigger for the crash is opening Photos app, waiting a few seconds, then it crashes every time unfortunately.

If I create a blank library, everything is fine. But it is blank and contains no photos.

I am unable to use Photos with my existing photos:
Either by repairing the library in Photos,
Rebuilding the to a new library using PowerPhotos,
or when the photos are manually imported into a blank library from Finder to Photos - the end result is the same.

The only clue I have is that there must be something about Portrait photo processing, I have noticed a couple of thumbnails for portrait photos have malformed thumbnails (looks like half of the image is vertical, the other half portrait orientation), so I deleted all of those images from my library and still had no positive results.

 

[ASentientBot]

The reliable trigger for the crash is opening Photos app, waiting a few seconds, then it crashes every time unfortunately.

If I create a blank library, everything is fine. But it is blank and contains no photos.

I am unable to use Photos with my existing photos:
Either by remaining the library,
Rebuilding the to a new library using PowerPhotos,
or when the photos are manually imported into a blank library from Finder to Photos - the end result is the same.

The only clue I have is that there must be something about Portrait photo processing, I have noticed a couple of thumbnails for portrait photos have malformed thumbnails (looks like half of the image is vertical, the other half portrait orientation), so I deleted all of those images from my library and still had no positive results.

I wonder if it's something with the specific image. Would you mind playing around and finding which photos are needed to cause the crash, and then uploading one somewhere so we can test?

 

[macosdon]

Yes, I got the same minor problems. For brightness control, I recommend brightness slider. It's good to use. I also installed the latest Windows 10 v1903 on MB4.1. It runs flawlessly.

 

[Rand0mUserNam3]

I wonder if it's something with the specific image. Would you mind playing around and finding which photos are needed to cause the crash, and then uploading one somewhere so we can test?

I tried deleting all portrait photos, and that didn't fix the issue.

I am going to keep trying. I will start again with a blank library, then import photos in smaller batches, until the problem arrises.

If I identify a problem image, I'll let you know!

I have a MacBook5,1 and would like to replicate the issue. Would you be able to tell me step by step the fastest way to do it? My Photos version is 4.0(3461.7.120) though.

I posted some additional details in this post: #15796
If portrait photos are indeed the culprit, maybe testing with a library containing some portrait photos taken with an iPhone XS?

 

[flygbuss]

Thanks for replying Well it seems like it wouldn't have to do with the CPU as I haven't had issues with other 2008 iMacs, the 20" model for example, which just have different clock speeds for what I assume is the same Penryn architecture. In the one computer I have here that I actually work with it did pass through 10.14.3, and it's possible the problem didn't occur during that version as there was a time when it didn't happen. In general I've had this as an intermittent issue in this machine. And every so often Patch Updater will show it's message about an audio or volume patch being overwritten, then maybe it will work for a while or maybe not-- I couldn't find a pattern as to why it stopped working well sometimes.

As for trying 10.14.3, how does one go about downloading an earlier version of Mojave? I keep all the OS versions but never thought to stockpile the minor revisions!

Ask @0403979 I think he might be able to provide 10.14.3