Jump to content
52 posts in this topic

Recommended Posts

  • 2 weeks later...

Anyone experiencing instability with this setup or similar? I have a Z390 Aorus Pro Wifi + 9900k + 5700xt and while my EFI isn't exactly the same as this one it's very similar. I'm getting kernel panics randomly. Turning the overclock and XMP off seems to help, but it's still unstable. Seems to be related to anything that tries to use the GPU.

Was rock solid on Monterey.

Edited by 8ender
1 hour ago, 8ender said:

Anyone experiencing instability with this setup or similar? I have a Z390 Aorus Pro Wifi + 9900k + 5700xt and while my EFI isn't exactly the same as this one it's very similar. I'm getting kernel panics randomly. Turning the overclock and XMP off seems to help, but it's still unstable. Seems to be related to anything that tries to use the GPU.

Was rock solid on Monterey.

It's quite solid to be honest. My specs are a little different though...

9 hours ago, aniuks27 said:

It's quite solid to be honest. My specs are a little different though...

 

I'm such an idiot. Apparently, weeks ago when I'd generated a new USBMap.kext I'd named the file USBPorts.kext and didn't update my config.plist. So I was just blowing right past the USB port limit. Monterey apparently didn't care that much about this, but Ventura cared a lot.

  • Like 1
  • Haha 1
  • 3 weeks later...

EFI folder with OpenCore 0.8.7

 

There are 4 config.plist files for different SMBIOS:

  • config-13-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
  • config-13-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
  • config-13-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
  • config-13-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS.

Remember to fill in your serial and ROM numbers (they are empty).

 

EFI-0.8.7.zip

  • Thanks 3
  • 2 weeks later...

@YangJsheng

 

Please add a signature to your user profile.

 

Does macOS detect you Vega 54 without SSDT? Does the GPU work fine on macOS? If both answers are yes, you don't need the SSDT.

 

But you can try it. SSDT-BRG0 or SSDT-VEGA. BRG0 is simpler si I would start with it. Don't pay attention to the VEGA name, it's not specific to Vega cards.

 

Both SSDTs need the correct IOReg path to the GPU:

  • gfxutil tool >> copy the line of the graphic card
  • Hackintool >> PCIe tab >> mouse over the Vega card >> copy IOReg tab.

paste here the IOREg path and I'll say to you how it must be written into the SSDT.

On 12/18/2022 at 8:35 PM, miliuco said:

EFI folder with OpenCore 0.8.7

 

There are 4 config.plist files for different SMBIOS:

  • config-13-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
  • config-13-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
  • config-13-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
  • config-13-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS.

Remember to fill in your serial and ROM numbers (they are empty).

 

EFI-0.8.7.zip 6.54 MB · 21 downloads

 

And please, remember to remove from this EFI :

 

CPUFriendDataProvider.kext (i think DataProvider for i7 9700k and absolutely not suitable for other CPU...)

 

and

 

UTBMap.kext (usb map, maybe not suitable for your system...)

 

 

and make your own........... 

  • Like 1

@D3v1L

 

Yes, UTBMap only for Z390 Aorus Elite and the kext for i7 9700 (and only for MacPro7,1 SMBIOS, iMacPro1,1 or iMac19,1 don't need it).

Edited by miliuco
  • Like 1
  • 2 weeks later...

Hey all! I'm experiencing a very strange behaviour from one of my devices and I do suspect that it is the device's drivers issue, but, I'm not sure though.

 

The touch functionality in my Wacom Intuos tablet (CTH-690) worked fine until recently that I noticed it doesn't. While the pen works fine and the touch is on, when I try to use my fingers on the tablet, it isn't working and the mouse isn't moving. I tried to completely remove the drivers and erase every trace of wacom, then install the drivers again, but to no avail. I tried connecting the device to another active USB hub that I have and it isn't working still, but, on the case's and motherboards USB ports, it works fine, even on a passive USB hub it also works.

 

Then I put the tablet back to the USB hub it was originally connected and put my computer to sleep, left the house, when I returned I woke the computer and I noticed that the touch functionality was working perfectly fine.

 

I reboot the computer, no touch... I put my computer to sleep, let it "power down", then woke it up and it was working! 

 

I have no clue for why the USB that the tablet is connected allows the touch functionality to work after waking up but not after powering up, could it be related to USBMap kext? I haven't touched it... very strange behaviour... 

 

Thanks!

@panosru

Good morning. I think that it's better to open a new thread, your issue seems unrelated to the theme of this thread. I'm sure you'll get more help in this way.

Edited by miliuco
  • Thanks 1

Oh cr@p! I messed up the topics! Sorry! 

Edited by panosru
  • Like 1

Hello, please see if this is the case?

 

ACPI(_SB_)#ACPI(PCI1)#ACPI(QR2A)#ACPI(H000)#PCI(0000)#PCI(0000)

 

\_SB_.PCI1.QR2A.H000              1002:687f

 

Edited by YangJsheng

@YangJsheng

 

You have looked at the GPU Device Manager on Windows, right? There is a property named Location paths, here you can see 2 keys, the ACPI path and the PCI path. For example, in my machine these are the 2 keys:

 

PCIROOT(0)#PCI(0100)#PCI(0000)#PCI(0000)#PCI(0000)

ACPI(_SB_)#ACPI(PCI0)#ACPI(PEG0)#ACPI(PEGP)#PCI(0000)#PCI(0000)

 

Spoiler

gpu-path-1.png.5316cfe272e7f1f893180b151d98a817.png

 

How to translate them to the strings used on macOS?
 

PCI path >> to be used in config.plist

  • I use it all.
  • The # separator becomes /
  • PCIROOT(0) becomes PciRoot(0x0)
  • PCI becomes Pci
  • The 4 numbers in each PCI block are converted to 2 pairs of hexadecimal numbers:
    PCI(0100) >> Pci(0x1,0x0), PCI(0000) >> Pci(0x0,0x0).
  • The result is:
    PciRoot(0x0)/Pci(0x1.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)

ACPI path >> to be used in SSDT

  • I use only ACPI blocks.
  • The # separator is converted to .
  • ACPI(_SB_) becomes _SB_
  • ACPI(PCI0) becomes PCI0
  • ACPI(PEG0) becomes PEG0
  • ACPI(PEGP) becomes PEGP
  • The result is: _SB_.PCI0.PEG0.PEGP
     
Spoiler

gpu-path-2.png.3129316a24e57fbb4334feaa54342ef0.png

 

Do the same checking your own values.

 

Edited by miliuco
  • Like 1
On 2023/1/24 at PM4点43分, YangJsheng said:

Thank you, thank you, thank you very much! Please help me to see the error.

 

  PCIROOT(80)#PCI(0200)#PCI(0000)#PCI(0000)#PCI(0000)

ACPI(_SB_)#ACPI(PCI1)#ACPI(QR2A)#ACPI(H000)#PCI(0000)#PCI(0000)

ACPI(_SB_)#ACPI(PCI1)#ACPI(QR2A)#ACPI(PXSX)#PCI(0000)#PCI(0000)

 

PCIROOT(80). how to modify?

PCIROOT(80)/PCI(0200)/PCI(0x0.0x0)/PCI(0x0.0x0)/PCI(0x0.0x0)

 

Where in config.plist?

 

On 2023/1/24 at PM4点43分, YangJsheng said:

ACPI(_SB_)#ACPI(PCI1)#ACPI(QR2A)#ACPI(H000)#PCI(0000)#PCI(0000)

The result is:_SB_.PCI1.QR2A.H000     

download ssdt?

1002:687f

 

xk

Edited by YangJsheng

@YangJsheng

 

The PCI path for config.plist can be

PciRoot(0x80)/Pci(0x2,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

 

The ACPI path for SSDT can be as you say

_SB_.PCI1.QR2A.H000

 

I attach the SSDT-VEGA adapted to your ACPI path, try it and comment if it works.

Remember to put SST-VEGA-aml into the ACPI folder and also add it to the config.plist.

SSDT-VEGA.dsl is text plain, so you can see the code.

 

SSDT-VEGA.aml SSDT-VEGA.dsl

Edited by miliuco
  • 1 month later...

EFI updated to OpenCore 0.9.0

There are 4 config.plist files for different SMBIOS:

  • config-13-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
  • config-13-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
  • config-13-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
  • config-13-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS.

Remember to fill in your serial and ROM numbers (they are empty).

 

Note: UTBMap.kext (next to USBToolBox.kext) is made for Gigabyte Z390 Aorus Elite. If you have a different motherboard, you must have your own USB ports map.

 

EFI-0.9.0.zip

Edited by miliuco
  • Like 3
  • 1 month later...

EFI updated to OpenCore 0.9.1

 

There are 4 config.plist files for different SMBIOS:

  • config-13-imac-amd.plist: iMac19,1 + dGPU AMD + iGPU enabled in BIOS
  • config-13-imac-intel.plist: iMac19,1 + iGPU enabled in BIOS as main card
  • config-13-imacpro.plist: iMacPro1,1 + dGPU AMD + iGPU disabled in BIOS
  • config-13-macpro.plist: MacPro7,1 + dGPU AMD + iGPU disabled in BIOS.

Remember to fill in your serial and ROM numbers (they are empty).

 

Note: UTBMap.kext (next to USBToolBox.kext) is made for Gigabyte Z390 Aorus Elite. If you have a different motherboard, you must have your own USB ports map.

EFI-0.9.1.zip

  • Like 4
  • Thanks 1
  • 1 month later...

Hi,

 

though my mobo ( Z390 Aorus Pro ) is not exactly the same I do hope I may find some answers in this thread.

My problem is that I cannot get my ethernet to work. 

 

The Aorus Pro uses the same i219V (7)  (Vendor 0x8086 / Device 0x15BC ) as the Aorus Elite and it's flawless working with Big Sur, but since Monterey I could never get it to work.

Though IORegistry Explorer and About This Mac show the port as connected and as en0 there's no way I can use it. 

Under Network Settings all looks good, I get an DHCP adress, green lights everywhere but  It is only constantly switching on and off. 😞

 

I have been searching the internet countless hours for a solution. So far without any success !

On one of these sites someone talked about wrong DisableIoMapper setting and VT-D enable/disable in Bios, I played around with various settings but no...  no joy !

 

Do you guys use the ethernet ? Is it working for you OOB ?

 

Thanks for any thoughts & recommendations.

i219V_1.png

i219V_2.png

×
×
  • Create New...