macOS 10.14 Mojave on Unsupported Macs Thread

[redheeler]

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

View attachment 767266

Nice, perhaps there is hope for my Early 2011 17" MacBook Pro after all. Will have to attempt a Mojave install sometime over the weekend.

One question though: Would the kexts from 10.12.6 also work, or must it be that early build of 10.12? The 17" MBP is running Sierra 10.12.6 at the moment.

 

[dosdude1]

Nice, perhaps there is hope for my Early 2011 17" MacBook Pro after all. Will have to attempt a Mojave install sometime over the weekend.

One question though: Would the kexts from 10.12.6 also work, or must it be that early build of 10.12? The 17" MBP is running Sierra 10.12.6 at the moment.

I used 10.12.3 kexts, and it worked, so I'd assume 10.12.6 kexts would work as well.

 

[BookEmDanno]

...

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

View attachment 767266

Excellent dude!

Can hardly wait for your patch. Although I've been using Mojave boot from an external SSD drive on my unsupported MacBook Air 13" mid-2011, it does work but with sound and graphics glitches.

Mahalo Nui Loa (Thank You very much)

Danno

 

[visberry]

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

View attachment 767266

I am lost, what about NVIDIA 320/M

 

[dosdude1]

I am lost, what about NVIDIA 320/M

Mojave won't even boot on that machine at this point.

 

[AnonMac50]

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

View attachment 767266

This gives hope for my 2010 15". What about the GT 330M inside, would that work? I've lent this computer to a friend so I can't test it myself.

 

[visberry]

Mojave won't even boot on that machine at this point.

Can I help in any way, I have spare MacBook Pro 2010?

 

[Badruzeus]

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

View attachment 767266

Thanks. About a weird tint on Menu Bar, I also get this issue with Nvidia Fermi. But have no problem if Appearance=Dark, seems Apple bug with certain graphics, not really sure #atm caused of "Beta".

#EDIT: On Beta 1, my kexts on LE / SLE are all vanilla.. and Menu Bar tint issue was already there.

 

[ricoc90]

Just to give some additional information:

I've also had the flat gray menu bar (and finder and context menus) on the first beta with my GT 710 Kepler card. Apps that required Metal didn't work either (basically the ported iOS apps; Stocks, News etc) . The second beta fixed this for me. However, my card does support Metal so maybe the issue lays there?

 

[jackluke]

Sorry to be so blunt but literally NOTHING you have said in this post makes technical sense. We know that the OS will boot on computers without SSE4.2 because I tried it on virtualbox. The problem with IOUSBFamily is that the OHCI driver is removed (every computer with pre-Nehalem/Core i series processors uses OHCI) and the old driver doesn't work. There also seems to be some problem with CPU power management on Core 2 Duos but we're not sure yet. There's no sse4.2 requirement.

Sorry but I have to reply, I could be agree on the part: “no correlation SSE4.2 with IOUSB”

I admitted before "I say a nonsense", but "NOTHING" uppercase seems a little to much.

But if you confirmed that these sentences are nonsenses:

1) on any based MacOS X series there is a stage 1 Apple logo with a progress bar (or loading circle), followed by a stage 2 Apple logo with a progress bar (called when graphics kext are fully loaded);

2) if notice a Prohibitory symbol after started up the machine macOS in stage 1, this usually depends from a mismatched Extensions kexts permission folder (maybe occurred after downgraded or wrongly patched some kexts) or an invalid PrelinkedKernels folder content generated;

3) the kernel unix executable in MacOS located in S/L/Kernels (since Yosemite) is one of the main responsible in booting MacOS libraries, frameworks, services, processes and kexts


then today I have learned something.


After all, believe or not, I did already understood that the kp could depend from some:
AppleACPIPlatform.kext
IOPlatformPluginFamily.kext
IOPlatformPluginLegacy.kext

and lets say also all the other **ACPI** tagged kexts

But I don't like to play with these tricky kexts so I dropped.

No controversy on my part.


-------------------------------------------------------------------


I confirm QE/CI work on IntelHD3000, thanks to the guy that on that non-mac i3 has found the trick, and yes Mojave light mode has translucent greyed menu bar, but I don’t care since I use it in dark mode, and that is the main reason I will switch to Mojave.

I used MacOS Sierra 10.12.6 IntelHD3000 kexts they are just five:

AppleIntelHD3000Graphics.kext
AppleIntelHD3000GraphicsGA.kext
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext


So apparently this time a simple kext/bundle adding has worked fine.

 

[jackluke]

Can I help in any way, I have spare MacBook Pro 2010?

I do have a similar machine a macbook 2010, if you want try a thrill, premised you boot with:
nvram boot-args=“-no_compat_check” (set from any MacOS recovery)

You can boot a Mojave recovery partition or a Mojave usb installer.

Perhaps you could miss any USB HID included internal keyboard and trackpad. The only way to play with would be a Bluetooth keyboard/mouse but I get them unpaired too, even if they are paired before in the other HighSierra recovery and from a Mojave supported mac.

So I repeat this laptop without Mojave’s recognized usb is almost useless.
I continue to think (getting wrong) that a patched kernel or on the fly patched kext to emulate or bypass a SSE4.2 cpu instruction is required to boot Mojave and his IOUSB Family HID on machines with our similar hardware, this is my opinion.

 

[Starplayr]

VMware Fusion will run on your machine. It runs on my 2006 Mac Pro just fine. I have Fusion 8.x (at least 8.1 could be later) on mine.

It will support SSE 4.x if your CPU has that feature. It will not create / emulate SSE 4.x if it is not supported by your CPU.

This machine can’t run the latest VMWare fusion 10, least my quad core same model can’t

Parallels will sim SSE4.2 and USB3 our of the box. No mods.
[doublepost=1529667734][/doublepost]

This machine can’t run the latest VMWare fusion 10, least my quad core same model can’t

Parallels will sim SSE4.2 and USB3 our of the box. No mods.

Beta 2 runs very good after installing Parallels Tools. No metal but the video does not lag either.

 

[smokesletsgo]

Sorry but I have to reply, I could be agree on the part: “no correlation SSE4.2 with IOUSB”

I admitted before "I say a nonsense", but "NOTHING" uppercase seems a little to much.

But if you confirmed that these sentences are nonsenses:

1) on any based MacOS X series there is a stage 1 Apple logo with a progress bar (or loading circle), followed by a stage 2 Apple logo with a progress bar (called when graphics kext are fully loaded);

2) if notice a Prohibitory symbol after started up the machine macOS in stage 1, this usually depends from a mismatched Extensions kexts permission folder (maybe occurred after downgraded or wrongly patched some kexts) or an invalid PrelinkedKernels folder content generated;

3) the kernel unix executable in MacOS located in S/L/Kernels (since Yosemite) is one of the main responsible in booting MacOS libraries, frameworks, services, processes and kexts


then today I have learned something.


After all, believe or not, I did already understood that the kp could depend from some:
AppleACPIPlatform.kext
IOPlatformPluginFamily.kext
IOPlatformPluginLegacy.kext

and lets say also all the other **ACPI** tagged kexts

But I don't like to play with these tricky kexts so I dropped.

No controversy on my part.


-------------------------------------------------------------------


I confirm QE/CI work on IntelHD3000, thanks to the guy that on that non-mac i3 has found the trick, and yes Mojave light mode has translucent greyed menu bar, but I don’t care since I use it in dark mode, and that is the main reason I will switch to Mojave.

I used MacOS Sierra 10.12.6 IntelHD3000 kexts they are just five:

AppleIntelHD3000Graphics.kext
AppleIntelHD3000GraphicsGA.kext
AppleIntelHD3000GraphicsGLDriver.bundle
AppleIntelHD3000GraphicsVADriver.bundle
AppleIntelSNBGraphicsFB.kext


So apparently this time a simple kext/bundle adding has worked fine.

Could you share these kexts?

edit: nevermind. extracted the kexts from Sierra installation app.

 

[Starplayr]

I do have a similar machine a macbook 2010, if you want try a thrill, premised you boot with:
nvram boot-args=“-no_compat_check” (set from any MacOS recovery)

You can boot a Mojave recovery partition or a Mojave usb installer.

Perhaps you could miss any USB HID included internal keyboard and trackpad. The only way to play with would be a Bluetooth keyboard/mouse but I get them unpaired too, even if they are paired before in the other HighSierra recovery and from a Mojave supported mac.

So I repeat this laptop without Mojave’s recognized usb is almost useless.
I continue to think (getting wrong) that a patched kernel or on the fly patched kext to emulate or bypass a SSE4.2 cpu instruction is required to boot Mojave and his IOUSB Family HID on machines with our similar hardware, this is my opinion.

So you have Mojave booted to the GUI just no input devices (yet)?
[doublepost=1529676458][/doublepost]

Could you share these kexts?

edit: nevermind. extracted the kexts from Sierra installation app.

here is a dumb question.

On the recovery partition, where is the kernel stored?

 

[abcdefg12345]

Using @Badruzeus's info, I was able to get full graphics acceleration with Intel HD Graphics 3000 under Mojave on my 2011 13" MacBook Pro!! It seems to work great, with the exception of the menu bar, which has a weird tint to it. I'll test it with some more GPUs, and if it works, it may be time for an automated patch release!

This is good news for me, Im staying on my early 2011 MacBook Pro until apple update their Mac hardware with coffee lake cpu hopefully during august event.

Hoping apple will release a 15 inch touch bar MacBook Pro with i9 processor, 16gb ram, 500gb ssd as a base model for the 15 inch Macs with a price no higher than their current pricing.

 

[Starplayr]

About the USB issue, would Adding USB-C or USB3 in a Mac Pro work around this USB problem on at least the Mac Pro Systems?

Also on Machines with Thunderbolt, would a USB adapter work?

Just looking for workarounds.
[doublepost=1529679638][/doublepost]

This is good news for me, Im staying on my early 2011 MacBook Pro until apple update their Mac hardware with coffee lake cpu hopefully during august event.

Hoping apple will release a 15 inch touch bar MacBook Pro with i9 processor, 16gb ram, 500gb ssd as a base model for the 15 inch Macs with a price no higher than their current pricing.

Needs to be 32GB RAM, 6-8 USBC/Thunderbolt3 ports. I hate that connector btw. They easily come loose from Adapterland. The old stuff 2012 and 2014 MacBook Pros are still my favorite Units. I love my 2009 MacBookPros (have not even attempted MoJo on em yet).

 

[tsialex]

About the USB issue, would Adding USB-C or USB3 in a Mac Pro work around this USB problem on at least the Mac Pro Systems?

Also on Machines with Thunderbolt, would a USB adapter work?

Just looking for workarounds.

No, because a lot of things are connected on the internal USB bus, like keyboard/trackpad/Bluetooth.

 

[Starplayr]

No, because a lot of things are connected on the internal USB bus, like keyboard/trackpad/Bluetooth.

Right but if the USB 1.1 / 2.0 bus is not working a PCIe Card or Thunderbolt adapter should and would work with devices connected to those adddd ports. They won’t be on the same Bus. And they will probably use different drivers.

Another engineering workaround would be some type of emulator for the legacy USB bus to work.

I don’t think Bluetooth is on the same channel or bus as USB. It uses its own card much like WiFi.
[doublepost=1529683383][/doublepost]USB on my Mac Pro 2008 in recovery and install works on Mo. Have not gotten it to boot natively to know if it does not.

I am pretty impressed with Parallels running Mojave. Got 4k video to work with scaling with Parallels tools installed. It’s fast enough to develop software on.
[doublepost=1529683451][/doublepost]

Right but if the USB 1.1 / 2.0 bus is not working a PCIe Card or Thunderbolt adapter should and would work with devices connected to those adddd ports. They won’t be on the same Bus. And they will probably use different drivers.

Another engineering workaround would be some type of emulator for the legacy USB bus to work.

[doublepost=1529683383][/doublepost]USB on my Mac Pro 2008 in recovery and install works on Mo. Have not gotten it to boot natively to know if it does not.

I am pretty impressed with Parallels running Mojave. Got 4k video to work with scaling with Parallels tools installed. It’s fast enough to develop software on.

 

[jackluke]

So you have Mojave booted to the GUI just no input devices (yet)?
[doublepost=1529676458][/doublepost]here is a dumb question.

On the recovery partition, where is the kernel stored?

No, I have booted GUI from Mojave recovery or Mojave usb installer (that are the same thing) with no input devices.

Exactly that's the core of the matter, on the recovery partition the Mojave kernel is embedded in the prelinkedkernels folder, and I tried to cheat my main Mojave system but is like it can't match a file signature and so rebuilds immediately the kext kernel cache during the boot.

But please (I refer not to you in general), do not confuse, if boots on Virtualbox from unsupported mac a Mojave with SSE4.1 or usb devices then there are good chances for my real mac host machine, Virtualbox is an amazing software but it is a BIOS-UEFI virtualization, not pure EFI, infact Clover or similar bootloader is needed, I could understand if someone succeed in booting Mojave from unsupported mac guest virtual machine on VMFusion or Parallels but also in this case the behavior is still different from a real mac host machine EFI pure.

 

[Starplayr]

No, I have booted GUI for Mojave recovery or Mojave usb installer (that are the same thing) without input devices.

Exactly that's the core of the matter on the recovery partition the Mojave kernel is embedded in the prelinkedkernels folder, and I tried to cheat my main Mojave system but is like it can't match a file signature and so rebuild immediately the kext kernel cache during the boot.

But please (I refer not to you in general), I cannot read if boots on Virtualbox from unsupported mac a Mojave with SSE4.1 or usb devices then there are good chances for my real mac, Virtualbox is an amazing software but it is a BIOS-UEFI virtualization, not pure EFI, infact Clover is needed, I could understand if someone succeed in booting Mojave from unsupported mac virtual machine on VMFusion or Parallels but also in this case the behavior is still different from a real mac pure EFI.

Just it clarify what I have working:

I have USB devices working on a real Mac on Mojave’s recovery partition. 2008 3,1

On Virtualbox, no input, until I installed the 3.0 USB Ext’s for VirtualBox’s host. 1.1 did not work and that seems to like what you are getting now on a real machine. I know it’s not the same thing and its just a simulation. It does use Apple EFI’s bootloader after Clover, but also does not install for me as the emulated hardware out of the box does seem to have the right instructions. It only boots the installer thats it. And does not install.

Now on Parallels it does run like a supported Mac does. Clover is not needed and it uses Apple’s EFI partition accurately. It does the entire install and goes into the goes without any issues. I'd go further into this but there does not seem to be any interest, so I won't.

My Mac’s EFi does not work really at all with Apple’s new EFI scheme because it’s firmware does not have an update path. And this could be the main problem why my Mac cannot boot Mojave MacOS all the way. That is if SSE4,2 is really not required. Jury still lit on that one because I cannot get to stage 2 ever natively.

I am trying to be helpful here and test other avenues. I know the ultimate goal is to run as native with as few patches as possible. I can’t get the 2008 model to boot without some type of emulation. And the fact that Parallels runs Mojave perfectly fine on my unsupported Mac indicates the hardware can do it with the proper emulation whether it’s the firmware/EFI/UEFI/SMBIOS, USB3, SSSE3, SSE4.2, Metal2/3, Clover, Kext.

Chow

 

[BookEmDanno]

Mojave Beta 2 on unsupported Macbook Air 13" mid-2011

Update on my issues regarding Beta 2 (did not encounter these on Beta 1)

1. Graphics --- partially fixed. Maps is rendering properly. My screen brightness is adjustable but my keyboard lights are not.
2. Sound --- still does not work.

So I guess copying the AppleIntelHD3000* kext, plugin and bundle files from Sierra did the trick.
The AppleHDA.kext file from same source did not work to resolve the sound issue.

Do you guys have any suggestions or extra files to copy from either Sierra or High Sierra?

Mahalo (Thanks)

 

[parrotgeek1]

Mojave Beta 2 on unsupported Macbook Air 13" mid-2011

View attachment 767303

Update on my issues regarding Beta 2 (did not have encounter these on Beta 1)

1. Graphics --- partially fixed. Maps is rendering properly. My screen brightness is adjustable but my keyboard lights are not.
2. Sound --- still does not work.

So I guess copying the AppleIntelHD3000* kext, plugin and bundle files from Sierra did the trick.
The AppleHDA.kext file from same source did not work to resolve the sound issue.

Do you guys have any suggestions or extra files to copy from either Sierra or High Sierra?

Mahalo (Thanks)

Use high Sierra hda instead of sierra

 

[jackluke]

I have managed to extract the prelinkedkernel file the one in the Mojave recovery.

I have compiled the binary lzvn and then extracted the content, well as deduced it contains the kernel, some main system kexts and a couple of dictionary files, will try tomorrow if can cheat the main system prelinkedkernel, even if I have compared the extracted recovery kernel with main system kernel and they have the same size 15,8 mb so I don’t think this could resolve the standard Mojave quick reboot issue since I expected two different files lets say a different recovery kernel, instead they look the same.

 

[Starplayr]

I have compiled the binary lzvn and then extracted the content, well as deduced it contains the kernel, some main system kexts and a couple of dictionary files, will try tomorrow if can cheat the main system prelinkedkernel, even if I have compared the extracted recovery kernel with main system kernel and they have the same size 15,8 mb so I don’t think this could resolve the standard Mojave quick reboot issue since I expected two different files lets say a different recovery kernel, instead they look the same.

I saw the prelinked kernel but did not know what to do with it.

I must say that is some great work. It may not help you, but I believe that may lead to others getting Mojave off the ground that could not previously.

I'll try to find out what is causing the USB not to work. I am booting the recovery partition with Clover and it is probably doing some stuff under the hood, allowing the USB to run. I'll the same partition on how you guys are launching it and see if my USB goes away. We may be able to find what the correlation is and what's missing.

 

[tsialex]

I don’t think Bluetooth is on the same channel or bus as USB. It uses its own card much like WiFi.

Even on a Mac Pro, Bluetooth modules are connected on the internal USB bus. A lot of other things are connected on the internal bus of MacBooks/MacBooks Pro.