dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-108882-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3746 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108882

            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=142636&action=edit
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 
https://amdgpu-install.readthedocs.io/en/latest/
and used

amdgpu-pro-install --opencl=legacy

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=legacy

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 found
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 

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             
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: radeonsi             
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: radeonsi             

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#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.

[-- Attachment #1.2: Type: text/html, Size: 5430 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-11-28  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 23:43 bugzilla-daemon [this message]
2019-07-29 16:47 ` [Bug 108882] Many different installation problems with amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 bugzilla-daemon
2019-11-19  7:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108882-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox