miliuco Posted June 7, 2022 Share Posted June 7, 2022 @MorenoAv @eSaF and me >> we are the champions 😀 Note that all are z390. 2 Link to comment Share on other sites More sharing options...
Anto65 Posted June 7, 2022 Share Posted June 7, 2022 I add myself to the list 😂 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 7, 2022 Share Posted June 7, 2022 @antuneddu Maybe our mobos, perfectly working so far, need more help than newer for Ventura. Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 7, 2022 Share Posted June 7, 2022 8 minutes ago, miliuco said: @MorenoAv @eSaF and me >> we are the champions 😀 Note that all are z390. H310 here. Seems like 300-series mobos are out of luck for now. 1 Link to comment Share on other sites More sharing options...
JorgeMax Posted June 7, 2022 Share Posted June 7, 2022 Look, I'm on this list too. B360 and stuck in this firmware business in the second stage of installation 1 Link to comment Share on other sites More sharing options...
Anto65 Posted June 7, 2022 Share Posted June 7, 2022 8 minutes ago, miliuco said: @antuneddu Maybe our mobos, perfectly working so far, need more help than newer for Ventura. Sure ... But what? I have tried everything and more 🤷♂️ 1 Link to comment Share on other sites More sharing options...
miliuco Posted June 7, 2022 Share Posted June 7, 2022 1 minute ago, antuneddu said: Sure ... But what? I have tried everything and more 🤷♂️ Me too. Even disabling SSDT-PMC thinking that it’s related to AvoidRuntimeDefrag that has to do with NVRAM. 1 Link to comment Share on other sites More sharing options...
Anto65 Posted June 7, 2022 Share Posted June 7, 2022 “a required firmware update could not be installed” 😵 1 3 Link to comment Share on other sites More sharing options...
PoMpIs Posted June 7, 2022 Share Posted June 7, 2022 (edited) 7 minutes ago, miliuco said: Me too. Even disabling SSDT-PMC thinking that it’s related to AvoidRuntimeDefrag that has to do with NVRAM. And if you put a SMBIOS of MacPro 7.1 or iMacPro??? By trying you don't lose anything 🤷♂️ PS: I'm trying Apple TV and Amazon Prime video and they don't work for me in Ventura 🤔 Edited June 7, 2022 by PoMpIs 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 7, 2022 Share Posted June 7, 2022 @PoMpIs Already tried, different SMBIOS. Tu máquina potente acepta mejor al nuevo. 3 Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 8, 2022 Share Posted June 8, 2022 So after a bit of back and forward, i discovered that the issue is with the implementation of avoidRuntimeDefrag in open core, in fact all the systems that doesn't need it can boot macos ventura, while the others gets stuck near pci configuration end, so we have to wait for the acida thera team to figure it out i suppose, and so the only system that can boot it for now are macs (having a firmware that supports apfs booting) and more recent hackintishes. I hope they can figure this issue out soon, because for all i have seen even socket 1366 systems can boot the new os (as my mac pro 5,1 was able to do) 4 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 8, 2022 Share Posted June 8, 2022 22 minutes ago, ITzTravelInTime said: So after a bit of back and forward, i discovered that the issue is with the implementation of avoidRuntimeDefrag in open core, in fact all the systems that doesn't need it can boot macos ventura, while the others gets stuck near pci configuration end, so we have to wait for the acida thera team to figure it out i suppose, and so the only system that can boot it for now are macs (having a firmware that supports apfs booting) and more recent hackintishes. I hope they can figure this issue out soon, because for all i have seen even socket 1366 systems can boot the new os (as my mac pro 5,1 was able to do) And all 300 series chipsets with 8th or 9th gen CPUs are affected, right? Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 8, 2022 Share Posted June 8, 2022 Just now, PropoFlexWX4 said: And all 300 series chipsets with 8th or 9th gen CPUs are affected, right? Honestly it depends, some people have been also able to boot with 8 and 9 gen it seems, so as long as you system can boot into monterey without avoidruntimedefrag activated you should be able to boot the new os too. 1 Link to comment Share on other sites More sharing options...
Ellybz Posted June 8, 2022 Share Posted June 8, 2022 (edited) X299 - With the latest OpenCore 082, the quirk suggested and the minimum kexts needed to boot, I'm getting a constant boot loop at the line: IOPlatformHaltRestartAction -> AppleSMC I tried changing SMBIOS and also with -igfxvesa Nada. No me quierrreeeee 😭 Any ideas? @MorenoAv You can also add me to your list 🤣 . Never give up. Never surrender ! Edited June 8, 2022 by Ellybz 2 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 8, 2022 Share Posted June 8, 2022 2 minutes ago, Ellybz said: X299 - With the latest OpenCore 082, the quirk suggested and the minimum kexts needed to boot, I getting a constant boot loop at the line: IOPlatformHaltRestartAction -> AppleSMC Any ideas? @MorenoAv You can also add me to your list 🤣 . Never give up. Never surrender ! That is precisely the error I'm seeing. gIOScreenLockState. Seems like some sort of issue with graphics. Link to comment Share on other sites More sharing options...
Skyfallkavu Posted June 8, 2022 Share Posted June 8, 2022 2 minutes ago, PropoFlexWX4 said: That is precisely the error I'm seeing. gIOScreenLockState. Seems like some sort of issue with graphics. Exactly mine on Z370. Good job getting a picture of it, that was frustrating me. Link to comment Share on other sites More sharing options...
matgeo Posted June 8, 2022 Share Posted June 8, 2022 2 hours ago, antuneddu said: “a required firmware update could not be installed” 😵 Try -disablegfxfirmware. That was the solution for me (Intel UHD 620). 2 1 Link to comment Share on other sites More sharing options...
Anto65 Posted June 8, 2022 Share Posted June 8, 2022 (edited) Thx i Will try Edited June 8, 2022 by antuneddu Link to comment Share on other sites More sharing options...
Dragster27 Posted June 8, 2022 Share Posted June 8, 2022 28 minutes ago, Skyfallkavu said: Exactly mine on Z370. Good job getting a picture of it, that was frustrating me. Same error here on Dell XPS 7590 i7 9th gen... Link to comment Share on other sites More sharing options...
Skyfallkavu Posted June 8, 2022 Share Posted June 8, 2022 34 minutes ago, Dragster27 said: Same error here on Dell XPS 7590 i7 9th gen... It has to be something with memory space inaccuracy if we all get it at the same point. If I leave this off, I get NVMe errors booting into Monterey. I was trying to mess with other quirks with no success. Does anyone have their KASLR slide values calculated? I provide mine but have it set to 0 1 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 8, 2022 Share Posted June 8, 2022 14 minutes ago, Skyfallkavu said: It has to be something with memory space inaccuracy if we all get it at the same point. If I leave this off, I get NVMe errors booting into Monterey. I was trying to mess with other quirks with no success. Does anyone have their KASLR slide values calculated? I provide mine but have it set to 0 Leave what off? And if you can boot into Ventura, than its fine! Link to comment Share on other sites More sharing options...
Skyfallkavu Posted June 8, 2022 Share Posted June 8, 2022 17 minutes ago, PropoFlexWX4 said: Leave what off? And if you can boot into Ventura, than its fine! I meant the AvoidRuntimeDefrag quirk, and no, since it looks like 300 series boards typically need this quirk enabled to boot anything. We’re either stuck in the Ventura installer on GPU errors or unable to boot Monterey with it disabled. I myself get NVMe errors on Monterey, so it seems PCIE allocation is the culprit here. It’s something with how the kernel is allocating PCIE address space on our boards. Properly declared KASLR slides might be a solution? I only have 140 pages available. Link to comment Share on other sites More sharing options...
Middleman Posted June 8, 2022 Share Posted June 8, 2022 So I tried to boot the Ventura installer on my GA Z590I Vision D board with OC 0.8.2. using same settings used for Monterey 12.3. Nope, looks like a no go either. Link to comment Share on other sites More sharing options...
iGPU Posted June 8, 2022 Share Posted June 8, 2022 Formatted an internal NVMe drive, and installed Ventura very easily on an ASUS Z690 Max Extreme with OC v082, latest updated kexts, after downloading file as described here. boot argument -lilubetaall was necessary as was Booter/Quirks/AvoidRuntimeDefrag being disabled. *** also, need to remember to re-set any MaxKernel to either blank or 22.99.99; otherwise those items won't be loaded in Ventura. *** One nice thing is that both I225V and Aquantia AQC113 are working as shown below in Ventura (using only Kernel/Quirks/ForceAquantiaEthernet): The built-in thunderbolt has drivers loaded but is not working (Spoiler): Spoiler Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted June 8, 2022 Share Posted June 8, 2022 5 hours ago, PoMpIs said: Does it let you set the automatic login? I don't know how to put it 🤦♂️ Doesn't work for me neither. I guess automatic-login is either not implemented yet or there's an issue with the GUI. Unless you can enable it via terminal we have to wait for the next update Link to comment Share on other sites More sharing options...
Recommended Posts