- Joined
- Jul 13, 2011
- Messages
- 267
- Motherboard
- Z370 Aorus Gaming 7-OpenCore
- CPU
- i9-9900K
- Graphics
- RX 580
Would you like to try with a GA-Z170X-Gaming G1? I'm curios with the method your using (your script) and will like to try. I always use hot patches and a couple of SSDT's. I'll like to do it my self and then compare it with yours to see the differences and improvements. I never tried before because some people believe that after mayor changes in hardware or UEFI/BIOS settings is then necessary to extract again and create a new one. Let me know if you want to try with this board.. My board is a little different because it use to be Gigabyte's flagship motherboard during the days of Z170X.So lockdown has given me a lot of extra time in the evenings, as I'm not going down the pub right now.
I have made DSDT scripts for H270, Z270, and Z370 Gigabyte mobo's. (Z390 work in progress).
Although I will not be sharing the actual scripts themselves, if anyone wants to try out a full patch DSDT for those boards, just send me your vanilla DSDT (F4 Clover, etc), along with what the mobo is and what bios version.
(Just post them up here by reply).
I may also need an IOReg screenshot or file to find out the addresses of extra devices such as USB 3.1 or Atheros Killer Lan, etc, if you want them showing up in PCI.
Full Patch DSDT works in Clover and OpenCore and fixes way more than just using a bunch of SSDT files.
Boot times are also better.
Fixes include:
Darwin
RTC
DMAC
FWHD
HPET
ALS0
EC
USBX
Return Zero
Plugin Type
SATA
SLPB
MCHC
XHCI
Ethernet
SBUS
BUS1
PNLF
WAK
Mutex
PRW
HDMI
IGPU
PTS
PMC
IMEI
HDEF
Rename Devices
Fix Warnings
This is for Gigabyte GA-Z170Z-Gaming G1 UEFI F22i Using alcid:7 with and SDDT Also alcid:4, kind of works with only one output missing. alcid:7 also has the same missing output, is the only issue pending.Sure man. Just upload your vanilla.
An IOReg would also be good. Also the mobo name and bios version so others with the same board can grab it.
I only put in stuff that's built into the mobo, unless requested otherwise, so hardware changes are no problem.
Bios version updates need a new one, but apart from that....
Also, let me know what alcid number you're using?
Give this a try.This is for Gigabyte GA-Z170Z-Gaming G1 UEFI F22i Using alcid:7 with and SDDT Also alcid:4, kind of works with only one output missing. alcid:7 also has the same missing output, is the only issue pending.
Thanks for your DSDT. Here are the results:Give this a try.
One has your Samsung NVMe added.
The other one does not.
alcid = 7 is in the DSDT now.
Let me know what shows up in PCI from just the DSDT?
The only rename you'll need in OpenCore is SAT0 to SATA.
See attached.
The GA-Z170X-Gaming G1 is a really lovely looking board!
I really dig the fact that the audio op-amps are Dip-8, and on sockets.
You could probably put something even better sounding in there than the JRC's and the Burr Brown's.
Both of those are running in Class B.
The other USB 3.1 controller is a Gigabyte USB3.1 5.25" Front Bay Expansion Port (GC-USB3.1 BAY)I put the IGPU on a slot to make it show up in PCI.
If it goes in as built in, it won't show up. This is normal.
I can do that if you want? See attached.
Other Display Controller happens automatically in PCI when you have a graphics card as well. Also normal.
The audio device on that board is not fully supported in OSX, which is possibly why you get that weird looking second one. That is not in the DSDT!
The DSDT only has the one HDEF added and that's on alcid =7 (showing up right at the top in your PCI), and should work without the alcid being added anywhere else.
The HDMI controller would normally show up with something like an RX580 or 590, etc. It is in the DSDT.
I know the Vega 64 handles things a little differently.
The only thing you should put into Device Properties in Clover is the Vega 64.
Let the DSDT do the rest and then see what shows up.
Your IOReg also shows another USB 3.1 controller but I've only added the ASMedia one for now as it wasn't clear exactly what the other one was?
Definitely don't put SMBus in Clover Device Properties as your puter won't sleep if you do.
The general rule that seems to work best is:
Internal mobo stuff = DSDT.
External added cards, etc = Device Properties.
Let me know if everything is running correctly?