FWIW it's in drm-fixes now. https://cgit.freedesktop.org/drm/drm/commit/?id=2f14c0c8cae8e9e3b603a3f91909baba66540027
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > 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. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
