Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

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!

 

Screenshot 2021-07-25 at 5.11.44 PM.png

Edited by ndungu6678
Link to comment
Share on other sites

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 by kushwavez
Link to comment
Share on other sites

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.

  • Like 2
  • Thanks 3
Link to comment
Share on other sites

2 hours ago, eSaF said:

Unlike the last Beta this update was trouble free. :thumbsup_anim:

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

 

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

13 minutes ago, miliuco said:

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

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. :hysterical:

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???!!!

Edited by eSaF
  • Like 1
  • Haha 4
Link to comment
Share on other sites

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. :hysterical:

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.

  • Like 2
Link to comment
Share on other sites

1 minute ago, 1Revenger1 said:

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

I am using the latest OC Nightly commit also see attached of entry in my config.plist.

Spoiler

1717055071_ScreenShot2021-07-27at21_59_33.thumb.png.b61a304a47ef8f601ad158278d8908d3.png

 

  • Like 2
Link to comment
Share on other sites

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.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

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 by MorenoAv
  • Like 1
Link to comment
Share on other sites

10 minutes ago, MorenoAv said:

MQUPIN Fenvi T-919 brand new I don't have bluetooth no matter what I do,

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.

  • Like 2
Link to comment
Share on other sites

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 by MorenoAv
  • Sad 2
Link to comment
Share on other sites

@5T33Z0 and everyone with an onboard i225-V LAN implementation hosted by an Intel Z490 chipset. 

After upgrading my test setup from Monterey beta 3 to beta 4, the i225-V connection problems persist, however with a variation. Manually setting the network speed to 100baseTX renders onboard networking usable and, as it seems, reliable as well. When I then increase the speed to 1000baseT it only works for a short time, whereafter networking becomes unresponsive and thus unusable.

In my OC 0.7.1 config file the only parameter used to enable the i225-V is the boot argument  dk.e1000=0, which I also use in Big Sur, where it works flawlessly. 

Another observation is that an ASIX AX88179 Gigabit USB adapter fails to load under Monterey whereas this unit works flawlessly, under Big Sur, using ASIX's latest DEXT driver.

Keen to learn from others what headway they have made in their attempts in getting the i225-V network adapter working properly under Monterey.

 

Greetings Henties

 

 

  • Like 1
Link to comment
Share on other sites

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