Contribute
Register

Z490 & Z590 - Will Z590 ever have macOS Support ?

CaseySJ said:
This shows some interesting, but puzzling results:

IOReg shows that Thunderbolt is attached to PC00 --> PCI-Bridge@1C,4 --> PCI-Bridge @0 in both cases. But PCI-Bridge@1C,4 is actually RP05 according to the DSDT screenshot (#2 below). So where did RP05 go? This is why macOS rejects our Thunderbolt SSDT -- because the SSDT is looking for RP05, which macOS does not find.
View attachment 514267


But the DSDT in both cases clearly shows that PC00 --> RP05 is defined at address 1C,4. So why is RP05 removed by macOS. It seems macOS might be having problems with other parts of the DSDT as well.
View attachment 514268


We can generate the boot log as follows:
Bash: 
log show --last boot | head -2000 > ~/Documents/bootlog.txt
Note that there are two hyphens in "--last".
Click to expand...
I wonder what BIOS version he's running, and whether Gigabyte has a bug in their ACPI implementation...
 
TripleYoThreat said:
Can anyone test the UHD 750 aka 11th gen iGPU, possibly faking the ID? If it works with graphics acceleration while spoofing, say, the uhd 630, I'll buy one tonight.
Click to expand...
Any news on the use of graphics in these newer CPUs, possibly through spoofing? Been away from the community for a while because of school and because my hackintosh has been running great, but I’m thinking maybe it’s time for an upgrade. I have a dedicated GPU but want to retain the use of the iGPU combined with the discrete one for video renders and stuff. (I forgot the actual name of the feature.) If it isn’t possible, I may go with an 10900K instead of an 11700K but I’d rather get the newer generation for a bit of future proofing and faster cores for games.
 
8Cores8Threads said:
Any news on the use of graphics in these newer CPUs, possibly through spoofing? Been away from the community for a while because of school and because my hackintosh has been running great, but I’m thinking maybe it’s time for an upgrade. I have a dedicated GPU but want to retain the use of the iGPU combined with the discrete one for video renders and stuff. (I forgot the actual name of the feature.) If it isn’t possible, I may go with an 10900K instead of an 11700K but I’d rather get the newer generation for a bit of future proofing and faster cores for games.
Click to expand...
I bought mine, will have everything on Wednesday. I aim to be using the iGPU only, so you will hear from me on this thread. I believe it should work faked as a UHD 630 - if anyone can confirm that will be great.
 
  • Like
Reactions: Api
CaseySJ said:
  • Because hot plug works on ASUS and MSI Z590 boards, we believe there’s a problem with Gigabyte’s firmware (BIOS). So it may be necessary to wait for an update.
Click to expand...
Can I get more info on the ASUS hot plugging? Or AML, or anything like that. Any link(s) would be great
energy23 said:
I'm on a 4790K processor. I've waited this long to upgrade. So what's another 6 months? And to be honest, the 4790K isn't really holding me back. It does everything I need. It is perfectly capable with gaming (its not a bottleneck with a RX 5700 XT). The only thing that sucks is HandBrake compression. As fast as 11th gen CPUs are, they come with many downsides (price, heat and power consumption). At worst, if alder lake CPUs don't work, I'll enjoy a nice price cut on an 11th gen CPU.

Fingers crossed, though.
Click to expand...
I'm on the same boat! I've got a Haswell, too. A 4690K. I honestly still find it snappy. I click an app, and it opens. It was 'sluggish' before I jumped to an NVMe. Now it feels equivalent to the 10th gen computers I've built. I guess it's a bit of fun and future proofing.
I like the way you think though, that you can go for Alder Lake or get a price cut on Rocket Lake.
I don't expect to regret this. I think worse comes to worst I can sell it off and make myself another.
 
8Cores8Threads said:
Any news on the use of graphics in these newer CPUs, possibly through spoofing? Been away from the community for a while because of school and because my hackintosh has been running great, but I’m thinking maybe it’s time for an upgrade. I have a dedicated GPU but want to retain the use of the iGPU combined with the discrete one for video renders and stuff. (I forgot the actual name of the feature.) If it isn’t possible, I may go with an 10900K instead of an 11700K but I’d rather get the newer generation for a bit of future proofing and faster cores for games.
Click to expand...
I have news about this, and it is bad. I was going to test this earlier but it seems others have beaten me to it. The reports from ****** on the latest Opencore build just released has confirmed that the Rocket Lake IGPU simply cannot run with macOS, and in fact it has to be disabled before it gets recognized by the system at bootup. So most are running/testing it with a dGPU instead.

On the other hand, 10th gen Comet Lake IGPU should to be able to run in macOS with a dGPU (from what I remember) and can also run HEVC and 4K decoding via IGPU if the device properties is setup properly.
 
Hoist
Other |  i5 7500 |  HD 530
Mirage (Acer Nitro 5)
Z370 Extreme4 |  i7 8700K |  GeForce GTX 1050 Ti
Rodimus Prime
Z490 Aorus Xtreme |  i5 10500 |  GeForce GTX 1060 WindForce OC 6GB
Arcee
Z490 Vision D |  i7 9700 |  Radeon Other
CaseySJ said:
This shows some interesting, but puzzling results:

IOReg shows that Thunderbolt is attached to PC00 --> PCI-Bridge@1C,4 --> PCI-Bridge @0 in both cases. But PCI-Bridge@1C,4 is actually RP05 according to the DSDT screenshot (#2 below). So where did RP05 go? This is why macOS rejects our Thunderbolt SSDT -- because the SSDT is looking for RP05, which macOS does not find.
View attachment 514267


But the DSDT in both cases clearly shows that PC00 --> RP05 is defined at address 1C,4. So why is RP05 removed by macOS. It seems macOS might be having problems with other parts of the DSDT as well.
View attachment 514268


We can generate the boot log as follows:
Bash: 
log show --last boot | head -2000 > ~/Documents/bootlog.txt
Note that there are two hyphens in "--last".
Click to expand...

@CaseySJ

I have tested SSDT-DTPG.aml + SSDT-TB3HP-JHL8540-GIGABYTE-Z590i-VISION-D.aml again.

Now the command for the log did work. Thanks a lot!

Best,
Chris
 

Attachments

  • Christopher’s iMac_DTPG+SSDT-TB3HP-JHL8540-GIGABYTE-Z590i-VISION-D.ioreg
    6.5 MB · Views: 55
  • System DSDT_DTPG+Christopher’s iMac_DTPG+SSDT-TB3HP-JHL8540-GIGABYTE-Z590i-VISION-D.dsl
    2.3 MB · Views: 60
  • bootlog.txt
    349.3 KB · Views: 91
SchmockLord19 said:
@CaseySJ

I have tested SSDT-DTPG.aml + SSDT-TB3HP-JHL8540-GIGABYTE-Z590i-VISION-D.aml again.

Now the command for the log did work. Thanks a lot!

Best,
Chris
Click to expand...
Something is very wrong with Gigabyte BIOS...

Code: 
kernel: (AppleACPIPlatform) SSDT 0x000000003A26B000 00063B (v02 CASEY  JHL8540  00000000 INTL 20180427)
kernel: (AppleACPIPlatform) SSDT 0x000000003A26B000 00063B (v02 CASEY  JHL8540  00000000 INTL 20180427)
kernel: (AppleACPIPlatform) 
kernel: (AppleACPIPlatform) 
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) SSDT 0x000000003A26A000 000096 (v02 OSY86  USBW     00001000 INTL 20161210)
kernel: (AppleACPIPlatform) SSDT 0x000000003A26A000 000096 (v02 OSY86  USBW     00001000 INTL 20161210)
kernel: (AppleACPIPlatform) 
kernel: (AppleACPIPlatform) 
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x45AEB
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x45AEB
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x45AF4
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x45AF4
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x464A8
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x464A8
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x464B1
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x464B1
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x46E65
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x46E65
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x46E6E
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x46E6E
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x47823
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x47823
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x4782C
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x4782C
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x481E1
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x481E1
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) ACPI Warning:
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x481EA
kernel: (AppleACPIPlatform) Unsupported module-level executable opcode 0x70 at table offset 0x481EA
kernel: (AppleACPIPlatform)  (20160930/psloop-285)
Lots of Unsupported module-level executable opcode messages. To be fair, we've seen these before, but what's strange is that macOS always tells us how many SSDTs/Tables were loaded from ACPI. In this case, there is no such message!

But on my Z490 Vision D we have this. Even though one table (SsdtEc) failed to load, the other 19 were loaded.

kernel: (AppleACPIPlatform) SSDT 0x00000000389D7000 0008A3 (v02 CASEY TBTTITAN 00000000 INTL 20181213)
kernel: (AppleACPIPlatform) SSDT 0x00000000389D7000 0008A3 (v02 CASEY TBTTITAN 00000000 INTL 20181213)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) SSDT 0x00000000389D6000 0003F3 (v02 hack _UIAC 00000000 INTL 20200110)
kernel: (AppleACPIPlatform) SSDT 0x00000000389D6000 0003F3 (v02 hack _UIAC 00000000 INTL 20200110)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) ACPI:
kernel: (AppleACPIPlatform) SSDT 0x00000000389D5000 000096 (v02 OSY86 USBW 00001000 INTL 20200110)
kernel: (AppleACPIPlatform) SSDT 0x00000000389D5000 000096 (v02 OSY86 USBW 00001000 INTL 20200110)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform)
kernel: (AppleACPIPlatform) ACPI Error:
kernel: (AppleACPIPlatform) ACPI Error:
kernel: (AppleACPIPlatform) [_STA]
kernel: (AppleACPIPlatform) [_STA]
kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS
kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS
kernel: (AppleACPIPlatform) (20160930/dswload-462)
kernel: (AppleACPIPlatform) (20160930/dswload-462)
kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
kernel: (AppleACPIPlatform) During name lookup/catalog
kernel: (AppleACPIPlatform) During name lookup/catalog
kernel: (AppleACPIPlatform) (20160930/psobject-310)
kernel: (AppleACPIPlatform) (20160930/psobject-310)
kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
kernel: (AppleACPIPlatform) (SSDT: SsdtEC) while loading table
kernel: (AppleACPIPlatform) (SSDT: SsdtEC) while loading table
kernel: (AppleACPIPlatform) (20160930/tbxfload-319)
kernel: (AppleACPIPlatform) (20160930/tbxfload-319)
kernel: (AppleACPIPlatform) ACPI Error:
kernel: (AppleACPIPlatform) ACPI Error:
kernel: (AppleACPIPlatform) 1 table load failures, 19 successful
kernel: (AppleACPIPlatform) 1 table load failures, 19 successful

So it seems we might need to wait for a BIOS update. Which version of BIOS are you running at the moment?
 
Yeah these early Z590 BIOS' are a mess. On MSI, before I returned it, it wouldn't hold an all-core overclock on Rocket Lake in Cinebench... it would down clock to 4.6 GHz. I've heard YouTubers complaining about the same thing.

At least the f5a BIOS on Gigabyte didn't have that issue if you disable TVB frequency clipping. But Thunderbolt hot plug is broken. I reached out to Gigabyte last week about missing hot plug and some other weird quirks in their BIOS. For instance, if you disable the Thunderbolt controller, save, restart, the Tthunderbolt settings disappear from the BIOS, and you can't access them until you clear CMOS or load Optimized Defaults.

They haven't gotten back to me yet. But it seems that Gigabyte has pulled F5a (at least from their worldwide site, not sure about other locales) from their website: https://www.gigabyte.com/Motherboard/Z590-VISION-D-rev-10/support#support-dl-bios
 
dehjomz said:
Yeah these early Z590 BIOS' are a mess. On MSI, before I returned it, it wouldn't hold an all-core overclock on Rocket Lake in Cinebench... it would down clock to 4.6 GHz. I've heard YouTubers complaining about the same thing.

At least the f5a BIOS on Gigabyte didn't have that issue if you disable TVB frequency clipping. But Thunderbolt hot plug is broken. I reached out to Gigabyte last week about missing hot plug and some other weird quirks in their BIOS. For instance, if you disable the Thunderbolt controller, save, restart, the Tthunderbolt settings disappear from the BIOS, and you can't access them until you clear CMOS or load Optimized Defaults.

They haven't gotten back to me yet. But it seems that Gigabyte has pulled F5a (at least from their worldwide site, not sure about other locales) from their website: https://www.gigabyte.com/Motherboard/Z590-VISION-D-rev-10/support#support-dl-bios
Click to expand...
They wrote back to me today to install the F5a.
I wrote back that nothing helped. Maybe that's why they took it off the site.
But it is still on the server.
https://download.gigabyte.com/FileList/BIOS/mb_bios_z590i-vision-d_f5a.zip
I described them the problem with Thunderbolt. A representative of Gigabyte will call me tomorrow.
 
Last edited:
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top