Jump to content
19 posts in this topic

Recommended Posts

 

Attached you will find my config.plist with Opencore 0.7.9

I would like to upgrade to Monterey 12.3 and to be honest I have already tried, but it doesn't boot so I went back. I'd like to try again though! Is there something wrong with my config.plist?

config.plist

Edited by johnny28

Try amending the following to your config.plist: 

 

  1. Kernel > Quirks > SetApfsTrimTimeout to (Number value) - previous patch using values -1 or 999 yields no effect for SSD trims on macOS 12
  2. Misc > Security > SecureBootModel to Disabled (String value) - can revert back to Default once macOS 12 installs successfully


Good luck!

Edited by aben
On 3/20/2022 at 5:10 PM, aben said:

Try amending the following to your config.plist: 

 

  1. Kernel > Quirks > SetApfsTrimTimeout to (Number value) - previous patch using values -1 or 999 yields no effect for SSD trims on macOS 12
  2. Misc > Security > SecureBootModel to Disabled (String value) - can revert back to Default once macOS 12 installs successfully


Good luck!

Don’t work.

My apologies for overlooking this but looks like AMD CPUs will now require AppleMCEReporterDisabler.kext for successful boot on macOS 12.3+ as it appears that Apple made changes to the SMC kernel which now tends to block non-Apple hardware from booting on 12.3+. Attaching the relevant kext below, this should hopefully fix your boot issues.

 

AppleMCEReporterDisabler.kext.zip

Edited by aben

My proficiency with running macOS on AMD systems is extremely limited (sorry about that) however I suggest you have a go at this potential solution outlined in this attached post (under UPDATE-2) for the issue you mentioned: https://www.insanelymac.com/forum/topic/335877-amd-mojave-kernel-development-and-testing/?do=findComment&comment=2658085

All the best and hope you get to enjoy the flavors of macOS Monterey on your AMD rig!

 

Edited by aben
On 3/22/2022 at 3:26 AM, aben said:

My apologies for overlooking this but looks like AMD CPUs will now require AppleMCEReporterDisabler.kext for successful boot on macOS 12.3+ as it appears that Apple made changes to the SMC kernel which now tends to block non-Apple hardware from booting on 12.3+. Attaching the relevant kext below, this should hopefully fix your boot issues.

 

AppleMCEReporterDisabler.kext.zip 2.81 kB · 2 downloads

Is this across the board for any non-Apple Hardware?

as in any

@makk

Only required for certain desktop-SMBIOS configs when coupled with Intel Ivy Bridge-based Xeon CPUs and now, once again, for AMD CPUs as well, starting with macOS 12.3+, due to Apple bringing back the check with AppleIntelMCEInteruptController which was first introduced with macOS Catalina 10.15 beta 4+. Affected SMBIOS:

  1. MacPro6,1
  2. MacPro7,1
  3. iMacPro1,1

 

Edited by aben
20 hours ago, aben said:

@makk

Only required for certain desktop-SMBIOS configs when coupled with Intel Ivy Bridge-based Xeon CPUs and now, once again, for AMD CPUs as well, starting with macOS 12.3+, due to Apple bringing back the check with AppleIntelMCEInteruptController which was first introduced with macOS Catalina 10.15 beta 4+. Affected SMBIOS:

  1. MacPro6,1
  2. MacPro7,1
  3. iMacPro1,1

 

 

@aben

 

Well how can we find out about all hardware?

 

where is this list?

 

Thank you! 

@makk

Info regarding the requirement of AppleMCEReporterDisabler kext for successful boot only when using AMD CPU's and dual-socket systems (eg; Intel Ivy Bridge based Xeon CPUs) can be found here: https://dortania.github.io/OpenCore-Install-Guide/ktext.html#extras

18 minutes ago, aben said:

@makk

Info regarding the requirement of AppleMCEReporterDisabler kext for successful boot only when using AMD CPU's and dual-socket systems (eg; Intel Ivy Bridge based Xeon CPUs) can be found here: https://dortania.github.io/OpenCore-Install-Guide/ktext.html#extras

@aben

 

Thanks I read that the other day.

 

What I mean is from the source Apple.

So how to work around this?

 

The profiles such as MacBook14,3 and so on lists the hardware it is privy to and can use. Anything not listed is non useable?  but this what hackers do, make it useable.

 

That's what clover is, opencore is and all these patched kexts that finds a way.

 

So how to tackle this problem?

 

What do you suggest?

 

I just purchased a used Acer Nitro 5 which is 4 cores no threads similar to the Phenom AMD no threads just cores.

 

It has the Nvidia GTX 1050 Ti and the Intel Core i5 7300HQ.

And I want this to scream in Monterey. LOL! So I have to hack the {censored} out of it so everything works and smokes

it's predecessors.  Just to do it is the fun.

 

Like building from scratch a desktop tower, but in this case is to take what is there a good source not the best source

and make it a screamer.  Like building a race car from what is a sort of a racecar.

Vanilla is no fun.  Might as well buy a mac

6 hours ago, makk said:

@aben

 

Thanks I read that the other day.

 

What I mean is from the source Apple.

So how to work around this?

 

The profiles such as MacBook14,3 and so on lists the hardware it is privy to and can use. Anything not listed is non useable?  but this what hackers do, make it useable.

 

That's what clover is, opencore is and all these patched kexts that finds a way.

 

So how to tackle this problem?

 

What do you suggest?

 

 @makk 

I'm afraid I don't quite apprehend what you mean here with respect to the boot issue mentioned by OP however, rest assured, the source I shared with you is the relevant source shared by the creators themselves of the mighty OpenCore boot-loader which, yes like you mentioned, allows you and myself to successfully run macOS with the help of patches, workarounds and relevant kexts provided by the same respected developers who go out of their way to help implement the back-end workarounds/hacks for us including the related AppleMCEReporterDisabler kext which, again, in this case is a patched kext, to be used only for users on AMD CPUs and dual sock systems when used with the listed SMBIOSes on macOS 10.15 and later. 

If you do not happen to experience the above mentioned issue by OP with regards to boot on AMD systems, then you are good. If you do have other issues that needs to be discussed, I would suggest you post a new thread for the same in the relevant forums, following InsanelyMac's posting guidelines.

Thank you!

Edited by aben
On 3/23/2022 at 1:21 PM, aben said:

My proficiency with running macOS on AMD systems is extremely limited (sorry about that) however I suggest you have a go at this potential solution outlined in this attached post (under UPDATE-2) for the issue you mentioned: https://www.insanelymac.com/forum/topic/335877-amd-mojave-kernel-development-and-testing/?do=findComment&comment=2658085

All the best and hope you get to enjoy the flavors of macOS Monterey on your AMD rig!

 

excuse my ignorance, how do you activate single-user mode?

1 hour ago, johnny28 said:

excuse my ignorance, how do you activate single-user mode?


There are two approaches:

  1. Holding Windows key + S before Apple logo boot screen (this method may not work on systems with broken firmware and/or incompatible SATA controllers)
  2. Use boot-arg value: -s (preferred method)

no problem I was looking for something similar to this AppleMCE for Intel, such as board id ignoring and the rest of the hardware by spoofing.

 

I think the person has FileVault2 enabled by default on Monterey at the creation time.

and he might be thinking it is something else.

10 hours ago, aben said:


There are two approaches:

  1. Holding Windows key + S before Apple logo boot screen (this method may not work on systems with broken firmware and/or incompatible SATA controllers)
  2. Use boot-arg value: -s (preferred method)

How can I check that I was able to activate user-mode?

1 hour ago, johnny28 said:

How can I check that I was able to activate user-mode?

@johnny28

 

Hello can you do me a favor and see if FileVault is enabled?

At the time of creating your login id and configs, you are presented with a dialog of options and benefits

to enable and disable, right after installing, You are presented with what to choose: Wifi, Ethernet, login id name password

and so forth.  One thing that is listed is FileVault. If this is enabled, your boot up is different from having no FileVault enabled.

 

Go into System Preference, FileVault and see it is enabled, if it is disable it.

11 hours ago, johnny28 said:

How can I check that I was able to activate user-mode?


Upon further testing, it looks like booting into true Single-User mode using traditional methods is no longer possible on macOS Catalina and later due to Apple leveling up their System Integrity Protection aka SIP which now locks system volumes to read-only mode. You will still need to go through Recovery Mode (Windows key + R) and run commands via Terminal to mount the volume with write permissions in order to make the relevant modifications to system files and/or configs which was previously possible with Single-User mode prior to Catalina.

Have you tried clean-installing macOS Monterey onto a separate partition of your SSD? If you haven't, I highly suggest you try this first as this would help us narrow down the issue you are facing better. If this works and you are able to login, then you may opt for the following options: 

  1. Use Time Machine to create a backup of your Big Sur user-profile and restore to clean-installed Monterey volume either via initial Setup screen or Migration Assistant, whichever works better for your situation.
  2. Try the approach of skipping the Setup Assistant and creating new user; but this will require you to boot into Recovery Mode and execute the relevant commands to create temp user as outlined in this post: https://www.insanelymac.com/forum/topic/335877-amd-mojave-kernel-development-and-testing/?do=findComment&comment=2658085

If you still face the login issue even after attempting the above mentioned options then I'm afraid it is due to a deeper underlying issue which can be quite hard to diagnose given the fact AMD systems require tons of kernel patching when it comes to hackintosh.

I'd also highly recommend you try posting your login issue at dedicated AMD forums which specifically caters to macOS on AMD systems, looks pretty active so you'll most likely find better support there: https://amd-osx.com
 

Edited by aben
×
×
  • Create New...