dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108521] RX 580 as eGPU amdgpu: gpu post error!
Date: Fri, 26 Oct 2018 05:30:51 +0000	[thread overview]
Message-ID: <bug-108521-502-VDahn3HjtG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108521-502@http.bugs.freedesktop.org/>


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

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

--- Comment #25 from Robert Strube <rstrube@gmail.com> ---
acpi=off is the only parameter necessary to get the eGPU up and running.
Setting this parameter allows the Thunderbolt PCI bridge to correctly have it's
resources allocated. This incidentally also completely disables the Vega M
(even with Vanilla kernel that does not have the device IDs commented out).

I'm wondering where I can report the Thunderbolt Controller / Bridge bug? 
Perhaps you fine folks can point me in the right direction?

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

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

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

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

  parent reply	other threads:[~2018-10-26  5:30 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  5:14 [Bug 108521] RX 580 as eGPU amdgpu: gpu post error! bugzilla-daemon
2018-10-23 14:25 ` bugzilla-daemon
2018-10-23 16:00 ` bugzilla-daemon
2018-10-23 16:00 ` bugzilla-daemon
2018-10-23 20:08 ` bugzilla-daemon
2018-10-24  6:24 ` bugzilla-daemon
2018-10-24 20:44 ` bugzilla-daemon
2018-10-25  1:13 ` bugzilla-daemon
2018-10-25  1:15 ` bugzilla-daemon
2018-10-25  1:34 ` bugzilla-daemon
2018-10-25  2:12 ` bugzilla-daemon
2018-10-25  2:16 ` bugzilla-daemon
2018-10-25  3:06 ` bugzilla-daemon
2018-10-25  3:21 ` bugzilla-daemon
2018-10-25  7:05 ` bugzilla-daemon
2018-10-25 14:56 ` bugzilla-daemon
2018-10-25 15:01 ` bugzilla-daemon
2018-10-25 15:02 ` bugzilla-daemon
2018-10-25 15:07 ` bugzilla-daemon
2018-10-25 15:11 ` bugzilla-daemon
2018-10-25 15:12 ` bugzilla-daemon
2018-10-25 15:12 ` bugzilla-daemon
2018-10-25 15:13 ` bugzilla-daemon
2018-10-25 20:05 ` bugzilla-daemon
2018-10-26  4:42 ` bugzilla-daemon
2018-10-26  5:11 ` bugzilla-daemon
2018-10-26  5:14 ` bugzilla-daemon
2018-10-26  5:15 ` bugzilla-daemon
2018-10-26  5:30 ` bugzilla-daemon [this message]
2018-10-26 10:35 ` bugzilla-daemon
2018-10-26 16:49 ` bugzilla-daemon
2018-11-29 22:54 ` bugzilla-daemon
2018-11-29 23:47 ` bugzilla-daemon
2018-11-30  1:26 ` bugzilla-daemon
2018-11-30  1:35 ` bugzilla-daemon
2018-11-30  1:43 ` bugzilla-daemon
2018-11-30  1:51 ` bugzilla-daemon
2019-01-09 21:05 ` bugzilla-daemon
2019-01-09 21:08 ` bugzilla-daemon
2019-01-09 21:09 ` bugzilla-daemon
2019-01-09 21:10 ` bugzilla-daemon
2019-01-09 21:13 ` bugzilla-daemon
2019-01-09 22:26 ` bugzilla-daemon
2019-03-29 10:01 ` bugzilla-daemon
2019-03-29 10:06 ` bugzilla-daemon
2019-03-29 13:00 ` bugzilla-daemon
2019-03-29 13:10 ` bugzilla-daemon
2019-03-29 13:56 ` bugzilla-daemon
2019-03-29 16:31 ` bugzilla-daemon
2019-03-29 17:43 ` bugzilla-daemon
2019-03-30 11:42 ` bugzilla-daemon
2019-03-30 11:44 ` bugzilla-daemon
2019-03-30 11:51 ` bugzilla-daemon
2019-04-01 16:14 ` bugzilla-daemon
2019-04-19 19:46 ` bugzilla-daemon
2019-04-25  0:18 ` bugzilla-daemon
2019-04-25  0:18 ` bugzilla-daemon
2019-04-25  0:19 ` bugzilla-daemon
2019-11-02  9:13 ` bugzilla-daemon
2019-11-02  9:15 ` bugzilla-daemon
2019-11-02  9:37 ` bugzilla-daemon
2019-11-02  9:39 ` [Bug 108521] RX 580 / Vega56 " bugzilla-daemon
2019-11-20  7: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-108521-502-VDahn3HjtG@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 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).