OS : Lucid
radeon version : lucid up to date
Video chipset : Ati Xpress 1100 RC410, recognized as Xpress 200M (Asus F5R notebook).
When I try to start a race, the game crash with this trace :
%%% etracer warning: Attempt to bind to Texture unloaded texture: `b-herring_run_icon'
drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.
Dmesg says :
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
Please attach your full dmesg.
Also what kernel version, ddx version, mesa version, and xserver are you running?
Created attachment 37745 [details]
Lucid up to date versions :
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
I have also some problems with neverballs (Reflexions options gives huge graphics glitches) and Blender (menus don't show up correctly on v2.49b, I don't use 3D desktop effects).
Why Radeon Xpress1100 is recognized as Xpress 200M?
(In reply to comment #4)
> Why Radeon Xpress1100 is recognized as Xpress 200M?
Programming-wise, they are the same.
(In reply to comment #5)
> (In reply to comment #4)
> > Why Radeon Xpress1100 is recognized as Xpress 200M?
> Programming-wise, they are the same.
I just read a post on ubuntu-fr forums.
Changing KMS to radeon.modeset=1 don't change anything, but changing it to nomodeset solves somes problems. Extreme Tux Racer don't crash anymore (but the game is very slow -- DRI is still enabled). Neverball "reflexions" option don't make graphics glitches, but the render don't change whatever the option is activated or not. Blender menus show up correctly.
So, I think that this bug can be closed, it's more e KMS'bug rather than a DRI's bug.
As per https://bugs.freedesktop.org/show_bug.cgi?id=29432#c6 .