Just thought I'd come back and update the thread that took the gamble and successfully updated to an even newer F9a Bios on my z590 Vision D and all is running smoothly on Ventura 13.4. For any future on-lookers it is safe to use. Not sure of any felt differences and pretty sure thunderbolt hot...
Hey all!
Curious if anyone has tried the new bios, version F8, that was released recently (Apr 26, 23)? I'm nervous to be the guinea pig :)
Gigabyte's website says "Improve Thunderbolt compatibility issues". So I'm crossing fingers and hoping that maybe this might improve some hot-swap issues...
Wow... to my amazement... after I was nearly ready to give up on this my hero "DreamWhite" on GitHub has come to the rescue and done exactly what I was looking to do here (literally pushed this code like 6hrs ago / I can't believe I stumbled across this)...
Perhaps this was a long shot! So this will be my last attempt to bump this thread... , but any .kext wrangling experts or code wizards feeling generous/sympethetic?! :)
Seeking some Hackintosh expert eyes/input on this one...
I run a Corsair CommanderPro Fan Controller Bridge– which macOS registers the vendor/product IDs and believes there is a UPS (uninterrupted power supply) plugged in and running off the battery when it detects the Corsair Commander Pro...
@jimbojingle one more thought came to mind. If you check out the github link @aclee shared you'll notice some notes shared about how this kext works and how it is implemented. Note the bottom "boot arguments" section with a few things you may try– you can enable verbose logging to see if that...
@jimbojingle I really wish I could be more help, but I'm just not sure. If what you have mirrors that snippet above then I'm stumped. It's working great on my end– I just updated my EFI. Rebooted– message gone. You added this to your `config.plist`? And you also added that `CommanderProFix.kext`...
Nothing fancy on this end– I added the .kext to the kext folder, opened my opencore config with ProperTree and did the "Shift + R" key combo which searches your opencore folder for any changes or added kexts, etc and automatigically adds them. Then booted and voila!
That said– here is a...
@aclee so many thank yous!
I installed your CommanderProFix.kext and it worked like a charm– no more annoying UPS power-saving non-sense. I can actually update OSX now, etc.
For others faced with this annoying an unexpected outcome of the Commander Pro – this kext works great.
Tested on Big...
Gotchya. @huntie21 How about sleep– does your sleep work/function properly? "Commander Pro" isn't affecting/interfeering there?
I just got my z590 i9 combo working in a corsair 680x which also uses a "Commander Pro" and am stuck with this dreaded UPS hurdle as well. I'm going to try a few...
Wow this is really annoying– I just stumbled across this myself with a new build... will be watching closely to see if anyone can figure out a work around here.
Sorry not sure I can't help there. I've never attempted the iGPU only path so any ideas I have would only be guessing, but I know it is very much doable and have seen other's success stories who aren't using a dGPU. It may be as simple as taking this setup and then changing your BIOS config in...
@arnaud2 I know this thread is a bit old now, but I did want to update on my end that I've got my build running smoothly now! Since we had similar set ups I thought this might be helpful: https://github.com/McCallumDillon/Hackintosh-Z390-Aorus-Pro
@arnaud2 any luck?
I too with the holiday haven't revisited this too much, but I was/am having a very bizarre issue now. With my EFI shared in that github link above I was able to install BigSur and update to 11.1 just fine– even got FileVault working. That said! This was all done on an SSD–...
@arnaud2 I have a similar build and going to follow along here...
Question: How did you do your SSDTs (ACPI/*.aml) files? When I followed the Dortania guide attempting with the pre-build ones I wasn't having any luck. After I switched to my own built using SSDTTime I started to see some...
I just noticed v5.1 r5125 was released yesterday. Git commit notes "Resolved legacy boot (6,7) file." Not sure what that means exactly, but I'm curious if this new release would solve the issues we were having with r5124.
Anyone following or a part of this thread brave enough to give it a try...
I'm in the exact same boat. attempting to update to 5124 goofed my boot. I can boot to Windows, but when I select the OSX partition it freezes immediately. I'll be watching this thread to see if you have any success. I'm going to attempt to install the previous version of Clover and report back...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.