You are not logged in.

#51 2022-11-20 13:10:06

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

I installed Xonotic from the AUR, since i'm mostly familiar with it. Running the game using xonotic-glx results in the game using the Intel card, when tried running using DRI_PRIME=1 mangohud xonotic-glx the game runs on the AMD Graphics, plays just a few miliseconds of music and freezes. using DRI_PRIME=1 xonotic-glx results in the game using the Intel card.

pacman -Qs xf86- :

local/xf86-input-libinput 1.2.1-1 (xorg-drivers)
    Generic input driver for the X.Org server based on libinput
local/xf86-video-amdgpu 22.0.0-1 (xorg-drivers)
    X.org amdgpu video driver
local/xf86-video-nouveau 1.0.17-2 (xorg-drivers)
    Open Source 3D acceleration driver for nVidia cards
local/xf86-video-vmware 13.3.0-4 (xorg-drivers)
    X.org vmware video driver

Offline

#52 2022-11-20 20:37:13

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

xf86-video-nouveau is only useful for (some) nvidia cards.
xf86-video-vmware is meant to be used inside a archlinux guest VM and is useless in any other situation.
Please remove both.

for testing purposes you want a simple setup with a low number of unknowns .

I installed Xonotic from the AUR

Aur builds are of unknown quality and incorrect build environments can cause runtime errors. In short : they add unknowns .

Xonotic is in community repo  , use that.

Mangohud also adds unknowns, don't use it while testing.

sanity check :
post output of

$ glxinfo -B
$ DRI_PRIME=1 glxinfo -B

.

Last edited by Lone_Wolf (2022-11-20 20:37:41)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#53 2022-11-21 17:12:59

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

I removed the said packages from the system with Xonotic, and reinstalled it from the Community Repo.

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 520 (SKL GT2) (0x1916)
    Version: 22.2.3
    Accelerated: yes
    Video memory: 7731MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

DRI_PRIME=1 glxinfo -B :

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon R5 M330 (hainan, LLVM 14.0.6, DRM 3.48, 6.0.8-arch1-1) (0x6660)
    Version: 22.2.3
    Accelerated: yes
    Video memory: 2048MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 2041 MB, largest block: 2041 MB
    VBO free aux. memory - total: 3852 MB, largest block: 3852 MB
    Texture free memory - total: 2041 MB, largest block: 2041 MB
    Texture free aux. memory - total: 3852 MB, largest block: 3852 MB
    Renderbuffer free memory - total: 2041 MB, largest block: 2041 MB
    Renderbuffer free aux. memory - total: 3852 MB, largest block: 3852 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 2048 MB
    Total available memory: 5913 MB
    Currently available dedicated video memory: 2041 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon R5 M330 (hainan, LLVM 14.0.6, DRM 3.48, 6.0.8-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Offline

#54 2022-11-22 11:45:19

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

The glxinfo outputs match with a PRIME system running X .

It appears Xonotic has 3 commands that can start it :
usr/bin/xonotic-dedicated
usr/bin/xonotic-glx
usr/bin/xonotic-sdl

That does suggest it doesn't use PRIME (or maybe it forces PRIME)

Try running xonotic-glx and xonotic-dedicated .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#55 2022-11-23 13:29:04

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

xonotic-dedicated seems to be the server software for the game, xonotic-glx starts with the Intel card using the command xonotic-glx with no parameters or nothing.

using DRI_PRIME=1, the game launches and freezes after a very short while.

Last edited by rktf (2022-11-24 16:16:02)

Offline

#56 2022-11-24 16:52:52

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

Guess we need to check something else.

install knetwalk from extra and run it from terminal with DRI_PRIME=1 .
Play it, and check if the rotation of elements is smooth

If there's any output in terminal, post it .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#57 2022-11-24 16:59:14

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

I installed and ran knetwalk with DRI=PRIME=1, in the windowed mode i played a round and it was all fine. However when i tried to set it to fullscreen it created some graphical glitches and froze completely. There are no outputs in the terminal.

Last edited by rktf (2022-11-24 17:11:58)

Offline

#58 2022-11-25 10:15:41

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

Does running it on the intel card work fine on both windowed & full screen ?

Install a simple WM like openbox and try running knetwalk with PRIME there .
Does full screen also freeze / crash ?

Note : if you don't want / like openbox any Xorg Window Manager without a compositor is ok .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#59 2022-11-25 12:35:17

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

Intel card (running knetwalk without DRI) runs absolutely fine, i tried resizing it a few times and it never had an issue.

I used openbox for the WM, since i had it installed, and i use Plasma/Openbox time to time (the previous tests were made with regular Plasma/X11), Intel card once again works fine, AMD Card freezes the whole desktop when full screened. When it happens, i can't interact with anything nor close knetwalk, shutting the system down shows two amdgpu related errors :

Nov 25 15:14:11 rkpc kernel: Asynchronous wait on fence drm_sched:gfx:16e timed out (hint:submit_notify [i915])
Nov 25 15:14:11 rkpc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=555, emitted seq=557
Nov 25 15:14:11 rkpc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Nov 25 15:14:11 rkpc kernel: amdgpu 0000:01:00.0: amdgpu: GPU recovery disabled.

Also it seems like knetwalk and Xorg doesn't stop and require me to wait around two minutes before the computer finally shuts down.

Offline

#60 2022-11-26 17:43:58

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

so not a (X or wayland) compositor issue, but a driver crash at kernel level .

can you post the full journal from that crash ?
https://wiki.archlinux.org/title/System … ing_output for info how to retrieve older parts of journal.

With such crashes the system is often unresponsive, see https://wiki.archlinux.org/title/Keyboa … el_(SysRq) for options to allow some things.

Could you try installing linux-lts and boot that to verify if that has this also ?
(linux and linux-lts coexist fine, but you'll need to configure your bootloader to be able to choose between them at boottime. how to do that depends on your bootloader)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#61 Yesterday 18:33:24

rktf
Member
Registered: 2022-11-04
Posts: 31

Re: Graphics Card not detected

Since i was unable to find the old entry, i went ahead and replicated the steps to get a new one.

I tested both with Linux Kernel and Linux-lts kernel, I hope it's not a problem since i can verify the driver errors are logged in these ones aswell.

Offline

#62 Today 13:55:56

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,495

Re: Graphics Card not detected

The linux kernel log doesn't include the crash, but the linux-lts log does.

I"ve found plenty of reports with similar messages, https://gitlab.freedesktop.org/drm/amd/-/issues/1915 seems relevant .

especially this comment from alex deucher :

https://gitlab.freedesktop.org/drm/amd/-/issues/1915#note_1639070 wrote:

If you are getting a reproducible hang related to a specific app, please file a new mesa/mesa ticket.

I suggest you file an issue at https://gitlab.freedesktop.org/mesa/mesa/-/issues and post the link to the issue.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

Board footer

Powered by FluxBB