Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

Just now, eSaF said:

Already disabled in BIOS by default. Will have to be patient and wait for the OC Devs to offer up a solution or as @Hervé suggested bite the bullet and dust off my Clover Folder which will be more fun as I left that behind a few versions ago.

 

SecureBootModel is still an OC setting. You might try to set it to disable irrespective of your BIOS settings.

Link to comment
Share on other sites

20 minutes ago, mnfesq said:

 

SecureBootModel is still an OC setting. You might try to set it to disable irrespective of your BIOS settings.

Tried OC 0.7.0 and 0.7.1 with SecureBootModel=Disabled. No luck.

  • Sad 1
Link to comment
Share on other sites

For those of you who cannot update to Beta 2 using OC but don't want to abandon OC, you can install Clover 5137 on your EFI partition and select the setting in the Clover installer to use the bootloader chooser.  It installs a BOOTX64.efi file in your BOOT folder and when you boot, you can hold down the space bar and it will give you the option to choose your bootloader, which for me is either Clover or OpenCore.  It shouldn't be that hard to get Clover to work for you since you can use most of your Quirk settings. in OC for the Quirk settings in Clover.

 

Untitled.thumb.png.6de54bc32e86e54fef5999ac797c4b18.png

Edited by mnfesq
  • Like 2
Link to comment
Share on other sites

Most the time when people have issues with getting the update to show up is because their APFS seal is broken it they have SIP disabled. The APFS seal should be not broken and SIP should be enabled.

  • Like 1
Link to comment
Share on other sites

Successful and smooth update to beta2 on my Skylake NUC6i5SYH, OC 0.7.0, SIP enabled but SecureBootModel set to disabled in OC config.plist.

 

Just like normal OTA delta update, process finished after 3 reboots...

 

Spoiler

1352820810_Montereybeta2updateoffered.png.7c0e7d501db725460e6307059c2e28db.pngboot1.thumb.png.006455de5d992650e9f5a885996c0794.pngboot2.thumb.png.fa32c2cd1516905eabcbbe8ebe24f85c.png905015640_Montereybeta2_21A5268h.thumb.png.b21f1c24cfa6f893d83523ad344e4732.png

 

Graphics card is now shown in "About This Mac" 😀

 

cc @SavageAUS: Re OpenCanopy icons in the above OpenCore GUI screenshot - these are from @blackosx's GIT repo Set3/Light/HardDrive

Edited by fusion71au
Link to OpenCanopy icons added
  • Like 1
Link to comment
Share on other sites

4 minutes ago, 5T33Z0 said:

@naiclub If the csr-active config is not correct, you won't get updates,I guess (just like in Big Sur). Enable SIP temporarily.

The keyword "partially".

For update you have to enable SIP partially.

  • Like 2
Link to comment
Share on other sites

Guest 5T33Z0

Updates are working fine here with EF0F0000 

 

1751201984_Bildschirmfoto2021-06-29um07_08_20.png.0b9e7059a31329903931818148a95c65.png

 

SIP looks more than just "partially" disabled to me:

770689392_Bildschirmfoto2021-06-29um07_09_51.png.8cba82fbaaed62e7deaee4aa7423074d.png

Edited by 5T33Z0
Link to comment
Share on other sites

33 minutes ago, 5T33Z0 said:

@naiclub If the csr-active config is not correct, you won't get updates,I guess (just like in Big Sur). Enable SIP temporarily.

 

28 minutes ago, Slice said:

The keyword "partially".

For update you have to enable SIP partially.

I had this set up before installing, but it didn't work, so I went back to clover

345983040_2564-06-2912_34_18.thumb.png.430efd4b6b21d178bf7b17d8b6989ba6.png

  • Like 1
Link to comment
Share on other sites

10 hours ago, antuneddu said:

Sorry but what's in it, it's not the bootloader that detects updates

 

Few month ago, users noticed that the value assigned to csr-active-config had an influence on the appearance of updates. I don't know if it is the same for Monterey.

Link to comment
Share on other sites

Guest 5T33Z0

@chris1111 After updating to the lastes beta of Monterey I noticed that you have to Patch HD4000 again oherwise the screen stays at the boot screen, while the system is actually running in the background (I got an email Notification, etc). So I took the disk out, put it in an external case, started macOS Catalina on my Laptop, ran HD4000 Patcher v2 and mounted the Monteray disk. After selecting the Monteray-DISK partition, I get this error:

 

131009245_Bildschirmfoto2021-06-29um08_28_11.png.50161e0d7587b39b10a16fcec427bba0.png

 

2104105923_Bildschirmfoto2021-06-29um08_40_15.thumb.png.b8fed9d1d05dd79ce891e6f08c6c897a.png

Edited by 5T33Z0
Link to comment
Share on other sites

50 minutes ago, Matgen84 said:

 

Few month ago, users noticed that the value assigned to csr-active-config had an influence on the appearance of updates. I don't know if it is the same for Monterey.

The same. It is the bit 4. The difference between EF0F and FF0F.

  • Thanks 1
Link to comment
Share on other sites

18 minutes ago, Slice said:

The same. It is the bit 4. The difference between EF0F and FF0F.

 

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Just now, hiphopboy said:

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

You don't list your hardware. Who can help you?

Link to comment
Share on other sites

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