- Joined
- Mar 6, 2013
- Messages
- 266
- Motherboard
- Gigabyte X299X Designare 10G
- CPU
- i9-10980XE
- Graphics
- AMD 6900XT
- Mobile Phone
Hi @Ellybz - I was wondering whether you might have a moment to help me understand a little more about using DeviceProperties, as you explained back in July:
I am still working on SSDTs for the Designare and I have started to use DeviceProperties instead of SSDT _DSM sections. I am following your method - look in Hackintool to get device path, and then specify the properties using DeviceProperties. I am copying the properties out of the SSDTs that dolgarrenan provided.
This seems to work well, at least in the few I've tested.
But I would like to understand this a bit better, and in particular to understand whether there any situations where I can't use DeviceProperties, and an SSDT must be used?
To put it another way: if I converted every _DSM section in my SSDTs to DeviceProperties in config.plist, would I run into any problems?
You said "if only a matter of cosmetic issue", which suggests that not every _DSM could convert to DeviceProperties?
And the OpenCore manual says:
"For all kernel drivers, which may inspect the IODeviceTree plane without probing (e.g. Lilu and its plugins such as WhateverGreen) it is particularly important to ensure device presence in the ACPI tables. Failing to do so may result in all kinds of erratic behaviour caused by ignoring the injected device properties as they were not constructed at the first stage."
Which also suggests the same. But I don't yet know how I can know which properties are OK to specify in DeviceProperties, and which must be in an SSDT?
The reason that I like the idea of DeviceProperties is that it only applies to macOS, and it allows the user to see everything in config.plist, rather than having to check between config.plist and SSDTs to see what's being set up.
I have had a look around for an example EFI that uses DeviceProperties in the way you described, but so far I have not found any. I found one example EFI from you (in the X299 BigSur thread), and also looked at lolflatsix's EFIs in the same thread, but neither had any DeviceProperties configured. dolgarrenan's EFI uses DeviceProperties to configure a couple of Thunderbolt devices, but the vast majority are configured via SSDT.
Thanks in advance for any advice.
If it is only a matter of cosmetic issue, I suggest you to use device properties in OpenCore vs SSDTs ( old school ).
Very simple and effective. You'll need Hackintool: PCIe section. Look for your device, right click to copy the device path and report the elements inside OC /DeviceProperties. If you want to add some vendor ID or other fields, you'll find them with IOReg. Check the exemples below and you should be all
I am still working on SSDTs for the Designare and I have started to use DeviceProperties instead of SSDT _DSM sections. I am following your method - look in Hackintool to get device path, and then specify the properties using DeviceProperties. I am copying the properties out of the SSDTs that dolgarrenan provided.
This seems to work well, at least in the few I've tested.
But I would like to understand this a bit better, and in particular to understand whether there any situations where I can't use DeviceProperties, and an SSDT must be used?
To put it another way: if I converted every _DSM section in my SSDTs to DeviceProperties in config.plist, would I run into any problems?
You said "if only a matter of cosmetic issue", which suggests that not every _DSM could convert to DeviceProperties?
And the OpenCore manual says:
"For all kernel drivers, which may inspect the IODeviceTree plane without probing (e.g. Lilu and its plugins such as WhateverGreen) it is particularly important to ensure device presence in the ACPI tables. Failing to do so may result in all kinds of erratic behaviour caused by ignoring the injected device properties as they were not constructed at the first stage."
Which also suggests the same. But I don't yet know how I can know which properties are OK to specify in DeviceProperties, and which must be in an SSDT?
The reason that I like the idea of DeviceProperties is that it only applies to macOS, and it allows the user to see everything in config.plist, rather than having to check between config.plist and SSDTs to see what's being set up.
I have had a look around for an example EFI that uses DeviceProperties in the way you described, but so far I have not found any. I found one example EFI from you (in the X299 BigSur thread), and also looked at lolflatsix's EFIs in the same thread, but neither had any DeviceProperties configured. dolgarrenan's EFI uses DeviceProperties to configure a couple of Thunderbolt devices, but the vast majority are configured via SSDT.
Thanks in advance for any advice.
Last edited: