After installing Linux Mint KDE 17.1 automatically was used xorg driver and textures in games such as X3 Terran Conflict, Star Conflict is black.
With proprietary driver fglrx 2:13.350.1-0ubuntu2 textures looks fine, but shockwave flash works bad (freezes and other).
Current version of xorg driver is 1:7.5.99+git1501140731.c80ea1~gd~t.
My videocard is ATI Radeon mobility HD 5650.
I don't know what to do.
If I need to attach something, please discribe how to do it, thanks.
Sounds like you might need to install libtxc-dxtn0 for S3TC support.
My system already have latest libtxc-dxtn-s2tc0
When I launching X3TC game through console, after appearing of game menu, in console I just see something like "can not to load texture, using dummy... can not load dummy..." and this message repeating infinitely.
I guess X3TC is a 32-bit game. Do you have the libtxc-dxtn-s2tc0 32-bit version, and not only the 64-bit one ?
Also, what give this command:
$ glxinfo |grep "GL_EXT_texture_compression_s3tc"
How to check version of libtxc-dxtn-s2tc0 ?
grimdoll@grimdoll-Aspire-5740:~ > glxinfo |grep "GL_EXT_texture_compression_s3tc"
And I have no idea, what does it mean, sorry, but thanks for help.
I would like to show what's happening in console while I'm running Star Conflict, but this game runs through steam, and don't show any usefull info in console, just only about steam.
How did you install the s2tc lib ?
To be honest, I do not know. I try so many guides to install xorg drivers, to install proprietary drivers. May be it was installed during installation of Linux Mint.
Could you tell us what reports these commands :
$ file /usr/lib32/libtxc_dxtn.so
$ file /usr/lib/libtxc_dxtn.so
$ file /usr/local/lib32/libtxc_dxtn.so
$ file /usr/local/lib/libtxc_dxtn.so
And also :
$ glxinfo |grep "OpenGL core profile version string"
"ERROR: cannot open `/usr/lib/libtxc_dxtn.so' (No such file or directory)" for all of those commands
grimdoll@grimdoll-Aspire-5740:~ > glxinfo |grep "OpenGL core profile version string"
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.0-devel (git-6fd4a61 2015-02-04 trusty-oibaf-ppa)
I should have ask you this instead :
$ whereis libtxc_dxtn.so
grimdoll@grimdoll-Aspire-5740:~ > whereis libtxc_dxtn.so
I dont understand, what wrong with it =)
What does this say:
locate libtxc_dxtn.so | xargs file
Or, you can just try
sudo apt-get install libtxc-dxtn0:i386
which should either install the 32-bit version of the library or tell you that it's already installed.
Ok, thanks, now I installed it and:
grimdoll@grimdoll-Aspire-5740:~ > locate libtxc_dxtn.so | xargs file
/usr/lib/x86_64-linux-gnu/libtxc_dxtn.so: symbolic link to `/etc/alternatives/libtxc-dxtn-x86_64-linux-gnu'
Thank you all very much, it solved my problem, I will write down this command for the future.
Created attachment 113190 [details]
Rangers with xorg driver
Can someone tell what is wrong with it? With proprietary driver all works fine.
(In reply to Grimdoll from comment #16)
> Created attachment 113190 [details]
> Rangers with xorg driver
> Can someone tell what is wrong with it? With proprietary driver all works
There are some failing shaders in the log, this might have been fixed by some register spilling work in the llvm, you may try to get a never llvm and mesa from some ppa (dunno how that works on Mint), or compile them yourself.
Also I'll give you few hints how to write better bug reports so people can help you more ;-)
1) One problem per bug, e.g. don't recycle old bug reports for new problems as you did in comment 16, open a new bug.
2) For 3D stuff such as games, the most important component isn't the xorg driver, but the mesa (3D driver), llvm (for Radeons) and kernel. It is important to always post which version of those components you have installed.
3) Always describe exact steps how to reproduce the issue. This means full name of the program, version, download links if available so people can reproduce it and help you.
3) Posting screenshot is also a good idea. Another interesting info is output of glxinfo (this shows your mesa and opengl version and extensions), dmesg (kernel output), but usually developers can ask for those.
4) If your versions of mesa, llvm or kernel is lower than latest versions, it is possible that your problem was already fixed in the latest version (which also may be the case in this bug). In that case try to get latest version via your distro or some ppa or compile it by yourself and test it before filling a bug. This could save developers a lot of time, by not having to look at already fixed issues.
Sidenote: also pay extra attention to the 32bit vs 64 bit stuff, 32 bit programs (most Steam games and closed source games) need 32bit mesa, libdrm, llvm, libtxc-dxtn etc... so always double check that you indeed have the right components installed or that you upgraded the right ones.
Ah, sorry about the llvm confusion, I didn't realize its r600, so it doesn't need llvm for graphics.
1) It is true, but this thread have some info about my system, and peopole no need to ask it twice. And I though that second bug had relation to first one.
2) All asked info about system is in this thread
3) Name of the game is Space Rangers HD - A War Apart, launching with wine 1.7.34,
with proprietary drivers fglrx 2:13.350.1-0ubuntu2 no issues with this game. Steps: Launching game, start planetary battle. I see blinking screen between normal grafic and black screen repeating infinitely. Info about this process in console.
4) I don't know, have I latest versions of libs or not, I just install it by:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get dist-upgrade
Created attachment 113203 [details]
Created attachment 113204 [details]
So what component I need to check for Gallium r600?
So, a few things you could try:
The bug could be in Wine (different drivers can lead to different behaviour), the game (Mesa sometimes follows the OpenGL spec better than other drivers and exposes bugs in apps) or in the driver.
You could try different options in Wine and in the game to see if it changes the behaviour.
You seem to be using a snapshot of Mesa, you could try the latest stable version to rule out a regression.
Ask others who play the same game using Mesa drivers if they have the same problem (even better if they use another driver, noveau or i965)
Lastly, you could use the apitrace tool to create a trace of the game and upload it somewhere and link it to the bug report.
1) This game works with option d3dx9 libs setted as native, with builtin it would not work at all;
2) I don't know how to use stable mesa, I tried to revert to standard Ubuntu drivers by:
$ sudo apt-get install ppa-purge
$ sudo ppa-purge ppa:oibaf/graphics-drivers
But it didn't help. Drivers remain the same;
3) I have no friends with Linux;
4) Please describe how to use apitrace.
The first issue was missing libtxc-dxtn-s2tc0 which will never be a problem again \o/. Then the user started posting about a completely different game, which could have been a wine bug. Please open new bug reports for different problems.