miliuco Posted July 30, 2021 Share Posted July 30, 2021 6 hours ago, pet1 said: I'm not seeing anything related to that setting. Just CSM which is enabled, other os. UEFI only. and secure boot keys disabled. Usually most of us have CSM disabled, it's only useful for legacy Windows, it's not for macOS. 3 Link to comment Share on other sites More sharing options...
ndungu6678 Posted July 30, 2021 Share Posted July 30, 2021 (edited) 17 hours ago, pet1 said: I have the same issue. I don't have TPM available in my bios. What other suggestions might there be? Guys !- i have been plagued by the same issue since beta 3 -even with SIP enabled and secure boot set to disable-also can't find TPM in bios so had to ignore that. I successfully downloaded the update but had a repeated boot loop preventing the completion of the update-anyway i finally succeeded in installing beta 4. I use Open Core 0.7.2 with VirtualSMC, Lilu and WhaterverGreen plus others, so what i did was to build a separate Clover 5133 EFI boot loader with minimal kexts( FakeSMC a few other essential ones for my board- HP Pavillion Gaming 595 , RX 580, i5 9400F, 16GB DDR4)-note even the config.plist file has to be re-built specific for Clover-do not try and replace with your Open Core one. I replaced my Open Core EFI with the Clover one and this allowed me to get past the boot loop and eventually complete the update. I had the same problem with beta 3 and had to use full installer to update in that instance-I suspect the culprit is related to a kext -because even after replacing the EFI, it went past the point of the initial boot loop, but it hanged further on with a warning about refusal of a kext. I was about to give up and try removing all the remaining kexts left in the EFI folder in Library, but after one more reboot it completed the update !. After updating, i removed the Clover EFI and one put back my original Open Core EFI. Now it boots perfectly ! - what baffles me is I have never had to change the contents of my EFI in the past and updates have been a breeze- My Big Sur EFI is identical to this one on Monterey and i have no issue whatsoever with updates there- anyway good luck !: Edited July 30, 2021 by ndungu6678 3 Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted July 30, 2021 Share Posted July 30, 2021 On 7/28/2021 at 10:56 PM, Rocky12 said: Beta 4 Full Installer http://swcdn.apple.com/content/downloads/31/06/071-71557-A_F68IOP9JSU/bjx1ln0wuifn37408kguq3obcd05itznjk/InstallAssistant.pkg Thanks Rocky, I'm unable to do updates but I can do full installs so this helped a lot. 2 Link to comment Share on other sites More sharing options...
miliuco Posted July 30, 2021 Share Posted July 30, 2021 12 hours ago, eSaF said: To be honest if the rig is functioning ok then at this stage I wouldn't worry too much about it at least until the next Beta. Did you update or a clean install? Mine is a clean install maybe that's where the difference is and why both of mine says Sealed who knows. Yes, I have updated, it's not a fresh install. This can be a difference. 3 Link to comment Share on other sites More sharing options...
pet1 Posted July 30, 2021 Share Posted July 30, 2021 (edited) Clean install has nothing to do with it. I've tried with several clean installs and it does the same thing each time. I will note that the same behavior occurs with 11.5 and 11.51. The way I was able to get around the issue for 11.5, 11.51 and 12 beta 4 was to boot into recovery mode after the boot loop starts happening and reinstall over your existing installed drive. When it's done it will somehow update to 12 beta 4. The same works for 11.5 and 11.51. We know at this point that it's opencore related since clover works fine. Looks like opencore needs to play catch-up cause the install code is a bit different. If another update came out as of now we'd still be having the same problem. Installing from usb installer works perfectly as well but updates still not working. Edited July 30, 2021 by pet1 2 Link to comment Share on other sites More sharing options...
bidero Posted July 30, 2021 Share Posted July 30, 2021 (edited) On 7/28/2021 at 7:59 AM, WizeMan said: Updated from beta 3, without issues this time. Live Text is simply amazing. Hide contents Beta 4 installed without any issues, but I can't get live text to work. I have no idea what's the problem. EDIT: Problem solved! It does work, but the system language has to be set to English Edited July 31, 2021 by bidero 2 Link to comment Share on other sites More sharing options...
Partime Posted July 30, 2021 Share Posted July 30, 2021 19 hours ago, eSaF said: Maybe it is there but under a different name in the BIOS. On the Gigabyte boards it is called TTP, most modern boards has this feature in one form or another. It might also be Intel Platform Trust Technology (PTT) on gigabyte. this worked for me. The BIOS of GIGABYTE Motherboards Features TPM 2.0 Function to Support Windows 11 Upgrade | News - GIGABYTE Global 2 Link to comment Share on other sites More sharing options...
HenryV Posted July 30, 2021 Share Posted July 30, 2021 22 hours ago, eSaF said: As far as I can tell mine is still Sealed. Reveal hidden contents A subsequent reboot showed snapshot cleanup in the scrolling verbose text. Afterward was able to backup with SuperDuper. Reboot a couple of times if necessary if SuperDuper fails due to broken seal issue. Another issue is Super Duper can not find previous volumes and does not proceed. Need to go into ApplicationSupport and delete the SuperDuper data and relaunch the program to get rid of this issue. 1 Link to comment Share on other sites More sharing options...
pet1 Posted July 30, 2021 Share Posted July 30, 2021 (edited) 14 hours ago, ndungu6678 said: Guys !- i have been plagued by the same issue since beta 3 -even with SIP enabled and secure boot set to disable-also can't find TPM in bios so had to ignore that. I successfully downloaded the update but had a repeated boot loop preventing the completion of the update-anyway i finally succeeded in installing beta 4. I use Open Core 0.7.2 with VirtualSMC, Lilu and WhaterverGreen plus others, so what i did was to build a separate Clover 5133 EFI boot loader with minimal kexts( FakeSMC a few other essential ones for my board- HP Pavillion Gaming 595 , RX 580, i5 9400F, 16GB DDR4)-note even the config.plist file has to be re-built specific for Clover-do not try and replace with your Open Core one. I replaced my Open Core EFI with the Clover one and this allowed me to get past the boot loop and eventually complete the update. I had the same problem with beta 3 and had to use full installer to update in that instance-I suspect the culprit is related to a kext -because even after replacing the EFI, it went past the point of the initial boot loop, but it hanged further on with a warning about refusal of a kext. I was about to give up and try removing all the remaining kexts left in the EFI folder in Library, but after one more reboot it completed the update !. After updating, i removed the Clover EFI and one put back my original Open Core EFI. Now it boots perfectly ! - what baffles me is I have never had to change the contents of my EFI in the past and updates have been a breeze- My Big Sur EFI is identical to this one on Monterey and i have no issue whatsoever with updates there- anyway good luck !: Did you complete the update by running it from scratch booting from the clover partition? Or, did you run the Macintosh HD partition from the previous failed update after copying clover EFI? Edited July 30, 2021 by pet1 Link to comment Share on other sites More sharing options...
mnfesq Posted July 31, 2021 Share Posted July 31, 2021 20 hours ago, ndungu6678 said: Guys !- i have been plagued by the same issue since beta 3 -even with SIP enabled and secure boot set to disable-also can't find TPM in bios so had to ignore that. I successfully downloaded the update but had a repeated boot loop preventing the completion of the update-anyway i finally succeeded in installing beta 4. I use Open Core 0.7.2 with VirtualSMC, Lilu and WhaterverGreen plus others, so what i did was to build a separate Clover 5133 EFI boot loader with minimal kexts( FakeSMC a few other essential ones for my board- HP Pavillion Gaming 595 , RX 580, i5 9400F, 16GB DDR4)-note even the config.plist file has to be re-built specific for Clover-do not try and replace with your Open Core one. I replaced my Open Core EFI with the Clover one and this allowed me to get past the boot loop and eventually complete the update. I had the same problem with beta 3 and had to use full installer to update in that instance-I suspect the culprit is related to a kext -because even after replacing the EFI, it went past the point of the initial boot loop, but it hanged further on with a warning about refusal of a kext. I was about to give up and try removing all the remaining kexts left in the EFI folder in Library, but after one more reboot it completed the update !. After updating, i removed the Clover EFI and one put back my original Open Core EFI. Now it boots perfectly ! - what baffles me is I have never had to change the contents of my EFI in the past and updates have been a breeze- My Big Sur EFI is identical to this one on Monterey and i have no issue whatsoever with updates there- anyway good luck !: I had the situation where Clover worked to install but OC did not work. It turned out that, for me, something changed my settings and securedbootmodel was changed from disabled to default. When I changed it back to disabled, OC installed as wells as Clover. Link to comment Share on other sites More sharing options...
pet1 Posted July 31, 2021 Share Posted July 31, 2021 24 minutes ago, mnfesq said: I had the situation where Clover worked to install but OC did not work. It turned out that, for me, something changed my settings and securedbootmodel was changed from disabled to default. When I changed it back to disabled, OC installed as wells as Clover. The issue we're referring to is regarding updating via software update. Fresh install from usb on either clover or oc works fine. Link to comment Share on other sites More sharing options...
mnfesq Posted July 31, 2021 Share Posted July 31, 2021 8 minutes ago, pet1 said: The issue we're referring to is regarding updating via software update. Fresh install from usb on either clover or oc works fine. Yes, that was the same for me. When I used software update I could not complete the first stage of installation after the first reboot. The Macintosh HD installer never disappeared and installation never completed no matter how many times I tried to boot to the Macintosh HD installer. If I selected my system hard drive, it would skip to the third stage of installation but, when I got to the desktop, it was still the old version. Sorry you haven't been able to solve your problem. I solved mine and shared what worked for me. 2 Link to comment Share on other sites More sharing options...
Bios-PC Posted July 31, 2021 Share Posted July 31, 2021 hi everybody I have z590 motherboard , with Big Sur everything work perfect when I install Monterey I got into system and after 1-5 minute I got the system freeze here is one log : panic(cpu 4 caller 0xffffff80101efe83): Kernel trap at 0xffffff8012bab75d, type 14=page fault, registers: CR0: 0x0000000080010033, CR2: 0x0000000000000058, CR3: 0x000000089b1fc012, CR4: 0x00000000003626e0 RAX: 0x0000000000000000, RBX: 0xffffff937b31a0a0, RCX: 0x0000000000000000, RDX: 0x0000000000420000 RSP: 0xfffffff0ca003bd0, RBP: 0xfffffff0ca003c00, RSI: 0xffffff86af2f56c0, RDI: 0xffffff937b31a0a0 R8: 0x0000000000000016, R9: 0x0000000000000002, R10: 0xffffff937b04c8c0, R11: 0xffffff80109e4db4 R12: 0xffffff8011066698, R13: 0x00000000e00002bd, R14: 0xffffff86af2f56c0, R15: 0xffffff937c041c3c RFL: 0x0000000000010246, RIP: 0xffffff8012bab75d, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x0000000000000058, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0 Panicked task 0xffffff86b1d8d1a0: 3 threads: pid 83: systemstats Backtrace (CPU 4), panicked thread: 0xffffff86bc44f8b0, Frame : Return Address 0xfffffff0ca003600 : 0xffffff80100a83dd 0xfffffff0ca003650 : 0xffffff80102000c5 0xfffffff0ca003690 : 0xffffff80101efa93 0xfffffff0ca0036e0 : 0xffffff8010047a60 0xfffffff0ca003700 : 0xffffff80100a87ad 0xfffffff0ca003820 : 0xffffff80100a7f66 0xfffffff0ca003880 : 0xffffff801091b779 0xfffffff0ca0038f0 : 0xffffff80101efe83 0xfffffff0ca003a70 : 0xffffff80101efb68 0xfffffff0ca003ac0 : 0xffffff8010047a60 0xfffffff0ca003ae0 : 0xffffff8012bab75d 0xfffffff0ca003c00 : 0xffffff8010826324 0xfffffff0ca003c20 : 0xffffff801415b3ed 0xfffffff0ca003cd0 : 0xffffff801082683f 0xfffffff0ca003d00 : 0xffffff801089a258 0xfffffff0ca003d70 : 0xffffff80101abed6 0xfffffff0ca003dc0 : 0xffffff8010083069 0xfffffff0ca003e50 : 0xffffff801009a009 0xfffffff0ca003ee0 : 0xffffff80101d4da2 0xfffffff0ca003fa0 : 0xffffff8010048246 Kernel Extensions in backtrace: com.apple.iokit.IOPCIFamily(2.9)[CEACB131-F3A1-3E52-9F2C-AFF22FF196F7]@0xffffff8012b9d000->0xffffff8012bc7fff as.vit9696.WhateverGreen(1.5.1)[696AA9AE-C508-3E4C-9CCE-4FBFF7DB95DA]@0xffffff8014153000->0xffffff80141cbfff dependency: as.vit9696.Lilu(1.5.4)[809BC306-CD75-382C-A93A-6D072B207915]@0xffffff8013f41000->0xffffff8013f6bfff dependency: com.apple.iokit.IOPCIFamily(2.9)[CEACB131-F3A1-3E52-9F2C-AFF22FF196F7]@0xffffff8012b9d000->0xffffff8012bc7fff Process name corresponding to current thread (0xffffff86bc44f8b0): systemstats Boot args: alcid=1 shikigva=128 watchdog=0 -v Mac OS version: 21A5284e Kernel version: Darwin Kernel Version 21.0.0: Mon Jul 5 02:28:23 PDT 2021; root:xnu-8019.0.46.0.4~11/RELEASE_X86_64 Kernel UUID: 1EAC491D-E0B4-34AB-8564-6705561A7E9E KernelCache slide: 0x000000000fe00000 KernelCache base: 0xffffff8010000000 Kernel slide: 0x000000000fe10000 Kernel text base: 0xffffff8010010000 __HIB text base: 0xffffff800ff00000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 616259970337 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000008f7bf4e738 Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x000000256f42a974 0x0000000000000000 anyone also got these problem best regards Link to comment Share on other sites More sharing options...
SavageAUS Posted July 31, 2021 Share Posted July 31, 2021 @Bios-PC Have you updated all your kexts? Sent from my iPhone using Tapatalk 1 1 Link to comment Share on other sites More sharing options...
ndungu6678 Posted July 31, 2021 Share Posted July 31, 2021 (edited) 14 hours ago, pet1 said: Did you complete the update by running it from scratch booting from the clover partition? Or, did you run the Macintosh HD partition from the previous failed update after copying clover EFI? I completed by running the already present Macintosh HD partition -not from scratch Edited July 31, 2021 by ndungu6678 1 Link to comment Share on other sites More sharing options...
Bios-PC Posted July 31, 2021 Share Posted July 31, 2021 3 hours ago, SavageAUS said: @Bios-PC Have you updated all your kexts? Sent from my iPhone using Tapatalk yes all the kext updated Link to comment Share on other sites More sharing options...
greythorne Posted July 31, 2021 Share Posted July 31, 2021 On 7/26/2021 at 7:27 AM, silencer51 said: 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. I mounted the EFI partition in windows 11. True enough, only about 8mb of space left out of the 200mb i created. The whole EFI folder is about 50mb. Really weird where the remaining space went to. I did mount the EFI in windows 11 and ran chkdsk /f /r on it but to no available! Is it possible to format and copy over the EFI folder on the EFI partition in Monterey? Can it be done without a usb? Link to comment Share on other sites More sharing options...
miliuco Posted July 31, 2021 Share Posted July 31, 2021 3 hours ago, greythorne said: I mounted the EFI partition in windows 11. True enough, only about 8mb of space left out of the 200mb i created. The whole EFI folder is about 50mb. Really weird where the remaining space went to. Mount EFI partition in macOS and empty the trash. 2 Link to comment Share on other sites More sharing options...
eSaF Posted July 31, 2021 Share Posted July 31, 2021 55 minutes ago, miliuco said: Mount EFI partition in macOS and empty the trash. Also while you're there go into the EFI/Resources/Audio folder and remove the audio files that are not in your native language, although they are small, by removing them it will free up even more space on the partition. 2 Link to comment Share on other sites More sharing options...
mnfesq Posted July 31, 2021 Share Posted July 31, 2021 (edited) 8 hours ago, Bios-PC said: yes all the kext updated If you have Xcode and Hackintool installed, you could use them build updates for Lilu 1.5.5 and Whatevergreen 1.5.2. You do see in the KP log you posted that those are the most-likely culprits: Kernel Extensions in backtrace: com.apple.iokit.IOPCIFamily(2.9)[CEACB131-F3A1-3E52-9F2C-AFF22FF196F7]@0xffffff8012b9d000->0xffffff8012bc7fff as.vit9696.WhateverGreen(1.5.1)[696AA9AE-C508-3E4C-9CCE-4FBFF7DB95DA]@0xffffff8014153000->0xffffff80141cbfff dependency: as.vit9696.Lilu(1.5.4)[809BC306-CD75-382C-A93A-6D072B207915]@0xffffff8013f41000->0xffffff8013f6bfff dependency: com.apple.iokit.IOPCIFamily(2.9)[CEACB131-F3A1-3E52-9F2C-AFF22FF196F7]@0xffffff8012b9d000->0xffffff8012bc7fff Edited July 31, 2021 by mnfesq 1 Link to comment Share on other sites More sharing options...
surenmunoo Posted August 1, 2021 Share Posted August 1, 2021 Updated to Beta, easy and painless. Took 15 minutes on 11th Gen with Z490 Vision D, everything still works as it should. Link to comment Share on other sites More sharing options...
pet1 Posted August 1, 2021 Share Posted August 1, 2021 (edited) Was able to update through software update by deleting pk boot key which disables secure boot in bios. Rebooted and started software update again and went through without looping. Seems as though the update has to be restarted from desktop after making the changes and can't just run the final stage of update after making changes. Edited August 1, 2021 by pet1 1 Link to comment Share on other sites More sharing options...
eng_redaesm Posted August 1, 2021 Share Posted August 1, 2021 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 ? Link to comment Share on other sites More sharing options...
HenryV Posted August 1, 2021 Share Posted August 1, 2021 On 7/31/2021 at 12:17 PM, greythorne said: I mounted the EFI partition in windows 11. True enough, only about 8mb of space left out of the 200mb i created. The whole EFI folder is about 50mb. Really weird where the remaining space went to. I did mount the EFI in windows 11 and ran chkdsk /f /r on it but to no available! Is it possible to format and copy over the EFI folder on the EFI partition in Monterey? Can it be done without a usb? If you are interested in not disturbing an existing FAT32/ESP while tweaking/configuring a separate bootloader for a new or upgraded installation, you may want to check out the partitioning/bootloader info here: https://www.insanelymac.com/forum/topic/346639-updated-tips-and-observations-for-big-sur-and-monterey/ 1 Link to comment Share on other sites More sharing options...
Alex HQuest Posted August 1, 2021 Share Posted August 1, 2021 On 7/28/2021 at 2:00 AM, Cyberdevs said: Hi guys I'm just curious, is there any news regarding Intel's 11th Gen support in the new Monterey beta release? 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. 1 1 Link to comment Share on other sites More sharing options...
Recommended Posts