Installing AMDGPU-PRO Ubuntu Driver under Slackware 14.2?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've noticed that your git doesn't exist anymore. Are you still going to update your script for amdgpu-pro-driver-16.5?
I actually changed things around since I don't know how well each driver version is supported (and what needs to be done). I have created a directory for the 16.30, 16.40, and 16.50 releases and have SlackBuilds in each (the download link is near the top of each SlackBuild). Although, I believe that 16.50 (possibly 16.40 too) need something compiled in there, but I haven't found any solid information on it. Give it a try and let me know your results.
Right now, all my packages do is repackage the Ubuntu driver's individual .deb files (found after extracting the main tarball) and create one giant Slackware package. If something does need to be compiled, I'll need to work that into the script.
I compiled the right xorg-server-1.18.4 from git based upon this line: "[ 47433.439] compiled for 1.18.4, module version = 1.1.99"
Perhaps I need to make an "/etc/X11/xorg.conf" to get a working screen?
Also, makepkg is complaining about zero-length documentation files.
Code:
[ 47433.405]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 47433.405] X Protocol Version 11, Revision 0
[ 47433.405] Build Operating System: Linux 4.9.0-rc8+ x86_64
[ 47433.405] Current Operating System: Linux 64 4.9.0-rc8+ #1 SMP Fri Jan 6 06:19:55 UTC 2017 x86_64
[ 47433.405] Kernel command line: auto BOOT_IMAGE=Linux64 ro root=802
[ 47433.405] Build Date: 10 January 2017 03:27:34AM
[ 47433.405]
[ 47433.406] Current version of pixman: 0.35.1
[ 47433.406] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 47433.406] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 47433.406] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 10 03:32:11 2017
[ 47433.406] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 47433.406] (==) No Layout section. Using the first Screen section.
[ 47433.406] (==) No screen section available. Using defaults.
[ 47433.406] (**) |-->Screen "Default Screen Section" (0)
[ 47433.406] (**) | |-->Monitor "<default monitor>"
[ 47433.406] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 47433.406] (==) Automatically adding devices
[ 47433.406] (==) Automatically enabling devices
[ 47433.406] (==) Automatically adding GPU devices
[ 47433.406] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 47433.406] (==) FontPath set to:
[ 47433.406] (**) ModulePath set to "/opt/amdgpu-pro/lib/xorg/modules,/usr/lib/xorg/modules"
[ 47433.406] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 47433.406] (II) Loader magic: 0x802660
[ 47433.406] (II) Module ABI versions:
[ 47433.406] X.Org ANSI C Emulation: 0.4
[ 47433.406] X.Org Video Driver: 20.0
[ 47433.406] X.Org XInput driver : 22.1
[ 47433.406] X.Org Server Extension : 9.0
[ 47433.407] (++) using VT number 1
[ 47433.407] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
[ 47433.407] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 47433.433] (--) PCI:*(0:1:0:0) 1002:7300:1002:0b36 rev 202, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, 0xfea00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[ 47433.433] (II) Open ACPI successful (/var/run/acpid.socket)
[ 47433.433] (II) "glx" will be loaded by default.
[ 47433.433] (II) LoadModule: "dri2"
[ 47433.433] (II) Module "dri2" already built-in
[ 47433.433] (II) LoadModule: "glamoregl"
[ 47433.433] (II) Loading /opt/amdgpu-pro/lib/xorg/modules/libglamoregl.so
[ 47433.438] (II) Module glamoregl: vendor="X.Org Foundation"
[ 47433.438] compiled for 1.18.4, module version = 1.0.0
[ 47433.438] ABI class: X.Org ANSI C Emulation, version 0.4
[ 47433.438] (II) LoadModule: "glx"
[ 47433.438] (II) Loading /opt/amdgpu-pro/lib/xorg/modules/extensions/libglx.so
[ 47433.439] (II) Module glx: vendor="X.Org Foundation"
[ 47433.439] compiled for 1.18.0, module version = 1.0.0
[ 47433.439] ABI class: X.Org Server Extension, version 9.0
[ 47433.439] (==) AIGLX enabled
[ 47433.439] (II) Applying OutputClass "amdgpu-pro" to /dev/dri/card0
[ 47433.439] loading driver: amdgpu
[ 47433.439] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
[ 47433.439] loading driver: amdgpu
[ 47433.439] (==) Matched amdgpu as autoconfigured driver 0
[ 47433.439] (==) Matched amdgpu as autoconfigured driver 1
[ 47433.439] (==) Matched ati as autoconfigured driver 2
[ 47433.439] (==) Matched ati as autoconfigured driver 3
[ 47433.439] (==) Matched modesetting as autoconfigured driver 4
[ 47433.439] (==) Matched fbdev as autoconfigured driver 5
[ 47433.439] (==) Matched vesa as autoconfigured driver 6
[ 47433.439] (==) Assigned the driver to the xf86ConfigLayout
[ 47433.439] (II) LoadModule: "amdgpu"
[ 47433.439] (II) Loading /opt/amdgpu-pro/lib/xorg/modules/drivers/amdgpu_drv.so
[ 47433.439] (II) Module amdgpu: vendor="X.Org Foundation"
[ 47433.439] compiled for 1.18.4, module version = 1.1.99
[ 47433.439] Module class: X.Org Video Driver
[ 47433.439] ABI class: X.Org Video Driver, version 20.0
[ 47433.439] (II) LoadModule: "ati"
[ 47433.439] (WW) Warning, couldn't open module ati
[ 47433.439] (II) UnloadModule: "ati"
[ 47433.439] (II) Unloading ati
[ 47433.439] (EE) Failed to load module "ati" (module does not exist, 0)
[ 47433.439] (II) LoadModule: "modesetting"
[ 47433.439] (II) Loading /opt/amdgpu-pro/lib/xorg/modules/drivers/modesetting_drv.so
[ 47433.439] (II) Module modesetting: vendor="X.Org Foundation"
[ 47433.439] compiled for 1.18.4, module version = 1.18.4
[ 47433.439] Module class: X.Org Video Driver
[ 47433.439] ABI class: X.Org Video Driver, version 20.0
[ 47433.439] (II) LoadModule: "fbdev"
[ 47433.439] (WW) Warning, couldn't open module fbdev
[ 47433.439] (II) UnloadModule: "fbdev"
[ 47433.439] (II) Unloading fbdev
[ 47433.439] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 47433.439] (II) LoadModule: "vesa"
[ 47433.440] (WW) Warning, couldn't open module vesa
[ 47433.440] (II) UnloadModule: "vesa"
[ 47433.440] (II) Unloading vesa
[ 47433.440] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 47433.440] (II) AMDGPU: Driver for AMD Radeon chipsets: BONAIRE, CARRIZO, FIJI,
HAINAN, HAWAII, KABINI, KAVERI, MULLINS, OLAND, PITCAIRN, POLARIS10,
POLARIS11, STONEY, TAHITI, TONGA, TOPAZ, VERDE
[ 47433.440] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 47433.440] (II) [KMS] Kernel modesetting enabled.
[ 47433.440] (II) AMDGPU(0): ShareFD: disabled
[ 47433.465] (DB) AMDGPU(0): open fd=10
[ 47433.465] (WW) Falling back to old probe method for modesetting
[ 47433.465] (II) AMDGPU(0): AMDGPU DDX hybrid version: 16.50.5
[ 47433.465] (EE) AMDGPU(0): Failed to open amdgpu hybrid version
[ 47433.465] (II) AMDGPU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 47433.465] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32
[ 47433.465] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 47433.465] (==) AMDGPU(0): Default visual is TrueColor
[ 47433.465] (==) AMDGPU(0): RGB weight 888
[ 47433.465] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[ 47433.465] (--) AMDGPU(0): Chipset: "FIJI" (ChipID = 0x7300)
[ 47433.465] (II) Loading sub module "fb"
[ 47433.465] (II) LoadModule: "fb"
[ 47433.465] (WW) Warning, couldn't open module fb
[ 47433.465] (II) UnloadModule: "fb"
[ 47433.465] (II) Unloading fb
[ 47433.465] (EE) AMDGPU: Failed to load module "fb" (module does not exist, 0)
[ 47433.490] (II) UnloadModule: "amdgpu"
[ 47433.490] (EE) Screen(s) found, but none have a usable configuration.
[ 47433.490] (EE)
Fatal server error:
[ 47433.490] (EE) no screens found(EE)
[ 47433.490] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 47433.490] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 47433.490] (EE)
[ 47433.528] (EE) Server terminated with error (1). Closing log file.
For some reason, it isn't finding a usable configuration for your screens. Was this working with an older version of amdgpu-pro? If so, it may be something that needs to be configured/compiled with the newer version of the the driver. Do you currently have a /etc/X11/xorg.conf or anything in /etc/X11/xorg.conf.d/? If so, try removing or renaming (like adding a .bak to them) them so X can use its default configuration.
Do you currently have a /etc/X11/xorg.conf or anything in /etc/X11/xorg.conf.d/?
Not at the time of your question. I did and do have a /usr/share/X11/xorg.conf.d directory which have files that do not appear prevent starting X.
There is some progress. With amdgpu-pro-driver-16.50-362463-x86_64-1_bass.txz installed, I recompiled the xorg build order from mesa/mesa to util/lndir. This time xserver was compiled with option "--with-module-dir=/opt/amdgpu-pro/lib/xorg/modules" X starts now. I don't know, for now, what enabled X to start. Mouse and keyboard will not work with "--with-module-dir" set to /opt/amdgpu-pro/lib/xorg/modules even after recompiling evdev. So, I created an xorg.conf with these lines:
(EE) AMDGPU(0): Failed to open amdgpu hybrid version
(EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/amdgpu_dri.so failed (/usr/lib64/xorg/modules/dri/amdgpu_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(==) AIGLX enabled
(EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/amdgpu_dri.so failed (/usr/lib64/xorg/modules/dri/amdgpu_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
Even though AIGLX is claiming software rendering steam games are running--except Dota 2 in vulkan mode which gives error: ~/.local/share/Steam/SteamApps/common/dota 2 beta/game/bin/linuxsteamrt64/dota2: symbol lookup error: /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so: undefined symbol: amdgpu_va_range_alloc_in_range
I suspect Steam is still using the opensource drivers.
I may try rebuilding opensource mesa without vulkan or uninstall mesa after I solve amdgpu_dri.so not being found.
I started a new job and then the holidays hit. Finally settling down from all that. About to give it another shot. Looks like I have some reading to do. ;-)
Thanks.
Quote:
Originally Posted by Ztcoracat
mpyusko
Were you able to get that driver working for your Slackware system?
Not at the time of your question. I did and do have a /usr/share/X11/xorg.conf.d directory which have files that do not appear prevent starting X.
There is some progress. With amdgpu-pro-driver-16.50-362463-x86_64-1_bass.txz installed, I recompiled the xorg build order from mesa/mesa to util/lndir. This time xserver was compiled with option "--with-module-dir=/opt/amdgpu-pro/lib/xorg/modules" X starts now. I don't know, for now, what enabled X to start. Mouse and keyboard will not work with "--with-module-dir" set to /opt/amdgpu-pro/lib/xorg/modules even after recompiling evdev. So, I created an xorg.conf with these lines:
That should allow X to look for the modules in the correct directory without any recompilings.
Quote:
Originally Posted by charlie4
Xorg.0.log gives me new errors:
Code:
(EE) AMDGPU(0): Failed to open amdgpu hybrid version
(EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/amdgpu_dri.so failed (/usr/lib64/xorg/modules/dri/amdgpu_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(==) AIGLX enabled
(EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/amdgpu_dri.so failed (/usr/lib64/xorg/modules/dri/amdgpu_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
Even though AIGLX is claiming software rendering steam games are running--except Dota 2 in vulkan mode which gives error: ~/.local/share/Steam/SteamApps/common/dota 2 beta/game/bin/linuxsteamrt64/dota2: symbol lookup error: /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so: undefined symbol: amdgpu_va_range_alloc_in_range
I suspect Steam is still using the opensource drivers.
I may try rebuilding opensource mesa without vulkan or uninstall mesa after I solve amdgpu_dri.so not being found.
This looks a little more straightforward. It looks like Ubuntu doesn't handle things the same way Slackware does in regards to 64bit libs (they have them in /usr/lib/x86_64-linux-gnu instead of /usr/lib64). Simply creating the /usr/lib64/xorg/modules/dri/ directory structure, moving the amdgpu_dri.so file to it, and removing the empty folder should hopefully fix it. But, I ended up needing to add a new variable at the top for DRIARCH to specify i386 or x86_64 since that is how they were stored under /usr/lib/. Changes have been commmitted and pushed, so grab the latest copy and let me know if it works.
I'm not sure why you would need that because the package includes /usr/share/X11/xorg.conf.d/10-amdgpu-pro.conf that contains:
I believed, 'ModulePath "/usr/lib/xorg/modules"' was for 32-bit libraries only. So, I had my .bash_profile build function install modules to /usr/lib64/xorg/modules--which is where my evdev.drv is. I will recompile xserver back to "/usr/lib/xorg/modules" or "/usr/lib64/xorg/modules" instead of "/opt/amdgpu-pro/lib/xorg/modules" to confirm that "/usr/share/X11/xorg.conf.d/10-amdgpu-pro.conf" works by itself.
Sidenote: I'm using universal distro xorg git builder type functions that is able to install multiple versions of X on the same machine without overwriting standard installs--to be released one day for git testers.
I'll checkout the latest amdgpu-pro-driver.SlackBuild.
(EE) AMDGPU(0): Failed to open amdgpu hybrid version
(EE) AIGLX error: DRI driver not found
(EE) AIGLX: reverting to software rendering
(EE) GLX: could not load software renderer
X starts though without an /etc/X11/xorg.conf file.
I will attempt building, into the "opt" directory, mesa through to xserver with the libGL.so amdgpu-pro install using environment variables: GL_LIBS, GL_CFLAGS, LLVM_LIB_SEARCH_PATH, LLVM_LIBDIR, LLVM_LDFLAGS because the libGL* amdgpu-pro drivers don't come with include or *.pc files.
So maybe my steps are:
1) build mesa into opt (to get some includes and *.pc files)
2) install pro drivers over the mesa install
3) build every module after mesa referencing the pro driver opt install.
I think the first is not an issue unless you have a hybrid graphics setup. The others are a little disconcerting, but there's not enough info to troubleshoot. Can you post your whole Xorg.0.log? I can dig into it after work today.
[ 211.437] (WW) AMDGPU(0): Option "VendorName" is not used
[ 211.438] (WW) AMDGPU(0): Option "ModelName" is not used
These two lines occur right before the errors. Is your modeline right around there? I'm not seeing any other reason why this would error here. Is there maybe any messages in dmesg?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
