From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108882] Many different installation problems with amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 Date: Tue, 27 Nov 2018 23:43:35 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1872722106==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 8A2E76E039 for ; Wed, 28 Nov 2018 00:20:05 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1872722106== Content-Type: multipart/alternative; boundary="15433622150.D19D8d1.20459" Content-Transfer-Encoding: 7bit --15433622150.D19D8d1.20459 Date: Tue, 27 Nov 2018 23:43:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108882 Bug ID: 108882 Summary: Many different installation problems with amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel@lists.freedesktop.org Reporter: elmar@yasara.org Created attachment 142636 --> https://bugs.freedesktop.org/attachment.cgi?id=3D142636&action=3Dedit The various logs Dear AMD Team, unfortunately installation of your amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 goes wrong at many spots. So far I had been using fglrx happily, but now I needed Vulkan support, so I decided to upgrade. Since I got a AMD Radeon R9 290X I followed instructions at=20 https://amdgpu-install.readthedocs.io/en/latest/ and used amdgpu-pro-install --opencl=3Dlegacy the script ran through, I rebooted, and got a black screen. Logging in remotely and looking at /var/log/Xorg.0.log I saw lots of entries about fglrx. Since your instructions don't mention uninstalling old drivers, and your amdgpu-pro-install doesn't complain, I don't think that's my fault. Next, I uninstalled fglrx, to be sure also amdgpu-pro-uninstall, rebooted, = and went for another amdgpu-pro-install --opencl=3Dlegacy After another reboot, a 'startx' finally gave me a running X-server, but no OpenGL/GLX (running glxinfo yielded 'no GLX visual found'). Next I checked what amdgpu-pro-install did to my /etc/X11/xorg.conf and fou= nd this: Section "ServerLayout" Identifier "Main" Option "AIGLX" "false" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" EndSection This doesn't look like it's a proper xorg.conf for amdgpu-pro. After some googling, I replaced xorg.conf with this file: /usr/share/X11/xorg.conf.d/00-amdgpu-pro.conf=20 After an X-server restart, 'glxinfo' in a terminal gave a different error: libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20= =20=20=20 libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20= =20=20=20 libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20= =20=20=20 Whenever there is a permission problem, I try again as 'root', and indeed, things worked. After some googling, I did cd /dev/dri ls -l crw-rw----+ 1 root video 226, 0 Nov 27 23:06 card0 crw-rw----. 1 root video 226, 64 Nov 27 23:06 controlD64 crw-rw----+ 1 root video 226, 128 Nov 27 23:06 renderD128 Then I did chmod a+rw * and got crw-rw-rw-+ 1 root video 226, 0 Nov 27 23:06 card0 crw-rw-rw-. 1 root video 226, 64 Nov 27 23:06 controlD64 crw-rw-rw-+ 1 root video 226, 128 Nov 27 23:06 renderD128 And magically, after many hours of fiddling, OpenGL and OpenCL worked for a normal user. Yupppie! So I figured it's time to file a bug report, ended up at https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html#generat= ing-a-bug-report This page shows countless commands to run to save my system config. And amazingly, each command is shown with a '$' in front. This means that I cannot just copy the entire script into a terminal, but instead have to do it line-by-line manually, or copy it to a text editor and cut the $s out. Seriously? Hope this report helped to improve things... Regards, Elmar --=20 You are receiving this mail because: You are the assignee for the bug.= --15433622150.D19D8d1.20459 Date: Tue, 27 Nov 2018 23:43:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 108882
Summary Many different installation problems with amdgpu-pro-18.40-67= 6022-rhel-6 driver in CentOS 6.10
Product DRI
Version unspecified
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu-pro
Assignee dri-devel@lists.freedesktop.org
Reporter elmar@yasara.org

Created attachment 142636 <=
a href=3D"attachment.cgi?id=3D142636&action=3Dedit" title=3D"The variou=
s logs">[details]
The various logs

Dear AMD Team,

unfortunately installation of your amdgpu-pro-18.40-676022-rhel-6 driver in
CentOS 6.10 goes wrong at many spots.

So far I had been using fglrx happily, but now I needed Vulkan support, so I
decided to upgrade.
Since I got a AMD Radeon R9 290X I followed instructions at=20
https://amdgpu=
-install.readthedocs.io/en/latest/
and used

amdgpu-pro-install --opencl=3Dlegacy

the script ran through, I rebooted, and got a black screen.
Logging in remotely and looking at /var/log/Xorg.0.log I saw lots of entries
about fglrx.
Since your instructions don't mention uninstalling old drivers, and your
amdgpu-pro-install doesn't complain, I don't think that's my fault.

Next, I uninstalled fglrx, to be sure also amdgpu-pro-uninstall, rebooted, =
and
went for another

amdgpu-pro-install --opencl=3Dlegacy

After another reboot, a 'startx' finally gave me a running X-server, but no
OpenGL/GLX (running glxinfo yielded 'no GLX visual found').

Next I checked what amdgpu-pro-install did to my /etc/X11/xorg.conf and fou=
nd
this:

Section "ServerLayout"
   Identifier   "Main"
   Option "AIGLX" "false"
EndSection

Section "Device"
        Identifier "Videocard0"
        Driver "radeon"
EndSection

This doesn't look like it's a proper xorg.conf for amdgpu-pro. After some
googling, I replaced xorg.conf with this file:
/usr/share/X11/xorg.conf.d/00-amdgpu-pro.conf=20

After an X-server restart, 'glxinfo' in a terminal gave a different error:

libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20=
=20=20=20
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20=
=20=20=20
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: radeonsi=20=20=20=20=20=20=20=20=20=20=
=20=20=20

Whenever there is a permission problem, I try again as 'root', and indeed,
things worked.
After some googling, I did

cd /dev/dri
ls -l
crw-rw----+ 1 root video 226,   0 Nov 27 23:06 card0
crw-rw----. 1 root video 226,  64 Nov 27 23:06 controlD64
crw-rw----+ 1 root video 226, 128 Nov 27 23:06 renderD128

Then I did
chmod a+rw *
and got

crw-rw-rw-+ 1 root video 226,   0 Nov 27 23:06 card0
crw-rw-rw-. 1 root video 226,  64 Nov 27 23:06 controlD64
crw-rw-rw-+ 1 root video 226, 128 Nov 27 23:06 renderD128

And magically, after many hours of fiddling, OpenGL and OpenCL worked for a
normal user. Yupppie!

So I figured it's time to file a bug report, ended up at

https://amdgpu-install.readthedocs.io/en/lates=
t/install-bugrep.html#generating-a-bug-report

This page shows countless commands to run to save my system config. And
amazingly, each command is shown with a '$' in front.
This means that I cannot just copy the entire script into a terminal, but
instead have to do it line-by-line manually, or copy it to a text editor and
cut the $s out.
Seriously?

Hope this report helped to improve things...

Regards,
Elmar


You are receiving this mail because:
  • You are the assignee for the bug.
= --15433622150.D19D8d1.20459-- --===============1872722106== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1872722106==--