From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202449] New: vrr_capable not showing up in xrandr with eDP display.
Date: Tue, 29 Jan 2019 15:16:05 +0000 [thread overview]
Message-ID: <bug-202449-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=202449
Bug ID: 202449
Summary: vrr_capable not showing up in xrandr with eDP display.
Product: Drivers
Version: 2.5
Kernel Version: 4.20
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: haxk612@gmail.com
Regression: No
Created attachment 280847
--> https://bugzilla.kernel.org/attachment.cgi?id=280847&action=edit
xrandr --props
xrandr doesnt show vrr_capable option for eDP display but the option is there
with HDMI.
While its true that my internal display on laptop doesnt report that it
supports FreeSync but i know that it works with Freesync because when i edit
EDID in windows freesync works.
But im sure the issue isnt that my display doesnt report Freesync since when i
connect a monitor that i know isnt freesync capable to HDMI the option is still
there.
I attach output of "xranr --props" of my laptop.
Laptop has Ryzen 5 2500U with VEGA8 (Raven Ridge)
and dedicated RX560X.
VEGA 8 is connected directly to internal display (eDP) and RX560X is connected
to HDMI port.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-29 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 15:16 bugzilla-daemon [this message]
2019-01-29 15:31 ` [Bug 202449] vrr_capable not showing up in xrandr with eDP display bugzilla-daemon
2019-01-29 15:33 ` bugzilla-daemon
2019-01-29 15:45 ` bugzilla-daemon
2019-01-29 15:46 ` bugzilla-daemon
2019-01-30 13:59 ` bugzilla-daemon
2019-01-30 19:59 ` bugzilla-daemon
2019-01-30 20:12 ` bugzilla-daemon
2019-01-30 20:17 ` bugzilla-daemon
2019-01-31 18:53 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-202449-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox