Jump to content

[pre-release] macOS Monterey


1,859 posts in this topic

Recommended Posts

Guest 5T33Z0
2 hours ago, MacWill said:


"Device ID" 😊

 

I just realized: you are using a Z590 Vision G which uses a revision 3 of the I225 which is compatible with macOS while the Z490 uses Revision 2. So no wonder that it works for you and not for other Z490 Vision G users…

Edited by 5T33Z0
Link to comment
Share on other sites

6 hours ago, 5T33Z0 said:

 

Read the thread. There are guides on how to get IvyBridge working. It's complicated but not impossible. But if you ask me, it's not worth it.

I have a Ivy Bridge with the following specs: ASUS H61M-A/USB, GT630, 4GG Ram, 120 GB M.2 SSD with adapter to connect to sata, 500GB HD. Running Montery dual boot with Windows 11 and it runs pretty will and as fast as my Haswell with out boot delay and autologin off.  Windows 11 on a normal HD performs very well. If you have a graphics card supported OOB the installation is smooth as silk.

Link to comment
Share on other sites

1 hour ago, Hervé said:

The matter really related to IvyBridge HD4000 graphics.

 

Add the Geforce 730 GT then done, dont worry about the internal graphic

 

Hope soon release the second beta :))

 

Edited by hiphopboy
Link to comment
Share on other sites

13 hours ago, ombra88 said:

I see, tried with it but nothing still stuck with apple logo and scattered lines when booting.

It's crazy to leave dGPUs doing nothing for this new os..😤

If Whatevergreen.kext was used, you may try add "-wegnoigpu" to boot-argument to disable IGPU and booted by dGPU (in your case which's R9 290X).

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

On 6/19/2021 at 4:20 PM, 5T33Z0 said:

 

Read the thread. There are guides on how to get IvyBridge working. It's complicated but not impossible. But if you ask me, it's not worth it.

 

I updated my OpenCore USB Stick to 0.7.1 and it boots fine, just need to check if all the hardware is working correctly now.

Edited by D-an-W
Link to comment
Share on other sites

Hello,

I was trying to install Monterey on my rig. It's on my signature.

 

For that, I've had to turn off multi core processing. I think is something related to CpuTscSync.

Do yo guys have also this problem? Currently I'm installing with this option off.

Maybe the plugin needs an update.

Link to comment
Share on other sites

16 hours ago, pepitillo said:

Hello,

I was trying to install Monterey on my rig. It's on my signature.

 

For that, I've had to turn off multi core processing. I think is something related to CpuTscSync.

Do yo guys have also this problem? Currently I'm installing with this option off.

Maybe the plugin needs an update.

Me too.

In Acer M4610 hackintosh I must add cpus=1 to boot properly even I have used VoodooTSCSync.kext, CpuTscSync.kext, and TSCAdjustReset.kext which is the only one among my 10+ hackintoshs had this issue.

Edited by jsl2000
Link to comment
Share on other sites

Anyone have sudden reboots with Monterey. I installed and it worked for a while but recently it just freezes the screen and reboots itself after being frozen for about 2 minutes. 

What’s changed recently? New kext? New program?


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

3 hours ago, surenmunoo said:

Added an AMD AX7870 Graphics card only and changed symbols to iMacPro1.1 to work with that card

AMD AX7870 is supposed to work in macOS? It isn't in Dortania's GPU guide.

If you are using USB map kext, have you changed here SMBIOS model as in config.plist?

Link to comment
Share on other sites

hi guys,

i got MacOS Monterey up and running, but i was trying to make bluetooth to work and installed BlueToolFixup.kext, and the hack froze on apple logo, so i signed it to my other hack in other ssd and deleted the kext,

 

now my problem is that i cant access Monterey anymore, i got "This version of Mac OS X is not supported on this platform!", while it was working before,

 

and  ssd name is BigSur 750 but after i access it through other Mac, it got - data name on it at the end "BigSur 750 - Data". 

 

 

IMG_6270.JPG

IMG_6269.JPG

Link to comment
Share on other sites

On 6/19/2021 at 1:29 PM, 5T33Z0 said:

 

Thanks for the screenshot. What does "ID do DIspositvo" mean in english. I don't have that in my list.

It means ID of the device.  Dispositivo=device

Edited by HenryV
Link to comment
Share on other sites

Guest 5T33Z0

@ham4ever I ran into the same issue after after booting High Sierra on my stystem and then trying to get back into Big Sur. It seems like it breaks the seal or something in Big Sur or something. NVRAM Reset didn't fix it.

 

My workaround was:

adding boot-arg: -no_compat_check to config.plist

reboot into Big Sur

re-install Big Sur on top of the existing install.

remove the -no_compat_check boot-arg

reboot.

 

Maybe there's another way to repair the seal (bless?) but that's how I did it.

 

Edited by 5T33Z0
Link to comment
Share on other sites

3 hours ago, 5T33Z0 said:

@ham4ever I ran into the same issue after after booting High Sierra on my stystem and then trying to get back into Big Sur. It seems like it breaks the seal or something in Big Sur or something. NVRAM Reset didn't fix it.

 

My workaround was:

adding boot-arg: -no_compat_check to config.plist

reboot into Big Sur

re-install Big Sur on top of the existing install.

remove the -no_compat_check boot-arg

reboot.

 

Maybe there's another way to repair the seal (bless?) but that's how I did it.

 

 

if it is the same thing that happens in my hacks with high sierra and big sur the situation is this:
high sierra in HFS started with Clover, at the first start it modifies the SystemVersion present in the big sur preboot; it is to be restored with a plist editor
Terminal:

Diskutil list

diskutil mount diskxsY

Locate

/ System / Volumes / Preboot

or

open / System / Volumes / Preboot

 

/ System / Library / CoreServices / SystemVersion.plist

Edited by iCanaro
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

Guest 5T33Z0
47 minutes ago, iCanaro said:

 

if it is the same thing that happens in my hacks with high sierra and big sur the situation is this:
high sierra in HFS started with Clover, at the first start it modifies the SystemVersion present in the big sur preboot; it is to be restored with a plist editor
Terminal:

Diskutil list

diskutil mount diskxsY

Locate

/ System / Volumes / Preboot

or

open / System / Volumes / Preboot

 

/ System / Library / CoreServices / SystemVersion.plist

 

Ahhh, okay, this totally makes sense. Thanks for the explanation.

Link to comment
Share on other sites

1 hour ago, 5T33Z0 said:

 

Ahhh, okay, this totally makes sense. Thanks for the explanation.

Thanks for this solution which fixed my Clover's booting problem of Big Sur (11.x to be shown as 10.13.6) for a long time !

Link to comment
Share on other sites

12 minutes ago, jsl2000 said:

Thanks for this solution which fixed my Clover's booting problem of Big Sur (11.x to be shown as 10.13.6) for a long time !

 

months ago I broke the boxes a lot to Jief and Slice for this inexplicable bug, then it was understood that the cause was high sierra which changed the systemversion in the big sur preboot, coupled with the Clover boot method (OC started regularly as it did not is based on what the systemversion reports), when everything was understood and since I was then the only one with this singular problem, nothing was done.
NB: if you restore the systemversion, then in the subsequent starts of high sierra, it does not change anything, it happens again at the next big sur update

  • Like 3
Link to comment
Share on other sites

Guest 5T33Z0

@iCanaro It's definitely a High Sierra and not a bootloader issue. Because it happened to me too with OpenCore.

Edited by 5T33Z0
Link to comment
Share on other sites

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