Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

Why can't OC update? Now use CLOVER to update instead. Can anyone help me answer?

ภาพถ่ายหน้าจอ 2564-06-29 เวลา 00.43.49.png

265166905_2564-06-2901_26_27.thumb.png.c4a3b4c7fb0ba4a04f06a06659fae003.png

 

uh, why is it so much faster than the first beta?:thumbsup_anim:

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

Updated without any trouble here. Graphics card is now displayed in the ATM screen. Still no bluetooth (it's pretty ancient but worked in Big Sur) and my other internal drives are still appearing on my desktop, with some of them having eject icons in the Finder sidebar (despite being non-removable). I guess something has changed in the generic AHCI controller.

  • Like 2
Link to comment
Share on other sites

I couldn't get beta 2 to install using OC .71 but it installed just fine with Clover 5137.  Same thing with bluetooth.  Works fine with Clover, not so with OC.  Still working on getting it to work with OC.

  • Like 4
Link to comment
Share on other sites

5 minutes ago, mnfesq said:

I couldn't get beta 2 to install using OC .71 but it installed just fine with Clover 5137.  Same thing with bluetooth.  Works fine with Clover, not so with OC.  Still working on getting it to work with OC.

Hi @mnfesq what bluetooth do you have? 

I have an Fenvi T- 919 and I can't make It work with OC 0.7.1, I tried everything, but I managed to install Monterey Beta 2, with OC...

Thanks 

unnamed.jpg

  • Like 1
Link to comment
Share on other sites

5 minutes ago, MorenoAv said:

Hi @mnfesq what bluetooth do you have? 

I have an Fenvi T- 919 and I can't make It work with OC 0.7.1, I tried everything, but I managed to install Monterey Beta 2, with OC...

Thanks 

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

  • Like 3
Link to comment
Share on other sites

8 minutes ago, mnfesq said:

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

In my case, OC 0.71 does not detect any updates. do it many times until I have to go back to use CLOVER

Link to comment
Share on other sites

53 minutes ago, antuneddu said:

Sorry but what's in it, it's not the bootloader that detects updates

I'm very new to OC. I don't understand much EN language. Always use google translate. I really want to know what's in bootloader or not What part do you have doubts? please tell me thank you

must try to return OC the previous version again 0.6.5
This one feels much more flexible. DSDT.aml can be customized as needed. and feel that version 0.7.1 Very sensitive, can't make a little mistake (broken)

Edited by naiclub
Link to comment
Share on other sites

1 hour ago, mnfesq said:

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

Strange but true I also had the same problem with OC and Macintosh hd .. solved by putting on clover, let's hope someone sheds some light on this I'm very curious

Link to comment
Share on other sites

2 minutes ago, antuneddu said:

Strange but true I also had the same problem with OC and Macintosh hd .. solved by putting on clover, let's hope someone sheds some light on this I'm very curious

Me too. It seems to be installing beta 2, rebooting, etc., but at the end I stay in beta 1. Tried 2 times.

Link to comment
Share on other sites

20 minutes ago, Hervé said:

Straight & easy update with Clover r5133 on my Skylake/HD520 Dell Latitude E7270 laptop.

E7270_i7-6600U_HD520_12.0.b2.jpg

 

More complicated update with OpenCore v0.7.0 on my Haswell/HD4400 Toshiba Satellite Pro R50-B: initiated the update, rebooted from the temp install partition a 1st time, then a 2nd time. On 3rd boot of that temp partition, laptop went into a boot loop. Booted the original Monterey partition and laptop went through a xx minutes remaining as if finishing off the update but, on reaching the desktop -> Monterey beta1.  <_<

 

Clover still better for me... :P

 

I have the same problem, I was never able to complete update to B2 since i don't have clover :O

 

Link to comment
Share on other sites

I think there must be a crash at OC 0.7.1. I have tried reverting to version 0.6.0. It's much better. Show CPU name exactly As it should be (0.7.1 listed as unknown CPU iMac Pro1.1), this could be the main reason for not being able to update.

1545153465_2564-06-2904_42_07.thumb.png.df36858a21386a43e8d3b841d7b821bb.png

1560674965_2564-06-2904_52_44.thumb.png.f10b434f87963cf9cb9600f45941c601.png

Edited by naiclub
Link to comment
Share on other sites

Well there we have it, This update has broken my Monterey install by way of at the first reboot where it creates the HD installer volume it goes into an endless series of reboot loops when selected to complete the install. Using the latest OC release also with previous boot args used in the first one makes no difference. Although I can boot into the original install, I now have an extra useless install volume at the boot menu. So I am having all the fun at the fair with this update although I'm at a lost as to what else to try. :cry:

 

It seems like the Clover gang has left us OC boys behind on this one!!! :smoke:

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

6 minutes ago, eSaF said:

Well there we have it, This update has broken my Monterey install by way of at the first reboot where it creates the HD installer volume it goes into an endless series of reboot loops when selected to complete the install. Using the latest OC release also with previous boot args used in the first one makes no difference. Although I can boot into the original install, I now have an extra useless install volume at the boot menu. So I am having all the fun at the fair with this update although I'm at a lost as to what else to try. :cry:

 

It seems like the Clover gang has left us OC boys behind on this one!!! :smoke:

Happened to me until I changed SecureBootModel to Disabled

  • Like 2
Link to comment
Share on other sites

19 minutes ago, eSaF said:

Well there we have it, This update has broken my Monterey install by way of at the first reboot where it creates the HD installer volume it goes into an endless series of reboot loops when selected to complete the install. Using the latest OC release also with previous boot args used in the first one makes no difference. Although I can boot into the original install, I now have an extra useless install volume at the boot menu. So I am having all the fun at the fair with this update although I'm at a lost as to what else to try. :cry:...

Exactly as you. I've tried OC 0.7.1 and 0.70. 😬 

13 minutes ago, Irish_Man said:

Happened to me until I changed SecureBootModel to Disabled

I'll try and comment.

Link to comment
Share on other sites

13 minutes ago, Irish_Man said:

Happened to me until I changed SecureBootModel to Disabled

Already disabled in BIOS by default. Will have to be patient and wait for the OC Devs to offer up a solution or as @Hervé suggested bite the bullet and dust off my Clover Folder which will be more fun as I left that behind a few versions ago.

  • Like 1
Link to comment
Share on other sites

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