Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

6 hours ago, 5T33Z0 said:

@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:

 

 

 

 

You are select the wrong disk

 

See disk 5 is the good one

Link to comment
Share on other sites

2 hours ago, SavageAUS said:

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

To answer my own question, at least for me Beta 2 has solved my long boot with auto login disabled.

Now it boots faster than Big Sur.

Link to comment
Share on other sites

1 hour ago, naiclub said:

Do you have any good tips to help me?

The tip is impossible. But I have to say that sleep works if all devices works including embedded audio even if you not use it.

The same about all other devices.

As well there is a dependency on good DSDT. Clover introduced several fixes (FixDSDT) that help computer sleep and wake.

  • Like 1
Link to comment
Share on other sites

16 minutes ago, Hervé said:

Was finally able to update my Toshiba laptop to beta2 but only after re-installing from scratch with OC 0.7.0 with SecureBoot set to "disabled" (changed from "default"). I initiated the beta2 download but had to leave for a couple of hours. On my return, the beta2 update had fully completed and I found myself at the beta2 desktop. So all is well now with OpenCore.

 

Satellite_Pro_R50-B_12.0.b2.jpg

SecureBoot set to "disabled" I turned it off a long time ago. Why can't I find the update yet?

Link to comment
Share on other sites

4 minutes ago, naiclub said:

SecureBoot set to "disabled" I turned it off a long time ago. Why can't I find the update yet?

Check to see if you APFS volume is Sealed using Terminal 

diskutil apfs list

 

Screen Shot 2021-06-29 at 10.05.59 AM.png

  • Like 2
Link to comment
Share on other sites

Guest 5T33Z0
1 hour ago, chris1111 said:

You are select the wrong disk

 

See disk 5 is the good one

 

I tried that as well. No luck. BTW, disk5 is 1,1 megabyte…

Link to comment
Share on other sites

Updated to beta 2 on my Skylake build and OC 0.7.1 without issues, sleep is working properly.

Beta 2 is quite usable but will stay with Big Sur for a few more Monterey beta iterations before I consider adopting Monterey permanently.332590820_Screenshot2021-06-29at5_47_49PM.thumb.png.f3233d12524473de706ad992e3939f44.png

Screenshot 2021-06-29 at 5.48.40 PM.png

  • Like 2
Link to comment
Share on other sites

Following @Hervé direction, happy to say I managed to do the update after a clean install (so much for using it as my daily driver :hysterical:). Won't want to go through that again, was about to give up on Tim Apple

Spoiler

868383210_ScreenShot2021-06-29at16_51_46.thumb.png.ceea0bd2253f67e234a63b3e6f0eb167.png

and go and play on Bill Gates latest offering. :wink_anim:

  • Like 2
Link to comment
Share on other sites

7 hours ago, miliuco said:

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.

@eSaF

This way doesn’t work for you?

 

EDIT: posted before reading your last message. 

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

On 6/29/2021 at 4:07 PM, Pavo said:

Check to see if you APFS volume is Sealed using Terminal 




diskutil apfs list

 

 

I tried to learn more about the implications of a broken seal and found this which implies that "diskutil apfs list"  Sealed status on Intel Macs is ambiguous.  The seal on my boot volume shows as "Broken" (with Snapshot Volume indicated as sealed) but I don't notice any problems.  I have SIP fully enabled in OC config.plist.

 

What are the supposed implications of having an APFS Volume Seal that is "No" or "Broken?"

  • Like 3
Link to comment
Share on other sites

Am I right in assuming not disabling SecureBootMode in the config.plist breaks the Sealed Volume which in turn inhibits the update? If that is the case, what good is that inclusion that can be overlooked and caused a few headaches with this update. Casting no aspersions towards the OC Devs doing a fantastic job, just trying to feed my curiosity and reduce my ignorance level. :angel:

  • Like 1
Link to comment
Share on other sites

50 minutes ago, eSaF said:

Am I right in assuming not disabling SecureBootMode in the config.plist breaks the Sealed Volume which in turn inhibits the update? If that is the case, what good is that inclusion that can be overlooked and caused a few headaches with this update. Casting no aspersions towards the OC Devs doing a fantastic job, just trying to feed my curiosity and reduce my ignorance level. :angel:

As long as you don't modify the system files in any way as to need to create a new snapshot to retain the changes, nor create a new snapshot and delete the install/upgrade snapshot, you should be able to update incrementally, without a full installer.

Link to comment
Share on other sites

Smooth update from b1-b2 with exception of a KP hiccup (clover 5137) while rebooting during the incremental update/install.  Switch to Open Core to complete update/install and no further problems booting with clover.

 

Has anyone noticed that running "sudo purge" in beta 2 frees up approximately 500 to 800 plus megabytes of RAM, even after a clean boot without opening any apps?

 

Is anyone running Monterey with swap disabled and min 8 GIGS RAM without issues?

 

No issues with brew, ntfs-3g, macFUSE 4.20 beta, ext RW after update/install.

 

AirportItlwm for intel wifi functions after update.

 

Verbose boot shows large number of scrolling lines indicating "private".

 

Have fruity engineers cordoned off part of the kernel for digital rights management?

 

 

Link to comment
Share on other sites

23 hours ago, mnfesq said:

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

Interestingly, installing to HP laptop also took alternating between clover and OC to finish install/update of beta2.

clover reboots-->KP-->switch to OC to finish-->back to clover and boot without issues

Link to comment
Share on other sites

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