Summary: | Unsupported opcode 8(BGNLOOP)/11(BRK)/27(ENDLOOP) in vertex shader | ||
---|---|---|---|
Product: | Mesa | Reporter: | Pablo Estigarribia <pablodav> |
Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | sa, zeradar |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
glxinfo
dmesg |
Created attachment 23061 [details]
dmesg
*** Bug 19192 has been marked as a duplicate of this bug. *** There is a new piglit test, glsl-vs-loop, for this bug. Mass version move, cvs -> git *** Bug 23564 has been marked as a duplicate of this bug. *** commit 7c0152fbaeb21ab423a9de339b85c54d1713432b Author: Eric Anholt <eric@anholt.net> Date: Thu Sep 10 09:44:30 2009 -0700 i965: Enable loops in the VS. Passes piglit glsl-vs-loop testcase. Bug #20171 |
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.
Created attachment 23060 [details] glxinfo usr/local/games/Savage2/savage2.bin Mesa 7.3 implementation error: Unsupported opcode 8 (BGNLOOP) in vertex shader Please report at bugzilla.freedesktop.org Mesa 7.3 implementation error: Unsupported opcode 11 (BRK) in vertex shader Please report at bugzilla.freedesktop.org Mesa 7.3 implementation error: Unsupported opcode 27 (ENDLOOP) in vertex shader Please report at bugzilla.freedesktop.org savage2.bin: brw_curbe.c:86: calculate_curbe_offsets: Assertion `total_regs <= 32' failed. Savage2 - Fatal Error: Abort signal received I get this message when trying to start savage 2 in ubuntu Jaunty alpha with latest updates. I have Intel Video Card: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) On xorg.conf I added this line to work fine with opengl: Section "Device" Identifier "Configured Video Device" Option "AccelMethod" "UXA" EndSection In attachment you will see dmesg and glxinfo... I have no idea if it could be fixed, but I made this report trying to help in something.