ileikcaek Posted July 27, 2020 Share Posted July 27, 2020 For those having issues getting into recovery (unsupported error), setting UEFI > APFS > JumpstartHotPlug to true worked for me. Recovery Images booted fine after. - I still haven't figured out my updating or installation on bare metal issue. trying the update in CLI gives errors about Mac OS not being booted in snapshot mode and that it must be to be able to update. The big 12.88GB Update begins installing but goes to restart too soon and stage 2 fails, this is the same experience as trying to fresh install from my installation USB. The only method to get Big Sur updated each time seems to be just installing it fresh to the SSD in VMware each time and this is definitely not ideal going forwards. 3 Link to comment Share on other sites More sharing options...
markl18 Posted July 27, 2020 Share Posted July 27, 2020 (edited) 10 minutes ago, Cyberdevs said: I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot. Here is my latest OC folder and the updated kext. You might need to remove the SSDTs and reconfigure the kexts. Haswell Last update.zip if you clean installed the DP3 why did you needed to install the update? I guess you installed the DP2 and then updated to DP3 and now it ended up in the current situation, am I correct? exactly did that picture I included do anything for anyone curious Edited July 27, 2020 by markl18 Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 27, 2020 Share Posted July 27, 2020 1 minute ago, markl18 said: exactly So what I suggested earlier is to download the DP3 full installer and do a clean install with that. 1 Link to comment Share on other sites More sharing options...
markl18 Posted July 27, 2020 Share Posted July 27, 2020 3 minutes ago, Cyberdevs said: So what I suggested earlier is to download the DP3 full installer and do a clean install with that. where do I get dp3 full installer and what does this error about update date Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 27, 2020 Share Posted July 27, 2020 @markl18 Use @crazybirdy's script to download the full installer: I'm not sure what that error means. 1 1 Link to comment Share on other sites More sharing options...
valeryimm Posted July 27, 2020 Share Posted July 27, 2020 15 hours ago, mnfesq said: It appears that VoodooInput.kext is located as a plugin in both VoodooI2C.kext and VoodooPS2Controller.kext. Perhaps it is the presence of 2 of the same kexts that is causing your KP. Yes, you're right. I removed on of the kexts. Still no luck with SATA drives. Link to comment Share on other sites More sharing options...
markl18 Posted July 27, 2020 Share Posted July 27, 2020 1 minute ago, valeryimm said: Yes, you're right. I removed on of the kexts. Still no luck with SATA drives. as far as those kexts goes they have to be in certain order like gpis first than service and then i2c Link to comment Share on other sites More sharing options...
valeryimm Posted July 27, 2020 Share Posted July 27, 2020 Just now, markl18 said: as far as those kexts goes they have to be in certain order like gpis first than service and then i2c OK, gonna try Link to comment Share on other sites More sharing options...
swede420 Posted July 27, 2020 Share Posted July 27, 2020 (edited) ga-z170m-d3h i7-6700 rx570 success installing Big Sur without issues. Edited July 27, 2020 by swede420 Link to comment Share on other sites More sharing options...
valeryimm Posted July 27, 2020 Share Posted July 27, 2020 18 minutes ago, valeryimm said: OK, gonna try Yes, it works! Now Disk Utility can see my SATA Drive. Thank you very much Link to comment Share on other sites More sharing options...
markl18 Posted July 27, 2020 Share Posted July 27, 2020 1 minute ago, valeryimm said: Yes, it works! Now Disk Utility can see my SATA Drive. Thank you very much my pleasure if I only new what was the question Link to comment Share on other sites More sharing options...
eSaF Posted July 27, 2020 Share Posted July 27, 2020 @Cyberdevs - Yep you was spot on - Updating OC cured booting without the need for boot-args vsmcgen=1. Funny thing is I thought I had the latest from here https://github.com/williambj1 as I normally do being lazy but I just compiled my own like you advised, now booting without that boot-arg - Thanks again. 1 2 Link to comment Share on other sites More sharing options...
Stefanalmare Posted July 27, 2020 Share Posted July 27, 2020 2 minutes ago, eSaF said: @Cyberdevs - Yep you was spot on - Updating OC cured booting without the need for boot-args vsmcgen=1. Funny thing is I thought I had the latest from here https://github.com/williambj1 as I normally do being lazy but I just compiled my own like you advised, now booting without that boot-arg - Thanks again. OCBuilder.app! The easiest way. OC and latest kexts. 1 click. 3 1 Link to comment Share on other sites More sharing options...
Alex HQuest Posted July 27, 2020 Share Posted July 27, 2020 (edited) 3 hours ago, eSaF said: @Alex HQuest - I'd be interesting to see what your temps are at idle because quite frankly seems a little hot but if the rig was under load, it's understandable. I was installing Xcode during that screen capture. I'm still doing a lot of data xfers, so not truly "idle" from a CPU standpoint, but yeah, this one shows regular temps as they usually are like. Good thing is, even while under full load, package and/or core temps are hardly over 65C - perks of a custom loop water cooling Spoiler 2 hours ago, Cyberdevs said: I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot. As I mentioned, I did fetched the latest and greatest from GitHub, but more likely the build tools I'm using decided to cache something, then. Or some code was "repurposed" from Xcode 12 when I recompiled on Xcode 11 (Lilu fails on Xcode 12, but OpenCorePkg compiles just fine). Will retry after cleaning my local caches to act as a "pristine" build. Thanks for the hint though. Edited July 27, 2020 by Alex HQuest Double posting 1 Link to comment Share on other sites More sharing options...
Ludox Posted July 27, 2020 Share Posted July 27, 2020 Big Sur B3 su Asus Z87 Plus 3 Link to comment Share on other sites More sharing options...
MorenoAv Posted July 27, 2020 Share Posted July 27, 2020 Hi Guys good night, Tonight I have good news, I don't know why, but I have macOS BS in boot, instead of PreBoot... and I have boot disk in system preferences... the only thing that I did was exchange theall my kexts with fresh compiled kexts and all is perfect. The only thing that annoys me is the fact that at boot ClearNvram, and Open Shell don't remain hidden although I have HideAuxiliary=Yes, how do I solve this? Thanks 3 Link to comment Share on other sites More sharing options...
iCanaro Posted July 28, 2020 Share Posted July 28, 2020 49 minutes ago, MorenoAv said: The only thing that annoys me is the fact that at boot ClearNvram, and Open Shell don't remain hidden although I have HideAuxiliary=Yes, how do I solve this? in the tools are set as auxiliary clean nvram and open shell? Link to comment Share on other sites More sharing options...
markl18 Posted July 28, 2020 Share Posted July 28, 2020 hi if anybody has a tpl0 device can anybody get this compiled SSDT-TPL0.dsl Link to comment Share on other sites More sharing options...
eSaF Posted July 28, 2020 Share Posted July 28, 2020 (edited) Spoiler @MorenoAv - Yes Big Sur will appear in the Startup Disk section if you have another OS X disk on the system as well but if you remove it leaving just Windows and BS, it will no longer be in there - Well that is how it is on my system. Edited July 28, 2020 by eSaF 1 Link to comment Share on other sites More sharing options...
Gigamaxx Posted July 28, 2020 Share Posted July 28, 2020 9 hours ago, JahStories said: @Gigamaxx @arsradu Any news about that phantom gpu? I noticed it cause iStatPro shows the absent r9 card as under full memory load xD No but I created a patch with Hackintool for Kabylake graphics and it was in the patch as well. Link to comment Share on other sites More sharing options...
Matgen84 Posted July 28, 2020 Share Posted July 28, 2020 12 hours ago, Cyberdevs said: @Matgen84 I disabled the OpenCanopy and now I can boot into the Big Sur's recovery lol @Cyberdevs I don't use Opencanopy and I can't boot into Big Sur's Recovery. What ScanPolicy do you use ? Link to comment Share on other sites More sharing options...
SavageAUS Posted July 28, 2020 Share Posted July 28, 2020 [mention]eSaF [/mention] I’ve updated OC and kexts today (ocbuilder app) 28/07/2020 and mine still says Preboot. I did not check startup disk yet though but will once I bath the monsters.....I mean kids Yep still Preboot and still no big sur disk in startup. Sent from my iPhone using Tapatalk 3 Link to comment Share on other sites More sharing options...
MorenoAv Posted July 28, 2020 Share Posted July 28, 2020 6 hours ago, iCanaro said: in the tools are set as auxiliary clean nvram and open shell? That was that, after change that to Auxiliary=Yes, solved it... Thanks @iCanaro ... 1 Link to comment Share on other sites More sharing options...
jsl2000 Posted July 28, 2020 Share Posted July 28, 2020 (edited) At last Clover bootloader works at Big Sur beta3 in my FX-6300 hackintosh. Wake up from S3 sleep working too. By OpenCore 0.6.0 it always got CMOS Reset issue. Major bugs in AMD CPU hackintoshs to be fixed: 1. Only Firefox Developer Edition and Google Chrome fully working, Safari and Firefox not fully compatible yet ! Edited July 28, 2020 by jsl2000 1 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 28, 2020 Share Posted July 28, 2020 38 minutes ago, jsl2000 said: At last Clover bootloader working at Big Sur beta3 in my FX-6300 hackintosh without issues. @jsl2000 You're lucky. The latest Clover commit don't work on my Z390 Aorus Master (i7 9700K): I can't boot Big Sur Beta 3. Details in Clover discussion topic. 1 Link to comment Share on other sites More sharing options...
Recommended Posts