General TC > General TC Talk
TC64 unable to get Xorg 3d with an AMD APU video on 14x RC1
aus9:
Hi
I am aware that running TC64 14x when its not yet final is an issue.
However I have previously has glxgears running on at least 11x and vulkan cube spinning on sway on 11x.
I do have a reasonable 2d setup as follows:
--- Code: ---inxi -Gxxx
Graphics:
Device-1: AMD driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,HDMI-A-2 bus-ID: 26:00.0
chip-ID: 1002:15d8 class-ID: 0300 temp: 30.0 C
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) FULL HD
res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.63")
diag: 551mm (21.7") modes: max: 1920x1080 min: 720x400
API: OpenGL Message: Unable to show GL data. Required tool glxinfo
missing.
--- End code ---
There is a post of another member with a different AMD APU (graphics supplied by CPU) and the inspection of his log suggested amongst other things a bug in llvm.
I do not have any xorg.conf, or component under ../xorg.conf.d
Nor do I have any bootloader config attempting any blacklist or resolution etc
I load Xorg-7.7-3d and exit to prompt
at console
--- Code: ---sudo su
Xorg -configure
X -config /root/xorg.conf.new
--- End code ---
I wait a while then get the failed wait for X message.
For those interested I have made my log a txt file and it should be clickable
https://www.dropbox.com/s/ltdjss9da0aou0b/xorg-log.txt
To save you clicking it....here is the relevant error msg
--- Quote ---[ 141.425] (EE) Backtrace:
[ 141.439] (EE) 0: /usr/local/lib/xorg/Xorg (xorg_backtrace+0x56) [0x5647b3f76d3f]
[ 141.439] (EE) 1: /usr/local/lib/xorg/Xorg (0x5647b3e78000+0xfee1a) [0x5647b3f76e1a]
[ 141.440] (EE) 2: /lib/libc.so.6 (0x7f504e06a000+0x36870) [0x7f504e0a0870]
[ 141.440] (EE) 3: /lib/libc.so.6 (0x7f504e06a000+0x700db) [0x7f504e0da0db]
[ 141.440] (EE) 4: /lib/libc.so.6 (gsignal+0x12) [0x7f504e0a07ff]
[ 141.440] (EE) 5: /lib/libc.so.6 (abort+0xd3) [0x7f504e090419]
[ 141.440] (EE) 6: /lib/libc.so.6 (__assert_fail+0x0) [0x7f504e09af28]
[ 141.440] (EE) 7: /lib/libc.so.6 (__assert_perror_fail+0x0) [0x7f504e09af6c]
[ 141.440] (EE) 8: /usr/local/lib/libLLVM-13.so (0x7f5048684000+0x917de0) [0x7f5048f9bde0]
[ 141.440] (EE) 9: /usr/local/lib/libLLVM-13.so (0x7f5048684000+0x92fb8a) [0x7f5048fb3b8a]
[ 141.440] (EE) 10: /usr/local/lib/libLLVM-13.so (LLVMBuildInBoundsGEP2+0x51) [0x7f5048fb3c7d]
[ 141.441] (EE) 11: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x924823) [0x7f504cb7d823]
[ 141.441] (EE) 12: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x599b40) [0x7f504c7f2b40]
[ 141.441] (EE) 13: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x59df2a) [0x7f504c7f6f2a]
[ 141.441] (EE) 14: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x9b0102) [0x7f504cc09102]
[ 141.441] (EE) 15: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x522cc4) [0x7f504c77bcc4]
[ 141.441] (EE) 16: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x523b72) [0x7f504c77cb72]
[ 141.441] (EE) 17: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x524f83) [0x7f504c77df83]
[ 141.441] (EE) 18: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0x53d87b) [0x7f504c79687b]
[ 141.441] (EE) 19: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0xa246a) [0x7f504c2fb46a]
[ 141.441] (EE) 20: /usr/local/lib/dri/radeonsi_dri.so (0x7f504c259000+0xda8c8) [0x7f504c3338c8]
[ 141.441] (EE) 21: /lib/libc.so.6 (0x7f504e06a000+0x6e835) [0x7f504e0d8835]
[ 141.441] (EE) 22: /lib/libc.so.6 (0x7f504e06a000+0xd3dcc) [0x7f504e13ddcc]
[ 141.441] (EE)
[ 141.441] (EE)
Fatal server error:
[ 141.441] (EE) Caught signal 6 (Aborted). Server aborting
--- End quote ---
Of interest to me....that you might miss....I think there is some strangeness with my input devices in log
--- Quote ---[ 140.333] (**) ModulePath set to "/usr/local/lib/xorg/modules"
[ 140.333] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 140.333] (WW) Disabling Mouse0
[ 140.333] (WW) Disabling Keyboard0
--- End quote ---
slightly offtopic....but proof that its not my bios settings.....I have another distro installed and glxgears runs well there.
On that other distro it uses amdgpu not the radeon driver FWIW
I do not run sway on that other distro.
Thanks for reading
curaga:
Your log shows the same issue, a llvm assert.
aus9:
thanks for confirming its only llvm.
Juanito:
Mesa has been recompiled against llvm-15 in 14.x x86_64 - testing would be welcome by users with amd or radeon hardware.
aus9:
Hi Rich
Others may reply here so please do not mark as solved at this early stage please.
Juanito
thankyou thankyou thankyou.
Firstly bootlist takes me to Xorg 2d. I then exit to console prompt and load 3d with no attempt to make an xorg.conf
--- Code: ---startx
--- End code ---
launches 3d as expected.
I can upload 3d xorg.log later which I have saved but main details are as follows
1) Xorg 3d needed no xorg.conf as Curaga as prev mentioned it should be confless for most users
2) glxgears from mesa-demos spins as expected close to my frame rate as per code box
--- Code: ---glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
SNIP
301 frames in 5.0 seconds = 60.004 FPS
SNIP
tc@box:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
1920x1080 60.00*+ 74.97 59.96 50.00 59.94 59.93
--- End code ---
3) I can now get into sway on wayland. llvm was the party stopper until upgrade
4) inxi provides good information for those who like such.....as the Xorg logs as you know only need snippets IMHO
--- Code: ---inxi -Gxxx # on Xorg-7.7-3d, actually this is the second capture I forgot to capture it before launching sway, so ignore xwayland
Graphics:
Device-1: AMD driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,HDMI-A-2 bus-ID: 26:00.0
chip-ID: 1002:15d8 class-ID: 0300 temp: 29.0 C
Display: server: X.Org v: 1.21.1.6 with: Xwayland v: 21.1.4 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) FULL HD
res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.63")
diag: 551mm (21.7") modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.7 renderer: AMD Radeon Vega 8 Graphics
(raven LLVM 15.0.7 DRM 3.49 6.1.2-tinycore64) direct-render: Yes
--- End code ---
logout and launch sway give me
--- Code: ---inxi -Gxxx # on wayland
Graphics:
Device-1: AMD driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,HDMI-A-2 bus-ID: 26:00.0
chip-ID: 1002:15d8 class-ID: 0300 temp: 30.0 C
Display: wayland server: X.org with: Xwayland v: 21.1.4 compositor: sway
v: 1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 hz: 60
dpi: 102 scale: 1 size: 480x270mm (18.9x10.63") diag: 551mm (21.7") modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.7 renderer: AMD Radeon Vega 8 Graphics
(raven LLVM 15.0.7 DRM 3.49 6.1.2-tinycore64) direct-render: Yes
--- End code ---
If others are reading this.....the key points are the "Display driver", the result for direct-render
and if they work.....expect API results similar to last lines
Trivia IMHO
Xorg would show multiple loading and unloading of various drivers, inxi summarises this part of the Xorg log
Unloading fbdev
Unloading vesa
and key snippet from log
--- Quote ---Server terminated successfully
--- End quote ---
There are no errors in my log according to my eyesight
Navigation
[0] Message Index
[#] Next page
Go to full version