Messages

16

User Zone / Re: Graphics Card install

« on: December 05, 2019, 06:50:02 am »

I've filed a bug report here, feel free to add comments to it:
https://gitlab.freedesktop.org/drm/amd/issues/984

17

User Zone / Re: Graphics Card install

« on: December 04, 2019, 11:32:55 pm »

This issue is due to Navi display support only being enabled for X86.
See here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/Kconfig#L23
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/Makefile#L27
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c#L629

Basically, before this will work the following needs to happen:
Either the DC code needs to be modified to use integer math instead of floating point math or

• The kernel_fpu_begin / kernel_fpu_end APIs need to be added for POWER (currently only supported on x86 and s390)
• The KConfig files need to be updated to enable POWER in addition to X86
• The Makefiles need to be modified to not assume x86 (and sse / sse2)

18

User Zone / Re: Graphics Card install

« on: December 04, 2019, 06:19:14 am »

Code: [Select]

No outputs definitely connected, trying again...
This isn't a POWER problem, this is an AMD GPU driver / hardware problem.  We're going to need a lot more info including the monitor model etc. -- last time I saw this you had to flip DisplayCore on or off, but Navi may require DisplayCore to operate at all.  If the latter is the case, you'll need to contact AMD support to get the driver fixes.

Yes, agreed, it's a problem with the driver (again, I'm assuming it's only a driver issues on ppc64le and not x86_64, but that's only an assumption) as it's not even detecting that there's anything that a monitor could be plugged into.
Note that I did test with amdgpu.dc=1 and amdgpu.dc=0 and there was no change, however my understanding is that navi only works it enabled like you said

Do you know the best way to contact AMD about this? I can run through the appropriate channels to try to get the support improved.

19

User Zone / Re: Graphics Card install

« on: December 03, 2019, 10:53:03 pm »

FYI, I tested this our a month or so ago, with build of the kernel / mesa / etc from git and was never able to get it to to work. I've also just re-tested with Fedora rawhide, and am seeing the same behaviour.

Effectively, the graphics card is detected fine, however no output ports are detected when starting X11, and as a result, no screens are found.
Normally, I'd expect to see something like the following in the X11 log:

Code: [Select]

[   716.370] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section
[   716.370] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section
[   716.370] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section
[   716.371] (II) AMDGPU(0): Output HDMI-A-0 has no monitor section
[   716.404] (II) AMDGPU(0): EDID for output DisplayPort-0

With Navi 10 on rawhide, I instead see the following (no outputs type are even detected, so it doesn't probe them):

Code: [Select]

[  1002.413] (II) AMDGPU(0): glamor X acceleration enabled on AMD NAVI10 (DRM 3.35.0, 5.4.0-2.fc32.ppc64le, LLVM 9.0.0)
[  1002.413] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[  1002.413] (==) AMDGPU(0): TearFree property default: auto
[  1002.413] (==) AMDGPU(0): VariableRefresh: disabled
[  1002.413] (II) AMDGPU(0): KMS Pageflipping: enabled
[  1002.413] (WW) AMDGPU(0): No outputs definitely connected, trying again...
[  1002.413] (WW) AMDGPU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[  1002.413] (II) AMDGPU(0): mem size init: gart size :1fe810000 vram size: s:1f7b70000 visible:fd50000
[  1002.413] (==) AMDGPU(0): DPI set to (96, 96)
[  1002.413] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
...
Fatal server error:
[  1002.416] (EE) no screens found(EE)

So, my assumption right now is that the current code has a bug on ppc64 where outputs ports are not detected properly. Note that I'll do some additional tests this weekend, but I expect this will require some sort of fix changes in the kernel/amdgpu driver.