<div dir="ltr">Christian,<div><br></div><div>Thanks for the response. That got me in the right direction.</div><div>After trial and error I found the cause - Thunderbolt Boot Support option must be disabled in BIOS.</div><div>If I disable it I can boot to Ubuntu and looks like amdgpu inits okay. If I enable with no other changes, init fails.</div><div><br></div><div>The last issue was one of my own - forgetting to use DRI_PRIME and xrandr correctly.</div><div>Happy to say the Red Devil is working now in eGPU mode! <br>It's about a 20% perf loss over PCI-E slot and right in line with our previous tests.<br><br>As always thank you for your continued time and support.<br>We'll be happy to give a shout out to you guys for the help at article/video time.</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-size:12.8px"><span style="font-size:12.8px">Respectfully,</span><br></div><div style="font-size:12.8px"><div> </div><div>Daniel S. Moran (garwynn)</div><div>PC Hardware Editor - XDA-Developers</div><div>Phone: 1-559-316-0760/+81-90-5484-4155</div><div>Article Links: <a href="http://www.xda-developers.com/author/garwynn" style="color:rgb(17,85,204)" target="_blank">http://www.xda-developers.com/author/garwynn</a></div><div>E-mail: <a href="mailto:xdagarwynn@gmail.com" style="color:rgb(17,85,204)" target="_blank">xdagarwynn@gmail.com</a> | Twitter: @xdagarwynn</div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Apr 9, 2018 at 10:48 PM, Christian König <span dir="ltr"><<a href="mailto:christian.koenig@amd.com" target="_blank">christian.koenig@amd.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_-6687502937288805473moz-cite-prefix">Hi Daniel,<br>
      <br>
      your problem is that the system BIOS is buggy and doesn't assign
      resources to the card:<br>
      <blockquote type="cite">    Region 0: Memory at <ignored>
        (64-bit, prefetchable)<br>
            Region 2: Memory at <ignored> (64-bit, prefetchable)<br>
            Region 4: I/O ports at 9000 [size=256]<br>
            Region 5: Memory at <ignored> (32-bit,
        non-prefetchable)<br>
            Expansion ROM at <ignored> [disabled]</blockquote>
      <br>
      The kernel actually tries to assign resources to the bridges, but
      fails as well because the BIOS didn't reserved any during startup.<br>
      <blockquote type="cite">[    0.179743] pci 0000:12:00.0: can't
        claim BAR 14 [mem 0x01c00000-0xef0fffff]: no compatible bridge
        window<br>
        [    0.179745] pci 0000:12:00.0: [mem 0x01c00000-0xef0fffff]
        clipped to [mem 0xef000000-0xef0fffff]<br>
        [    0.179747] pci 0000:12:00.0:   bridge window [mem
        0xef000000-0xef0fffff]<br>
        [    0.179751] pci 0000:13:01.0: can't claim BAR 14 [mem
        0x01c00000-0x01ffffff]: no compatible bridge window<br>
        [    0.179753] pci 0000:14:00.0: can't claim BAR 14 [mem
        0x01c00000-0x01ffffff]: no compatible bridge window<br>
        [    0.179754] pci 0000:15:00.0: can't claim BAR 14 [mem
        0x01d00000-0x01dfffff]: no compatible bridge window<br>
        [    0.179756] pci 0000:08:04.0: can't claim BAR 13 [io 
        0xb000-0xcfff]: address conflict with PCI Bus 0000:12 [io 
        0x9000-0xbfff]<br>
        [    0.179782] pci 0000:14:00.0: can't claim BAR 0 [mem
        0x01c00000-0x01c03fff]: no compatible bridge window<br>
        [    0.179789] pci 0000:16:00.0: can't claim BAR 0 [mem
        0xd0000000-0xdfffffff 64bit pref]: no compatible bridge window<br>
        [    0.179791] pci 0000:16:00.0: can't claim BAR 2 [mem
        0xe0200000-0xe03fffff 64bit pref]: no compatible bridge window<br>
        [    0.179793] pci 0000:16:00.0: can't claim BAR 5 [mem
        0x01d00000-0x01d7ffff]: no compatible bridge window<br>
        [    0.179798] pci 0000:16:00.1: can't claim BAR 0 [mem
        0x01da0000-0x01da3fff]: no compatible bridge window</blockquote>
      <br>
      There isn't much you can do except for trying to update the BIOS
      and if that doesn't help replace your motherboard.<br>
      <br>
      Regards,<br>
      Christian.<br>
      <br>
      <br>
      Am 09.04.2018 um 15:33 schrieb Daniel Moran:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Christian,
        <div>Andrey,</div>
        <div><br>
          Thank you for the responses.</div>
        <div>Here's the requested dmesg/lspci. Also pulled journalctl
          just in case but didn't see anything that stands out.</div>
        <div><br>
          I'll take another look at the BIOS settings to see if anything
          else may explain the memory error.</div>
        <div>I've got 16GB in the system at the moment, can bump up to
          32 - also added a larger swap just in case that was the issue.
          (No change.)<br>
          <br>
          As always thank you for your continued time and support.</div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="m_-6687502937288805473gmail_signature" data-smartmail="gmail_signature">
            <div dir="ltr">
              <div style="font-size:12.8px"><span style="font-size:12.8px">Respectfully,</span><br>
              </div>
              <div style="font-size:12.8px">
                <div> </div>
                <div>Daniel S. Moran (garwynn)</div>
                <div>PC Hardware Editor - XDA-Developers</div>
                <div>Phone: 1-559-316-0760/+81-90-5484-<wbr>4155</div>
                <div>Article Links: <a href="http://www.xda-developers.com/author/garwynn" style="color:rgb(17,85,204)" target="_blank">http://www.xda-<wbr>developers.com/author/garwynn</a></div>
                <div>E-mail: <a href="mailto:xdagarwynn@gmail.com" style="color:rgb(17,85,204)" target="_blank">xdagarwynn@gmail.com</a> |
                  Twitter: @xdagarwynn</div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class="gmail_quote">On Mon, Apr 9, 2018 at 3:52 PM,
          Christian König <span dir="ltr"><<a href="mailto:christian.koenig@amd.com" target="_blank">christian.koenig@amd.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <div class="m_-6687502937288805473m_6490513933917362009moz-cite-prefix">Please
                provide the full dmesg of the system as well as the
                output of "lspci -s 0000:16:00.0 -vvvv" as attachment.<br>
                <br>
                Thanks,<br>
                Christian.<br>
                <br>
                Am 09.04.2018 um 06:00 schrieb Andrey Grodzovsky:<br>
              </div>
              <blockquote type="cite">
                <p>Just from a quick look it seems to fail in
                  amdgpu_device_init->ioremap with ENOMEM, that would
                  explain why you don't see any more prints - this
                  failure is very early in the device init process.</p>
                <p>No idea why ioremap would fail in this case and not
                  even sure which implementation of ioremap to look into
                  for your case.</p>
                <p>Adding Christian for this.</p>
                <p>Andrey<br>
                </p>
                <br>
                <div class="m_-6687502937288805473m_6490513933917362009moz-cite-prefix">On
                  04/07/2018 03:16 AM, Daniel Moran wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">Also, to clarify... if I move it into a
                    regular slot, turn off the eGPU it works as
                    expected. <br>
                    Tested with Intel iGPU enabled and disabled, made
                    sure i915 loaded without error and can connect
                    display to it.<br>
                    <br>
                    <img src="cid:part4.5298E0C0.FD307FFA@amd.com" width="562" height="407"><br>
                    <br>
                    <div>Again, thank you in advance for any
                      time/support offered.</div>
                  </div>
                  <div class="gmail_extra"><br clear="all">
                    <div>
                      <div class="m_-6687502937288805473m_6490513933917362009gmail_signature" data-smartmail="gmail_signature">
                        <div dir="ltr">
                          <div style="font-size:12.8px"><span style="font-size:12.8px">Respectfully,</span><br>
                          </div>
                          <div style="font-size:12.8px">
                            <div> </div>
                            <div>Daniel S. Moran (garwynn)</div>
                            <div>PC Hardware Editor - XDA-Developers</div>
                            <div>Phone: 1-559-316-0760/+81-90-5484-415<wbr>5</div>
                            <div>Article Links: <a href="http://www.xda-developers.com/author/garwynn" style="color:rgb(17,85,204)" target="_blank">http://www.xda-develope<wbr>rs.com/author/garwynn</a></div>
                            <div>E-mail: <a href="mailto:xdagarwynn@gmail.com" style="color:rgb(17,85,204)" target="_blank">xdagarwynn@gmail.com</a> |
                              Twitter: @xdagarwynn</div>
                          </div>
                        </div>
                      </div>
                    </div>
                    <br>
                    <div class="gmail_quote">On Sat, Apr 7, 2018 at 3:58
                      PM, Daniel Moran <span dir="ltr"><<a href="mailto:xdagarwynn@gmail.com" target="_blank">xdagarwynn@gmail.com</a>></span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                        <div dir="ltr">Hello all,
                          <div><br>
                          </div>
                          <div>I've got a Powercolor Red Devil Vega 56
                            here that I'm trying to get working in eGPU
                            mode.<br>
                            I think on the BIOS/hardware side it's now
                            all fleshed out.</div>
                          <div>Now I'm at a point where amdgpu tries to
                            init and reaches a fatal error.<br>
                            <br>
                            Set loglevel=8 doesn't get any additional
                            messages.</div>
                          <div>Here's what it does report (full dmesg
                            attached):</div>
                          <div><br>
                          </div>
                          <div>
                            <div>[  429.005909] [drm] amdgpu kernel
                              modesetting enabled.</div>
                            <div>[  429.006080] [drm] initializing
                              kernel modesetting (VEGA10 0x1002:0x687F
                              0x148C:0x2388 0xC3).</div>
                            <div>[  429.006082] amdgpu 0000:16:00.0:
                              Fatal error during GPU init</div>
                            <div>[  429.006155] amdgpu: probe of
                              0000:16:00.0 failed with error -12</div>
                            <div><br>
                              Using the following commands to unload
                              & reload for testing. Since it's as an
                              eGPU I'm using the i7-7700K iGPU (i915
                              module) as the primary and these commands
                              work in terminal without requiring a
                              reboot.</div>
                            <div><br>
                            </div>
                            <div>sudo rmmod amdgpu</div>
                            <div>sudo modprobe -v amgpu</div>
                            <div><br>
                            </div>
                            <div>Pulled the UMR and tried to make, fails
                              on Cmake. I'll attach log in a text.<br>
                              Also will attach a full dmesg and lspci
                              dump. uname -a below:</div>
                            <div><i>Linux testbox 4.15.15-041515-generic
                                #201803311331 SMP Sat Mar 31 17:34:21
                                UTC 2018 x86_64 x86_64 x86_64 GNU/Linux</i><br>
                              <br>
                              Any other ideas on how I can debug this
                              further? Feel I'm so close, don't want to
                              let this go.</div>
                            Thank you in advance for your time.<br>
                            <br clear="all">
                            <div>
                              <div class="m_-6687502937288805473m_6490513933917362009m_-3777984591867274688gmail_signature">
                                <div dir="ltr">
                                  <div style="font-size:12.8px"><span style="font-size:12.8px">Respectfully,</span><br>
                                  </div>
                                  <div style="font-size:12.8px">
                                    <div> </div>
                                    <div>Daniel S. Moran (garwynn)</div>
                                    <div>PC Hardware Editor -
                                      XDA-Developers</div>
                                    <div>Phone:
                                      1-559-316-0760/+81-90-5484-415<wbr>5</div>
                                    <div>Article Links: <a href="http://www.xda-developers.com/author/garwynn" style="color:rgb(17,85,204)" target="_blank">http://www.xda-develope<wbr>rs.com/author/garwynn</a></div>
                                    <div>E-mail: <a href="mailto:xdagarwynn@gmail.com" style="color:rgb(17,85,204)" target="_blank">xdagarwynn@gmail.com</a> |
                                      Twitter: @xdagarwynn</div>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                  <br>
                  <fieldset class="m_-6687502937288805473m_6490513933917362009mimeAttachmentHeader"></fieldset>
                  <br>
                  <pre>______________________________<wbr>_________________
amd-gfx mailing list
<a class="m_-6687502937288805473m_6490513933917362009moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org" target="_blank">amd-gfx@lists.freedesktop.org</a>
<a class="m_-6687502937288805473m_6490513933917362009moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/amd-gfx</a>
</pre>
                </blockquote>
                <br>
              </blockquote>
              <br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div>