You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With our refactor of DeviceProperty pathing generation, we omit to check if the acpi-path entry is present on the device we plan to inject onto. Because of this, our injected properties fail to apply and can result in lose of display output on certain machines (namely those with PCIe bridges on the GPU itself, Vega and Navi series being most prominent)
To resolve, we need to implement the following:
Verification of acpi-path, if omitted fall back on boot-args
Add ACPI table building to allow device property injection
ACPI table generation will be exclusive to Mac Pros as they have a known set pathing for their PCIe devices, other devices could be added in the future
The text was updated successfully, but these errors were encountered:
With our refactor of DeviceProperty pathing generation, we omit to check if the
acpi-path
entry is present on the device we plan to inject onto. Because of this, our injected properties fail to apply and can result in lose of display output on certain machines (namely those with PCIe bridges on the GPU itself, Vega and Navi series being most prominent)To resolve, we need to implement the following:
acpi-path
, if omitted fall back on boot-argsACPI table generation will be exclusive to Mac Pros as they have a known set pathing for their PCIe devices, other devices could be added in the future
The text was updated successfully, but these errors were encountered: