From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 192921] New: Low frame rates and unrecognized monitor after kernel upgrade
Date: Fri, 20 Jan 2017 02:39:55 +0000 [thread overview]
Message-ID: <bug-192921-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=192921
Bug ID: 192921
Summary: Low frame rates and unrecognized monitor after kernel
upgrade
Product: Drivers
Version: 2.5
Kernel Version: 4.10.0
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: stevengruspier@gmail.com
Regression: No
Before upgrading my kernel (4.8.16), there was always a problem where at boot
the refresh rate was too high, so my screen would flicker. I could only set the
refresh rate to 120Hz max without any flickering. This was due to a bug or
feature that had yet to be added to the kernel (was fixed in the DAL patched
unofficial kernel).
After upgrading the kernel to 4.9.3 I noticed that on boot there was no
flickering at 144Hz anymore, but when trying to play games and videos there are
issues with low frame rates. I then went to the display menu to check settings
and noticed that the monitor now says "unknown". I installed 4.10.0 rc 3 from
the rawhide repo with the same results.
Distro: Fedora 25
GPU: ASUS Strix AMD R9 380 4GB
Monitor: MG278Q (2560 x 1440 @ 144Hz)
--
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:[~2017-01-20 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 2:39 bugzilla-daemon [this message]
2017-01-20 2:40 ` [Bug 192921] Low frame rates and unrecognized monitor after kernel upgrade bugzilla-daemon
2017-01-20 2:50 ` bugzilla-daemon
2017-01-20 2:51 ` bugzilla-daemon
2017-01-20 2:57 ` bugzilla-daemon
2017-01-20 3:00 ` bugzilla-daemon
2017-01-20 3:01 ` bugzilla-daemon
2017-01-20 3:19 ` bugzilla-daemon
2017-01-20 13:21 ` bugzilla-daemon
2017-01-20 16:24 ` bugzilla-daemon
2017-01-20 16:28 ` bugzilla-daemon
2017-01-20 17:03 ` 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-192921-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;
as well as URLs for NNTP newsgroup(s).