[pre-release] macOS Monterey

[miliuco]

3 hours ago, surenmunoo said:

Added an AMD AX7870 Graphics card only and changed symbols to iMacPro1.1 to work with that card

AMD AX7870 is supposed to work in macOS? It isn't in Dortania's GPU guide.

If you are using USB map kext, have you changed here SMBIOS model as in config.plist?

[ham4ever]

hi guys,

i got MacOS Monterey up and running, but i was trying to make bluetooth to work and installed BlueToolFixup.kext, and the hack froze on apple logo, so i signed it to my other hack in other ssd and deleted the kext,

 

now my problem is that i cant access Monterey anymore, i got "This version of Mac OS X is not supported on this platform!", while it was working before,

 

and  ssd name is BigSur 750 but after i access it through other Mac, it got - data name on it at the end "BigSur 750 - Data". 

 

 

[HenryV]

On 6/19/2021 at 1:29 PM, 5T33Z0 said:

 

Thanks for the screenshot. What does "ID do DIspositvo" mean in english. I don't have that in my list.

It means ID of the device.  Dispositivo=device

Edited June 21, 2021 by HenryV

[Guest 5T33Z0]

@ham4ever I ran into the same issue after after booting High Sierra on my stystem and then trying to get back into Big Sur. It seems like it breaks the seal or something in Big Sur or something. NVRAM Reset didn't fix it.

 

My workaround was:

adding boot-arg: -no_compat_check to config.plist

reboot into Big Sur

re-install Big Sur on top of the existing install.

remove the -no_compat_check boot-arg

reboot.

 

Maybe there's another way to repair the seal (bless?) but that's how I did it.

 

Edited June 22, 2021 by 5T33Z0

[iCanaro]

3 hours ago, 5T33Z0 said:

@ham4ever I ran into the same issue after after booting High Sierra on my stystem and then trying to get back into Big Sur. It seems like it breaks the seal or something in Big Sur or something. NVRAM Reset didn't fix it.

 

My workaround was:

adding boot-arg: -no_compat_check to config.plist

reboot into Big Sur

re-install Big Sur on top of the existing install.

remove the -no_compat_check boot-arg

reboot.

 

Maybe there's another way to repair the seal (bless?) but that's how I did it.

 

 

if it is the same thing that happens in my hacks with high sierra and big sur the situation is this:
high sierra in HFS started with Clover, at the first start it modifies the SystemVersion present in the big sur preboot; it is to be restored with a plist editor
Terminal:

Diskutil list

diskutil mount diskxsY

Locate

/ System / Volumes / Preboot

or

open / System / Volumes / Preboot

 

/ System / Library / CoreServices / SystemVersion.plist

Edited June 22, 2021 by iCanaro

[apfelnico]

I'm happy. The first beta is running:

 

 

 

 

 

 

 

 

 

 

 

 

 

[Guest 5T33Z0]

47 minutes ago, iCanaro said:

 

if it is the same thing that happens in my hacks with high sierra and big sur the situation is this:
high sierra in HFS started with Clover, at the first start it modifies the SystemVersion present in the big sur preboot; it is to be restored with a plist editor
Terminal:

Diskutil list

diskutil mount diskxsY

Locate

/ System / Volumes / Preboot

or

open / System / Volumes / Preboot

 

/ System / Library / CoreServices / SystemVersion.plist

 

Ahhh, okay, this totally makes sense. Thanks for the explanation.

[jsl2000]

1 hour ago, 5T33Z0 said:

 

Ahhh, okay, this totally makes sense. Thanks for the explanation.

Thanks for this solution which fixed my Clover's booting problem of Big Sur (11.x to be shown as 10.13.6) for a long time !

[iCanaro]

12 minutes ago, jsl2000 said:

Thanks for this solution which fixed my Clover's booting problem of Big Sur (11.x to be shown as 10.13.6) for a long time !

 

months ago I broke the boxes a lot to Jief and Slice for this inexplicable bug, then it was understood that the cause was high sierra which changed the systemversion in the big sur preboot, coupled with the Clover boot method (OC started regularly as it did not is based on what the systemversion reports), when everything was understood and since I was then the only one with this singular problem, nothing was done.
NB: if you restore the systemversion, then in the subsequent starts of high sierra, it does not change anything, it happens again at the next big sur update

[Guest 5T33Z0]

@iCanaro It's definitely a High Sierra and not a bootloader issue. Because it happened to me too with OpenCore.

Edited June 22, 2021 by 5T33Z0

[iCanaro]

5 hours ago, 5T33Z0 said:

@iCanaro It's definitely a High Sierra and not a bootloader issue. Because it happened to with OpenCore.

 

anyway I assure you that OC started regularly up to 0.6.6 (lately I don't update OC), this bug I had on the Z68, Z97 and T-RyZo

[LockDown]

3 hours ago, iCanaro said:

diskutil mount diskxsY

diskxsY of highsierra or bigsur/Monterey?

Edited June 22, 2021 by ellaosx

[Guest 5T33Z0]

@ellaosx Big Sur Preboot if I understood correctly.

 

BTW: latest 0.7.1 OpenCore build add a new enty to config.plist: Kernel > Scheme > CustomKernel. Just in case you get "no schema for" error on boot

[Slice]

On 6/21/2021 at 12:41 PM, miliuco said:

AMD AX7870 is supposed to work in macOS?

Sure!

[Guest 5T33Z0]

Lenovo T530 with IntelHD4000 running Monterey with Dual Screen Support. Here's how I did it (took less than an hour and 2 boot attempts):

• If you can, use a working PC and install Monterey on an extra SSD
• Download Chris1111's Monterey Patcher https://github.com/chris1111/Patch-HD4000-Monterey to patch in Intel HD4000 Support and run it. Many Thanks for this great tool.
• Get the EFI from your Laptop on a USB Stick and modify it:
  • For Broadcom BT users: disable BrcmBluetoothInjector.kext, add BlueToolFixup.kext (can be found in this thread), update config with ProperTree
  • Modify config.plist with SMBIOS infos (I am using macBookPro11,4) and add additional necessary boot-args mentioned in Chris' Repo
• Shutdown your PC
• Take out the disk and the USB drive
• Put the disk in your Lapotop
• Boot from the Stick
• Bingo! Monterey on a Laptop from 2013

 

EFI available on my github repo:  https://github.com/5T33Z0/Lenovo-T530-Hackinosh-OpenCore

 

Edited June 24, 2021 by 5T33Z0

[jsl2000]

1 hour ago, 5T33Z0 said:

Lenovo T530 with IntelHD4000 running Monterey with Dual Screen Support.How I did it (took less than an hour and 2 boot attempts):

• If you can, use a working PC and install Monterey on an extra SSD
• Download Chris1111's Monterey Patcher https://github.com/chris1111/Patch-HD4000-Monterey to patch in Intel HD4000 Support and run it
• Get the EFI from your Laptop on a USB Stick and modify it:
  • For Broadcom BT users: disable BrcmBluetoothInjector.kext, add BlueToolFixup.kext (can be found in this thread), update config with ProperTree
  • Modify config.plist with SMBIOS infos (I am using macBookPro11,4) and add additional necessary boot-args mentioned in Chris' Repo
• Shutdown your PC
• Take out the disk and the USB drive
• Put the disk in your Lapotop
• Boot from the Stick
• Bingo! Monterey on a Laptop from 2013

 

Did you find than Firefox is not so stable as Google Chrome or Safari at Monterey after patching of HD4000 ?

My Z77 hackintosh had this issue.

Hackintool also open and quit, but fixed by newest version of 3.6.1.

[Guest 5T33Z0]

@jsl2000 Yes, Firefox insta-crashes when trying to close windows or tabs. Safari works fine, though.

Edited June 23, 2021 by 5T33Z0

[jsl2000]

30 minutes ago, Hervé said:

Repeatable issues I've experienced after installing Monterey + OCLP 0.1.9 patching on my Ivy Bridge/HD4000 Dell Latitude E6230 laptop (granted it's installed on an external USB-attached SSD) :

• high CPU speeds (CPU running mostly in Turbo mode) + high temperature even after returning to MBP9,2 or MPB10,2 for proper CPU SpeedStep
• noticeable sluggishness/lag overall
• sudden and unexpected OS crashes/laptop resets after a few minutes
• instantaneous laptop reset on clicking restart, i.e. no clean shutdown

Oddly enough, outside a few people showing "I've done it" with a basic screenshot, I can't say I've seen much feedback on Ivy Bridge/HD4000 systems' behaviour after installing & patching Monterey but, somehow, I don't believe I'm a lone case re: the above matters... To me, it sure ain't useable yet.

In my Z77(Ivy Bridge) with desktop HD4000 after OCLP only Firefox did not work properly.

Both Safari and Google Chrome work stably and reliably.

Looking forward to Monterey beta2 coming soon for test !

Edited June 23, 2021 by jsl2000

[Stefanalmare]

45 minutes ago, Hervé said:

Repeatable issues I've experienced after installing Monterey + OCLP 0.1.9 patching on my Ivy Bridge/HD4000 Dell Latitude E6230 laptop (granted it's installed on an external USB-attached SSD) :

• high CPU speeds (CPU running mostly in Turbo mode) + high temperature even after returning to MBP9,2 or MPB10,2 for proper CPU SpeedStep
• noticeable sluggishness/lag overall
• sudden and unexpected OS crashes/laptop resets after a few minutes
• instantaneous laptop reset on clicking restart, i.e. no clean shutdown

Oddly enough, outside a few people showing "I've done it" with a basic screenshot, I can't say I've seen much feedback on Ivy Bridge/HD4000 systems' behaviour after installing & patching Monterey but, somehow, I don't believe I'm a lone case re: the above matters... To me, it sure ain't useable yet.

I have Probook 4540s. None of the symptoms you have on your laptop happen to mine. Unless safari, when I write in google page no letters appear. Until now...........

[ombra88]

On 6/20/2021 at 3:35 AM, jsl2000 said:

If Whatevergreen.kext was used, you may try add "-wegnoigpu" to boot-argument to disable IGPU and booted by dGPU (in your case which's R9 290X).

I see, I’ll have to try but can’t at the moment. Would be cool to see someone with the same spec try to work it out fully.

Anyway cheers man  

[chris1111]

It run smooth here on HP Probook 6570b 

[chris1111]

1 hour ago, Hervé said:

@chris1111, I'm not sure your packaged patcher actually operates properly on external disks. I tried it on my USB-attached Monterey SSD. It prompts for the Monterey disk which I select in the list, renames it to Monterey-DISK and then prompts me to select the APFS volume called Monterey-DISK within the list of all volumes. When I do so it returns an error message "you did not select a volume called Monterey-DISK". 

But I'll retry after a complete reformatting of the disk, might be a side-effect of previous OCLP patching.

 

Also, I'm not sure that alcid=12 should be part of the necessary boot-args. 

 

You have tu use this on Monterey 12 and I never see this kind of message after 100 test because I am not a mistake

alcid=12 is typo correct now

Edited June 23, 2021 by chris1111

[Guest 5T33Z0]

I've had it running for at least 4 to 6 hours today on my laptop. Not a single KP besides the Firefox issue.

[Stefanalmare]

2 hours ago, Hervé said:

@chris1111, I'm not sure your packaged patcher actually operates properly on external disks. I tried it on my USB-attached Monterey SSD. It prompts for the Monterey disk which I select in the list, renames it to Monterey-DISK and then prompts me to select the APFS volume called Monterey-DISK within the list of all volumes. When I do so it returns an error message "you did not select a volume called Monterey-DISK". 

But I'll retry after a complete reformatting of the disk, might be a side-effect of previous OCLP patching.

 

Also, I'm not sure that alcid=12 should be part of the necessary boot-args. 

 

I tried also chris patch with the same result: you did not select a volume called Monterey-DISK. Internal SSD with OCLP.

[chris1111]

33 minutes ago, Hervé said:

@chris1111 J Will put the disk inside the laptop and retry.

OMG I can not wait to see it I suspect the rest

No No man I also lots of  test SSD USB 3 in external case 

Probably your not boot with csr-active-config  EF0F0000 

Dont know what's wrong with you the disk number is suppose to be no 5

This is what I have on all test

Anyway if you have issue post on GitHub this not a good place here

 

 

It is  report success here also  by lots of other tester

 

Edited June 23, 2021 by chris1111