Gigabyte x570 AQRUS Xtreme Attempt(10.13 High Sierra) OpenCore 6.9 - Stuck

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
Coolbean,

To boot Big Sur you'll likely need SSDT-CPUR & SSDT-EC-USBX-DESKTOP.aml in ACPI, OC 0.6.9, Lilu, Whatevergreen, AppleALC, VirtualSMC, USBPorts.kext and SMBIOS iMacPro1,1. No need for boot-args other than alcid for your soundcard.

For the Aquantia you could try this. Your PCIRoot settings may differ so add it in Devices using the + button:

View attachment 3251

Btw that device-id is this: 4b00000001000000010000003f0000000100000002010c00d041080a0000000001010600041c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001

And the last bit for model says Aqtion.
I was able to get the right PciRoot tree with into my config.plist
Hacktool_PCI_10Gig_Aguantia_x570_xtreme.png

After i updated the PCI Root path all the changes show up in IORegisterExplorer to Aquantia,
---but did not work with device ID you gave and when I use it the Device Name would not show up in Hacktool so I just left it out now seeing if that works but still no luck
IORegisterExplorer_10gig_Aquantia.png

Config_plist_PCI_Root_Aquantia.png

If you have another address to try for device ID, I can try it.
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
I was able to get the right PciRoot tree with into my config.plist
View attachment 3365

After i updated the PCI Root path all the changes show up in IORegisterExplorer to Aquantia,
---but did not work with device ID you gave and when I use it the Device Name would not show up in Hacktool so I just left it out now seeing if that works but still no luck
View attachment 3366

View attachment 3367

If you have another address to try for device ID, I can try it.
I see. Did you not try using the longer device-id I gave in the post?
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
oh, I thought you got a working version of High Sierra on X570 with 1080 ti? I'm not looking to run Big Sur since I need the Nvidia web drivers for my 1080 ti. do you have a working EFI for High Sierra? I'll take whatever you got as a starting point. thanks!
Yes I am using 10.13.4 right now
-- only catch is I copied my partition from my old hackintosh with 10.13.4 and Nvidia drivers already installed.
-- once you get that on to an SSD/HD in you PC you can use AudioGods EFI (Link here) for your board and just replace "agdpmod=pikera" from boot-args to "nvda_drv_vrl=1"
-- boot=args are separated by space " "
-- Use GenSMBIOS (attached) to generate MLB, SystemSerialNumber and SystemUUID (link to guide here)
and it will boot right up for you. And since AudioGod was able to get you board fully mapped and working everything for the most part should work on your board.
Then you have to send AudioGod all the thanks and praise once you boot in to OSX on your new PC in his thread i linked! :)

Boot-args_Nvidia.png
 

Attachments

  • GenSMBIOS.zip
    438.8 KB · Views: 1

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
I see. Did you not try using the longer device-id I gave in the post?
yes, I used it in Device ID but it did not work and caused Device name to go blank in Hacktool so I tried to boot without Device ID in config.plist, but still did not work
However without the Device ID in config.plist the Device Name was no longer blank and showed correctly. So left it like this for now.
I can try any other Device ID you think might work.
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
yes, I used it in Device ID but it did not work and caused Device name to go blank in Hacktool so I tried to boot without Device ID in config.plist, but still did not work
However without the Device ID in config.plist the Device Name was no longer blank and showed correctly. So left it like this for now.
I can try any other Device ID you think might work.
Okay how about this. Run Opencore Configurator, but use the version that fits your current version of OC (as later versions do not mix well with earlier versions of OC config plists). Go to the Device Properties, delete your current Aquantia settings list on the far right and then using the List PCI Devices selector, select Add Device and try and add the Aquantia card property back in. It might populate it with the correct info.
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
yes, I used it in Device ID but it did not work and caused Device name to go blank in Hacktool so I tried to boot without Device ID in config.plist, but still did not work
However without the Device ID in config.plist the Device Name was no longer blank and showed correctly. So left it like this for now.
I can try any other Device ID you think might work.
Almost forgot the most obvious solution...check your Windows Device Manager settings and see what comes up for the hardware device id. Whatever that comes up you need to put it in reverse byte order in the EFI as device-id.
 

AudioGod

Guru
Guru
Joined
Nov 7, 2020
Messages
1,386
@Middleman Some boards just don’t like device properties injecting and there’s not a lot we can do about it as the OC crew won’t address it unless some bright spark does all the work and fixes it for them. They don’t do AMD generally. :(
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
@Middleman Some boards just don’t like device properties injecting and there’s not a lot we can do about it as the OC crew won’t address it unless some bright spark does all the work and fixes it for them. They don’t do AMD generally. :(
Yes I realise that but in my experience it's fine 90% of the time (even on an AMD). Windows device-ids are mostly compatible with macOS ones.
Opencore Configurator I have to admit is a very handy tool. It's been able to identify a number of devices I've added in the past so it shouldn't be a problem.
But in anycase, my guess it's mostly because his device-id is missing.
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
Okay how about this. Run Opencore Configurator, but use the version that fits your current version of OC (as later versions do not mix well with earlier versions of OC config plists). Go to the Device Properties, delete your current Aquantia settings list on the far right and then using the List PCI Devices selector, select Add Device and try and add the Aquantia card property back in. It might populate it with the correct info.
No luck with this method, although when Opencore Configurator added PCI device it did not add a Device_Id
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
Almost forgot the most obvious solution...check your Windows Device Manager settings and see what comes up for the hardware device id. Whatever that comes up you need to put it in reverse byte order in the EFI as device-id.
There are a lot of properties in windows 10 Device Property list for the Aquantia 10Gig Ethernet.
The closest I can find is "Reported device Ids hash" below. (does this mean I should try device_id = "EEB4F344" ?)
Only_device_ID_10gig_Aquantia_Win10.png

Below is the full Property list,
let me know if you see one that should have the correct device_Id and i can post value to see if it makes sense to try
Full_Property_List_10gig_Aquantia_Win10.png

Also looking through the list and their values,
below property looks like it may be ID we are looking for but the Property name is strange so not sure what to make of it.
Possible_Device_ID_10gig_Aquantia_Win10.png
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
There are a lot of properties in windows 10 Device Property list for the Aquantia 10Gig Ethernet.
The closest I can find is "Reported device Ids hash" below. (does this mean I should try device_id = "EEB4F344" ?)
View attachment 3373

Below is the full Property list,
let me know if you see one that should have the correct device_Id and i can post value to see if it makes sense to try
View attachment 3374

Also looking through the list and their values,
below property looks like it may be ID we are looking for but the Property name is strange so not sure what to make of it.
View attachment 3375
You just need Hardware IDs. It will tell you the device and vendor ids. You will need the device-id, and place it in reverse-byte-order.
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
You just need Hardware IDs. It will tell you the device and vendor ids. You will need the device-id, and place it in reverse-byte-order.
Hardware ID's below:
Hardware_IDs.png
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
I just realised - rechecking the posts, the line with the long value I posted in my initial posts was actually for key 'device-properties' not 'device-id'.
That may be where you went wrong.

So you'll need to redo the lines like this:
key: device-properties
value: 4b00000001000000010000003f0000000100000002010c00d041080a0000000001010600041c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001
type: STRING
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
I just realised - rechecking the posts, the line with the long value I posted in my initial posts was actually for key 'device-properties' not 'device-id'.
That may be where you went wrong.

So you'll need to redo the lines like this:
key: device-properties
value: 4b00000001000000010000003f0000000100000002010c00d041080a0000000001010600041c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001
type: STRING
didn't work:
config_plist_device-properties.png

IORegisterExplorer_Device-Properties.png
Maybe try to boot yours in windows and look for what device property this address is under and let me know so I can pull it from windows and swap it. so it would be correct one for my board.
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
Also tried it as data instead of string, just in case it need to be, still no luck
config_plist_device-properties_Data.png

IORegisterExplorer_Device-Properties_Data.png
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
Also tried it as data instead of string, just in case it need to be, still no luck
View attachment 3394

View attachment 3393
Okay. With the device-properties in place using STRING type, try to add another line in like this:

key: device-id
value: 07D16A1D
type: DATA

but instead, once filled in move this line to just after AAPL,slot-name, and move the model name line to the bottom of the list. Load order of the keys is important.
 

CoolBean

Member
AMD OS X Member
Joined
May 11, 2021
Messages
47
Okay. With the device-properties in place using STRING type, try to add another line in like this:

key: device-id
value: 07D16A1D
type: DATA

but instead, once filled in move this line to just after AAPL,slot-name, and move the model name line to the bottom of the list. Load order of the keys is important.
did not work and hacktool still looses Device Name when inserting devie-id
config_plist_device-properties_Data2.png

IORegisterExplorer_Device-Properties_Data2.png

Hacktool_PCI_10Gig_Aguantia_x570_xtreme2.png
 

Middleman

Active member
AMD OS X Member
Joined
Jan 29, 2021
Messages
723
Top Bottom
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.