Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 662282 - x11-drivers/xf86-video-amdgpu: fails loading with undefined symbol: fbImageGlyphBlt
Summary: x11-drivers/xf86-video-amdgpu: fails loading with undefined symbol: fbImageGl...
Status: RESOLVED DUPLICATE of bug 661502
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-27 17:19 UTC by Niklas Haas
Modified: 2018-08-01 22:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (file_662282.txt,7.75 KB, text/plain)
2018-07-27 17:19 UTC, Niklas Haas
Details
xorg log (file_662282.txt,4.23 KB, text/plain)
2018-07-27 17:20 UTC, Niklas Haas
Details
build log (file_662282.txt,26.77 KB, text/plain)
2018-07-27 17:20 UTC, Niklas Haas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Niklas Haas 2018-07-27 17:19:41 UTC
Created attachment 541296 [details]
emerge --info

The built amdgpu_drv.so fails loading for me. Attached are all relevant logs.
Comment 1 Niklas Haas 2018-07-27 17:20:18 UTC
Created attachment 541318 [details]
xorg log
Comment 2 Niklas Haas 2018-07-27 17:20:59 UTC
Created attachment 541338 [details]
build log
Comment 3 Niklas Haas 2018-07-27 17:21:46 UTC
Upon advice from #radeon I tried removing -Wl,--as-needed from the linker flags (by manually editing the generated Makefile before the compile step), but this did not change anything.
Comment 4 Niklas Haas 2018-07-27 17:27:12 UTC
FWIW I tried the following configurations:

- libdrm-9999 + mesa-9999 + xf86-video-amdgpu-9999
- libdrm-2.4.92 + mesa-18.1.4 + xf86-video-amdgpu-18.0.1-r1

I did not yet try other gcc versions.
Comment 5 Enne Eziarc 2018-08-01 15:10:41 UTC
Same error with -18.0.1-r1 and -9999 here.

The workaround at https://forums.freebsd.org/threads/x-org-failed-to-load-module-radeon.59717/#post-343120 works for me, FWIW.
Comment 6 Niklas Haas 2018-08-01 16:37:24 UTC
> The workaround at https://forums.freebsd.org/threads/x-org-failed-to-load-module-radeon.59717/#post-343120 works for me, FWIW.

That one works for me too. I forgot to mention this.
Comment 7 Alexander Tsoy 2018-08-01 17:20:04 UTC
(In reply to Niklas Haas from comment #2)
> Created attachment 541338 [details]
> build log
That's interesting. Your link command:

libtool: link: x86_64-pc-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/amdgpu_video.o .libs/amdgpu_misc.o .libs/amdgpu_probe.o .libs/amdgpu_bo_helper.o .libs/amdgpu_dri2.o .libs/amdgpu_dri3.o .libs/amdgpu_drm_queue.o .libs/amdgpu_kms.o .libs/amdgpu_present.o .libs/amdgpu_sync.o .libs/drmmode_display.o .libs/amdgpu_glamor.o .libs/amdgpu_glamor_wrappers.o .libs/amdgpu_pixmap.o   -Wl,--as-needed -ldrm_amdgpu -lgbm -L/lib64 -ludev  -march=native -O2 -g -Wl,-O1   -Wl,-soname -Wl,amdgpu_drv.so -o .libs/amdgpu_drv.so


My link command:

libtool: link: x86_64-pc-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/amdgpu_video.o .libs/amdgpu_misc.o .libs/amdgpu_probe.o .libs/amdgpu_bo_helper.o .libs/amdgpu_dri2.o .libs/amdgpu_dri3.o .libs/amdgpu_drm_queue.o .libs/amdgpu_kms.o .libs/amdgpu_present.o .libs/amdgpu_sync.o .libs/drmmode_display.o .libs/amdgpu_glamor.o .libs/amdgpu_glamor_wrappers.o .libs/amdgpu_pixmap.o   -ldrm_amdgpu -lgbm -L/lib64 -ludev  -O2 -march=bdver2 -mtune=bdver2 -mno-tbm -mno-fma4 -mno-xop -mno-lwp -Wl,-O1 -Wl,--as-needed   -Wl,-soname -Wl,amdgpu_drv.so -o .libs/amdgpu_drv.so

As you can see, the position of "-Wl,--as-needed" argument is different. What if you downgrade libtool and elt-patches to their stable versions (libtool-2.4.6-r3 and elt-patches-20170815)?
Comment 8 Alexander Tsoy 2018-08-01 18:14:44 UTC
Ah, sorry, forget what I said. 18.0.1-r1 doesn't run elibtoolize.
Comment 9 Alexander Tsoy 2018-08-01 18:50:39 UTC
This is a dupe of bug 661502
Comment 10 Chí-Thanh Christopher Nguyễn gentoo-dev 2018-08-01 22:06:39 UTC

*** This bug has been marked as a duplicate of bug 661502 ***