Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

Hi @all

Using Clover, I can download the new Beta. But SMBIOS Imac17,1 failed for my Z390, to update Beta 7. I don't know why 😪

So I want to remove "macOS Install Data" folder. I find 3 strange folder in System/Volumes/Monterey

  • macOS Install Data (11,7Go) --->2021-07-06
  • Previous Content (256,6Mo) ----> 2021-09-05 (Probably from previous   Beta !)
  • Boot folder. (283,2Mo) ---> 2021-09-15.   With  a lot of .im4m files and the X86_64SURamdisk.dmg
Spoiler

177341744_Capturedcran2021-09-2218_34_51.png.9db3c62cc24faabd5eab4c54238285bd.png

 

 

Spoiler

1718400754_Capturedcran2021-09-2218_44_12.png.44323c52df2d0b24011e15f2b38540de.png

 

 

 

macOS Install Data folder this normal, but the date is incorrect (the version too I suppose). Does anyone have an idea on these files/folders, it is the first time that I notice their presence except macOS Install Data folder of course.

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

3 hours ago, Riley Freeman said:

 

Ouch. I hope they haven't completely killed Kepler support as I have a 670 on my Monterey hack.

 

I tried the update yesterday but after I got back to the desktop (after what looked like a successful update) the update was still showing up in Software Update. Checking the build on my system I was still on B6.

 

Looking at the update partition the last_update_result.plist gives this as the reason for the update failing: MSU 1140 (EFI ROM does not support large BaseSystems).

 

I'm using MP6,1 SMBIOS here. Not going to change it for a beta update so I'll sit this one out and see if it's a bug or something more significant.

 

 

With last OC build b7 update successfully hack iMac18,3.

 

Error -> "EFI ROM does not support large BaseSystems" as gone

 

Fred

  • Like 2
Link to comment
Share on other sites

1 minute ago, FredWst said:

With last OC build b7 update successfully hack iMac18,3.

 

Error -> "EFI ROM does not support large BaseSystems" as gone

 

Fred

 

Thanks Fred! I only run the release builds so I'm still on 0.7.3.

 

The drop of Kepler support is a bigger issue now. I'll check out the Kepler patch along with the next official OC release but this might be where I call it quits with Monterey and go back to something earlier.

  • Like 1
Link to comment
Share on other sites

@vit9696

 

Hack MacBookPro16,2 with Secure boot set in config.plist ApECID=0 and secureBootModel=j214k

I got update b7 proposed to update.

But got this error below. OC bug or bad config.plist ?

 

1516381872_Capturedcran2021-09-2219_41_52.png.83241618efcd2d91bf74a512b3e824e1.png 

 

Edit: update ok change -> secureBootModel to Disabled and back to j214k

 

Fred

 

 

Edited by FredWst
update ok change -> secureBootModel to Disabled and back to j214k
Link to comment
Share on other sites

16 minutes ago, meaganmargaret said:

If you use InstallScript_110fullapp (from Github, use google to find it), you can get the Beta 7 522h version.  Just downloaded it, and will be installing it on my secondary Beta machine soon.

That would be very handy, I will download it and put it on a spare USB drive incase of my mischievous dabbling with my present install, don't really want to go the whole way via Beta 6 again. :)

Seems like traffic on the site is pretty heavy at the moment, normally takes me 30 minutes for the D/Load but it is saying 3 hours so I will try again later.

Edited by eSaF
Link to comment
Share on other sites

6 minutes ago, meaganmargaret said:

 

 

Well even after downloading the full installer as listed by @antuneddu, I got the same error.  Must be my old Z370.....

 

Have you launched the app or created the usb?
Because if I launch the app it seems to work

366196555_Schermata2021-09-22alle22_37_39.png.c6d8adc4e8c96e4ec732a8800ca5d31d.png 

 

but if I try to create the usb it says that the installer is not valid

674546193_Schermata2021-09-22alle22_34_39.png.3ad4f1dc91d6aaf1dbc071b99f8a7dda.png

 

TINU app 

365835601_Schermata2021-09-22alle22_35_59.png.b6d837e4b24d3c830364c9ad389748b6.png

 

I'm wrong, or the installer has some problem ... I downloaded it 2 times 🤔

  • Like 1
Link to comment
Share on other sites

@antuneddu when I was doing a fresh install USB drive for Beta 6, I tried to use the latest version of TINU installer and it kept throwing up an error just like that so I use the previous version and I was abled to make the installer. Don’t know if there is a bug in the new version. I am in the process of making an install stick for Beta 7 so will see what happens and report findings. 

Link to comment
Share on other sites

3 minutes ago, meaganmargaret said:

 

Well, I think it's my machine, but I did try using the InstallAssistant and then booting with iMac 17, 1 and double clicking the Install macOS Monterey beta app, but it just spits out the same error for me....not sure why just yet.....

It worked for me with iMac 17.1 securebootmodel = default
So you haven't tried to create the usb? I wanted to find out if it works 🤔

3 minutes ago, eSaF said:

@antuneddu when I was doing a fresh install USB drive for Beta 6, I tried to use the latest version of TINU installer and it kept throwing up an error just like that so I use the previous version and I was abled to make the installer. Don’t know if there is a bug in the new version. I am in the process of making an install stick for Beta 7 so will see what happens and report findings. 

Thanks, I downloaded the latest of TINU, but even with the terminal it tells me that the installer is not valid

Link to comment
Share on other sites

6 minutes ago, antuneddu said:

Thanks, I downloaded the latest of TINU, but even with the terminal it tells me that the installer is not valid

I don't think there is anything wrong with the installer app because I am getting the same error. I think you can only install directly from the downloaded Monterey app it self over the previous Beta oppose to making an installer stick. If I remember correctly, Apple did that with a previous Beta can't remember if it was BS or Mojave, maybe someone with more memory cells than I can clarify.

Screen Shot 2021-09-22 at 22.09.00.png

  • Haha 2
Link to comment
Share on other sites

My fellow hackintosh gentlemen and gentle ladies, the solution for Beta7 is to update to the latest commit of OpenCore 0.7.4 beta.  Ensure PlatformInfo->Generic->AdviseFeatures is set to True.  See the latest commit here: https://github.com/acidanthera/OpenCorePkg/commit/1cb8490fd60f6b5f983d42e5bbf08e3d2d43d8f6

 

Edit: According to @Andrey1970 AdviseFeatures need not be enabled.

 

Using 'Default' SecureBootModel: Success!

 

MontereyBeta7.png.03b86d7b787afa24521c48d1daefa5a9.png

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

17 minutes ago, dehjomz said:

Ensure PlatformInfo->Generic->AdviseFeatures is set to True.  See the latest commit

I don't think mine was ever any different from way back and yet I still had to jump through hoops to install. Also running the latest OC nightly version.

Hang on - so what is the correct setting - True or False? - Ok I just read @Andrey1970 post so going forward I will try False in future Updates/Installs.

Screen Shot 2021-09-22 at 22.24.28.png

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

1 minute ago, eSaF said:

I don't think mine was ever any different from way back and yet I still had jump through hoops to install. Also running the latest OC nightly version. 

Screen Shot 2021-09-22 at 22.24.28.png

Did you run the commit that vit9696 posted 5 hours ago today: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true&version=0.7.4&sha=1cb8490fd60f6b5f983d42e5bbf08e3d2d43d8f6

Link to comment
Share on other sites

3 hours ago, FredWst said:

@vit9696

 

Hack MacBookPro16,2 with Secure boot set in config.plist ApECID=0 and secureBootModel=j214k

I got update b7 proposed to update.

But got this error below. OC bug or bad config.plist ?

 

1516381872_Capturedcran2021-09-2219_41_52.png.83241618efcd2d91bf74a512b3e824e1.png 

 

Edit: update ok change -> secureBootModel to Disabled and back to j214k

 

Fred

 

 

 

 

1516381872_Capturedcran2021-09-2219_41_52.png.83241618efcd2d91bf74a512b3e824e1.png

Because of this bug

Edited by FredWst
Link to comment
Share on other sites

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