[SOLVED] Help Me Fix My Video Card Problems: nvidia

seth · 2023-01-30 17:46:25

Steam: An X Error occurred
X Error of failed request:  GLXBadDrawable
Major opcode of failed request:  152
Serial number of failed request:  122

This is new, way more interesting and cycles back to your GPU.

glxinfo -B
glxinfo32 -B

/home/desktop/.local/share/Steam/steam.sh

pacman -Qs steam

josephgerth · 2023-01-30 17:58:30

$ glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 5604 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 525.85.05
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 525.85.05
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 525.85.05
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

$ glxinfo32 -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 5616 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 525.85.05
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 525.85.05
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 525.85.05
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

$ pacman -Qs steam

local/python-steamgriddb 1.0.5-1
    Python API wrapper for SteamGridDB.com
local/steam 1.0.0.75-1
    Valve's digital software delivery system
local/steam-native-runtime 1.0.0.75-2
    Native replacement for the Steam runtime using system libraries
local/steamcmd latest-3
    Steam Command Line Tools

d.ALT · 2023-01-30 19:15:14

Do you have any game(s) installed onto ArchLinux's root (sda3 in your case)?
Look at your Steam's Library for game(s) installed in your / (root): can you start / play any of these?

josephgerth · 2023-01-30 19:55:51

I installed one game (Lethal League) on my root folder. It ran. Shovel Knight (for example) was on my sdd partition and did not run. Moving it to my root partition (sda3) did not work. I get the same result.

EDIT: I should add, that all of my games are on sdd. Several continue to work just fine; I just tested Torchlight, for example.

Last edited by josephgerth (2023-01-30 20:02:28)

josephgerth · 2023-01-30 20:38:42

Update: I found a few workarounds!

I started by searching for info on Huntdown, a game I hadn't really cared to play, but still had the same issue. I found a launch option from a Discussion post on that game's board (titled "Black screen after starting") that suggested a windowed launch. I input this option, and the game launched just fine!

I then investigated a similar fix for Shovel Knight, which I found. The key is to go to the folder in steamapps and open render.bin and change the fullscreen value. For some reason, my value was at 2? (I assume 0 means no fullscreen and 1 means fullscreen? surely there isn't another option?)

These are workarounds, but I fear I haven't solved my root problem. One of the threads suggested that there is a bug in Unity?

Thanks for everyone's help---It seems that I will need to avoid fullscreen on some games!

seth · 2023-01-30 20:56:06

xrandr -q

Do you have more or less luck w/ the native runtime?
https://wiki.archlinux.org/title/Steam/ … am_runtime

josephgerth · 2023-01-30 21:26:39

$ xrandr -q

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm
   1920x1080     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)

seth · 2023-01-30 21:34:05

That's really as basic as can be - did you maybe configure an incompatible resolution in-game (1280x960, 1400x900, 1368x768, 1280x720, …)?

seth also wrote:

Do you have more or less luck w/ the native runtime?

josephgerth · 2023-01-30 22:09:13

As far as I can tell, there is no difference between steam, steam-native, and steam-runtime. I ran Crosscode on all three versions, and they each have the same issue (launches fullscreen, but only half the screen shows up?)

seth · 2023-01-30 22:15:23

launches fullscreen, but only half the screen shows up

Is half the screen black or half of the game outside the screen?

josephgerth · 2023-01-30 22:20:10

Half 1

Half 2

Last edited by josephgerth (2023-01-30 23:13:59)

seth · 2023-01-30 22:22:39

Please replace the oversized images w/ links.
If you use

xrandr --output DVI-D-0 --mode 1280x1024

, des the game then work as expected?

josephgerth · 2023-01-30 23:15:41

Nope; still split down the middle.

V1del · 2023-01-31 00:33:24

Looks like something being off with the WM/the WM enforcing a certain tiling that confuses the game, what is this? Tried something bog standard like openbox or so? Tried to force the window to be floating?

Last edited by V1del (2023-01-31 00:51:52)

josephgerth · 2023-01-31 02:07:43

I use Luke Smith's version of dwm.

I thought of that; and I have tried various tiling arrangements, including floating mode (a non-tiling arrangement). It has no effect.

Plus, some games start up just fine, as I've mentioned. This includes games that waltz right into fullscreen mode with nary a hitch.

I could try a different flavor of dwm... but I do really love this build!

seth · 2023-01-31 08:23:58

You could briefly try openbox to see whether it's dependent on the WM itfp and if so, file a bug against your WM.
I suspect the game doesn't actually flag itself as fullscreen, but tries to fake fullscreen behavior - check "xprop" on it.

josephgerth · 2023-02-01 02:45:19

Uhhh... Dumb question. How do I quickly switch windows managers? I tried to use openbox, but "A window manager is already running on screen 0".

I tried openbox --replace, and got the same message.

I tried killall dwm && openbox

and then got thrown back to tty where I could not log in; my xorg.conf was deleted so no screens were found (I tried both openbox and startx; neither worked).

I used sudo nvidia-xconfig to get a new xorg.conf, which got me back in through startx.

After trying killall dwm && openbox, I then tried to type in openbox. It says that it cannot open the display. I also tried i3; it gives me a simple "cannot open display."

This has to be easier than I am making it and I feel a bit embarrassed that I can't do what should be a simple task for any arch user!

seth · 2023-02-01 06:48:57

By replacing dwm w/ openbox or openbox-session in your xinitrc.

Sidebar:

my xorg.conf was deleted so no screens were found (I tried both openbox and startx; neither worked).
I used sudo nvidia-xconfig to get a new xorg.conf, which got me back in through startx.

Something's very fucked up then.
Remove the xorg.conf, try to startx and then post the xorg log, it's either in /var/log or ~/.local/share/xorg

josephgerth · 2023-02-01 12:23:09

Figured out the wm; Openbox has the same issue with Crosscode; only a quarter of it rendered, and it should have. I don't know how to take screenshots on Openbox so I did not do that, but if you look at my previous images, it's basically the same thing.

I notice that there is a patch for dwm, which I thought about trying, but if it's not related to the wm this might not be worth my time.

I have not tried your other suggestion yet; I'm busy today so I will wait until Thursday to give that a go. Thanks for your patience with this issue!

seth · 2023-02-01 12:49:58

While at it, run "xwininfo -all" and "xprop" on the window and post the outputs.

josephgerth · 2023-02-02 12:30:01

Quick note: The problem with Crosscode has nothing to do with my bigger issues; ProtonDB says it's a problem on the end of the developers. I followed the suggestions on that page (using compatibility mode) and now the game works well.

V1del · 2023-02-02 13:21:42

If that is the case, do you actually still have any "bigger" issues, that doesn't amount to game quirks explained in the protondb? Just from a general setup perspective based on the outputs you posted the general config seems to be correct now.

If none of these remain, please mark the topic as [SOLVED] by editing the title in your first post.

josephgerth · 2023-02-03 02:31:29

Summary of problems:

1. [Solved!] Steam is reading my graphics card as Mesa, when it should be nvidia.

2. [Solved!] Get games like Shovel Knight working.

3. [Solved!] Get Crosscode working. By switching to compatibility mode, the game runs as it should (including in fullscreen mode!) I only ran the game for 5 minutes on testing, but I will mark this as solved.

4. [Not solved] While games like Shovel Knight run, they only run in windowed mode. They will not run in full screen mode. Even in windowed mode, they do not run at full speed (is there a way to measure the FPS in Steam games?)

5. [Not solved] Why won't steam's Big Picture Mode work? It crashes within a few seconds. This is a feature that I almost never use, but I'm wondering if it provides a clue to help fix my setup.

I'm happy to mark this as solved for now, if you want.

seth · 2023-02-03 07:48:38

4. [Not solved] While games like Shovel Knight run, they only run in windowed mode. They will not run in full screen mode. Even in windowed mode, they do not run at full speed (is there a way to measure the FPS in Steam games?)

seth wrote:

While at it, run "xwininfo -all" and "xprop" on the window and post the outputs.

5. [Not solved] Why won't steam's Big Picture Mode work? It crashes within a few seconds. This is a feature that I almost never use, but I'm wondering if it provides a clue to help fix my setup.

Backtrace or steam console output?

josephgerth · 2023-02-04 04:00:45

OK... I fiddled around some more and made it worse. It turns out that my 1. has not yet been solved...

I patched my dwm with a Steam patch; this succeeded, so I went to reboot to load up xorg and thus restart my dwm properly. But, upon logging back in, I cannot get arch to find my nvidia driver again! I thought I went through the same steps as before, but alas:

$ glxinfo -B

name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa/X.org (0xffffffff)
    Device: llvmpipe (LLVM 15.0.7, 256 bits) (0xffffffff)
    Version: 22.3.4
    Accelerated: no
    Video memory: 15957MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.3.4
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.3.4
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

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

The go-to advice seems to be to delete /etc/X11/xorg.conf; but if I do that, tty tells no screens are found, and I therefore cannot start my wm. I can, as I mentioned before, get into root and run commands from the command line. The only way to log back into my wm is to use

$ sudo nvidia-xconfig

which creates a new xorg.conf file.

I have not changed anything nvidia related... I don't think. My /etc/mkinitcpio.conf file is still the same, and that should be calling modules for early loading; I have run

$ sudo mkinitcpio -P linux

to try and get everything linked; I get no errors.

So... it's clear that I have some kind of deeper issue going on here, and it might just be that I'm in over my head! At what point is a simple re-install suggested? I do want to learn these things but there are more important things for me to work on!

Last edited by josephgerth (2023-02-04 04:02:23)

Arch Linux

#26 2023-01-30 17:46:25

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#27 2023-01-30 17:58:30

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#28 2023-01-30 19:15:14

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#29 2023-01-30 19:55:51

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#30 2023-01-30 20:38:42

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#31 2023-01-30 20:56:06

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#32 2023-01-30 21:26:39

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#33 2023-01-30 21:34:05

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#34 2023-01-30 22:09:13

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#35 2023-01-30 22:15:23

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#36 2023-01-30 22:20:10

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#37 2023-01-30 22:22:39

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#38 2023-01-30 23:15:41

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#39 2023-01-31 00:33:24

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#40 2023-01-31 02:07:43

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#41 2023-01-31 08:23:58

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#42 2023-02-01 02:45:19

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#43 2023-02-01 06:48:57

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#44 2023-02-01 12:23:09

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#45 2023-02-01 12:49:58

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#46 2023-02-02 12:30:01

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#47 2023-02-02 13:21:42

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#48 2023-02-03 02:31:29

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#49 2023-02-03 07:48:38

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

#50 2023-02-04 04:00:45

Re: [SOLVED] Help Me Fix My Video Card Problems: nvidia

Board footer