| Bug ID | 99528 |
|---|---|
| Summary | Wine game doesn't redraw properly in fullscreen |
| Product | Mesa |
| Version | git |
| Hardware | Other |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | dark.shadow4@web.de |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 129133 [details] Trace from the game The windows game DXBall doesn't properly redraw in fullscreen mode. I assume it's an radeonsi bug, since others reported it working fine. Also, LIBGL_ALWAYS_SOFTWARE makes it render properly, although fairly slow. Apitrace attached, notice how the upper half is a static image while the lo= wer half is how it should look like. Also noteworthy is that it works sometimes. Seemingly random, the fullscreen game either renders fine or displays just a static image from the first men= u. System -Arch 64bit -Radeon R9 285 using amdgpu and opensource driver -Mesa 17.1.0-devel (git-0054dded03) Game in question: http://www.blitwise.com/Scorched_Reality/DXBall19.EXE Just run it with wine2.0
DXBall runs fine with 32-bit wineprefix, wine-2.0 (Staging), c=
ustom
~agd5f/linux/?h=3Ddrm-next-4.11-wip kernel, Debian testing Xfce and RX460.<=
/pre>
Still present for me with mesa 88752.3f064e9a40 and linux 4.9.= 6.
(In reply to Fabian Maurer from comment #3) > Still present for me with mesa 88752.3f064e9a40 = and linux 4.9.6. Those stock kernels have very little new amdgpu and radeon drivers code (s= ee diff in kernel.org), use latest drivers when you make bug reports. This ker= nel is latest and stable: https://cgit.freedesktop.org/~agd5f/linux/?h=3Ddrm-next-4.11-wip
Also Debian testing Xfce is more stable, easier and compatible= than Arch Linux.
(In reply to fin4478 from comment #4) > Those stock kernels have very little new amdgpu= and radeon drivers code > (see diff in kernel.org), use latest drivers when you make bug reports= . This > kernel is latest and stable: > https://cgit.freedesktop.org/~agd5f/linux/?h=3Ddrm-next-4.11-wip= Thanks, didn't know that. There's also h= ttps://cgit.freedesktop.org/~airlied/linux/log/?h=3Ddrm-next Which one of those should I chose, they both seem to be fairly recent. But = why is it 4.11?
(In reply to fin4478 from comment #4) > Those stock kernels have very little new amdgpu= and radeon drivers code > (see diff in kernel.org), use latest drivers when you make bug reports= . There is no such requirement. Depending on the circumstances, we may ask bug reporters to try a newer kernel, but in this case it seems unlikely that the problem is kernel related. > This kernel is latest and stable: > https://cgit.freedesktop.org/~agd5f/linux/?h=3Ddrm-next-4.11-wip= This is the development tree for the amdgpu/radeon drivers, with changes go= ing into the Linux 4.11 release, which will only get its first release candidate after the final 4.10 release. I.e. it's cutting edge, *not* stable.
| What | Removed | Added |
|---|---|---|
| Status | NEW | NEEDINFO |
No, I can't reproduce the problem anymore. Also not when using= mesa 17.1 - don't really know where it's fixed, but it works reliably now.
| What | Removed | Added |
|---|---|---|
| Status | NEEDINFO | RESOLVED |
| Resolution | --- | FIXED |