Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

On 6/28/2021 at 7:04 PM, Middleman said:

I have. Try to boot with SecureBoot disabled and use -lilubetaall -wegbeta -no_compat_check. Use EC060800 as the CPUID1Data and use USBInjectAll.kext with XHCIPortLimit enabled. Add the SMC plugins for processor and superio. Vit9696’s Intel I-225V kernel patch and also the FakePCIID Intel I225V needs to be disabled also because it is now natively supported. That could be the cause.

I have made those changes but cannot boot into the OS, not even into Big Sur. 

Link to comment
Share on other sites

16 minutes ago, Matgen84 said:

 

For Clover, I use 0x285 as you told me few month ago for Big Sur. Is it correct !

Yes, the bit4==0 so this is correct. I also use this value.

11 minutes ago, Matgen84 said:

Hi @all

I found a spare hard disk. What is the correct way for this HDD drive: format macOS journaled and Monterey will convert it to APFS. Or format it directly to APFS.

Let me know. Please.

No matter. But I prefered macOS journaled. Let Monterey choose right format by itself.

11 minutes ago, hiphopboy said:

my hack checking to software update but have no any update for new beta 2, already install Betaultility, please help me

What is your csr-active-config?

3 minutes ago, miliuco said:

Nothing. Tried OC 0.7.0 and 0.7.1. Csrutil enabled (00000000). Gatekeeper enabled. SecureBootModel=Disabled. No luck.

SMBIOS Model?

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

3 minutes ago, Slice said:

Yes, the bit4==0 so this is correct. I also use this value.

No matter. But I prefered macOS journaled. Let Monterey choose right format by itself.

What is your csr-active-config?

SMBIOS Model?

 

My csr-active : 85020000 SMBIOS iMacPro 1.1 2017

Link to comment
Share on other sites

3 minutes ago, Slice said:

SMBIOS Model?

@Slice I had that thought myself as it seems to be a last thing to try, also @miliuco and I have the same make and chip (z390) board so I am wondering if by some chance that has anything to do with not being to update to this latest Beta. Probably whistling in the wind here but I am throwing everything at it to get it working hoping something will stick.

  • Like 2
Link to comment
Share on other sites

8 minutes ago, Hervé said:

Re: SIP, it's the same story as with Big Sur: Apple Internal flag must be left unchanged (i.e. disabled); it's the 5th bit out of the 12 (at time of writing), hence csr-active-config values such as 0xFEF, not 0xFFF.


nible:               #3        |         #2        |         #1     
nibble bits:   4   3   2   1   |   4   3   2   1   |   4   3   2   1
bits:         12  11  10   9   |   8   7   6   5   |   4   3   2   1
               -   -   -   -       -   -   -   -       -   -   -   -
               |   |   |   |       |   |   |   |       |   |   |   |
               |   |   |   |       |   |   |   |       |   |   |   |
               /   |   |   |       |   |   |   |       |   |   |   |
   Unauth. Root    /   |   |       |   |   |   |       |   |   |   |
       Policy Over.    /   |       |   |   |   |       |   |   |   |
              Kext app.    /       |   |   |   |       |   |   |   |
                  Recov. OS        /   |   |   |       |   |   |   \
                     Device Config.    /   |   |       |   |   \    Kext Sig.
                            NVRAM Prot.    /   |       |    \   FS Prot.
                               DTrace Rest.    /       \     Task for PID
                                     Apple Int.         Kernel Debug.

If the flag is set, i.e. Apple Internal enabled, no updates are offered.

 

So what must i do ?

 

Link to comment
Share on other sites

37 minutes ago, miliuco said:

Nothing. Tried OC 0.7.0 and 0.7.1. Csrutil enabled (00000000). Gatekeeper enabled. SecureBootModel=Disabled. No luck.

@Slice

SMBIOS MacPro7,1.

 

@eSaF

Added TPM disabled in BIOS and 👍

 

So you know. in my case:

  • TPM disabled in BIOS.
  • Csrutil enabled (00000000).
  • Gatekeeper enabled.
  • SecureBootModel=Disabled in config.plist.

 

Edited by miliuco
  • Like 1
Link to comment
Share on other sites

27 minutes ago, miliuco said:

@Slice

SMBIOS MacPro7,1.

 

@eSaF

Added TPM disabled in BIOS and 👍

 

So you know. in my case:

  • TPM disabled in BIOS.
  • Csrutil enabled (00000000).
  • Gatekeeper enabled.
  • SecureBootModel=Disabled in config.plist.

 

 

Thanks :) TPM disabled, do you disable SecureBoot too in BIOS !

Link to comment
Share on other sites

Hi all,

like @Hervé

I have that problem with bluetooth since the first beta of Monterey, and I have it still with the new beta, but mine with a Fenvi T-919 card is always disabled, from the boot trough the reboot.

But even in my Big Sur after 11.2.3 bluetooth with the same card is awful, I stopped updating it or I loose bluetooth, even if I remap my USB ports, sometimes it works others it didn't work ...

 

  • Like 1
Link to comment
Share on other sites

12 hours ago, miliuco said:

Me too. It seems to be installing beta 2, rebooting, etc., but at the end I stay in beta 1. Tried 2 times.

 

Same for me. I have newest Clover and SIP 0x285. 

 

I have tried to install macOS beta1 again to repair the previous installation, and then run the Beta2 update again, but no luck.

 

Anyone have any ideas how to fix this issue?

Link to comment
Share on other sites

4 minutes ago, Common_Sense said:

Anyone have any ideas how to fix this issue?

That is the reason why a few of us are here trying to find a solution. As a matter of interest what is the chipset platform of your board? You have not populated your profile as per the rules, the reason I ask I see a pattern of success among Laptops and Dell desktops but Z390 boards are proving difficult. Don't know why I am just trying to dissimulate the difference.

  • Like 1
Link to comment
Share on other sites

Did beta 2 fix the long “2nd stage” boot? That required auto login? Mines updating now on my laptop so I will test soon but want to see other responses as well.


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

11 minutes ago, eSaF said:

That is the reason why a few of us are here trying to find a solution. As a matter of interest what is the chipset platform of your board? You have not populated your profile as per the rules, the reason I ask I see a pattern of success among Laptops and Dell desktops but Z390 boards are proving difficult. Don't know why I am just trying to dissimulate the difference.

 

I have an Intel Z87 motherboard + 4770K CPU and I am using iMac18,3. SMBIOS has been generated using GenSMBIOS (https://github.com/corpnewt/GenSMBIOS).

 

Maybe I should generate another SMBIOS with maybe some Mac Mini or earlier iMac, just to try installing the update?

 

Or maybe I need a clean installation of macOS, I guess could be some problem with an APFS partition, I know there is one partition used for updates. But I want to avoid re-installing if I can.

Link to comment
Share on other sites

 
I have an Intel Z87 motherboard + 4770K CPU and I am using iMac18,3. SMBIOS has been generated using GenSMBIOS (https://github.com/corpnewt/GenSMBIOS).
 
Maybe I should generate another SMBIOS with maybe some Mac Mini or earlier iMac, just to try installing the update?
 
Or maybe I need a clean installation of macOS, I guess could be some problem with an APFS partition, I know there is one partition used for updates. But I want to avoid re-installing if I can.

Can you make a separate partition to try a clean install? Then you can see if you can run it before updating your main system. That’s what I’ve done. Monterey is on a separate partition to Big Sur to test and when it’s stable / released I’ll update my main.


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

29 minutes ago, SavageAUS said:


Can you make a separate partition to try a clean install? Then you can see if you can run it before updating your main system. That’s what I’ve done. Monterey is on a separate partition to Big Sur to test and when it’s stable / released I’ll update my main.


Sent from my iPhone using Tapatalk

 

I tried installing again, this time I manually select to boot the "macOS Install" partition every time the installation reboots. I got an error message saying the APFS snapshot couldn't be deleted. After that I reboot and when I got in to macOS again, to my surprise, I now have Beta 2 installed. I can see new features in the GUI, so it is not just the version that has been changed, its updated.

IMG_5464.jpeg

Screenshot 2021-06-29 at 12.47.04.png

  • Confused 1
Link to comment
Share on other sites

9 minutes ago, Slice said:

It's only me who updated Monterey by one click "Update" and go to bed? At morning I found Monterey beta 2 ready and sleeping.

Clover 5137.

How do you do it without waking up and then freezes.

Link to comment
Share on other sites

2 hours ago, Hervé said:

1st new bug for me with this 2nd beta: on my E7270 fitted with an Apple BCM94360CS2 card, after a long/extended sleep, BT is disabled on wake. Impossible to turn it back on. Module is seen in SysInfo->USB but SysInfo->Bluetooth sure ain't happy with it...

12.0.b2_SysInfo-Bluetooth.jpg

 

10.0.b2_SysInfo-USB.jpg

 

On/Off switch of the BT PrefPane unresponsive.

12.0.b2_BT-PrefPane.jpg

 

Bluetooth only operational again after a reboot.

Had this problem since beta 1.

Solved by using BlueToolFixup.kext

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...