From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!
Date: Sun, 25 Nov 2018 12:10:48 +0000 [thread overview]
Message-ID: <bug-201763-2300-Ddo4tir5Gm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201763-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201763
fin4478@hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fin4478@hotmail.com
--- Comment #3 from fin4478@hotmail.com ---
Before reporting, test with latest drivers. That means with these:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.21-wip
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
Use the Oipaf ppa bionic version with Debian testing. Google how to use ppas in
Debian. Disable vsync in Xfce Compositor settings. Disable Thunar thumbnails
too.
You can use my kernel config as base, add more drivers for your hardware with
make xconfig.
--
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 prev parent reply other threads:[~2018-11-25 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 6:41 [Bug 201763] New: amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0! bugzilla-daemon
2018-11-22 6:46 ` [Bug 201763] " bugzilla-daemon
2018-11-22 15:52 ` bugzilla-daemon
2018-11-25 12:10 ` bugzilla-daemon [this message]
2018-11-25 12:11 ` bugzilla-daemon
2019-02-28 22:31 ` bugzilla-daemon
2019-02-28 22:33 ` bugzilla-daemon
2019-03-01 16:14 ` bugzilla-daemon
2019-03-30 2:22 ` bugzilla-daemon
2019-03-30 2:23 ` bugzilla-daemon
2019-03-30 2:24 ` bugzilla-daemon
2020-11-10 21:46 ` bugzilla-daemon
2020-11-19 10:43 ` bugzilla-daemon
2020-11-19 14:23 ` 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-201763-2300-Ddo4tir5Gm@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).