From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110795] Unable to install on latest Ubuntu (19.04)
Date: Tue, 25 Jun 2019 12:12:10 +0000 [thread overview]
Message-ID: <bug-110795-502-iLEoHD60VR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110795-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1404 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110795
--- Comment #25 from Etienne Lorrain <etienne_lorrain@yahoo.fr> ---
(In reply to Etienne Lorrain from comment #24)
> The script (attached to this bug) to install latest AMD drivers on ubuntu
> 19.04 for a RX590 on a Ryzen threadripper works for me, but leads to a
> Segmentation fault at address 0x0 of /usr/lib/xorg/Xorg seen in
> .local/share/xorg/Xorg.0.log
>
> Solution for me was to:
> sudo mv /usr/share/X11/xorg.conf.d/10-amdgpu.conf
> /usr/share/X11/xorg.conf.d/10-amdgpu.conf.bak
> sudo mv /usr/share/X11/xorg.conf.d/00-amdgpu.conf
> /usr/share/X11/xorg.conf.d/00-amdgpu.conf.bak
> as proposed by axlc in https://community.amd.com/thread/227165
> Then I had to reboot the PC, no more "loop login".
A shorter solution is to comment out (by adding # as first char) the line:
ModulePath "/opt/amdgpu/lib/xorg/modules"
in 00-amdgpu.conf and rename both files as their original names.
Maybe to use /usr/lib/xorg/modules/libglamoregl.so instead of
/opt/amdgpu/lib/xorg/modules/libglamoregl.so, different files with same names.
Or to use /usr/lib/xorg/modules/drivers/amdgpu_drv.so instead of
/opt/amdgpu/lib/xorg/modules/drivers/amdgpu_drv.so, different files with same
names.
There is only two real files in /opt/amdgpu/lib/xorg/modules/.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-25 12:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:44 [Bug 110795] Unable to install on latest Ubuntu (19.04) bugzilla-daemon
2019-05-29 21:46 ` bugzilla-daemon
2019-05-29 22:22 ` bugzilla-daemon
2019-05-29 23:58 ` bugzilla-daemon
2019-05-30 0:36 ` bugzilla-daemon
2019-05-30 0:59 ` bugzilla-daemon
2019-05-30 1:33 ` bugzilla-daemon
2019-05-30 1:49 ` bugzilla-daemon
2019-06-04 10:14 ` bugzilla-daemon
2019-06-07 2:43 ` bugzilla-daemon
2019-06-07 4:19 ` bugzilla-daemon
2019-06-07 4:21 ` bugzilla-daemon
2019-06-07 13:38 ` bugzilla-daemon
2019-06-07 15:25 ` bugzilla-daemon
2019-06-07 16:30 ` bugzilla-daemon
2019-06-10 20:28 ` bugzilla-daemon
2019-06-10 21:42 ` bugzilla-daemon
2019-06-12 8:12 ` bugzilla-daemon
2019-06-12 23:49 ` bugzilla-daemon
2019-06-12 23:51 ` bugzilla-daemon
2019-06-13 8:16 ` bugzilla-daemon
2019-06-13 9:58 ` bugzilla-daemon
2019-06-13 10:10 ` bugzilla-daemon
2019-06-13 23:46 ` bugzilla-daemon
2019-06-14 9:09 ` bugzilla-daemon
2019-06-14 9:11 ` bugzilla-daemon
2019-06-15 17:32 ` bugzilla-daemon
2019-06-15 17:41 ` bugzilla-daemon
2019-06-25 10:25 ` bugzilla-daemon
2019-06-25 12:12 ` bugzilla-daemon [this message]
2019-06-26 1:39 ` bugzilla-daemon
2019-06-26 1:42 ` bugzilla-daemon
2019-08-17 22:30 ` bugzilla-daemon
2019-08-18 4:12 ` bugzilla-daemon
2019-08-18 4:12 ` bugzilla-daemon
2019-08-20 13:20 ` bugzilla-daemon
2019-08-20 16:04 ` bugzilla-daemon
2019-08-23 7:37 ` bugzilla-daemon
2019-08-23 7:38 ` bugzilla-daemon
2019-08-23 8:26 ` bugzilla-daemon
2019-08-23 9:04 ` bugzilla-daemon
2019-08-26 8:15 ` bugzilla-daemon
2019-10-26 10:48 ` bugzilla-daemon
2019-11-17 21:46 ` bugzilla-daemon
2019-11-19 8:04 ` bugzilla-daemon
2019-11-25 12:47 ` 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-110795-502-iLEoHD60VR@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.