MacWill Posted June 19, 2021 Share Posted June 19, 2021 3 hours ago, 5T33Z0 said: Thanks for the screenshot. What does "ID do DIspositvo" mean in english. I don't have that in my list. "Device ID" 😊 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 19, 2021 Share Posted June 19, 2021 (edited) 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 June 19, 2021 by 5T33Z0 Link to comment Share on other sites More sharing options...
bisdak4920 Posted June 19, 2021 Share Posted June 19, 2021 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 More sharing options...
hiphopboy Posted June 20, 2021 Share Posted June 20, 2021 (edited) 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 June 20, 2021 by hiphopboy Link to comment Share on other sites More sharing options...
jsl2000 Posted June 20, 2021 Share Posted June 20, 2021 (edited) 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 June 20, 2021 by jsl2000 1 Link to comment Share on other sites More sharing options...
yapan4 Posted June 20, 2021 Share Posted June 20, 2021 Hi, @iCanaro Where can download HackCheck please? Link to comment Share on other sites More sharing options...
iCanaro Posted June 20, 2021 Share Posted June 20, 2021 37 minutes ago, yapan4 said: Hi, @iCanaro Where can download HackCheck please? here https://www.macos86.it/files/file/95-hack-check/ to download you need to introduce yourself and write a post, so a total of 2 posts https://www.macos86.it/forum/19-introduce-yourself/ 3 2 Link to comment Share on other sites More sharing options...
D-an-W Posted June 20, 2021 Share Posted June 20, 2021 (edited) 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 June 20, 2021 by D-an-W Link to comment Share on other sites More sharing options...
pepitillo Posted June 20, 2021 Share Posted June 20, 2021 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 More sharing options...
pepitillo Posted June 20, 2021 Share Posted June 20, 2021 Yes, little strange, but in fact my system is buggy without this kext (artifacts on the screen or semi-transparent apple logo at boot). You can take a look at this old post from my system : There's an issue for CpuTscSync on acidanthera bug tracker : https://github.com/acidanthera/bugtracker/issues/1676 Link to comment Share on other sites More sharing options...
jsl2000 Posted June 21, 2021 Share Posted June 21, 2021 (edited) 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 June 21, 2021 by jsl2000 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 21, 2021 Share Posted June 21, 2021 I just stumbled across this HD4000 Patcher for Monterey by @chris1111: https://github.com/chris1111/Patch-HD4000-Monterey Great. I am going to try this. I am wondering: could I just install macOS Monterey on a System which is supprted, patch the HD4000 support into it, put the EFI for my Ivy Bridge Laptop in, put the disk in the laptop and boot? Link to comment Share on other sites More sharing options...
surenmunoo Posted June 21, 2021 Share Posted June 21, 2021 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. 2 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 21, 2021 Share Posted June 21, 2021 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 More sharing options...
surenmunoo Posted June 21, 2021 Share Posted June 21, 2021 2 minutes ago, SavageAUS said: What’s changed recently? New kext? New program? Sent from my iPhone using Tapatalk Added an AMD AX7870 Graphics card only and changed symbols to iMacPro1.1 to work with that card Link to comment Share on other sites More sharing options...
miliuco Posted June 21, 2021 Share Posted June 21, 2021 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 More sharing options...
ham4ever Posted June 21, 2021 Share Posted June 21, 2021 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". Link to comment Share on other sites More sharing options...
HenryV Posted June 21, 2021 Share Posted June 21, 2021 (edited) 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 June 21, 2021 by HenryV Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 22, 2021 Share Posted June 22, 2021 (edited) @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 June 22, 2021 by 5T33Z0 Link to comment Share on other sites More sharing options...
iCanaro Posted June 22, 2021 Share Posted June 22, 2021 (edited) 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 June 22, 2021 by iCanaro 3 1 Link to comment Share on other sites More sharing options...
apfelnico Posted June 22, 2021 Share Posted June 22, 2021 I'm happy. The first beta is running: 6 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 22, 2021 Share Posted June 22, 2021 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 More sharing options...
jsl2000 Posted June 22, 2021 Share Posted June 22, 2021 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 More sharing options...
iCanaro Posted June 22, 2021 Share Posted June 22, 2021 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 3 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 22, 2021 Share Posted June 22, 2021 (edited) @iCanaro It's definitely a High Sierra and not a bootloader issue. Because it happened to me too with OpenCore. Edited June 22, 2021 by 5T33Z0 Link to comment Share on other sites More sharing options...
Recommended Posts