All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111482] Sapphire Pulse RX 5700 XT power consumption
Date: Sat, 28 Sep 2019 10:14:08 +0000	[thread overview]
Message-ID: <bug-111482-502-CGkTwMe6d1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111482-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111482

--- Comment #22 from Leon <leon@tutanota.de> ---
(In reply to Andrew Sheldon from comment #20)
> (In reply to Leon from comment #19)
> > By the way, since I have a x470 mb, it cannot be related to PCI express 4.0.
> > It's also not related to dual displays, since I'm running just one.
> 
> Not necessarily. Some x370 and x470 motherboards erroneously reported PCIE
> 4.0 support in earlier BIOS (AGESA) updates. You might want to update to the
> latest available bios, if that is the case with your board.
> 
> Although, since you are using 5.3.1 I don't think the bug has been fixed in
> mainline 5.3 yet. You might want to use amd-staging-drm-next, or wait for
> 4.1-rc1.

Already did even before installing the 5700 XT. Running bios P3.60 with AM4
1.0.0.3 ABB AGESA.

Thanks for the kernel suggestion though!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1874 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-09-28 10:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25  8:43 [Bug 111482] Sapphire Pulse RX 5700 XT power consumption bugzilla-daemon
2019-08-26 23:07 ` bugzilla-daemon
2019-08-27  4:47 ` bugzilla-daemon
2019-08-27  7:25 ` bugzilla-daemon
2019-08-27 22:20 ` bugzilla-daemon
2019-08-28 14:25 ` bugzilla-daemon
2019-08-29 16:27 ` bugzilla-daemon
2019-09-03  9:35 ` bugzilla-daemon
2019-09-03 16:54 ` bugzilla-daemon
2019-09-04  1:16 ` bugzilla-daemon
2019-09-04 22:16 ` bugzilla-daemon
2019-09-05  1:01 ` bugzilla-daemon
2019-09-05  2:20 ` bugzilla-daemon
2019-09-05 14:21 ` bugzilla-daemon
2019-09-05 14:24 ` bugzilla-daemon
2019-09-05 14:53 ` bugzilla-daemon
2019-09-05 18:16 ` bugzilla-daemon
2019-09-08  2:02 ` bugzilla-daemon
2019-09-10 19:27 ` bugzilla-daemon
2019-09-27 10:49 ` bugzilla-daemon
2019-09-27 10:51 ` bugzilla-daemon
2019-09-28  7:38 ` bugzilla-daemon
2019-09-28  9:05 ` bugzilla-daemon
2019-09-28 10:14 ` bugzilla-daemon [this message]
2019-10-05 11:55 ` bugzilla-daemon
2019-10-05 12:20 ` bugzilla-daemon
2019-10-06  4:45 ` bugzilla-daemon
2019-10-07  8:31 ` bugzilla-daemon
2019-10-07 10:05 ` bugzilla-daemon
2019-10-26  8:33 ` bugzilla-daemon
2019-11-01  3:01 ` bugzilla-daemon
2019-11-02  4:22 ` bugzilla-daemon
2019-11-03 16:55 ` bugzilla-daemon
2019-11-04 16:31 ` bugzilla-daemon
2019-11-04 16:42 ` bugzilla-daemon
2019-11-04 23:48 ` bugzilla-daemon
2019-11-05  0:37 ` bugzilla-daemon
2019-11-05  0:43 ` bugzilla-daemon
2019-11-05  0:50 ` bugzilla-daemon
2019-11-05  5:57 ` bugzilla-daemon
2019-11-08  1:35 ` bugzilla-daemon
2019-11-08  1:36 ` bugzilla-daemon
2019-11-08  6:36 ` bugzilla-daemon
2019-11-19  9:50 ` 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-111482-502-CGkTwMe6d1@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.