[pre-release] macOS Monterey

[WizeMan]

5 minutes ago, SavageAUS said:

As stated above if possible try install on a different drive. Also try with the bare minimum attached to your pc. Eg just keyboard, mouse and monitor and install USB.
You said you mapped your USB ports? Have you tried without your USB map?
Also check your using an appropriate smbios.


Sent from my iPhone using Tapatalk

 

Currently I do not have another drive to test. I have my USB ports mapped properly and USB behaves as good as it did when I was on Big Sur. My SMBIOS is perfect match for the specs, iMac19,1.

 

Also Wifi / BT Works as expected once booted (I have swapped the motherboard's intel card with an adapter + apple native card.

 

I will try to get a second drive to test.

Edited July 22, 2021 by WizeMan

[iCanaro]

On 7/14/2021 at 10:19 PM, Stefanalmare said:

Try this. Put your IOPCIPrimaryMatch.

X299NVMe.kext.zip 3.96 kB · 4 downloads

 

https://www.hackintosh-forum.de/forum/thread/54361-nvmexpress-apple-ssd-controller/?postID=708932

 

thanks for the work and the idea; I added vendor and device ID of my WD SN850

[WizeMan]

@mnfesq @SavageAUS @eSaF @Matgen84 @ellaosx @MorenoAv 

 

Thank you all so much for your effort to help me.

 

It seems like the partition map or the file system was borked during Monterey upgrade from Big Sur.

Even from the Monterey USB Installer I couldn’t erase the drive, I had to boot into windows and remove all partitions with diskpart.

 

Then did a fresh install of Monterey and boot time is really short now.

Edited July 22, 2021 by WizeMan

[HenryV]

2 hours ago, WizeMan said:

@mnfesq @SavageAUS @eSaF @Matgen84 @ellaosx @MorenoAv 

 

Thank you all so much for your effort to help me.

 

It seems like the partition map or the file system was borked during Monterey upgrade from Big Sur.

Even from the Monterey USB Installer I couldn’t erase the drive, I had to boot into windows and remove all partitions with diskpart.

 

Then did a fresh install of Monterey and boot time is really short now.

Good time to back up your partition table:

https://www.insanelymac.com/forum/topic/348084-backup-and-partition-table/

[SavageAUS]

[mention=270804]mnfesq[/mention] [mention=1083558]SavageAUS[/mention] [mention=1254664]eSaF[/mention] [mention=1110743]Matgen84[/mention] [mention=1576948]ellaosx[/mention] [mention=2128562]MorenoAv[/mention] 
 
Thank you all so much for your effort to help me.
 
It seems like the partition map or the file system was borked during Monterey upgrade from Big Sur.

Even from the Monterey USB Installer I couldn’t erase the drive, I had to boot into windows and remove all partitions with diskpart.
 
Then did a fresh install of Monterey and boot time is really short now.

I’m glad we were able to get it sorted for you.
Enjoy.


Sent from my iPhone using Tapatalk

[Stefanalmare]

Monterey see network drive as internal. It is a beta issue (no specific icon yet), or it is just me? It happen in 5 hacks.

[Slice]

37 minutes ago, Stefanalmare said:

Monterey see network drive as internal. It is a beta issue (no specific icon yet), or it is just me? It happen in 5 hacks.

It is not pluggable so it is internal. As far as I remember.

[Stefanalmare]

2 hours ago, Slice said:

It is not pluggable so it is internal. As far as I remember.

"Alex" it is network drive. Look BigSur vs Monterey.

 

Spoiler

 

Spoiler

 

Edited July 25, 2021 by Stefanalmare

[greythorne]

Ok this is strange. My EFI partition still has about 100++ mb of drive space available. In it I have windows/OC boot folder which in total is about 50 or so mb. Now I updated the kext and got a prompt that says insufficient drive space.

 

Any idea why? I am on Monterey Beta 3 & Win 11.

[ndungu6678]

4 minutes ago, greythorne said:

Ok this is strange. My EFI partition still has about 100++ mb of drive space available. In it I have windows/OC boot folder which in total is about 50 or so mb. Now I updated the kext and got a prompt that says insufficient drive space.

 

Any idea why? I am on Monterey Beta 3 & Win 11.

 

Hi- is your trash folder empty?-used to get same message when trying to replace old EFI folder with new updated one- emptying trash used to help sometimes!

[greythorne]

3 minutes ago, ndungu6678 said:

 

Hi- is your trash folder empty?-used to get same message when trying to replace old EFI folder with new updated one- emptying trash used to help sometimes!

Hmmm. I turned on the hidden files and folder. The Trash folder in EFI partition was hidden. There was no files in it, the folder was empty.

 

 

[ndungu6678]

29 minutes ago, greythorne said:

Hmmm. I turned on the hidden files and folder. The Trash folder in EFI partition was hidden. There was no files in it, the folder was empty.

 

 

 

What about trash folder in dock on desktop?-Look at mine below-On the left shows contents of trash folder on dock and on right contents of trash folder in EFI -could be some other files still in trash (or BIN) in dock! -if that does not work -no idea!

 

Edited July 25, 2021 by ndungu6678

[kushwavez]

7 hours ago, greythorne said:

Ok this is strange. My EFI partition still has about 100++ mb of drive space available. In it I have windows/OC boot folder which in total is about 50 or so mb. Now I updated the kext and got a prompt that says insufficient drive space.

 

Any idea why? I am on Monterey Beta 3 & Win 11.

I did have the exact same issue, but for me it's started on Big Sur.

Looks like the system can't really handle well the EFI partition, or it is the Finder. I'd use Commander One or even just the terminal for handling EFI.

I'd also run an fsck on it, every time I got an msg says that the filesystem is corrupted, that released the space too.

 

I'm not on Mac rn and I don't really remember the exact command, it's like fsck fat32 /dev/diskXsX or simply fsck /dev/diskXsX

try & luck

 

Last resort is reformatting the EFI.

For dual-boot you can look at my writeup about recreating EFI and stuff, maybe that'll help you. It's not that hard

 

Edited July 25, 2021 by kushwavez

[silencer51]

The EFI partition is fat32 and really easy to corrupt, just mount it in Windows and run chkdsk /f on it. This also fixes mysterious slowdowns/load times for opencore.

[Slice]

7 hours ago, kushwavez said:

I did have the exact same issue, but for me it's started on Big Sur.

Looks like the system can't really handle well the EFI partition, or it is the Finder. I'd use Commander One or even just the terminal for handling EFI.

I'd also run an fsck on it, every time I got an msg says that the filesystem is corrupted, that released the space too.

 

I'm not on Mac rn and I don't really remember the exact command, it's like fsck fat32 /dev/diskXsX or simply fsck /dev/diskXsX

try & luck

 

Last resort is reformatting the EFI.

For dual-boot you can look at my writeup about recreating EFI and stuff, maybe that'll help you. It's not that hard

 

I have some experience with it. For my observation FAT32 driver included in UEFI BIOS is often buggy so saving boot.log or screenshot may corrupt the file system.

So why I highly recommend to Clover's users to install Fat.efi driver. It looks like does nothing but it prevents the EFI file system corruption.

[Wayang-NT]

[Djlild7hina]

Easy update  not sure if Universal Control works yet or not tho.  

 

EDIT: Guess apple pulled the mention of Universal Control being live lol

Edited July 27, 2021 by Djlild7hina

[Riley Freeman]

Smooth update. XLD no longer crashes. It started doing this in B2 or B3.

[robertdes69]

no problem for update b4

 

[miliuco]

2 hours ago, eSaF said:

Unlike the last Beta this update was trouble free. 

I see in About this Mac that your RX580 card has 4 GB, is it correct?

 

Edited July 27, 2021 by miliuco

[Avery B]

7 minutes ago, eSaF said:

Correct, 4GB is all my RX580 has and it works quite well for my needs, besides it is all the wife permitted me to spend on the card at the time of purchase. You know what they say...'A happy Wife leads to a Happy Life' or something to that effect. 

PS - The last update gave me boot loop because I had Secure Boot Mode Default instead of Disabled also with TPM enabled. With this latest update I did not change those settings and the update was ok with Secure Boot Mode and TPM Enabled so maybe Apple changed something there in respect of those two settings???!!!

Are you on the latest OC commit? They recently changed the default to x86legacy rather than one of the other T2 models.

[miliuco]

Updated to Developer beta 4 build 21A5294g.

I have needed:

• SIP enabled (csr-active-config=00000000 in config.plist)
• Gatekeeper enabled (sudo spctl --master-enable in Terminal) in macOS.

But PTT Disabled in Bios and SecureBootModel Disabled in config.plist no longer seem to be needed.

SecureBootModel has a new value (x86legacy) since build 0.7.2 dc20977, this is the recommended value for Monterey on Macs without a T2 chip and, by extension, Hacks.
I have used SecureBootModel=x86legacy and the update has worked fine.

[MorenoAv]

I updated finally with OC 0.6.9 no latest kexts, with TPM disabled in bios and secure boot disabled in bios, and taking the opportunity updated Big Sur to the latest release... with the same OC.

My problem was, is the Clover no matter 5137 0r 5138, it boots the hack and I have bluetooth but it don't update or install macOS.

On other side with OC 0.7.1 or 0.7.2 it installs macOS, and with a MQUPIN Fenvi T-919 brand new I don't have bluetooth no matter what I do, for that reason right now I'm using Cover to boot macOS Monterey, Big Sur and Windows 11...

Just my two cents

 

PS: Sip disabled and Gatekeeper disabled...

Edited July 27, 2021 by MorenoAv

[silencer51]

Updated without issues to beta 4 with SIP enabled and Gatekeeper disabled on a Thinkpad T480.

[MorenoAv]

43 minutes ago, eSaF said:

I am surprised at the B/T problem you have with this card, I have this card installed and have zero problems with it booting Catalina, BS and now Monterey and Windows 11, it just works with no special injected kexts.

No dice after Big Sur 11.2.3 started my bluetooth problems with the Wifi / bluetooth cards that I own, an Fenvi T-919 of Fenvi store, but it is bad I always had problems with it, I had an AWB with and BCM943602CS combo card and that is good very good, but after sometime the wires that make the connection with the card broke I bought another adapter for that card but it never worked as before. After that I bought an BCM94360NG but for that I have to disassemble all my hack... so I bought the MQUPIN Fenvi and it works well in clover, not in OC I don't know why... if I change the EFI from my Monterey partition from clover to OC I loose right away my bluetooth icon in system preferences... 

Edited July 27, 2021 by MorenoAv