Jose Rodriguez wrote: > Hi > > I can't run Gtkradiant > (http://www.qeradiant.com/cgi-bin/trac.cgi) with the radeon > driver and the following hardware/software: > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 > [Mobility Radeon 9600 M10] > > Libraries and driver from Debian testing (6.6.193-3 driver's > version) > Libraries and driver from Debian unstable (6.7.195-2 > driver's version) > > The program crashes as soon as I try to use it, and the > following is read in its console: > > > Lighting mode requires OpenGL features not supported by your > graphics drivers: GL_ARB_shader_objects > GL_ARB_vertex_shader > GL_ARB_fragment_shader > GL_ARB_shading_language_100 > > > After it crashes the following appears in the terminal: > > > radiant.x86: vbo/vbo_split_inplace.c:97: flush_vertex: Assertion > `max_index >= min_index' failed. Aborted > > > I've been told in the Gtkradiant mailing list that it's a driver > issue, specifically: > > "[...]older Radeon cards have only the ability to address up to > 4096 vertices at a time [...] strictly speaking, that's not a chip limitation, but a driver limitation. Even oldest radeon could address 65536 vertices at a time. You have a much newer radeon though which could address 4 billion vertices in theory...
> GTKRadiant is > issuing more than this many vertices in one call. > > The hardware however has configurable base address for vertex > arrays, and configurable index bias, this allows it to issue the > large draw operation as several smaller ones that do not violate > the limits of the hardware. > > That error indicates the code for splitting the operations into > smaller ones, is broken. > > (All other drivers have to deal with this sort of hardware > limitation transparently as well, it's not an application error)" > > And been encouraged to report this here. I would like to ask for > confirmation that there's no workaround possible short of fixing > code (which I have no idea about). Yes, that certainly looks like a driver error, possibly in the vbo code but could be r300 specific. You could try a newer r300 dri driver (note the radeon ddx version is irrelevant here). Also, could you provide a backtrace from gdb? What are the max_index and min_index values? Roland ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
