[pre-release] macOS Monterey

[Alex HQuest]

24 minutes ago, 5T33Z0 said:

@antuneddu Where did you rename it? Mine is a Win 10 disk and I cannot rename it in FInder nor Desktop. In Disk Utility it's just called disk2S3

 

Add me to the lagged list of folks jumping to Beta 6 - just showed up for me, but I was a few days away from my computer.

[MorenoAv]

And I'm back and renamed my Windows 11 with a . before windows and ... pufff the disk icon on my desktop is gone...

Thanks @antuneddu, @Alex HQuest, that was the first to suggest renaming Windows with a dot before...

 

Edited September 1, 2021 by MorenoAv

[surenmunoo]

Adding a dot in front of Windows in Win 10 worked for me, no more disk icon on the desktop, Thanks 

[SavageAUS]

 
Sorry but it does not work.
Downloaded this HUGE ~11 GB file, but when I run it on my VMware Workstation Pro 16.1.x macOS Monterey older Beta VM, running on top of Windows 10 64-bit, I am not getting anything useful, I am afraid.
It shows something that is 35 MB (?? Where did the 11 GB go?) in size, installs that -- whatever it is, then stops saying installation has been successful (green checkmark shows).
But then NO new Beta version gets installed, or offered? Any ideas what is wrong here, and why? 
 

You might get help on the VMware thread, here it is off topic.


Sent from my iPhone using Tapatalk

[ndungu6678]

On 8/31/2021 at 2:59 PM, Shaneee said:

 

Your SecureBootModel is j185f. Set it to j160 and reboot and you'll get the update notification. While it's downloading set it back to j185f. Simple as that.

 

Thanks so much AudioGod and Shaneee!-after changing SecureBootModel to j160 voila!-update finally showed up for me -downloading right now and have changed SecureBootModel back to j137-SMBIOS -iMacPro1,1

 

Was about to download full InstallPackage but this worked!

 

 

Edited September 2, 2021 by ndungu6678

[AudioGod]

21 hours ago, antuneddu said:

🙂 It was enough to put a dot . in front of the name of the disk example  .Windows11   is not shown on the desktop but is accessible from the Finder 

Awesome tip Brother, That works a treat.

Before that I was preventing my Windows drives from mounting at startup but this is a much nicer solution.

Thank You Buddy. 👌

[Anto65]

Thank @Alex HQuest   I put into practice what he proposed, I had disabled the automunt via fstab but in this way it is much better

 

https://www.insanelymac.com/forum/topic/348725-pre-release-macos-monterey/?do=findComment&comment=2765400

 

Edited September 2, 2021 by antuneddu

[Guest 5T33Z0]

So I used Monterey for like 2 days now. Mostly to install all my Audio Software and plugins on it and at this stage it feels pretty stable already. Some Plugins and Apps don't work but most of it does. I feel that with Big Sur it took a lot longer until it was useable.

[Alex HQuest]

8 hours ago, 5T33Z0 said:

So I used Monterey for like 2 days now. Mostly to install all my Audio Software and plugins on it and at this stage it feels pretty stable already. Some Plugins and Apps don't work but most of it does. I feel that with Big Sur it took a lot longer until it was useable.

This is kind of expected. Big Sur introduced a lot of changes to make it (internally) more aligned with the iOS/iPadOS world, and to include the new M1 processors, whereas Monterey Jack cheese is just a bunch of updates on top of this new foundation. I'm curious to find out how long will the Intel processors be an option for the Mac line of products. Not only to know how long will the Hackintosh thrill with newest stuff, but to find out which other high performance options not AMD, Intel and Nvidia based we have available for both CPU and GPUs.

[Guest 5T33Z0]

My guess is about 3 to 5 years after the last line of Macs with Intel CPUs have been released until X86 Support will be dropped. Because you can't ship a 2.300 $ iMac in the fall 2021 (hypothecially) and in 2022 you can no longer install the latest macOS. That would be a bad look for Apple as far as product and customer support is concerned. For me, there's no alternative to macOS as far as work is concerned since I work in the field of audio. Windows is horrible for that. So unless some company get's into ARM for the PC consumer market and somehow these chips can run macOS (which is unlikely) I will probably have no other choice than buying an Apple machine – which is a frightening idea for me really.

 

[simmel]

I managed to get beta 6 show up with CLOVER. This is what I did:

 

1) updated CLOVER from 5138 to 5139 (no effect)

2) switched from VirtualSMC to FakeSMC with SMCHelper.efi (no effect)

3) changed SMBIOS from iMacPro1,1 to iMac17,1 and deleted NVRAM (update shows up)

 

Hope this helps!

[albyvar]

macOS Monterey beta 6 fully working on chuwi corebook pro

 

booted using clover 5127

 

[ombra88]

Any news on R290x and i7 4770k support, possibly using also iGpu?

[Slice]

9 hours ago, ombra88 said:

Any news on R290x and i7 4770k support, possibly using also iGpu?

I have no such hardware but why there will be any problem?

[ombra88]

3 hours ago, Slice said:

I have no such hardware but why there will be any problem?

When I tried If I am not mistaken the smbios needed to run both r9 290x and iGpu with Haswell is not supported by monterey

[Slice]

25 minutes ago, ombra88 said:

When I tried If I am not mistaken the smbios needed to run both r9 290x and iGpu with Haswell is not supported by monterey

I don't know how it is proposed to solve with Opencore but for Clover is it ordinary task to set SMBIOS model as iMac15,1 but Board-ID as Mac-77F17D7DA9285301 assuming both dGPU and iGPU.

[ombra88]

4 minutes ago, Slice said:

I don't know how it is proposed to solve with Opencore but for Clover is it ordinary task to set SMBIOS model as iMac15,1 but Board-ID as Mac-77F17D7DA9285301 assuming both dGPU and iGPU.

I see and thank you for the info!! Unfortunately I’d like to make it work on OC 😕

[Slice]

At your will.

[mnfesq]

7 hours ago, ombra88 said:

7 hours ago, Slice said:

I don't know how it is proposed to solve with Opencore but for Clover is it ordinary task to set SMBIOS model as iMac15,1 but Board-ID as Mac-77F17D7DA9285301 assuming both dGPU and iGPU.

I see and thank you for the info!! Unfortunately I’d like to make it work on OC 😕

 

Slice provided a perfect solution.  The problem for you is that OC does not yet allow sufficient configurability of SMBIOS.  Since you have access to the OC developers on this forum, you might suggest a future improvement by adding Board ID to the PlatformInfo/Generic section of the config.plist.  In the meantime, I have both Clover and OC in my EFI and use the boot selector that can be installed to BOOT in EFI to allow me to switch between Clover and OC at will.  (The boot selector can be installed as part of the Clover installer package.) It's amazing how far bootloaders have come in the OSx86 community.  Since Clover has been around longer than OC, it has more features.  I understand the allure of OC and I use it more often than Clover myself but OC still has a ways to go before it matches Clover in configurability.  Props to Slice.  It's sad to see him have to pitch Clover like it was 3-day old fish.  It's not.

 

To Mods:  Sorry that this was off-topic.

[Avery B]

It is possible to set board-id if you feel like setting every other field (other than generic) up. Would have to check the docs on that though.
Wouldn't it be possible to just use a Broadwell SMBIOS for example? Not quite sure what consequences that would have though.

[Guest 5T33Z0]

@ombra88 In OpenCore's sample-custom.plist there's a field for the Board ID called "BoardProduct" under PlatformInfo > SMBIOS which is the equivalent to BoardID in Clover.

Edited September 8, 2021 by 5T33Z0

[mnfesq]

3 hours ago, 5T33Z0 said:

@ombra88 In OpenCore's sample-custom.plist there's a field for the Board ID called "BoardProduct" under PlatformInfo > SMBIOS which is the equivalent to BoardID in Clover.

 

I take back what I said about OC's configurability.  I have not begun to memorize all of the options available in the sample-custom.plist and there certainly are many.  That said, the OC Configurator developers have Board Product filled out automatically when selecting an SMBIOS.  

[Tecnicaso Rico]

16 hours ago, ombra88 said:

I see and thank you for the info!! Unfortunately I’d like to make it work on OC 😕

OpenCore sets by default a specific board-id for every SMBIOS. But their is a work around to set your desire board-id without  interfering the PlatformInfo/Generic section.
Clone the OpenCorePkg repository: git clone https://github.com/acidanthera/OpenCorePkg.git
Edit AutoGenerated.c  with Xcode. This file is in: /OpenCorePkg/Library/OcMacInfoLib/AutoGenerated.c

 

 

And finally cd into the OpenCorePkg folder and run: ./build_oc_tool
An inconvenient with this method is the need to build  it again for every OpenCore update.
I wish OpenCore could select automatically the closest board-id when using the Platform/Generic mode.
For example: SMBIOS 17,1 has three different board-id's. One for i5-6500, another for i5-6600 and finally one for i7-6700K

Adding this feature will make OpenCore Generic SMBIOS selection more close to the the hardware being use and still being what it is: a generic solution.

 

 

[Guest 5T33Z0]

I have a Question regarding Board ID / Board Product. I have an Ivy Bridge Notebook (MacBookPro10,1) which can run BigSur (as MBP11,1) and Monterey (as MBP11,4 and patched in Drivers for the IntelHD4000). But as soon as I have to change the SystemProductName from MBP10 to MBP11, the CPU behavior changes: higher base clock, overall higher CPU useage and more fan noise because the CPU model used in MBP11 uses different board IDs and is tuned for CPUs of the Haswell Family. My workaround for this so far was to leave SystemProductName as MBP10,1 but use -no_compat_check.

 

Can't I just change the SystemProductName to MBP11,4 but use the Board ID of MBP10,1 instead to avoid this issue? Do I have to generate a new SMBIOS to fill out the fields of the SMBIOS section then?

 

EDIT:

 

So out of curiosity, I tested this in Clover (since it's easier to do): using an SMBIOS MacBookPro11,4 (Mac-06F11FD93F0323C5) with the BoardID for a MacBookPro10,1. (Mac-C3EC7CD22292981F). Unfortunely that didn't work (crossed-out circle). I guess the Board-ID is also checked for compatibility by macOS.

Edited September 9, 2021 by 5T33Z0

[Tecnicaso Rico]

3 hours ago, 5T33Z0 said:

I have a Question regarding Board ID / Board Product. I have an Ivy Bridge Notebook (MacBookPro10,1) which can run BigSur (as MBP11,1) and Monterey (as MBP11,4 and patched in Drivers for the IntelHD4000). But as soon as I have to change the SystemProductName from MBP10 to MBP11, the CPU behavior changes: higher base clock, overall higher CPU useage and more fan noise because the CPU model used in MBP11 uses different board IDs and is tuned for CPUs of the Haswell Family. My workaround for this so far was to leave SystemProductName as MBP10,1 but use -no_compat_check.

 

Can't I just change the SystemProductName to MBP11,4 but use the Board ID of MBP10,1 instead to avoid this issue? Do I have to generate a new SMBIOS to fill out the fields of the SMBIOS section then?

 

EDIT:

 

So out of curiosity, I tested this in Clover (since it's easier to do): using an SMBIOS MacBookPro11,4 (Mac-06F11FD93F0323C5) with the BoardID for a MacBookPro10,1. (Mac-C3EC7CD22292981F). Unfortunely that didn't work (crossed-out circle). I guess the Board-ID is also checked for compatibility by macOS.

It’s always recommended to use a SMBIOS as close as possible to your hardware specs. When using different board-id’s, these board id’s must be part of the SMBIOS being used. As mention before as an example,  iMac 17,1 has three different board-id’s so when using iMac 17,1 SMBIOS I should use one of those three board-id’s and not a board-id from a different SMBIOS.
People sometimes use a SMBIOS that doesn’t matches their hardware because they have different priorities (Like having full VDA Decoder support) but they get away from Power Management problems with the help of CPUFreind. There is also an interesting scenario where two different board-id’s are being used at once, and it’s with the Wonderfull magic perform by the WhateverGreen kext. This kext can spoof a different board-id only to the video section for full VDA Decoding purposes without changing the main board-id being used by macOS.
So finally when switching between different SMBIOS’s don’t mix board-id’s, just get away of Power Management problems with the help of CPUFreind.