Bug 74766 - no image output in Sonic Robo Blast 2 in OpenGL mode
Summary: no image output in Sonic Robo Blast 2 in OpenGL mode
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 10.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 00:12 UTC by thepouar
Modified: 2019-09-18 19:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
screenshot (25.03 KB, image/png)
2014-02-10 00:12 UTC, thepouar
Details
Xorg.0.log (41.98 KB, text/plain)
2014-02-10 16:45 UTC, thepouar
Details
dmesg.log (56.95 KB, text/plain)
2014-02-10 16:45 UTC, thepouar
Details
glxinfo.log (57.39 KB, text/plain)
2014-02-10 16:46 UTC, thepouar
Details

Description thepouar 2014-02-10 00:12:45 UTC
Created attachment 93729 [details]
screenshot

All I see is a bunch of gray and black rectangles in OpenGL mode
Comment 1 Michel Dänzer 2014-02-10 09:05:48 UTC
Please attach the /var/log/Xorg.0.log file and the output of glxinfo and dmesg.
Comment 2 thepouar 2014-02-10 16:45:08 UTC
Created attachment 93786 [details]
Xorg.0.log
Comment 3 thepouar 2014-02-10 16:45:38 UTC
Created attachment 93787 [details]
dmesg.log
Comment 4 thepouar 2014-02-10 16:46:01 UTC
Created attachment 93788 [details]
glxinfo.log
Comment 5 Michel Dänzer 2014-02-12 09:03:59 UTC
If you're building Mesa with the r600g LLVM compiler backend, does the environment variable R600_DEBUG=nollvm work around the problem?
Comment 6 thepouar 2014-02-12 13:58:58 UTC
(In reply to comment #5)
> If you're building Mesa with the r600g LLVM compiler backend, does the
> environment variable R600_DEBUG=nollvm work around the problem?

no
Comment 7 GitLab Migration User 2019-09-18 19:14:46 UTC
-- 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/494.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.