Created attachment 135384 [details] lspci
Created attachment 135385 [details] journalctl
Created attachment 135386 [details] Xorg,0.log
Created attachment 135387 [details] dmesg
Please read your logs a bit more carefully: [ 4.470352] [drm] amdgpu kernel modesetting enabled. [ 4.470438] [drm] This hardware requires experimental hardware support. See modparam exp_hw_support Alternatively you can also upgrade the driver.
> Alternatively you can also upgrade the driver. how to do it? I have already switched to mainline kernel $ uname -r 4.14.0-0.rc8.git3.1.vanilla.knurd.1.fc27.x86_64 but it not helps. And also I see here yet another problem. If I enter BIOS and switch off Intel GPU then gdm successfully works but without hardware acceleration. I think this is correct behavior even if internal graphics still enabled. Can you look into this issue?
Created attachment 135420 [details] system log
Created attachment 135421 [details] dmesg
(In reply to mikhail.v.gavrilov from comment #5) > > Alternatively you can also upgrade the driver. > how to do it? I have already switched to mainline kernel Mainline kernel only has experimental support for compute on Vega10, no support for displaying anything. You need to use Alex amd-staging-drm-next kernel or wait for 4.15. > And also I see here yet another problem. > If I enter BIOS and switch off Intel GPU then gdm successfully works but > without hardware acceleration. I think this is correct behavior even if > internal graphics still enabled. Can you look into this issue? That's because in this configuration the BIOS brings up your Vega10 for output and X just sticks with the Vesa driver because it can't find anything else. To use a Vega10 in a desktop machine you need development packages of the kernel, mesa and DDX. Pre compiled user space packages for Ubuntu can be found here for example: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa
(hitting send to early, sorry) but you still need to compile the kernel on your own. The alternative is to use AMDs DKMS package for the closed source driver, but that is targeted mostly for server compute as well and I don't know how well that works with a desktop card.
Created attachment 135426 [details] case 1 (Intel Graphics Processor -> Enabled, The initial display output -> IGGX)
Created attachment 135427 [details] case 2 (Intel Graphics Processor -> Enabled, Initial display output -> PCIe 2 slot)
Created attachment 135428 [details] case 3 (Intel Graphics Processor -> Disabled, Initial display output -> PCIe 2 slot)
> You need to use Alex amd-staging-drm-next kernel or wait for 4.15. Where I can find such kernel or patch set for 4.13 or 4.14 kernel? > That's because in this configuration the BIOS brings up your Vega10 for output and X just sticks with the Vesa driver because it can't find anything else. This is not explain why X can't finds Vega10 when iGPU is on, but BIOS initialize Vega10 GPU. I think you misunderstood me. 1) a. Intel Graphics Processor -> Enabled b. The initial display output -> IGGX c. A monitor is connected to the motherboard BIOS screenshot: https://bugs.freedesktop.org/attachment.cgi?id=135426 In this case only the Intel graphic works. System works as well as without Radeon video card. The Radeon turbine rotates at full speed all the time. 2) a. Intel Graphics Processor -> Enabled b. Initial display output -> PCIe 2 slot c. A monitor connected to Radeon BIOS screenshot: https://bugs.freedesktop.org/attachment.cgi?id=135427 In this case all BIOS output, boot messages and the console passes through the Radeon graphics card. But graphics subsusystem couldn't launched. The Radeon turbine works silent. Demonstration: https://youtu.be/jjGO650EE80 I think this is bug because even if video card unsupported it must works in VESA mode. This behaviour worked in Windows. 3) a. Intel Graphics Processor -> Disabled b. Initial display output -> PCIe 2 slot c. A monitor connected to Radeon BIOS screenshot: https://bugs.freedesktop.org/attachment.cgi?id=135428 In this case all BIOS output, boot messages and the console passes through the Radeon graphics card. Graphics subsusystem launched and works without hardware acceleration in graphic mode with resolution 1024x768. The Radeon turbine works silent. This behaviour also expected in case 2 > Pre compiled user space packages for Ubuntu can be found here for example: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa $ glxinfo | grep -i "OpenGL version" OpenGL version string: 3.0 Mesa 17.2.4 Which minimal version is needed? I see on Fedora 27 I have Mesa 17.2.4
The alternative is to use AMDs DKMS package for the closed source driver, but that is targeted mostly for server compute as well and I don't know how well that works with a desktop card. This is not suitable variant for me because closed source driver don't support Fedora.
(In reply to mikhail.v.gavrilov from comment #13) > a. Intel Graphics Processor -> Enabled > b. Initial display output -> PCIe 2 slot > c. A monitor connected to Radeon > BIOS screenshot: https://bugs.freedesktop.org/attachment.cgi?id=135427 > In this case all BIOS output, boot messages and the console passes through > the Radeon graphics card. > But graphics subsusystem couldn't launched. > The Radeon turbine works silent. > Demonstration: https://youtu.be/jjGO650EE80 > I think this is bug because even if video card unsupported it must works in > VESA mode. This behaviour worked in Windows. Interesting, that indeed that should work. Could be a bug in the VESA BIOS or the driver touching the hardware even if it decided not to do so. Please try booting with modprobe.blacklist=amdgpu on the kernel commandline. > $ glxinfo | grep -i "OpenGL version" > OpenGL version string: 3.0 Mesa 17.2.4 > Which minimal version is needed? > I see on Fedora 27 I have Mesa 17.2.4 Not the slightest idea when Vega10 support was added to Mesa, but 17.2.4 is only a few days old so that could work. I would try to get X working with only the kernel first. If you have that working and still no OpenGL you can still compile Mesa on your own. Alex Kernel branch is here BTW: https://cgit.freedesktop.org/~agd5f/linux/ You can also find a amd-staging-4.13 branch there, but that is a ~month old and not maintained any more. amd-staging-drm-next is the latest development work.
> Interesting, that indeed that should work. Could be a bug in the VESA BIOS or the driver touching the hardware even if it decided not to do so. > Please try booting with modprobe.blacklist=amdgpu on the kernel commandline. Adding to blacklist amdgpu not solve problem, but it pushed me to the idea of doing the same thing with the intel driver. And after adding i915.modeset=0 i915.blacklist=1 graphics subsusystem was launched sucessful even with enabled IGPU in BIOS. It seems that the intel driver is culprit here.
(In reply to mikhail.v.gavrilov from comment #16) > It seems that the intel driver is culprit here. Ah, of course. Yeah X prefers any driver over the Vesa driver, so when the Intel driver is available it doesn't seem to try the more crude fallback. Anyway that is rather desired behavior (Vesa is really only the last resort). So we should probably not change anything on that. Anyway please try Alex kernel branch, if that still doesn't work please leave me a note at Christian.Koenig@amd.com. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.