https://bugs.freedesktop.org/show_bug.cgi?id=50450
Bug #: 50450 Summary: OpenGL does not work or works very slowly on Radeon HD3850 Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: maksbotan@gentoo.org
Created attachment 62198 --> https://bugs.freedesktop.org/attachment.cgi?id=62198 lspci
I have ATI Radeon HD3850 on AGP bus with Pentium-4 PC. I observe very strange behavior of OpenGL applications: KWin, qudos, doomsday run slowly even not with high quality settings; Quake4 demo from ID site crashes right after map loading, just when rendering starts i suppose, and X server crashes with it. I attach my glxinfo, kernel config and lspci. Versions of used software are: mesa, libdrm and xf86-video-ati from git, linux kernel kernel 3.3.5, X.org server 1.12.1. I think this is bug in mesa or xf86-video-ati related to my video card. Please help me.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #7 from Andy Furniss lists@andyfurniss.entadsl.com 2012-05-29 06:26:59 UTC --- (In reply to comment #6)
Created attachment 62218 [details] quake4 console log
I attached Xorg log, dmesg and log of quake4, which crashes like i said. Sorry for mimetype, i thought bugzilla auto-detect would work.
np everyone does that.
Anyway I think I know why quake4 doesn't work: from your log -
/opt/quake4/q4base/paklibGL error: failed to load driver: r600 libGL error: Try again with LIBGL_DEBUG=verbose for more details. libGL error: failed to load driver: swrast libGL error: Try again with LIBGL_DEBUG=verbose for more details.
I suspect if you did run -
LIBGL_DEBUG=verbose quake4-demo
That you would see something like -
.... ./libstdc++.so.6: version `GLIBCXX_3.4.9' not found ....
This is caused by there being libstdc++.so.6 in the quake4 demo dir that is too old for mesa (well llvm to be precise).
Solution is to rename libstdc++.so.6 and libgcc_s.so.1 that are in /opt/quake4/ I guess, to something else which will make q4 use your system libs.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #1 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 03:39:36 PDT --- Created attachment 62199 --> https://bugs.freedesktop.org/attachment.cgi?id=62199 glxinfo
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #2 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 03:39:55 PDT --- Created attachment 62200 --> https://bugs.freedesktop.org/attachment.cgi?id=62200 kernel config
https://bugs.freedesktop.org/show_bug.cgi?id=50450
Andy Furniss lists@andyfurniss.entadsl.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #62199|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=50450
Andy Furniss lists@andyfurniss.entadsl.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #62198|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=50450
Andy Furniss lists@andyfurniss.entadsl.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #62200|application/octet-stream |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #3 from Andy Furniss lists@andyfurniss.entadsl.com 2012-05-29 04:57:03 PDT --- dmesg output and /var/log/Xorg.0.log would add more info.
If you use mime type text/plain for them it's easier for people to read the contents in their browser.
I've got an AGP 3850, but it's not in a PC at the moment, when I get time I'll put it back in an see if anything has regressed in the last few months.
With AGP it's quite possible that what works for me with the same card will give you problems just because we are not using the same mobo.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #4 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 05:27:08 PDT --- Created attachment 62215 --> https://bugs.freedesktop.org/attachment.cgi?id=62215 Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #5 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 05:27:36 PDT --- Created attachment 62216 --> https://bugs.freedesktop.org/attachment.cgi?id=62216 dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #6 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 05:28:41 PDT --- Created attachment 62218 --> https://bugs.freedesktop.org/attachment.cgi?id=62218 quake4 console log
I attached Xorg log, dmesg and log of quake4, which crashes like i said. Sorry for mimetype, i thought bugzilla auto-detect would work.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #8 from Maxim Koltsov maksbotan@gentoo.org 2012-05-29 06:51:37 PDT --- (In reply to comment #7)
Solution is to rename libstdc++.so.6 and libgcc_s.so.1 that are in /opt/quake4/ I guess, to something else which will make q4 use your system libs.
Thank you, it worked. But still i can't understand why doomsday runs so slow, I think it must run smoothly on my card. I also get weird screen artefacts in xonotic.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #9 from Andy Furniss lists@andyfurniss.entadsl.com 2012-05-29 08:07:33 PDT --- (In reply to comment #8)
(In reply to comment #7)
Solution is to rename libstdc++.so.6 and libgcc_s.so.1 that are in /opt/quake4/ I guess, to something else which will make q4 use your system libs.
Thank you, it worked. But still i can't understand why doomsday runs so slow, I think it must run smoothly on my card. I also get weird screen artefacts in xonotic.
I haven't tested those with a 3850, IIRC nexuiz was a bit slow - but then that was at 1920x1080 and reducing res/effects could make it playable.
I also never had the complication of a compositing desktop - maybe there is something there to be tweaked - maybe not.
I don't know gentoo, or any distro (using ancient LFS). Are you compiling mesa git or is gentoo - what options are being used?
I always used to test with vsync off, I can see from your xorg log that swapbuffers wait is on. I don't know how/where you would add the xorg.conf option in gentoo but in
Section "Device" Option "SwapbuffersWait" "off"
will disable that.
In addition you need to run the app with the env
vblank_mode=0
compositing desktop allowing that should disable vsync and gain a few fps
You could avoid using the env everytime by making/editing .drirc in your home dir to look like -
<driconf> <device screen="0" driver="dri2"> <application name="Default"> <option name="vblank_mode" value="0" /> </application> </device> </driconf>
Another thing you could check is whether gentoo does anything with gpu power settings.
cat /sys/class/drm/card0/device/power_method cat /sys/class/drm/card0/device/power_profile
The only difference gpu wise between your logs and what I remember mine to be is that your GTT is 64M. I used to use 256 - I have no idea if that will help anything at all, but you could try in bios settings increasing AGP Aperture size if you wanted to change it.
https://bugs.freedesktop.org/show_bug.cgi?id=50450
--- Comment #10 from Michel Dänzer michel@daenzer.net 2012-06-01 02:09:16 PDT --- Does passing radeon.agpmode=-1 on the kernel command line help?
https://bugs.freedesktop.org/show_bug.cgi?id=50450
Andreas Boll andreas.boll.dev@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Drivers/DRI/R600 |Drivers/Gallium/r600
--- Comment #11 from Andreas Boll andreas.boll.dev@gmail.com 2012-08-09 14:53:12 UTC --- glxinfo in comment 1 shows: OpenGL renderer string: Gallium 0.4 on AMD RV670
https://bugs.freedesktop.org/show_bug.cgi?id=50450
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #12 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/411.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org