This prevents the issue that there is no screen flickering anymore. The only minor difference is that the GUI of Plymouth with the splash screen and input field is not available. It is a regular input text field.
Besides this, I am going to redo the first bisect. I believe I have stopped one iteration too early. I will post the results when done.
That behavior difference is probably because Plymouth is racing with GPU driver load in some of your tests.
I am not worried about this. The Plymouth issue only showed when using the amdgpu.dcdebug boot parameter.
The retry of the first bisect including the last iteration has not changed the result of the first bisect.
arthur@pb450:~/.cache/yay/linux-mainline/src/linux-mainline$ git bisect bad
2f14c0c8cae8e9e3b603a3f91909baba66540027 is the first bad commit
commit 2f14c0c8cae8e9e3b603a3f91909baba66540027
Author: Mario Limonciello <mario.limonciello@amd.com>
Date: Tue Mar 5 14:34:24 2024 -0600
drm/amd/display: Use freesync when `DRM_EDID_FEATURE_CONTINUOUS_FREQ` found
The monitor shipped with the Framework 16 supports VRR [1], but it's not
being advertised.
This is because the detailed timing block doesn't contain
`EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max
frequencies. This check however is superfluous for this case because
update_display_info() calls drm_get_monitor_range() to get these ranges
already.
So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then
turn on freesync without extra checks.
v2: squash in fix from Harry
Closes: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/
Closes: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/
Closes: http://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338
Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
An issue report has been created at AMD Gitlab.
For people who have been following this community thread, but are not following the continuation on AMD’s Gitlab thread:
The first approach is to disable the new AMD GPU power saving feature called “Freesync Panel Refresh”. This is prevent non working FW16 laptops of users who will upgrade their OS to kernel 6.9.
Once the regression is prevented, AMD and Framework can take their time together to get this new feature working for the Framework 16 laptops.
To prevent that this issue falls in between the cracks, this regression has been added to the Linux kernel regression tracker.
The AMD panel replay functionality has been disabled for now, giving time for AMD to find the root cause and fix it properly. The ‘disable patch’ has landed in mainline.
Today I have built and booted Linux 6.9-rc7.
There is no regression. The system seems to function normally.