# 60hz vs 165hz Display Power Draw - 1W

**URL:** <https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289>\
**Category:** Framework Laptop 16\
**Tags:** framework-laptop-16-amd-7040\
**Created:** [March 2, 2024, 4:08pm UTC](https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289 "2024-03-02T16:08:41Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jerrod\_Frost](https://avatars.discourse-cdn.com/v4/letter/j/838e76/32.png) [@Jerrod\_Frost](https://community.frame.work/u/Jerrod_Frost)\
**Post date:** [March 10, 2024, 3:31am UTC](https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289/21 "2024-03-10T03:31:47Z")

</div>

If you’re using Linux, the reason for this is the 2 different EDID profiles. For 1.4 the VRR info isn’t there but for 2.0 the EDID VRR block is there. Since they do not match, it’s choosing the “default” of N/A. A kernel patch was just recently submitted to fix this.

---

<div class="post-metadata">

**Author:** ![Nickolas\_Grigoriadis](https://avatars.discourse-cdn.com/v4/letter/n/858c86/32.png) [@Nickolas\_Grigoriadis](https://community.frame.work/u/Nickolas_Grigoriadis)\
**Post date:** [March 11, 2024, 6:18am UTC](https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289/22 "2024-03-11T06:18:17Z")

</div>

Nice!

Do you have any idea on what Kernel version it will be a part of? 6.9? or will it likely miss that?

---

<div class="post-metadata">

**Author:** ![Jerrod\_Frost](https://avatars.discourse-cdn.com/v4/letter/j/838e76/32.png) [@Jerrod\_Frost](https://community.frame.work/u/Jerrod_Frost)\
**Post date:** [March 11, 2024, 1:11pm UTC](https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289/23 "2024-03-11T13:11:01Z")

</div>

> [@\[ANNOUNCEMENT\] Adaptive Sync / Freesync / VRR not working](http://community.frame.work/t/announcement-adaptive-sync-freesync-vrr-not-working/46674):
>
> With GNOME 46 picking up experimental VRR support and KDE Plasma supporting VRR, I wanted to share with people that a bug was found for Framework 16 where VRR isn’t advertised as capable. You can see from drm\_info |grep vrr that even though the Framework 16 panel should be capable, it doesn’t show that way from amdgpu. This stems from a mismatch in the EDID where it doesn’t consistently advertise VRR support in both blocks. The DisplayID 2.0 block advertises it, but the EDID 1.4 block doesn’t…

[Previous page](https://community.frame.work/t/60hz-vs-165hz-display-power-draw-1w/46289.md?page=1)