Video driver error linux OpenSUSE x86_64

Need help running G/Q/ZDoom/ECWolf/Zandronum/3DGE? Did your computer break? Ask here.

Moderator: GZDoom Developers

Video driver error linux OpenSUSE x86_64

Postby 7SyntaxError » Sat Jun 26, 2021 8:05 am

I installed GZdoom from the OpenSUSE Tumbleweed repository. Both Ultimate Doom and Doom 2 worked, but then I started messing with the settings. Specifically I believe that when I toggled the video to Vulkan in Doom 2 it stopped working. Ultimate Doom still works. However now Doom 2 does not work. I tried uninstalling GZdoom and reinstalling. I also tried uninstalling GZdoom again and also deleting the files in Home/.config/gzdoom and then reinstalling, but it still doesn't work. I'm assuming there are files somewhere else in the system that I need to delete or GZdoom modified my video driver files. If it modified any of my video driver files I don't know how to modify them myself or where to find them.

Edit: Ultimate Doom also does not work anymore.

I have OpenSUSE Tumbleweed x86_64 with AMD Oland R7 250 for the GPU.
Here is the output from the terminal:

GZDoom <4.6.0> - - SDL version

Compiled on
OS: openSUSE Tumbleweed, Linux 5.12.12-1-default on x86_64
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
adding /usr/share/doom/gzdoom.pk3, 633 lumps
adding /usr/share/doom/game_support.pk3, 2514 lumps
adding /home/mark/.config/gzdoom/DOOM2.WAD, 2919 lumps
adding /usr/share/doom/game_widescreen_gfx.pk3
, 1 lumps
I_Init: Setting up machine state.
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Family 6, Model 42, Stepping 7
Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX HyperThreading
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
Opened device Built-in Audio Analog Stereo
EFX enabled
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 174.45 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver x11
X connection to :0 broken (explicit kill or server shutdown).
Last edited by 7SyntaxError on Sun Jul 25, 2021 1:08 am, edited 1 time in total.
7SyntaxError
 
Joined: 26 Jun 2021
Operating System: Other Linux 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD with Vulkan Support

Re: Video driver error linux OpenSUSE x64

Postby 7SyntaxError » Sat Jul 24, 2021 10:35 pm

Update and solution:
Posting for reference for anyone else in search.

X connection to :0 broken (explicit kill or server shutdown).

It seems that there is a process taking up the x connection to "display :0" slot where :0 is a variable. I have not been able to isolate which process it is yet. GZDoom flatpak doesn't work under Xorg with my system setup.
However, Wayland does work and seems to be stable. Recommend you use Wayland to run GZDoom when encountering this Xorg error.

Operating System: openSUSE Tumbleweed 20210721
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.13.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 7.7 GiB of RAM
Graphics Processor: AMD OLAND
Last edited by 7SyntaxError on Sun Jul 25, 2021 3:30 am, edited 1 time in total.
7SyntaxError
 
Joined: 26 Jun 2021
Operating System: Other Linux 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD with Vulkan Support

Re: Video driver error linux OpenSUSE x86_64

Postby Rachael » Sun Jul 25, 2021 3:19 am

Wayland with GZDoom is kind of iffy. In most cases it will work just fine but the Wayland spec leaves way too much open for the desktop environment developer and a lot could go wrong.

So if you tell us what desktop environment you're using for the Wayland that would be helpful.

I do know it works with Weston, but it only works properly in fullscreen, there.
User avatar
Rachael
Admin
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Debian-like Linux (Debian, Ubuntu, Mint, etc) 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support

Re: Video driver error linux OpenSUSE x86_64

Postby 7SyntaxError » Sun Jul 25, 2021 3:33 am

Desktop environment underlined below:

Operating System: openSUSE Tumbleweed 20210723
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.13.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 7.7 GiB of RAM
Graphics Processor: AMD OLAND
7SyntaxError
 
Joined: 26 Jun 2021
Operating System: Other Linux 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD with Vulkan Support

Re: Video driver error linux OpenSUSE x86_64

Postby Rachael » Sun Jul 25, 2021 3:40 am

Thanks! That is helpful. :)
User avatar
Rachael
Admin
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Debian-like Linux (Debian, Ubuntu, Mint, etc) 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support


Return to Technical Issues

Who is online

Users browsing this forum: No registered users and 0 guests