Summary: | Bound by Flame game crashes GPU | ||
---|---|---|---|
Product: | Mesa | Reporter: | l.gambetta |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 11.0 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Messages printed into the journalctl log about this crash |
Description
l.gambetta
2015-12-04 08:33:02 UTC
I have just played the game few minutes, looks good with my config (RX480 with mesa/LLVM from Git and amd-stagin-4.9 kernel). Your config is different but as the bug is quite old, can you try again? Hopefully it should work now. Thanks. (In reply to Samuel Pitoiset from comment #1) > I have just played the game few minutes, looks good with my config (RX480 > with mesa/LLVM from Git and amd-stagin-4.9 kernel). Your config is different > but as the bug is quite old, can you try again? Hopefully it should work > now. Thanks. Yes, this bug is resolved, using this updated configuration: System: Host: accipigna Kernel: 4.9.6-1-MANJARO x86_64 (64 bit) Desktop: KDE Plasma 5.8.5 Distro: Manjaro Linux Machine: Device: desktop Mobo: ASRock model: FM2A88X Extreme4+ UEFI [Legacy]: American Megatrends v: P3.30 date: 05/13/2016 CPU: Quad core AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G (-MCP-) cache: 8192 KB clock speeds: max: 3700 MHz 1: 3700 MHz 2: 1700 MHz 3: 1700 MHz 4: 1700 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] Display Server: X.Org 1.19.1 driver: radeon Resolution: 1920x1080@60.00hz GLX Renderer: Gallium 0.4 on AMD PITCAIRN (DRM 2.48.0 / 4.9.6-1-MANJARO, LLVM 3.9.1) GLX Version: 3.0 Mesa 13.0.3 It remains slower (less FPS) than the Windows version, but playable. Thanks for the confirmation. Closing. |
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.