Tremulous Forum
General => Troubleshooting => Topic started by: Kennyyyyy on September 21, 2008, 09:58:10 am
-
Hi,
i have massive Problems with Tremulous when i start it.
First i become a black screen and than i see the loginpanel from KDE.
I use Mandriva 2008.1. I have this problem since i've updated from Mandriva 2008.0.
I've tried to start Trem from console but it is not easy to get any error messages if my KDE crashes... :-\
What can i do?
Thanks for answers..
Greetings
-
Are you sure you have the open gl drivers?
-
I don't know..
Where i can find it out?
-
start by posting your error message
-
I can't give any error messages. There aren't any... :'(
KDE crashes and i see only my Loginpanel kdm.
-
open a console and run tremulous.x68 &> ~/trem.log
And the post up trem.log
-
tremulous.x68 &> ~/trem.log shows only this:
bash: tremulous.x68: command not found
I've tried this with tremulous-t971.x68 too, but it's the same result.
Have i made anything wrong? O.o
-
You need to cd to the directory that contains it, then do this:
./tremulous.x86 &> ~/trem.log
Assuming your Tremulous executable is called tremulous.x86.
-
oh.. *shame*
Ok, here it is:
I only take the last lines, where the error is.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 39 requests (37 known processed) with 0 events remaining.
-
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 39 requests (37 known processed) with 0 events remaining.
sounds to me like either:
1/ you don't have video drivers installed, so you're using indirect rendering ( which is slow as fuck )
2/ you're using a graphics chipset that shares memory with the main RAM, and your VideoRam( the amount of memory given to the graphics chipset ) is too low
before going on "blind fixes", can you post the output of
glxinfo
please? :)
also, look in your /etc/X11/xorg.conf for a line with VideoRam (if there's no such line, there's no big deal, forget about it)
-
I have a Ati Radeon 9250. ::)
Here's the output of glxinfo:
name of display: :0.0
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
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_visual_select_group
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_SGI_video_sync, GLX_ARB_multisample,
GLX_ATI_pixel_format_float, GLX_ATI_render_texture
GLX version: 1.2
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 20060602 AGP 2x x86/MMX/SSE TCL
OpenGL version string: 1.3 Mesa 7.0.3-rc2
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 16 tc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 1 0 None
0x24 16 tc 0 16 0 r y . 5 6 5 0 0 16 8 0 0 0 0 1 0 Slow
0x25 16 tc 0 16 0 r y . 5 6 5 0 0 16 0 16 16 16 0 1 0 Slow
0x26 16 tc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 1 0 Slow
0x27 16 tc 0 16 0 r . . 5 6 5 0 0 16 0 0 0 0 0 1 0 None
0x28 16 tc 0 16 0 r . . 5 6 5 0 0 16 8 0 0 0 0 1 0 Slow
0x29 16 tc 0 16 0 r . . 5 6 5 0 0 16 0 16 16 16 0 1 0 Slow
0x2a 16 tc 0 16 0 r . . 5 6 5 0 0 16 8 16 16 16 0 1 0 Slow
0x2b 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 1 0 None
0x2c 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 0 0 0 0 1 0 Slow
0x2d 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 16 16 16 0 1 0 Slow
0x2e 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 1 0 Slow
0x2f 16 dc 0 16 0 r . . 5 6 5 0 0 16 0 0 0 0 0 1 0 None
0x30 16 dc 0 16 0 r . . 5 6 5 0 0 16 8 0 0 0 0 1 0 Slow
0x31 16 dc 0 16 0 r . . 5 6 5 0 0 16 0 16 16 16 0 1 0 Slow
0x32 16 dc 0 16 0 r . . 5 6 5 0 0 16 8 16 16 16 0 1 0 Slow
0x72 32 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
I can't find in the xorg.conf any point with videoram.
-
fix your graphics drivers (since it's just about impossible to get an fglrx that supports that card to compile against a recent kernel, you'll want to get radeon working properly with dri)
-
The 9250 is supported by the Xorg driver - open your /etc/X11/xorg.conf and under the device section change the Driver option to "radeon"
-
oh.. *shame*
Ok, here it is:
I only take the last lines, where the error is.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 39 requests (37 known processed) with 0 events remaining.
that error is related to the X_Nextevent code (i think thats it) ive created that error numerous times playing around with xlib its normally related when the screen windows closed but you still try to access events.
knowing that id say your gfx cards are screwed try taiyo's fix its the easiest solution.
after doing his fix do glxinfo again and look for direct rendering: yes chances are the trem codes trying to create the window and when it fails it doesn't quit.
you should think of using a more up to date client one thats moved to SDL anything based on revision 1000+ or so should be sdl
-
I've tried to change this. But when i reboot the mesa is here again... I've looked around in the internet and there are many people who have this problem.
I solved this problem now with a new installation. And now i will never make an update to a x.1 version. :(
-
name of display: :0.0
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
try using LIBGL_DEBUG=verbose glxinfoas suggested, it really means there's something wrong happening, I know that message doesn't show up when it's just non-installed drivers
-
Are you loading DRI?
Do you have the following in your xorg.conf:
Section "Module"
Load "glx"
Load "dri"
EndSection