FS#50025 - [linux] Radeon DPM not fixed upstream
Attached to Project:
Arch Linux
Opened by Amarildo (Amarildo) - Tuesday, 12 July 2016, 16:19 GMT
Last edited by Toolybird (Toolybird) - Saturday, 27 May 2023, 07:32 GMT
Opened by Amarildo (Amarildo) - Tuesday, 12 July 2016, 16:19 GMT
Last edited by Toolybird (Toolybird) - Saturday, 27 May 2023, 07:32 GMT
|
Details
Description:
Radeon Kernel developers took Pitcairn and several other GCN 1.0 cards (Southern Islands) off the DPM module list. This will cause the screen to flicker in certain resolutions, making it impossible to use such resolutions. It is possible to disable DPM for such cards, but this will cause a significant drop in performance. When the patch is reverted, the cards work fine. I already asked upstream to revert the commit more than 2 months ago [1], so it's clear they won't change it at all. I'm unable to edit the PKDBUILD's and compile my Kernels whenever there is an update, due to the lack of time, so I'm here asking if you're willing to consider making this patch official to the grsec Kernel. I updated the patch so that it works with newer versions of linux and linux-grsec [2]. There's also an example of a PKGBUILD with the new patch, it's really simple [3]. [1] https://bugzilla.kernel.org/show_bug.cgi?id=103271#c22 [2] https://raw.githubusercontent.com/amarildojr/AMDGPU-Radeon-DPM/master/dpm.patch [3] https://raw.githubusercontent.com/amarildojr/AMDGPU-Radeon-DPM/master/PKGBUILD Additional info: * package version(s) = any, from 3.16 onwards * config and/or log files etc = Kernel config is default from Arch. Hardware config: AMD FX 6300 (@ 4.4 GHz) R9 270X DualX OC Edition 16 GB DDR3 HyperX Fury 1866 MHz SyncMaster 796MB (monitor model) Steps to reproduce: Use Linux Kernel (linux; linux-grsec) without the patch above ([2]) and set monitor resolution to 1280x1024. Screen will flicker. Regards, Amarildo |
This task depends upon
Closed by Toolybird (Toolybird)
Saturday, 27 May 2023, 07:32 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please follow up with upstream.
Saturday, 27 May 2023, 07:32 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please follow up with upstream.
Comment by Amarildo (Amarildo) -
Tuesday, 12 July 2016, 16:21 GMT
Comment by
Daniel Micay (thestinger) -
Wednesday, 13 July 2016, 17:47 GMT
Comment by Amarildo (Amarildo) -
Thursday, 14 July 2016, 10:37 GMT
Comment by
Daniel Micay (thestinger) -
Thursday, 14 July 2016, 21:33 GMT
Comment by Amarildo (Amarildo) -
Friday, 15 July 2016, 05:24 GMT
Comment by Doug Newgard (Scimmia) -
Friday, 15 July 2016, 05:28 GMT
Comment by mattia (nTia89) - Sunday,
27 February 2022, 11:26 GMT
It was supposed to be assigned to the linux-grsec package. Sorry
for the mistake.
I'll incorporate any changes from core/linux into
community/linux-grsec, but I don't want to deviate from it for
issues that are present in vanilla kernels too.
I understand. Shall I open a new task, or can you assign Tobias
and Thomas to this one?
Should probably just copy-paste this into a new one, since this is
for [community].
No problem. Thank you for your support :)
Better yet, I'll just move it.
I cannot reproduce the issue. Is it still valid for you?