Comp_Lex wrote:Alright, this is the output of bt:
- Code: Select all
#0 0x00002aaaad4059f5 in Reassociate () from /usr/lib/dri/fglrx_dri.so
#14 0x00002aaaacfcc7c7 in __fgl_glLinkProgramARB ()
#15 0x0000000000468d51 in GL_Backend_CompileProgram (vertexstrings_count=13,
vertexstrings_list=0x7fffffbb0ce0, fragmentstrings_count=13,
fragmentstrings_list=0x7fffffbaccd0) at gl_backend.c:827
#16 0x0000000000471c46 in R_GLSL_CompilePermutation (permutation=2)
at gl_rmain.c:711
#17 0x000000000047250c in R_SetupSurfaceShader (lightcolorbase=0x877c38,
modellighting=false) at gl_rmain.c:825
Looks like we can't fix this because it isn't our bug but ATI's. As a workaround, set "OpenGL 2.0 Shaders" to off or, on the console, set "r_glsl 0". This will turn off the part that crashes, but also disable most of the graphics effects. Apparently this function sometimes works without crash and sometimes crashes (that is, __fgl_glLinkProgramARB).
Maybe we can work around it somehow, but for that someone of us would need to buy an ATI card, and probably nobody here wants to
Seriously, I don't have a spare fast enough PC. At university there is one I could use, but I don't have an ATI for it and I don't feel like buying one of the faster and expensive ones. Can you recommend a cheap ATI that is supported by the fglrx driver?
*edit* do you have the current version of the fglrx driver? See
https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=300. They also seem to have both a "certified" and a "current" driver - you might be better off trying the other one.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.