Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

6 hours ago, sonicthehedgehog2 said:

I have the same issue. I'm just going to wait as the RTM is not far away (25 Oct).

a-Steps to ensure that the update for Monterey RC 12.0.1 will show:

 

 

- Change your Config.plist/Misc/ Security/SecureBootModel to: Default ( restrictsEvents.kext is not needed anymore with OC 0.74  Previously mentioned by @Skyfallkavu )

- csr-active-config EF0F0000 

- Clean your NVRAM

 

Enroll again in the developer seed program ( using terminal):

sudo -i
enter your root password
/System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil

Unenroll first from the Beta Program:
/System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll

Enroll again in the DeveloperSeed Beta: 
/System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed

Close and re-open your System Preferences > Software Update
The new Beta should now show up. If it does not, Burn your hack, as it is cursed and get a new one 😂🖖

 

 

 

 

Edited by Ellybz
  • Like 2
  • Haha 4
Link to comment
Share on other sites

6 hours ago, hiphopboy said:

 

Thanks, my problem maybe cause i not set SecureBootModel to Disabled :D

 

The three points that I am telling you are to mention on the Github,

if you have a problem post an issue on the Github; here it is not the place for the problem of NV patch drivers.

Edited by chris1111
Link issue on github
  • Like 2
Link to comment
Share on other sites

Afaik, it's actually an issue in Apple's side. RestrictEvents forces it to look with the VMM flag enabled - though that catalog hasn't been updated yet on apples side. That's only enabled if you are using the "-revsbvmm" boot-arg looking at the source code, and you shouldnt need restrict events anyway for working updates with the latest OC release.

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

I need an advice. With last 3 updates (Monterey), after sleep, bluetooth doesn't start. I need to open Bluetooth Preferences and it start up. If not, it doesn't. It happens In Probook 4540s, i7 3840QM, 8GB ram, Azurewave 4360+20702 combo. What can I do to fix it?

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

50 minutes ago, 1Revenger1 said:

Afaik, it's actually an issue in Apple's side. RestrictEvents forces it to look with the VMM flag enabled - though that catalog hasn't been updated yet on apples side. That's only enabled if you are using the "-revsbvmm" boot-arg looking at the source code, and you shouldnt need restrict events anyway for working updates with the latest OC release.

 

Since updates still don't work for me I just wait until Monday and download Monterey from the app store.

Link to comment
Share on other sites

On 10/19/2021 at 6:26 PM, hiphopboy said:

 

Have any solution for install this not using Geforce Kepler Patcher ? My PC after run then it's can't boot, just enter to Recovery Mode.

 

Maybe it's a configuration issue. I installed drivers via Kepler Patcher yesterday and it worked fine.

Link to comment
Share on other sites

I think my bluetooth card is incompatible with Monterey 12.0.1. Can't enable BT. I've changed nothing as far as kexts and config are concerned befor updating from th e last beta. It's a BCM4352

Link to comment
Share on other sites

1 hour ago, 5T33Z0 said:

I think my bluetooth card is incompatible with Monterey 12.0.1. Can't enable BT. I've changed nothing as far as kexts and config are concerned befor updating from th e last beta. It's a BCM4352

I have a BCM4352 and just updated to 12.0.1. My bluetooth is working fine after the update with no changes. Have you tried the new unsupported kext?

Link to comment
Share on other sites

35 minutes ago, sonicthehedgehog2 said:

I have a BCM4352 and just updated to 12.0.1. My bluetooth is working fine after the update with no changes. Have you tried the new unsupported kext?

 

I had a look at the Transport settings. In Catalina it's "USB":

 

Bildschirmfoto.png.e5187e3951a9c3f3f9e98a23de26cb4f.png

 

But in Monterey it's "PCIe":

1392305598_Bildschirmfoto2021-10-21um13_23_54.png.6de619207456924373849d65967171e3.png

 

Which is the "new and unsupported Kext"?

Link to comment
Share on other sites

@5T33Z0 - If I may, I just checked my B/Tooth settings, albeit a T-919 Card and in Monterey the Transport is USB same as in BS and Catalina (see attached). Your B/Tooth problem maybe else where.

Screenshot 2021-10-21 at 1.06.46 pm.png

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

After I changed "MaxKernel" to 20.9.9 for FirmewareData and BrcmPatchRAM3 as well, it worked again:

 

539794972_Bildschirmfoto2021-10-21um14_25_13.thumb.png.1f4dea778eb8acb8b14b863725440c59.png

Edited by 5T33Z0
Link to comment
Share on other sites

58 minutes ago, 5T33Z0 said:

 

I had a look at the Transport settings. In Catalina it's "USB":

 

Bildschirmfoto.png.e5187e3951a9c3f3f9e98a23de26cb4f.png

 

But in Monterey it's "PCIe":

1392305598_Bildschirmfoto2021-10-21um13_23_54.png.6de619207456924373849d65967171e3.png

 

Which is the "new and unsupported Kext"?

The kext was posted earlier in this topic.

3 minutes ago, 5T33Z0 said:

After I changed "MaxKernel" to 20.9.9 for FirmewareData and BrcmPatchRAM3 as well, it worked again:

 

539794972_Bildschirmfoto2021-10-21um14_25_13.thumb.png.1f4dea778eb8acb8b14b863725440c59.png

Glad it worked out

  • Like 1
Link to comment
Share on other sites

6 minutes ago, sonicthehedgehog2 said:

The kext was posted earlier in this topic.

Glad it worked out

 

Actually, that was wrong! It wasn't working, It's just that the status wasn't updated so it looked like it was on.

 

So then I deleted MaxKernel settings for FirmwareData and BrcmPatchRAM3. Now, if I reboot, it's working. But once I turn it off, I can't turn it back on. Something is definitely starnge.

Link to comment
Share on other sites

I think I found the reason for the issue. The internal WiFI BT Card is now detected as a Dongle:

 

587996723_Bildschirmfoto2021-10-21um14_56_20.png.3b4fd50c50919e427bb3918694e47562.png

 

And once it's turned off you cannot turn it back on....

Edited by 5T33Z0
Link to comment
Share on other sites

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