Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

1 minute ago, Alex HQuest said:

 

11th Gen is the Windows ME of Intel processors: should have never  existed. I was sad when I built a new rig for wife, using a 10th gen i9-10900k a week prior to the 11th gen launch, not because I was one generation behind, but because I lost $150 since this processor became cheaper, and it is still much, much better than the 11th gen counterpart.

It will probably be worth waiting to see how the ARM transition works out. Whether marketing will move quickly to M1 or M2 based platforms without any more intel options. 

 

Might be a good time to polish those QEMU skills if you wnat to run Intel beyond gen 11.

  • Like 1
Link to comment
Share on other sites

Guest 5T33Z0
On 8/1/2021 at 12:06 PM, eng_redaesm said:

after many trails i'v successfully installed latest beta on my laptop 3rd gen i7 hd4000 card

using dortonia legacy patcher and chris.  hd4000 patcher 

working vga hd4000 and wifi Bluetooth   

 

but i'v a question every time i updating do in need to apply the patcher again ?

 

Yes you have to. If I see that there's an Update, I take the disk out, put it in my desktop, install it, apply the HD4000 patcher and then put it back in the notebook.

Link to comment
Share on other sites

20 hours ago, Alex HQuest said:

11th Gen is the Windows ME of Intel processors: should have never existed. I was sad when I built a new rig for wife, using a 10th gen i9-10900k a week prior to the 11th gen launch, not because I was one generation behind, but because I lost $150 since this processor became cheaper, and it is still much, much better than the 11th gen counterpart.

I don't wanna go off-topic about the specs of the 10th gen and 11th gen here but thanks for your input. I was just curious to see if there are any changes in that regard but I know it's highly unlikely that Apple provide any further Intel support, it was more like a wishful thinking.

Link to comment
Share on other sites

23 hours ago, eng_redaesm said:

after trying latest beta on my laptop 3rd gen intel hd4000 

 

it is very lagy does anyone experienced this

Beta 4 have noticed some boots are quick while others have considerable amount of hard drive thrashing before things settle down.

  • Thanks 1
Link to comment
Share on other sites

On 8/3/2021 at 12:05 AM, ameenjuz said:

anyone know how to fix X-vpn app on macOS 12 beta 4

connection faild another vpn is operating now but i don't have other vpn to run

You might need to wait for the developer of this app to update it. I remember when Big Sur first made changes to the way kernel extensions work, it took a few betas until the AnyConnect was updated - which by the way, works just fine on Monterey cheese.

  • Like 1
Link to comment
Share on other sites

It is strange why boot time is noticeably slower on Monterey than on Big Sur. 

 

More specifically, the boot stalls for one minute on:

SMCSuperIO: ssio: @ detected device ITE IT8686E

 

Then for about 30 seconds on:

Doing boot task: init_featureflags

 

I am on latest OpenCore Release 0.7.2 but this occured also on OC 0.7.1 Release

 

My kexts are latest releases:


- Lilu 1.5.5
- VirtualSMC 1.2.6 + SMCSuperIO + SMCProcessor
- AppleALC 1.6.3
- IntelMausiEthernet 1.0.7
- WhateverGreen 1.5.2
- USBMap.kext (I mapped my USBs using the dortania guide when in Catalina then did a re-map when I updated on Big Sur just in case)

 

IMG_5600.jpeg

 

I tried disabling Trim by setting 999 on SetApfsTrimTimeout and also a way larger value shown on the OC documentation just to test whether it's a Trim related issue, but no noticeable change was observed in boot time, so I believe it is not a TRIM thing.

 

Edited by WizeMan
  • Sad 1
Link to comment
Share on other sites

On 8/1/2021 at 8:48 PM, eng_redaesm said:

after trying latest beta on my laptop 3rd gen intel hd4000 

 

it is very lagy does anyone experienced this

Yes. I'm experiencing exactly the same issue. With the plus that using HD4000 and/or Dortania legacy patcher and/or chris.  hd4000 patcher prevents my Mac from booting and I have to use Recovering again…

Link to comment
Share on other sites

3 hours ago, WizeMan said:

It is strange why boot time is noticeably slower on Monterey than on Big Sur. 

 

More specifically, the boot stalls for one minute on:


SMCSuperIO: ssio: @ detected device ITE IT8686E

 

Then for about 30 seconds on:


Doing boot task: init_featureflags

 

 

Do you try to boot without VirtualSMC plugins. 🙂

  • Like 1
Link to comment
Share on other sites

It is strange why boot time is noticeably slower on Monterey than on Big Sur. 
 
More specifically, the boot stalls for one minute on:
SMCSuperIO: ssio: @ detected device ITE IT8686E

 
Then for about 30 seconds on:

Doing boot task: init_featureflags

 
I am on latest OpenCore Release 0.7.2 but this occured also on OC 0.7.1 Release
 
My kexts are latest releases:

- Lilu 1.5.5
- VirtualSMC 1.2.6 + SMCSuperIO + SMCProcessor
- AppleALC 1.6.3
- IntelMausiEthernet 1.0.7
- WhateverGreen 1.5.2
- USBMap.kext (I mapped my USBs using the dortania guide when in Catalina then did a re-map when I updated on Big Sur just in case)
 
IMG_5600.thumb.jpeg.2853c9c9be3ee020d5993345196fbd5b.jpeg
 
I tried disabling Trim by setting 999 on SetApfsTrimTimeout and also a way larger value shown on the OC documentation just to test whether it's a Trim related issue, but no noticeable change was observed in boot time, so I believe it is not a TRIM thing.
 


Are those the only kexts you are using?


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

21 minutes ago, Matgen84 said:

 

Do you try to boot without VirtualSMC plugins. 🙂

 

I will try only with VirtualSMC.kext, and report back. 

 

@Matgen84 I disabled SMCProcessor.kext and SMCSuperIO.kext from config.plist but did not affect boot time.

 

18 minutes ago, SavageAUS said:


Are those the only kexts you are using?


Sent from my iPhone using Tapatalk

 

Yes these are the only kext that are needed on my setup. I was also using SmallTreeIntel kext (to enable my second ethernet port) but have disabled it and tried again without change to boot time.

Edited by WizeMan
  • Confused 1
  • Sad 1
Link to comment
Share on other sites

Have also noticed unusual behavior with Monterey when booting to the login screen.

 

At times little delay getting to the login.  At other times seemingly slow hard disk access and substantial delayed appearance of the login screen.

 

There can be two startups, one right after the other, with no config changes, but notably different boot times to arrive at the login screen .

 

This issue does not manifest with Big Sur.

 

Anyone seeing intermittent slow disk access booting to the Monterey login?

 

Is anyone using an AHCI kext or special clover config or both to address this issue?

 

 

Edited by HenryV
Link to comment
Share on other sites

14 hours ago, WizeMan said:

It is strange why boot time is noticeably slower on Monterey than on Big Sur. 

 

More specifically, the boot stalls for one minute on:


SMCSuperIO: ssio: @ detected device ITE IT8686E

 

Then for about 30 seconds on:


Doing boot task: init_featureflags

 

I tried disabling Trim by setting 999 on SetApfsTrimTimeout and also a way larger value shown on the OC documentation just to test whether it's a Trim related issue, but no noticeable change was observed in boot time, so I believe it is not a TRIM thing.

 

 

I suspect that it is a Trim thing despite your revised settings.  Try disabling Trim altogether (and removing any Trim kext you might have somewhere in your system) and see if it makes a difference.  It did for me but, on balance, I chose to have Trim rather than a faster boot time.

Link to comment
Share on other sites

14 hours ago, mnfesq said:

 

I suspect that it is a Trim thing despite your revised settings.  Try disabling Trim altogether (and removing any Trim kext you might have somewhere in your system) and see if it makes a difference.  It did for me but, on balance, I chose to have Trim rather than a faster boot time.

I already tried with trim disabled (SetApfsTrimTimeout to 999) and have no kexts for trim, but no change in boot time.

Link to comment
Share on other sites

12 minutes ago, Partime said:

Anyone using OpenCoreBuilder under Montery? 

I can't get it to build..... tells me NASM not installed (I installed through BREW) and eventually hangs on "compiling the latest committed release...."

 

thanks

No need to build, you can find the latest nightly release here - Releases/Dortania/Build-Repo.GitHub, plus latest kext builds of Lilu, Whatevergreen etc, etc.

  • Like 2
Link to comment
Share on other sites

3 hours ago, Partime said:

Anyone using OpenCoreBuilder under Montery? 

I can't get it to build..... tells me NASM not installed (I installed through BREW) and eventually hangs on "compiling the latest committed release...."

 

thanks

I have to investigate a bit more, but my from source builds have lately all failing with signal 11 errors. Might want to try disabling my CPU’s overclock 😆

Link to comment
Share on other sites

3 hours ago, eSaF said:

No need to build, you can find the latest nightly release here - Releases/Dortania/Build-Repo.GitHub, plus latest kext builds of Lilu, Whatevergreen etc, etc.

this removes building, but what time consuming task making sure you have all the latest, unzipping, moving around, etc. Building was a lot simpler.

Is there an easy way to do this? I might just need to be educated.

thanks.

  • Confused 1
Link to comment
Share on other sites

17 minutes ago, Partime said:

this removes building, but what time consuming task making sure you have all the latest, unzipping, moving around, etc. Building was a lot simpler.

Is there an easy way to do this? I might just need to be educated...

Imo the time required to use releases created by Acidanthera is less than the time required to compile the source code.
Anyway, I also get an error and the compilation fails on Monterey beta 4 but it works fine on Big Sur 11.5.1.

  • Like 3
Link to comment
Share on other sites

34 minutes ago, Alex HQuest said:

I have to investigate a bit more, but my from source builds have lately all failing with signal 11 errors. Might want to try disabling my CPU’s overclock 😆

Seems that the last Xcode update isn’t compatible with OCBuilder anymore. It still builds on Big Sur but no longer Monterey. I would reach out to the author but he or she has been unfriendly to me in the past, so I am silent. 

Link to comment
Share on other sites

2 hours ago, miliuco said:

Imo the time required to use releases created by Acidanthera is less than the time required to compile the source code.

Absolutely - I don't understand @Parttime statement saying the opposite. :shock:

  • Like 3
Link to comment
Share on other sites

@dehjomz I think it's the other way round, at least from my vantage point, considering what little I know about OCbuilder. OCbuilder has always been a step or two, or more, behind mainstream OC development and has always been involved to somehow play catch-up to produce something which can do justice to the expectations of its user base. It will never be a tool that I will use to get my "hands dirty" on, so to speak. The OC monthly releases are the ones I have been using and never once has any version failed my expectations.   

I also argue that the present OCbuilder codebase is not compatible with the latest released Xcode, another catch-up that needs to be embarked upon by the OCbuilder developers. 

The OC source code of the latest 0.7.2 release, including all the kexts that I require for my hacks, compile just fine using the latest released Xcode version 12.5.1 build 12E507, therefore if one wants to be as close to the "coalface" as possible, OCbuilder is just NOT the way to go.

 

Greetings Henties

Link to comment
Share on other sites

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