macOS 10.14 Mojave on Unsupported Macs Thread

[Badruzeus]

Pardon my ignorance. How do you determine or confirm or view "acceleration"? Via System Report or ???

Thanks.

Many ways. No Manu Bar tranparency.. opening Lauchpad, Mission Control, screensavers, etc. but get terrible slow / lag issue it maybe caused by graphic acceleration problem.., no animation when add/remove Dashboard widgets, get error warning when opening DVDPlayer.app - Help - Show Supported Features, opening any video files using VLC you'll get a blank window.., VRam size (sometimes) not shown properly on About This Mac, wrong info about graphics details using 3rd party app (for example: OpenGL Extensions Viewer), not able to run any game that require graphics accel, etc.

 

[toru173]

After more indeep tests, I recap:

I do own a white macbook 2010 with core 2 duo Penryn architecture, Nvidia 320m MCP89 controller very similar to Nvidia 9400m MCP79.

We know that to boot on an unsupported mac the nvram parameter "-no_compat_check" (maybe in conjunction with "-kext-dev-mode=1") is mandatory.

I cannot install a Mojave system directly into my old macbook but I’ve installed it completely from another supported mac.

Without any alterations, or virtualization, or Clover boot loader, using instead a usb Mojave installer or a Mojave recovery partition or his basesystem.dmg restored to a internal disk partition, I can boot them till to GUI but without any USB devices detected and so without any input devices.
While if try to boot main mojave system it boots until a certain phase but then results in quick reboot or kp after GPU kexts are loaded but to me they are not the guilty.

Maybe due to ACPI SSDT issues, SSE4.2 instruction, USB family, we have no certainly.
That’s the focus point.

Compiling LZVN (thanks to who developed the sources from Yosemite beta), I have decompressed a prelinkedkernel file in “S/L/PLKernles” inside which there are:

- some general basilar kexts (they are in total about 140)

- a general dictionary plist file containing more than 2500 lines of plain text with refences to all the infos.plist of those kext

- the kernel unix executable file

Well after deep comparison I noticed that they fit to the same contained inside a compressed LZVN prelinkedkernel file withdrawn from a clean Mojave system installed on a supported mac, usb installer or recovery partition, exactly the same no differences.



I have to a premise:

the prelinkedkernel file since Yosemite release is the KEY to boot any future MacOS version’s frameworks, services, processes and any additional kexts.

When a prelinkedkernel is generated typically after a system installation, it creates a Kernecache ID with a signature, and after done you can boot a MacOS system even without a kernel file in S/L/Kernels while the Extensions folder is EVER required because there is a matching between the kext folder archived inside the prelinkedkernel and the real Extensions folder, instead the kernel is EMBEDDED IN.



I have done many attempts, I would say the relevance is:

Mojave kernel is XNU Darwin 18.0.0



Well, I have tried to cheat the main system, wanted to embed one of these:

Sierra 10.12.6 kernel = Darwin 16.7.0

High Sierra 10.13.6 beta 3 kernel = Darwin 17.7.0



But I could not succeeded, I mean the Mojave system, I don’t know how, calls ever his original Darwin 18.0.0, doesn’t care of S/L/Kernels folder content, even boot with a empty kernels folder since it has his original kernel embedded in prelinkedkernel file.

Just to point out, if you delete the prelinkedkernel file cannot more boot nothing and will see a Prohibitory symbol after the apple logo, but you can easily fix it copying the prelinkedkernel file from another Mojave installation to your Mojave S/L/Prelinkedkernels path.


In conclusion, I think that Metal feature in this case is the last of our issues since you can reach the GUI of MacOS even with a generic WXGA or non accelerated GPU kext.

So if you would like boot (without kernel panic or quick reboot and with input usb devices) Mojave on these kind old hardware core 2 duo, I would suggest these attempts only to those who feel very confident:

- Locate your parameter path boot plist and forcing to boot mac with a previous macOS kernel (or better embed it in LZVN archive creating a patched prelinkedkernel) and valuate the behavior.

- Or try to install Mojave with its required patch (osinstall.mpkg) directly from an unsupported mac and force a risky EFI firmware update on the unsupported mac maybe luckily eluding the platform hardware and features checks.


If I get some new ideas will do other tests and share my opinion.

I've tried similar methods in the past. There is information floating around with boot-args that supposedly ignore the kernel cache, but I think they have been deprecated (perhaps since Yosemite, as per your post). An ongoing project of mine is to get macOS to the command line using as little as possible. I'd custom build a relinked kernel, include basic kexts and either bash or busybox.

If we are getting in to the realms of kernel modification, we may need to wait until the source comes out! When I have some time I might go back to my previous project, but I'm currently working on the "Mojave wants to install to APFS" problem

 

[Badruzeus]

, but I'm currently working on the "Mojave wants to install to APFS" problem

There's method to get macOS Mojave installed into HFS+ Volume: GPT/MBR. (DWYOR)

 

[toru173]

There's method to get macOS Mojave installed into HFS+ Volume: GPT/MBR. (DWYOR)

Thank you for the heads up! I was heading in a similar direction, I just had to put it on hold while I finished assessment for Uni. I'll pull apart their OSInstaller and compare it to mine.

 

[Starplayr]

Thank you for the heads up! I was heading in a similar direction, I just had to put it on hold while I finished assessment for Uni. I'll pull apart their OSInstaller and compare it to mine.

I believe there are some plist files on the macOSInstaller that has a Boolean to install on AFPS or not. And I think it's in more than 1 place.

 

[toru173]

I believe there are some plist files on the macOSInstaller that has a Boolean to install on AFPS or not. And I think it's in more than 1 place.

You're right, however the OSInstaller program actually ignores these! I'm still pulling apart OSInstaller, but I found this string inside it which explains my troubles earlier:

 

[Starplayr]

You're right, however the OSInstaller program actually ignores these! I'm still pulling apart OSInstaller, but I found this string inside it which explains my troubles earlier:

View attachment 767605

Mmmmm... how about you remove its key (and its value)? Says it's ignoring the value, I wonder if the key is missing it will not do the conversion. Just a wild guess.

 

[jackluke]

I've tried similar methods in the past. There is information floating around with boot-args that supposedly ignore the kernel cache, but I think they have been deprecated (perhaps since Yosemite, as per your post). An ongoing project of mine is to get macOS to the command line using as little as possible. I'd custom build a relinked kernel, include basic kexts and either bash or busybox.

If we are getting in to the realms of kernel modification, we may need to wait until the source comes out! When I have some time I might go back to my previous project, but I'm currently working on the "Mojave wants to install to APFS" problem

After I unpacked the LZVN prelinkedkernel, noticing that essentials kexts are around 140, I tried too boot with "kextunload" command as like to create an emergency booting less than a safe mode but over than a recovery mode.

But another doubt pervades me:

mounting the EFI partition there are two .scap files related both to the mac firmware.

In particular there is this path /EFI/APPLE/EXTENSIONS with a 15 mb firmware.scap file

Premised that just mounting EFI partition is dangerous since during spotlight indexing could damage it and only if you are brave, but mainly very very expert can manage this;

Well, since these files are updated on every MacOS major upgrade I associate the things.

When anyone powers up his mac there is the typical chime sound which means every hardware motherboard EFI checks are passed so leads to (holding option key) Startup Manager.


From there can see that (on a laptop in my case but applicable to all macs) all these peripherals are detected and perfectly working:

- internal trackpad and keyboard (aka usb input devices);
- wifi and bluetooth (aka pci express devices I guess even if bluetooth is usb input)
- lets say a standard WXGA graphics not only in greyscale but high colors too (I can verify if using Refit or Refind bootloader)
- usb host controllers (like using a usb drive or external as booting device)
- thunderbolt, ethernet and so on

every these nice stuffs to me handling with that firmware.scap file, that is a compressed kexts container.
So what happens if we copy it from a supported mac? I think the risk of brick or unresponsive Startup Manager becomes very very high. So leave it for now.

In conclusion, I think and almost sure that there is a kind of three-way screening after boot a MacOS system between the firmware.scap, the prelinkedkernel and the S/L/E folder.

Thus forcing a Mojave 10.14 EFI firmware or patching many essentials kexts or a XNU kernel is the minimum requirement for booting on legacy machines. This is my opinion.

 

[soniXx123]

how u guys download the image of mac os? because i try in the developer area and my mac is not supported

 

[mikejrslac]

I patched image.
it has force-install mode.

but you should edit boot-args by typing this above
(반드시 아래의 코드를 terminal에 입력해주세요.)
sudo nvram boot-args="-no_compat_check"

this is our system requirements
(최소사양-HighSierra랑 동일)

• iMac (Late 2009) 및 이후 모델
• MacBook (Late 2009) 및 이후 모델
• MacBook Pro (Mid 2010) 및 이후 모델
• MacBook Air (Late 2010) 및 이후 모델
• Mac mini (Mid 2010) 및 이후 모델
• Mac Pro (Mid 2010) 및 이후 모델

This is unstable version. please do not use this with your main OS.
(불안정한 버전입니다. 멀티부팅으로 구성하여 설치하시기 바랍니다.)
Download_Link(다운로드)



If you want to make USB bootable installer,
use this tool.
download disk tool

[doublepost=1529924132][/doublepost]

I patched image.
it has force-install mode.

but you should edit boot-args by typing this above
(반드시 아래의 코드를 terminal에 입력해주세요.)
sudo nvram boot-args="-no_compat_check"

this is our system requirements
(최소사양-HighSierra랑 동일)

• iMac (Late 2009) 및 이후 모델
• MacBook (Late 2009) 및 이후 모델
• MacBook Pro (Mid 2010) 및 이후 모델
• MacBook Air (Late 2010) 및 이후 모델
• Mac mini (Mid 2010) 및 이후 모델
• Mac Pro (Mid 2010) 및 이후 모델

This is unstable version. please do not use this with your main OS.
(불안정한 버전입니다. 멀티부팅으로 구성하여 설치하시기 바랍니다.)
Download_Link(다운로드)



If you want to make USB bootable installer,
use this tool.
download disk tool

Can you describe how you patched the image to force-install so I can use the method to install the second beta build of Mojave ?

 

[testheit]

I'm new to this topic but I tested a few things on my MacBookPro5,1 (2008) so far:

- I could run Mojave inside VMware Fusion. I replaced GeForce*, NVDA* and IOAcceleratorFamily2 kexts with the one from Sierra (Pic 1)
- If I try to boot Mojave natively boot process get stuck (Pic 2)
- If I add LegacyUSBInjector.kext from dosdude1 and then try to boot natively the boot process didn't get stuck but I get a kernel panic later (Pic 4, Pic 5), right after Pic 3.

Am I doing something completely wrong? Or anything I could test?
If I could run Mojave in VM is it theoretically possible to run it natively on that machine?

 

[jackluke]

I'm new to this topic but I tested a few things on my MacBookPro5,1 (2008) so far:

- I could run Mojave inside VMware Fusion. I replaced GeForce*, NVDA* and IOAcceleratorFamily2 kexts with the one from Sierra (Pic 1)
- If I try to boot Mojave natively boot process get stuck (Pic 2)
- If I add LegacyUSBInjector.kext from dosdude1 and then try to boot natively the boot process didn't get stuck but I get a kernel panic later (Pic 4, Pic 5), right after Pic 3.

Am I doing something completely wrong? Or anything I could test?
If I could run Mojave in VM is it theoretically possible to run it natively on that machine?

I've done almost the same your tests, no need to replace GeForce*, NVDA* and IOAcceleratorFamily2 kexts since VMW use it's own vm tools, I suppose you are minimum on 8.5.8 since only from this version apfs file system is supported, anyway I confirm from a VM machine USB HOST input/output devices are correctly detected with no annoying verbose messages:

AppleUSBHostPort::disconnect: persistent enumeration failures

I started to think this kernel panic, assured what I said before, could depend also from apfs.efi or apfs.kext or something related, maybe installing Mojave in HFSplus file system could have a different behavior.

 

[testheit]

I've done almost the same your tests, no need to replace GeForce*, NVDA* and IOAcceleratorFamily2 kexts since VMW use it's own vm tools, I suppose you are minimum on 8.5.8 since only from this version apfs file system is supported, anyway I confirm from a VM machine USB HOST input/output devices are correctly detected with no annoying verbose messages:

AppleUSBHostPort::disconnect: persistent enumeration failures

I started to think this kernel panic, assured what I said before, could depend also from apfs.efi or apfs.kext or something related, maybe installing Mojave in HFSplus file system could have a different behavior.

Yes, it's Version 8.5.8 and I know that I doesn't have to replace kexts to run it inside the VM. But I also wanted to test, what happens if I boot it natively on my MacBook (I forgot to say that I installed Mojave onto a USB drive, so if I boot in VM or natively on my MacBook it's the same Mojave installation on the USB drive).
If I boot without the LegacyUSBInjector.kext and get stuck very early in the boot process is this a indicator that there are some problems with booting from USB devices (and apfs)? Maybe I could try to install Mojave onto a hfs partition.
What does the later kernel panic cause, when I add LegacyUSBInjector.kext?

 

[jackluke]

Yes, it's Version 8.5.8 and I know that I doesn't have to replace kexts to run it inside the VM. But I also wanted to test, what happens if I boot it natively on my MacBook (I forgot to say that I installed Mojave onto a USB drive, so if I boot in VM or natively on my MacBook it's the same Mojave installation on the USB drive).
If I boot without the LegacyUSBInjector.kext and get stuck very early in the boot process is this a indicator that there are some problems with booting from USB devices (and apfs)? Maybe I could try to install Mojave onto a hfs partition.
What does the later kernel panic cause, when I add LegacyUSBInjector.kext?

The same I use an external usb SATA ssd with GPT GUID partition map and Mojave installed from a supported Mac, I didn't know of a legacyUSBinjector kext, I think you have installed Mojave from a virtual machine that's why you stuck during native boot, instead I have installed from a supported Mac and apart USBHost error, natively external boot everything seems fine until, just before the LoginUI, a weird quick reboot occurs after all verbose lines went correctly.

The new interesting point is maybe try installing Mojave into a hfs+ and see what happens either virtual and natively.

 

[bosozoku]

Could someone check please, does dynamic background wallpaper change work on HD3000 with Sierra 10.12.x kexts?

 

[jackluke]

Could someone check please, does dynamic background wallpaper change work on HD3000 with Sierra 10.12.x kexts?

Dynamic Background/Wallpaper time-shifting feature according to the local sunset/sunrise DayTime-Light will not work neither on any supported Mac until maybe the Mojave golden master release.

Anyway there are other ways to achieve a similar effect with "Change pictures" every chosen minutes, but the real add on feature at least on Beta 2 doesn't still work on supported Mac.

There is on GitHub or elsewhere someone that explains how to get the Mojave desert wallpapers switching effect on previous MacOS.

 

[bosozoku]

Dynamic Background/Wallpaper time-shifting function according to the DayTime-Light Night and Day will not work neither on any supported Mac until the Mojave golden master release.

Anyway there are other ways with "Change pictures" every minutes, but the real add on at least on Beta 2 doesn't work.

Thank you!
I will get second HDD and try to install Mojave tomorrow.
Is there a complete tutorial how to install it without having developers account?
And to enable GPU acceleration and sound the following steps are: disable csrutil -> replace kexts with kextbeast -> rebuild kext cache -> enable csrutil, right?

 

[jackluke]

Thank you!
I will get second HDD and try to install Mojave tomorrow.
Is there a complete tutorial how to install it without having developers account?
And to enable GPU acceleration and sound the following steps are: disable csrutil -> replace kexts with kextbeast -> rebuild kext cache -> enable csrutil, right?

I use a dev account on a supported Mac, but Internet is resourceful.

Just the AppleHDA will be replaced, the intelHD3000 kexts are totally missing in Mojave, so will be freshly copied.

Those steps appear correct, provided that I don't like KextBeast.

 

[smokesletsgo]

[doublepost=1529924132][/doublepost]


Can you describe how you patched the image to force-install so I can use the method to install the second beta build of Mojave ?

Would like to know this also. Anyone?

 

[dosdude1]

Would like to know this also. Anyone?

I'll be working on a preliminary automated patcher in the next couple days, which will automate the process of creating a patched installer.

 

[DaniloGeekDude]

Many ways. No Manu Bar tranparency.. opening Lauchpad, Mission Control, screensavers, etc. but get terrible slow / lag issue it maybe caused by graphic acceleration problem.., no animation when add/remove Dashboard widgets, get error warning when opening DVDPlayer.app - Help - Show Supported Features, opening any video files using VLC you'll get a blank window.., VRam size (sometimes) not shown properly on About This Mac, wrong info about graphics details using 3rd party app (for example: OpenGL Extensions Viewer), not able to run any game that require graphics accel, etc.

Thank you for these info.
As for OpenGL Extensions Viewer, clicked on the link, and I only saw Windows and iOS versions. Anything similar that will work on a Mac?

Kind Regards.
[doublepost=1529936959][/doublepost]

I'll be working on a preliminary automated patcher in the next couple days, which will automate the process of creating a patched installer.

Thank you for your Sierra and High Sierra patcher. Your mention on the above Mojave (I'm assuming) is for a full featured patcher as your others?

Best Regards.

 

[dosdude1]

Thank you for these info.
As for OpenGL Extensions Viewer, clicked on the link, and I only saw Windows and iOS versions. Anything similar that will work on a Mac?

Kind Regards.
[doublepost=1529936959][/doublepost]

Thank you for your Sierra and High Sierra patcher. Your mention on the above Mojave (I'm assuming) is for a full featured patcher as your others?

Best Regards.

It will be eventually, but as of now it will only be a preliminary release for testing.

 

[redheeler]

We have. Just not on dual gpu laptops

Then would you mind listing which GPUs you have gotten working so far? Tried to boot from the same Mojave install on my Mid 2011 27" iMac, and as expected it booted without full acceleration (AMD Radeon HD 6770M). AMD6000Controller.kext also showed as loaded there.

 

[dosdude1]

Then would you mind listing which GPUs you have gotten working so far? Tried to boot from the same Mojave install on my Mid 2011 27" iMac, and as expected it booted without full acceleration (AMD Radeon HD 6770M). AMD6000Controller.kext also showed as loaded there.

We've gotten HD3000, Arrandale HD Graphics, and nVidia GeForce GT 330M (sort of) working so far.

 

[redheeler]

We've gotten HD3000, Arrandale HD Graphics, and nVidia GeForce GT 330M (sort of) working so far.

So really just the 330M so far, which is only found on a dual-GPU laptop (MacBook Pro from 2010). Not sure what @parrotgeek1 meant in his reply, unless he has gotten some working that you and I don't yet know about.

For the 330M, I assume you used the kexts from Sierra? If so, that method doesn't appear to work for the AMD GPUs from 2011 (the kext shows as loaded, but no Quartz Extreme acceleration).