Bug 112071 - 5700 XT: ppfeaturemask doesn't work with iGPU multi-monitor
Summary: 5700 XT: ppfeaturemask doesn't work with iGPU multi-monitor
Status: RESOLVED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: not set minor
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-20 10:46 UTC by zamundaaalp
Modified: 2019-10-20 22:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
/var/log/Xorg.0.log (90.56 KB, text/plain)
2019-10-20 18:54 UTC, zamundaaalp 		no flags Details
dmesg output (93.56 KB, text/plain)
2019-10-20 18:55 UTC, zamundaaalp 		no flags Details
View All

Description zamundaaalp 2019-10-20 10:46:00 UTC 
If the BIOS option "iGPU multi-monitor" is enabled (so I can use the internal GPU ports, namely DVI) amdgpu.ppfeaturemask doesn't do anything anymore.
"cat /sys/module/amdgpu/parameters/ppfeaturemask" gives the mask I set (either fffd7fff or simply 0xffffffff) but the files like /sys/class/drm/card0/device/pp_od_clk_voltage don't actually get created. They do if I disable iGPU multi-monitor.

Wether I'm on kernel 5.3.6 or 5.4rc2 doesn't matter, wether I'm on Mesa 19.2 or 19.3 (git) doesn't matter as well.
Comment 1 Alex Deucher 2019-10-20 18:28:51 UTC 
Please attach your dmesg output and xorg log (if using X).
Comment 2 zamundaaalp 2019-10-20 18:54:46 UTC 
Created attachment 145780 [details]
/var/log/Xorg.0.log
Comment 3 zamundaaalp 2019-10-20 18:55:32 UTC 
Created attachment 145781 [details]
dmesg output
Comment 4 zamundaaalp 2019-10-20 18:57:08 UTC 
Thanks for taking a look :)
Comment 5 zamundaaalp 2019-10-20 22:29:19 UTC 
I am really sorry. I completely overlooked that my external GPU might simply be card1 and the internal one card0. Because that's the case. The files are all there in /sys/class/drm/card1/device/ like expected.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.