[Bug 29363] [r300g] Starcraft 2: "r300 VP: Compiler error"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Feb 27 17:15:31 PST 2011


https://bugs.freedesktop.org/show_bug.cgi?id=29363

--- Comment #24 from Hannes <bugzilla at soulrebel.in-berlin.de> 2011-02-27 17:15:31 PST ---
Ah, I did not realise the Arch Mesa-packages lack s3tc support. I have
installed that now and get other (seemingly better but still strange
behaviour).

Directly after installing the lib, both SC2 and Doom3 bootet up correctly with
some minor drawing issues in the menus (90% correct i would say, compared to
the 2% before). Both games had in-game drawing issues that were severe,
(flickering lines, squares and other patterns on random textures…

After a restart I now have this:
- Doom3 works ok, with some minor drawing issues in-game (mostly related to
shadows), but playable
- SC2 shows loading screen and then crashes giving this (a a few hundred
times):

Please report at bugs.freedesktop.org
Mesa 7.11-devel implementation error: Unexpected texture format in
radeon_update_wrapper()

The above error was also printed the one time after install where I actually
started SC2 with some serious issues. Finally it prints:

fixme:win:EnumDisplayDevicesW ((null),0,0x4346d68,0x00000000), stub!
fixme:mmdevapi:AEV_GetMute stub
fixme:d3d:query_init Event query: Unimplemented, but pretending to be
supported.
fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used
fixme:imm:ImmReleaseContext (0x40022, 0x13c9c8): stub
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See
dmesg for more info.

And dmesg shows:

[drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z buffer (need
4096000 have 3502080) !
[drm:r100_cs_track_check] *ERROR* [drm] zbuffer (1280 4 0 800)
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

Should I open an extra report for this?

Thanks for your help.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the dri-devel mailing list