https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #56 from kumquad ---
More tests:
*pci=noacpi
PC is booting but either it freezes right after booting to GNOME or it blocks
the Touchpad/USB mouse/keyboard/Tochscreen from working
*amdgpu.dpm=0 or acpi=off
Screen turns black and
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #55 from kumquad ---
Created attachment 145876
--> https://bugs.freedesktop.org/attachment.cgi?id=145876=edit
Spectrex360 / Kernel 5.3.7 / Vega56 / normal boot
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
kumquad changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #53 from Robert Strube ---
Created attachment 144091
--> https://bugs.freedesktop.org/attachment.cgi?id=144091=edit
lspci kernel 5.0.x with nividia eGPU
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #52 from Robert Strube ---
Created attachment 144090
--> https://bugs.freedesktop.org/attachment.cgi?id=144090=edit
dmesg log with kernel 5.0.x with nvidia eGPU
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #51 from Robert Strube ---
Hello Everyone,
I realize it's been a long time since I updated this bug report, apologies in
advance. I decided to give up on eGPUs + Linux (over Thunderbolt 3) for a
while, and didn't get a chance to
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #50 from Dimitar Atanasov ---
There is two windows on this system. Small one below 4GB which is 2.5GB and
bigger one over 4GB which is 64GB. Address space for thunderbolt is only 200
MB. As I know AMDGPU needs 250 MB in low 4GB and
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #49 from Alex Deucher ---
(In reply to Dimitar Atanasov from comment #48)
> May be problem is the CPU, because it has only 16 PCIe lains, so 8 for vega
> M,
> 4 for NVME, and 4 for others, I have seen that card reader is also
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #48 from Dimitar Atanasov ---
May be problem is the CPU, because it has only 16 PCIe lains, so 8 for vega M,
4 for NVME, and 4 for others, I have seen that card reader is also connected on
PCIe.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Rasmus Thomsen changed:
What|Removed |Added
CC||cogi...@exherbo.org
--- Comment #47
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #46 from Rasmus Thomsen ---
FWIW, I'm also hit by this on a HP Spectre X360 with a Vega M configuration
(thought it's notable as the other reports seem to only come from Dell
machines?). Disabling the Vega M by doing `echo 1 >
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #45 from Alex Deucher ---
(In reply to Dimitar Atanasov from comment #44)
> Works with 4.19.32 witch acpi=off, but CPU is single core
Most likely some other device failed to get enumerated in that case and that
freed up resources
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #44 from Dimitar Atanasov ---
Works with 4.19.32 witch acpi=off, but CPU is single core
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #43 from Alex Deucher ---
(In reply to Dimitar Atanasov from comment #41)
> Created attachment 143805 [details]
> default boot vega 56
Similar issues on your system:
[ 168.653171] pci :3d:00.0: BAR 0: no space for [mem size
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #42 from Dimitar Atanasov ---
actualy with acpi=off, Vega 56 is not found at all during boot, only enclosure
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #41 from Dimitar Atanasov ---
Created attachment 143805
--> https://bugs.freedesktop.org/attachment.cgi?id=143805=edit
default boot vega 56
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #40 from Dimitar Atanasov ---
Created attachment 143804
--> https://bugs.freedesktop.org/attachment.cgi?id=143804=edit
acpi=off amd.dpm=0
Vega 56
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #39 from Dimitar Atanasov ---
I am with same problem. Computer is Dell Precision 5530 2-in-1 with VegaM
inside
EGPU is Vega56. EGPU is not starting even with acpi=off. Kernel 5.0.4
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #38 from Alex Deucher ---
(In reply to Robert Strube from comment #34)
> Created attachment 143044 [details]
> dmesg log amdgpu.dpm=0 with 580 as eGPU
>
> Another user is reporting a similar problem with a different Dell laptop
>
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #37 from Robert Strube ---
One additional comment, the user with the XPS 9370 was able to get the RX 580
working as an eGPU flawlessly in Windows 10. This lends some credibility to
the theory that it might not actually be a BIOS
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #36 from Robert Strube ---
(In reply to Robert Strube from comment #34)
> Created attachment 143044 [details]
> dmesg log amdgpu.dpm=0 with 580 as eGPU
>
> Another user is reporting a similar problem with a different Dell laptop
>
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Robert Strube changed:
What|Removed |Added
Attachment #143044|dmesg log amdgpu=0 with 580 |dmesg log amdgpu.dpm=0 with
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #35 from Robert Strube ---
Created attachment 143045
--> https://bugs.freedesktop.org/attachment.cgi?id=143045=edit
dmesg log pci=noacpi with 580 as eGPU
Another user has reported a similar problem with a different laptop (XPS
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #34 from Robert Strube ---
Created attachment 143044
--> https://bugs.freedesktop.org/attachment.cgi?id=143044=edit
dmesg log amdgpu=0 with 580 as eGPU
Another user is reporting a similar problem with a different Dell laptop (the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #33 from Alex Deucher ---
With respect to pci(e) devices, acpi=off and pci=noacpi are equivalent I think.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #32 from Robert Strube ---
Hi Alex,
I just tested acpi=off independently and not amdgpu.dpm=0 independently.
In regards to the other user, yes he had the exact same PCI resource issues as
me, what I'm curious to find out though,
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #31 from Alex Deucher ---
(In reply to Robert Strube from comment #30)
> Hi Alex,
>
> Thanks for the reply. I wanted to clarify an important point: When I
> disabled PM completely and ACPI completely, I did not see any PCI
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #30 from Robert Strube ---
Hi Alex,
Thanks for the reply. I wanted to clarify an important point: When I disabled
PM completely and ACPI completely, I did not see any PCI resource issues AND
the eGPU initialized successfully.
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #29 from Alex Deucher ---
(In reply to Robert Strube from comment #28)
> Quick update:
>
> I heard back from the ACPI BIOS kernel developers (see:
> https://bugzilla.kernel.org/show_bug.cgi?id=201527) and they seem to imply
> that
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #28 from Robert Strube ---
Quick update:
I heard back from the ACPI BIOS kernel developers (see:
https://bugzilla.kernel.org/show_bug.cgi?id=201527) and they seem to imply that
the PCI resource issues showing up in the dmseg log
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #27 from Robert Strube ---
Thanks for the response.
I think it was just a coincidence that the eGPU started working with acpi=off.
Taking a closer look at the issue it really does appear to be a BIOS problem
that prevents the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #26 from Christian König ---
I don't want to stop your cheering, but that isn't a perfect solution either.
(In reply to Robert Strube from comment #25)
> I'm wondering where I can report the Thunderbolt Controller / Bridge bug?
>
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #25 from Robert Strube ---
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
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #24 from Robert Strube ---
Created attachment 142209
--> https://bugs.freedesktop.org/attachment.cgi?id=142209=edit
dmesg log booting system with PM *DISABLED* and *WITH* eGPU
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #23 from Robert Strube ---
Edit: taking a closer look at the dmesg I see that disabling the PM did indeed
eliminate the PCI resource issues. So for some reason having PM enabled
affects the PCI resource allocation for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #22 from Robert Strube ---
OK! My hunch about the PM was right! The card is fully initialized now, so the
issue doesn't appear to be a PCI resource issue!
I took the brute force approach, compiled my own custom kernel that
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #21 from Robert Strube ---
Hi guys,
Apologies for the deluge of posts here, I've been trying really hard to
investigate this issue!
So I took a closer look at the PCI resource issues that you mentioned, I've
also been looking and
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #20 from Robert Strube ---
One more thing I thought of. Would it help if I posted my dmesg log with the
GTX 1060 connected as an eGPU?
As I mentioned previously this card *is* working with nouveau. I haven't
tested with the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Robert Strube changed:
What|Removed |Added
Attachment #142205|fresh dmesg log booting |fresh dmesg log booting
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #19 from Robert Strube ---
Created attachment 142205
--> https://bugs.freedesktop.org/attachment.cgi?id=142205=edit
fresh dmesg log booting system *wite* eGPU connected at boot
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #18 from Robert Strube ---
Created attachment 142204
--> https://bugs.freedesktop.org/attachment.cgi?id=142204=edit
sudo cat /proc/iomem *with* eGPU connected at boot
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #17 from Robert Strube ---
Created attachment 142203
--> https://bugs.freedesktop.org/attachment.cgi?id=142203=edit
lspci *with* eGPU attached at boot
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #16 from Robert Strube ---
Created attachment 142202
--> https://bugs.freedesktop.org/attachment.cgi?id=142202=edit
fresh dmesg log booting system *without* eGPU
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Robert Strube changed:
What|Removed |Added
Attachment #142200|lspci (no eGPU) |lspci with eGPU *not*
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #15 from Robert Strube ---
Created attachment 142201
--> https://bugs.freedesktop.org/attachment.cgi?id=142201=edit
sudo cat /proc/iomem when eGPU *not* connected
sudo cat /proc/iomem when eGPU *not* connected
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #14 from Robert Strube ---
Created attachment 142200
--> https://bugs.freedesktop.org/attachment.cgi?id=142200=edit
lspci (no eGPU)
lspci -t -nn -v output when the eGPU is *not* connected.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Christian König changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #12 from Robert Strube ---
Created attachment 142187
--> https://bugs.freedesktop.org/attachment.cgi?id=142187=edit
dmesg log booting system *without* eGPU
So I decided to do a sanity check and completely remove the eGPU from the
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #11 from Robert Strube ---
I disabled a bunch of devices in the BIOS (sound, SD card reader, etc.) and I
confirmed that they are no longer showing up in lspci, but I'm still getting
the same error.
I also found one suggestion to
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #10 from Alex Deucher ---
(In reply to Robert Strube from comment #9)
> Any suggestion for how I can increase the MMIO space for the BARs on the
> Thunderbolt bridges? Should I try to disable additional devices in the BIOS,
> etc.?
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #9 from Robert Strube ---
Any suggestion for how I can increase the MMIO space for the BARs on the
Thunderbolt bridges? Should I try to disable additional devices in the BIOS,
etc.? I'm a little out of my element here.
Thanks!
Rob
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #8 from Alex Deucher ---
There does not seem to be enough MMIO space for the BARs on the thunderbolt
bridges:
[0.436946] pci :04:00.0: BAR 13: no space for [io size 0x4000]
[0.436947] pci :04:00.0: BAR 13: failed to
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #7 from Robert Strube ---
Thanks for the suggestions! I took your advice and commented out the Vega M
device IDs located here: /drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
These are the lines of code that I commented out.
/* VEGAM */
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #6 from Robert Strube ---
Created attachment 142182
--> https://bugs.freedesktop.org/attachment.cgi?id=142182=edit
dmesg log booting system with eGPU (Vega M device IDs removed in kernel)
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #5 from Alex Deucher ---
If you can get any of the other methods to work you can remove the vegam device
id from the driver. That said, I doubt it will make a difference. Usually the
problem with thunderbolt is that pci BAR
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #4 from Robert Strube ---
I decided to apply a hack to 4.19 and see if I could get the eGPU to
initialize. I noticed that this code in /drivers/gpu/drm/amd/amdgpu/atom.c
if ((jiffies_to_msecs(cjiffies) > 5000)) {
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #3 from Robert Strube ---
Quick question:
Is it possible to completely disable the Vega M using kernel boot parameters.
I did try using pci-stub.ids=: with the PCI hex id for my Vega M
(1002:694e) but amdgpu was still
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Robert Strube changed:
What|Removed |Added
Attachment #142151|dmesg log booting system|dmesg log booting system
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #2 from Robert Strube ---
Created attachment 142151
--> https://bugs.freedesktop.org/attachment.cgi?id=142151=edit
dmesg log booting system with eGPU attched and powered
Starting at line:
[ 11.192733] ATOM BIOS:
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #1 from Alex Deucher ---
Please attach your dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=108521
Bug ID: 108521
Summary: RX 580 as eGPU amdgpu: gpu post error!
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
61 matches
Mail list logo
