macOS 10.14 Mojave on Unsupported Macs Thread

[Kaitozaki]

Hi i have a problem with my installation, i uploaded a picture, i have a imac mid 2011 27"

Please help me thank you...

 

[Larsvonhier]

I own a MacBookAir1,1 (albeit the hard drive died a few years ago and I never bothered to fix it). They don’t use a Penryn, they use a Merom, and thus have no SSE4.2 support, so it wouldn’t be able to run anything higher than El Capitan. But since the last 64-bit driver for the X3100 on that model was in 10.6.2, I can’t imagine getting anything newer than Lion running on it would be a good experience in any case. No proper sleep, poor performance and all that.

Performance with 10.10.5 is quite ok on my MB Air 1,1, and easy to install thanks to OSXhackers work - see website with the same name... ;-)

Overall performance/experience is way above what you could do with 10.6.8 or 10.7.x (in terms of updated software by far!).

 

[PBear.SF]

The current compatibility list:​

Mac Mini Mid-2011 (the HD 3000 variant works perfectly except for UI glitches)

Had great success installing Mojave Public Beta 1 in the above machine with macOS Mojave Patcher; then downloaded latest patcher and installed Public Beta 2 (no joy reinstalling over PB1 -- massive installer errors -- so had to wipe partition and install again from scratch, then joy). After booting the new Mojave Beta, I had a similar experience to Larsvonhier (Msg #2799) with the Patch Updater popping up as soon as I booted into the new Public Beta 2, saying I should update the Legacy Video Card patch.

Unlike Larsvonhier's experience, the patch updated successfully (although it did take quite a long time, maybe 10 minutes) -- but the results were not pleasing. Having had no video problems (in Dark Mode) using the previous Legacy Video Card patch, in fact no problems at all, with zero kernel panics, this new Legacy Video Card patch (version 3, I believe) resulted in repeated spinning pinwheels for several seconds when changing focus between various running programs, or between the desktop and active programs, as well as video glitches, such as various menu and tab bar elements going dark (i.e., greyed out) in active windows, until I would click on the desktop and, then, back on the active window again. There was also a general slowdown in the responsiveness of the system, compared to when using the previous Legacy Video Card patch.

In other words, I don't think this latest Legacy Video Card patch is a good match for my mid-2011 Mac mini running on an Intel HD 3000 GPU. (I rebooted into the installer USB and re-ran the Post Install routine for the previous Legacy Video Card patch, booted back into Mojave Public Beta 2, and now it is running perfectly.) But now, of course, the Patch Updater pops up again, urging me to install the latest Legacy Video Card update. I wish there were some way to tell the internal Patch Updater that I do not wish to install the new Legacy Video Card patch update and have it remember my choice (some sort of "hide update" option), so it would stop popping up all the time. I also wish there were a way to run the Patch Updater and see the list of currently installed patches -- which is currently only possible when there are no available updates showing.

 

[Larsvonhier]

That wasn’t even a GM kernel on ML either. You had to use the one from DP1.

There was actually a 64-bit kext in the 10.6.2 update, but Apple pulled it after that release. It worked, but had issues with sleep among other things.

Facts:
CPU is 64bit capable, 32bit EFI can be worked around (Pikeralpha).
My Air reports T7700 CPU, websearch tells "Penryn". Penryn has SSE4.x (and I write x, due to the fact that we sorted out Mojave does not need SSE4.2, just 4.1).
I wrote about x3100 and the driver situation, so don´t tell me what I already know... ;-)

Checked other sources: Processor is a L7700, not a T7700 (Geekbench got it wrong!), so it really is a Merom in a small special form factor only made for Apple. Heck.
That explains it...
[doublepost=1531671712][/doublepost]

How can I be sure what I download is the latest version of Mojave?

After downloading the beta of Mojave, just check that your installer App info says 14.0.12 (that´s currently the latest version).

 

[dosdude1]

Had great success installing Mojave Public Beta 1 in the above machine with macOS Mojave Patcher; then downloaded latest patcher and installed Public Beta 2 (no joy reinstalling over PB1 -- massive installer errors -- so had to wipe partition and install again from scratch, then joy). After booting the new Mojave Beta, I had a similar experience to Larsvonhier (Msg #2799) with the Patch Updater popping up as soon as I booted into the new Public Beta 2, saying I should update the Legacy Video Card patch.

Unlike Larsvonhier's experience, the patch updated successfully (although it did take quite a long time, maybe 10 minutes) -- but the results were not pleasing. Having had no video problems (in Dark Mode) using the previous Legacy Video Card patch, in fact no problems at all, with zero kernel panics, this new Legacy Video Card patch (version 3, I believe) resulted in repeated spinning pinwheels for several seconds when changing focus between various running programs, or between the desktop and active programs, as well as video glitches, such as various menu and tab bar elements going dark (i.e., greyed out) in active windows, until I would click on the desktop and, then, back on the active window again. There was also a general slowdown in the responsiveness of the system, compared to when using the previous Legacy Video Card patch.

In other words, I don't think this latest Legacy Video Card patch is a good match for my mid-2011 Mac mini running on an Intel HD 3000 GPU. (I rebooted into the installer USB and re-ran the Post Install routine for the previous Legacy Video Card patch, booted back into Mojave Public Beta 2, and now it is running perfectly.) But now, of course, the Patch Updater pops up again, urging me to install the latest Legacy Video Card update. I wish there were some way to tell the internal Patch Updater that I do not wish to install the new Legacy Video Card patch update and have it remember my choice (some sort of "hide update" option), so it would stop popping up all the time. I also wish there were a way to run the Patch Updater and see the list of currently installed patches -- which is currently only possible when there are no available updates showing.

That shouldn't be the case, as all that update does is add one kext needed for some AMD video cards... Try rebooting a couple times after installing the update, and see if it resolves itself.

 

[Larsvonhier]

That shouldn't be the case, as all that update does is add one kext needed for some AMD video cards... Try rebooting a couple times after installing the update, and see if it resolves itself.

Still strange that the patch update for legacy video cards takes so long. I admit I never waited the 10 minutes but canceled the update process. No problems afterwards, though, just version 2 of the video patch (but on non-AMD machines without disadvantages).

 

[Stratus Fear]

Facts:
CPU is 64bit capable, 32bit EFI can be worked around (Pikeralpha).
My Air reports T7700 CPU, websearch tells "Penryn". Penryn has SSE4.x (and I write x, due to the fact that we sorted out Mojave does not need SSE4.2, just 4.1).
I wrote about x3100 and the driver situation, so don´t tell me what I already know... ;-)

I didn’t say anything about the EFI or 64-bit capability of the CPU. Indeed, I know and agree you can boot OSes with 64-bit kernels since you only need a special boot.efi to do so. I just personally can’t stand the performance of the software renderer that you have to deal with without proper GPU support T7700 is a 2.4GHz Merom most commonly used in the iMac7,1. T6x00, T8x00, and T9x00 series are Penryn. No T7x00 is Penryn, they are all Merom. https://en.m.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors

I did make a mistake, though: I said SSE4.2 when I meant SSE4.1. Sierra and newer need SSE4.1. Merom doesn’t have that.

Checked other sources: Processor is a L7700, not a T7700 (Geekbench got it wrong!), so it really is a Merom in a small special form factor only made for Apple. Heck.
That explains it...

Indeed. There wasn’t a Penryn until MacBookAir2,1, I believe.

 

[PBear.SF]

That shouldn't be the case, as all that update does is add one kext needed for some AMD video cards... Try rebooting a couple times after installing the update, and see if it resolves itself.

Thanks for the info. But, as things are running swimmingly now, I don't think I'll try rocking the boat. If and when the next public beta is released, I will download the corresponding new version of your Patcher and that will, by default, have the latest Legacy Video Card patch included. Will see how things go then.

Cheers!

 

[dosdude1]

Still strange that the patch update for legacy video cards takes so long. I admit I never waited the 10 minutes but canceled the update process. No problems afterwards, though, just version 2 of the video patch (but on non-AMD machines without disadvantages).

That's just because the update is very large (About 250MB), so it takes awhile for it to download.

 

[giorgiorafael]

latest Mojave is up and running with wifi and FaceTime View attachment 770730

how did you get FaceTime to work?

Can anyone provide me a solution on how to get it to work? I tried replacing the kext but after I did everything was unresponsive, keyboard, mouse etc... I had to reinstall but still no iSight

 

[jackluke]

how did you get FaceTime to work?

Can anyone provide me a solution on how to get it to work? I tried replacing the kext but after I did everything was unresponsive, keyboard, mouse etc... I had to reinstall but still no iSight

What/which kext do you tried replacing?

The picture you quoted belongs to another kind of Mac totally different Intel Chipset from your machine, more over that Mac has a FaceTime HD camera not an iSight camera as your macbook.

From your pictures I see you have a C2D Penryn Nvidia Chipset's Macbook, and you have installed the macOS Mojave 10.14 beta 3 Update 1.

I do have a similar machine with Mojave beta 2 installed and to me iSight works without issues.

This iSight issue was explained and fixed earlier, but I recall my steps:

- You should have all the non-patched Mojave Beta 3 IOUSB*** Kexts installed in your Mojave S/L/E
- To make iSight working you need to replace only two kexts of them:

1) IOUSBHostFamily.Kext this is mandatory to make any USB responsive as you written, and this Kext must be taken from any High Sierra Installation;
2) IOUSBFamily.Kext that I uploaded on page 110 (or any IOUSBFamily.kext taken from the same High Sierra Installation where you took the first one).

Try these steps you should fix it.

Or instead doing all those steps with dosdude1's Mojave Patcher Post Install select your Mac model: MacBook6,1

 

[lefruitix]

What/which kext do you tried replacing?

The picture you quoted belongs to another kind of Mac totally different Intel Chipset from your machine, more over that Mac has a FaceTime HD camera not an iSight camera as your macbook.

From your pictures I see you have a C2D Penryn Nvidia Chipset's Macbook, and you have installed the macOS Mojave 10.14 beta 3 Update 1.

I do have a similar machine with Mojave beta 2 installed and to me iSight works without issues.

This iSight issue was explained and fixed earlier, but I recall my steps:

- You should have all the non-patched Mojave Beta 3 IOUSB*** Kexts installed in your Mojave S/L/E
- To make iSight working you need to replace only two kexts of them:

1) IOUSBHostFamily.Kext this is mandatory to make any USB responsive as you written, and this Kext must be taken from any High Sierra Installation;
2) IOUSBFamily.Kext that I uploaded on page 110 (or any IOUSBFamily.kext taken from the same High Sierra Installation where you took the first one).

Try these steps you should fix it.

Or instead doing all those steps with dosdude1's Mojave Patcher Post Install select your Mac model: MacBook6,1

That didn't work for my MB5,1

 

[Larsvonhier]

That didn't work for my MB5,1

I take it you made sure that after replacing the kexts you corrected the file attributes and the next boot in verbose showed that the kernel cache was prelinked new?

 

[lefruitix]

I take it you made sure that after replacing the kexts you corrected the file attributes and the next boot in verbose showed that the kernel cache was prelinked new?

no
[doublepost=1531679278][/doublepost]

I take it you made sure that after replacing the kexts you corrected the file attributes and the next boot in verbose showed that the kernel cache was prelinked new?

How can I change files` attributes?

 

[Edgecrusherr]

View attachment 770598 View attachment 770599 Dashboard is broken on supported devices as well. It is not a patcher issue but a Mojave issue.

Great point for everyone to remember, this is still early beta software.

 

[lefruitix]

Can I do kext replacing with kextutility instead of that?

 

[Larsvonhier]

no
[doublepost=1531679278][/doublepost]
How can I change files` attributes?

You can do it with terminal commands unix style or get the free tool "batchmod" and set the kext´s attrib. to root/wheel with it (compare with untouched kexts to see what it means).
[doublepost=1531679467][/doublepost]

Can I do kext replacing with kextutility instead of that?

sure, yes

 

[0403979]

Great point for everyone to remember, this is still early beta software.

Hopefully installer glitches and perhaps if we’re lucky transparency glitches will be fixed in beta 4.

 

[lefruitix]

Replacing IOUsb...xx doesn't work for me anyway.
[doublepost=1531680237][/doublepost]I did it like this.

 

[pkouame]

What/which kext do you tried replacing?

The picture you quoted belongs to another kind of Mac totally different Intel Chipset from your machine, more over that Mac has a FaceTime HD camera not an iSight camera as your macbook.

From your pictures I see you have a C2D Penryn Nvidia Chipset's Macbook, and you have installed the macOS Mojave 10.14 beta 3 Update 1.

I do have a similar machine with Mojave beta 2 installed and to me iSight works without issues.

This iSight issue was explained and fixed earlier, but I recall my steps:

- You should have all the non-patched Mojave Beta 3 IOUSB*** Kexts installed in your Mojave S/L/E
- To make iSight working you need to replace only two kexts of them:

1) IOUSBHostFamily.Kext this is mandatory to make any USB responsive as you written, and this Kext must be taken from any High Sierra Installation;
2) IOUSBFamily.Kext that I uploaded on page 110 (or any IOUSBFamily.kext taken from the same High Sierra Installation where you took the first one).

Try these steps you should fix it.

Or instead doing all those steps with dosdude1's Mojave Patcher Post Install select your Mac model: MacBook6,1

Hi @jackluke - an obvious question I forgot to ask: did your camera work on HS (13.5 or 6) as a "supported" machine"? I'm not sure when your mbp 7,1 went "unsupported". Then, it would make sense to experiment with those kexts.

 

[Larsvonhier]

Replacing IOUsb...xx doesn't work for me anyway.
[doublepost=1531680237][/doublepost]I did it like this.

Have you booted in verbose mode and seen the prelinked kernel cache being rebuilt (second boot after that)?
[doublepost=1531681089][/doublepost]

Replacing IOUsb...xx doesn't work for me anyway.
[doublepost=1531680237][/doublepost]I did it like this.

Root, wheel is correct, but set the checkmark to effect all enclosed files as well
Also: I recommend doing this while booted from another volume (old High Sierra i.e.), as I´m not sure that the running system does not interfere in some way... (but I could be wrong here and it does not matter).

 

[jackluke]

Replacing IOUsb...xx doesn't work for me anyway.
[doublepost=1531680237][/doublepost]I did it like this.

From that picture you posted you are on /Library/Extensions/
You have to go in /System/Library/Extensions/

From Finder press and keep "command + shift + G"

then type in: /System/Library/Extensions/
and go.


Edit:

iSight on your machine won't work with my method cause your machine supports until El Capitan 10.11 so you need to wait a patch for this.

 

[0403979]

From that picture you posted you are on /Library/Extensions/
You have to go in /System/Library/Extensions/

press and keep command + shift + G

then type in: /System/Library/Extensions/
and go.

I didn’t even realize that.

 

[Starplayr]

I think Apple still makes money off the older Macs I rent movies and buy apps or games from the App Store

I've always supported a Mac and iPhone eco system for app purchases and I write iOS software and games. We tried Amazon Kindle, but it is so much easier just supporting 1 eco system. Apple Rocks.

 

[ASentientBot]

Replacing IOUsb...xx doesn't work for me anyway.
[doublepost=1531680237][/doublepost]I did it like this.

It looks like you put them in /Library/Extensions, you need to replace the copies in /System/Library/Extensions.

Edit: Oops, @jackluke beat me to it.