[SOLVED] warzone2100 sbo on 14.1 with ati R7 graphics not working.

timsoft · 04-26-2015, 04:15 PM

warzone2100 sbo package compiles, but crashes when you try to play a game (by clicking on new campaign, or tutorial etc).
I am running slackware 14.1 (64bit and 32bit separately, dual boot) on amd A8 7600 APU which has on-chip R7 graphics.
I have installed OpenAL, physfs and quesogl from sbo (and also tried with GLee).I have the proprietary drivers installed (14.501.1003-141120a-178002C) (mainly because celestia and chromium-bsu is unusably slow with the open source ones)
the output I get (when running from Konsole) is below.

Code:

info    |10:03:36: [realmain:1133] Using /root/.warzone2100-3.1/logs/WZlog-0426_220336.txt debug file
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/swrast_dri.so
libGL error: failed to load driver: swrast
popup   |10:03:37: [screenInitialise:187] OpenGL GLSL shader version 1.20 is not supported by your system. Some things may look wrong. Please upgrade your graphics driver/hardware, if possible.
info    |10:03:44: [seq_Play:565] unable to open 'sequences/cam1/c001.ogg' for playback
error   |10:03:46: [initTerrain:803] Your graphics card and/or drivers do not seem to support glDrawRangeElements, needed for the terrain renderer.
error   |10:03:46: [initTerrain:804] - Do other 3D games work?
error   |10:03:46: [initTerrain:805] - Did you install the latest drivers correctly?
error   |10:03:46: [initTerrain:806] - Do you have a 3D window manager (Aero/Compiz) running?
error   |10:03:46: [levLoadData:1038] Failed stageThreeInitialise()!
fatal   |10:03:46: [startGameLoop:771] Shutting down after failure
AL lib: (EE) alc_cleanup: 1 device not closed

I'm sure I'm not the only person running with ati drivers. has anyone found a way to get warzone to work?

pataphysician · 04-26-2015, 05:35 PM

Are you sure you weren't at a root prompt #, when you ran that in Konsole?
because it seems to have the message

using /root/.warzone2100-3.1/logs/WZlog-0426_220336.txt debug file

which seems like it created a debug file under the root users home directory, which would be pretty hard for anybody but root to do.

if so the error message is probably irrelevant, try again at a non root prompt.

timsoft · 04-27-2015, 05:20 AM

I was running as root (xwindows via startx, and logically konsole so root should have full access to the screen/graphics device and stuff), but that seems a fair enough test to see if the software works or not. (I haven't had any issues running anything else as root). I'll try running it as a non-root user, and report back. thanks for the comment.

ReaperX7 · 04-27-2015, 06:08 AM

Quote:

Originally Posted by timsoft

warzone2100 sbo package compiles, but crashes when you try to play a game (by clicking on new campaign, or tutorial etc).
I am running slackware 14.1 (64bit and 32bit separately, dual boot) on amd A8 7600 APU which has on-chip R7 graphics.
I have installed OpenAL, physfs and quesogl from sbo (and also tried with GLee).I have the proprietary drivers installed (14.501.1003-141120a-178002C) (mainly because celestia and chromium-bsu is unusably slow with the open source ones)
the output I get (when running from Konsole) is below.

Code:

info    |10:03:36: [realmain:1133] Using /root/.warzone2100-3.1/logs/WZlog-0426_220336.txt debug file
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/swrast_dri.so
libGL error: failed to load driver: swrast
popup   |10:03:37: [screenInitialise:187] OpenGL GLSL shader version 1.20 is not supported by your system. Some things may look wrong. Please upgrade your graphics driver/hardware, if possible.
info    |10:03:44: [seq_Play:565] unable to open 'sequences/cam1/c001.ogg' for playback
error   |10:03:46: [initTerrain:803] Your graphics card and/or drivers do not seem to support glDrawRangeElements, needed for the terrain renderer.
error   |10:03:46: [initTerrain:804] - Do other 3D games work?
error   |10:03:46: [initTerrain:805] - Did you install the latest drivers correctly?
error   |10:03:46: [initTerrain:806] - Do you have a 3D window manager (Aero/Compiz) running?
error   |10:03:46: [levLoadData:1038] Failed stageThreeInitialise()!
fatal   |10:03:46: [startGameLoop:771] Shutting down after failure
AL lib: (EE) alc_cleanup: 1 device not closed

I'm sure I'm not the only person running with ati drivers. has anyone found a way to get warzone to work?

Can you run:

Code:

glxinfo | grep OpenGL

and post the output?

timsoft · 04-27-2015, 08:44 AM

response to pataphysician - it makes no difference running xwindows and warzone2100 as a non-root user
to ReaperX7 the output of glxinfo|grep OpenGL is as follows.

Code:

glxinfo|grep OpenGL
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: AMD Radeon(TM) R7 Graphics   
OpenGL version string: 1.4 (2.1 (4.4.13283 Compatibility Profile Context 14.501.1003))
OpenGL extensions:

sovietpower · 04-27-2015, 01:20 PM

Your graphics hardware acceleration isn't working. Can you try installing this?

http://support.amd.com/en-us/kb-arti...ta-driver.aspx

Code:

unzip ati-blah-blah-blah.zip
cd fglrx-14.20
chmod +X amd-driver-installer-14.20-x86.x86_64.run
./amd-driver-installer-14.20.-x86.x86_64.run

Follow the on screen instructions.

Also, rule of thumb is, don't run X as root.

ReaperX7 · 04-27-2015, 03:00 PM

If libGL isn't found or not loading could be a permission error.

Try adding your user to the "video" group.

Otherwise, as stated you'll have to install the driver to use it. If you are running the latest mesa, libdrm, kernel, and xf86-video-ati packages from Slackware (check -Current for them if needed), you can try to get the Radeon driver working. You might need libtxc_dxtn from SlackBuilds.org to give proper texture compression support. If you need to setup the driver, use DRIConf from SlackBuilds.org also.

The Proprietary/OEM driver will have varied results. Often these drivers do work, but not very well. Catalyst-14.12 should work for your R7. Just follow the instructions on how to install it.

timsoft · 04-27-2015, 03:38 PM

thanks for the pointers. I did download the latest (beta) driver (again). went through the "create a package" option (it detected slackware). it created fglrx-14.20-x86_64-1.tgz
which I re-installed. (it is what I had before). I get 5900 fps for glx gears, and the same error in warzone2100. my (non-root) user is in the video group, amongst a lot of others.
the link posted above takes you to the 14.6 beta drivers. the 14.12 release drivers found here
have this to say about themselves.

Quote:

32-Bit packages must be installed for 64-Bit Linux drivers to install or work.

I already went through a question on LQ about that see here
everything seemed ok (well celestia worked), until I tried with warzone2100.
as per that previous thread, I am trying to keep pure 64bit, to avoid multilib complications, and because I use 64bit (and 32bit seperately) for testing various slackbuilds.

do you think it is a "32 bit" issue.? I'll reboot into 32bit slackware 14.1 (which has the same ati driver) and see if it works there, and will post back here. I'll also download the release driver (14.12) and try that as well.

timsoft · 04-27-2015, 05:01 PM

it gives the same error in pure 32bit slackware 14.1
I tried installing the 14.12 release drivers. they appear to be the same as the beta ones (at list when you extract the zip, the fglrx version is the same.
setting LIBGL_DEBUG=verbose; export LIBGL_DEBUG
then running glxinfo gives a little more help

Code:

name of display: :0
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/swrast_dri.so
libGL error: failed to load driver: swrast
display: :0  screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: ATI
server glx version string: 1.4

a google for a solution hasn't worked so far.

ReaperX7 · 04-28-2015, 03:52 AM

Check your /etc/X11/xorg.conf and post it here. Maybe one of the settings isn't right.

timsoft · 04-28-2015, 07:11 AM

here is my xorg.conf

Code:

Section "ServerLayout"
	Identifier     "aticonfig Layout"
	Screen      0  "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Module"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]-0"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]-0"
	Driver      "fglrx"
	BusID       "PCI:0:1:0"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]-0"
	Device     "aticonfig-Device[0]-0"
	Monitor    "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

as you can see, very generic, created by aticonfig --initial
the attached monitor is a vga lcd screen 1680x1050 resolution, which is detected and runs at that resolution in both 64 and 32bit versions of slackware 14.1 (and windows 7).

ReaperX7 · 04-28-2015, 12:32 PM

Code:

Section "Module"
EndSection

That looks a bit bare.

Usually it has entries like.

Code:

Section "Module"
            Load       "glx"
EndSection

Do you have any files in directory /etc/X11/xorg.conf.d?

timsoft · 04-28-2015, 01:21 PM

nope. /etc/X11/xorg.conf.d directory is completely empty.
I tried adding a Load "glx" line in the Module section, but it seemed to make no difference. same message with glxinfo.

if it helps, the output when running celestia (which runs just fine) is below

Code:

libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Initializing ARB vertex programs . . .
Loading ARB vertex program: shaders/diffuse_arb.vp
Loading ARB vertex program: shaders/specular_arb.vp
Loading ARB vertex program: shaders/haze_arb.vp
Loading ARB vertex program: shaders/bumpdiffuse_arb.vp
Loading ARB vertex program: shaders/bumphaze_arb.vp
Loading ARB vertex program: shaders/shadowtex_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff_arb.vp
Loading ARB vertex program: shaders/rings_arb.vp
Loading ARB vertex program: shaders/ringshadow_arb.vp
Loading ARB vertex program: shaders/night_arb.vp
Loading ARB vertex program: shaders/glossmap_arb.vp
Loading ARB vertex program: shaders/diffuse2_arb.vp
Loading ARB vertex program: shaders/haze2_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff2_arb.vp
Loading ARB vertex program: shaders/specular2_arb.vp
Loading ARB vertex program: shaders/night2_arb.vp
Loading ARB vertex program: shaders/star_arb.vp
Loading ARB vertex program: shaders/multishadow_arb.vp
Loading ARB vertex program: shaders/texphong_arb.vp
Loading ARB vertex program: shaders/texphong_alpha_arb.vp
Loading ARB vertex program: shaders/ell_galaxy_arb.vp
All ARB vertex programs loaded successfully.                                                               
render path: 3

I'm nor sure why swrast is trying to be loaded by both, but celestia must ignore it and runs anyway (I assume that opengl functions are all in the hardware or fglrx driver, so swrast isn't really needed).

I did spot that under system settings-desktop effects some effects (blur, startup feedback and wobbly windows) could not be loaded with message saying the effect requires OpenGL which leads me to think that some software is not recognising the fglrx opengl implementation

ReaperX7 · 04-29-2015, 05:34 AM

If swrast is loading it means there is a driver failure. You might want to try removing the AMD driver and reinstall the mesa package. Afterwards, just use the free driver. It should work.

The glxinfo readout should report back as AMD FGLRX rather than swrast.

pataphysician · 04-29-2015, 07:30 AM

you might want to check for any errors in
/usr/share/ati/fglrx-install.log

also have you checked that you have a file in /etc/modprobe.d/ that blacklists the radeon driver, this would be the open source driver and it needs to be blacklisted

If nothing comes up wrong on the above, I would remove the fglrx slackware package you built and try again installing fglrx and choosing not to make a slackware package method. At least for me on R9 280x using the create a slackware package, results in no 32 bit drivers on my multilib system, there could be other issues as well, I doubt amd does any bug testing or anything on their slackware package building code. After reinstalling again check the fglrx-install.log

If later you need to remove this fglrx driver built without making a slackware package, there is a script in /usr/share/ati/amd-unistall.sh