| View previous topic :: View next topic |
| Author |
Message |
tsinghoi
n00b
Joined: 28 Sep 2005
Posts: 15
|
 Posted: Thu Sep 29, 2005 8:04 am Post subject: glxgears pulsate/lag |
 |
|
| originally when i ran glxgears it was pretty slow. stuff like the opengl screensavers were very slow. they lagged too... or pulsated, as in it goes, then it hesitates, then it goes, and hesitates at a consistant rate. and so on. Now i followed the gentoo Nvidia driver guide and i glxgears runs heck of a lot faster. so do the screensavers. BUT it still hesitate/pulsates/lags at a consistant rate. I thought that installing the nvida drivers would fix it, but it didnt. anyone have any idea what can be going on? knowledgewize im still a gentoo newbie, and im still learning a lot about linux. thanks in advance! |
|
| Back to top |
|
 |
frostschutz
Advocate
Joined: 22 Feb 2005
Posts: 2977
Location: Germany
|
| Posted: Thu Sep 29, 2005 10:46 am Post subject: |
|
|
Need more information, I guess.
Can you post the output of the 'glxinfo' command, as well as contents of /proc/driver/nvidia/agp/status and (relevant parts, e.g. graphics section of) /etc/X11/xorg.conf? |
|
| Back to top |
|
|
Vortex375
Veteran
Joined: 03 Mar 2005
Posts: 1739
Location: Deutschland
|
| Posted: Thu Sep 29, 2005 1:13 pm Post subject: |
|
|
If you are using the nvidia drivers, install the application nvidia-settings. Then open nvidia-settings, select "OpenGL Settings" and enable "Sync to VBlank".
This synchronizes the framerate to your monitor's refresh rate, usually resulting in a much lower but constant bitrate.
Usually you should not notice any diffrence in most applications whether this option is turned on or not, but maybe it solves your problem. |
|
| Back to top |
|
|
tsinghoi
n00b
Joined: 28 Sep 2005
Posts: 15
|
| Posted: Thu Sep 29, 2005 11:23 pm Post subject: |
|
|
Well I found the problem... I had some SuperKaramba themes running at the same time. it worked fine after i closed superkaramba... but it thought what the nvidia drivers did was use the proccessing power of the video card rather than the computer... so shouldnt the superkaramba themes not affect it? it would be annoying to shutdown superkaramba everytime i want to use opengl stuff. is this normal?
Vortex375: I installed nvidia-settings and enabled sync to VBlank. You werent kidding about it being much slower... BUT it fixed the problem WITH glxgears lagging ONLY. BUT when i tied to view the opengl screensavers, they still lagged/pulsated. (not to mention they were slower too).
frostschutz: im not sure if this info is of anymore use... but here it is anyways:
glxinfo:
| Code: |
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.3
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_ARB_multisample
client glx vendor string: NVIDIA Corporation
client glx version string: 1.3
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_NV_float_buffer
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_ARB_multisample, GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce3/AGP/SSE
OpenGL version string: 1.5.2 NVIDIA 66.29
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multisample,
GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_point_parameters,
GL_ARB_point_sprite, GL_ARB_shadow, GL_ARB_shader_objects,
GL_ARB_shading_language_100, GL_ARB_texture_border_clamp,
GL_ARB_texture_compression, GL_ARB_texture_cube_map,
GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader,
GL_ARB_window_pos, GL_S3_s3tc, GL_EXT_texture_env_add, GL_EXT_abgr,
GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_minmax,
GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_Cg_shader,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_paletted_texture, GL_EXT_pixel_buffer_object,
GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_shared_texture_palette, GL_EXT_stencil_wrap, GL_EXT_texture3D,
GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_object,
GL_EXT_vertex_array, GL_HP_occlusion_test, GL_IBM_rasterpos_clip,
GL_IBM_texture_mirrored_repeat, GL_KTX_buffer_region, GL_NV_blend_square,
GL_NV_copy_depth_to_color, GL_NV_depth_clamp, GL_NV_fence,
GL_NV_fog_distance, GL_NV_light_max_exponent,
GL_NV_multisample_filter_hint, GL_NV_occlusion_query,
GL_NV_packed_depth_stencil, GL_NV_pixel_data_range, GL_NV_point_sprite,
GL_NV_register_combiners, GL_NV_register_combiners2,
GL_NV_texgen_reflection, GL_NV_texture_compression_vtc,
GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_NV_texture_shader,
GL_NV_texture_shader2, GL_NV_vertex_array_range,
GL_NV_vertex_array_range2, GL_NV_vertex_program, GL_NV_vertex_program1_1,
GL_SGIS_generate_mipmap, GL_SGIS_multitexture, GL_SGIS_texture_lod,
GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_slice_accum
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess
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
----------------------------------------------------------------------
0x21 16 tc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 0 0 None
0x22 16 dc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 0 0 None
0x23 16 tc 0 16 0 r . . 5 6 5 0 4 16 0 16 16 16 16 0 0 None
0x24 16 tc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 0 0 None
0x25 16 tc 0 16 0 r . . 5 6 5 0 4 24 8 16 16 16 16 0 0 None
0x26 16 tc 0 16 0 r y . 5 6 5 0 4 0 0 16 16 16 16 0 0 None
0x27 16 tc 0 16 0 r . . 5 6 5 0 4 0 0 16 16 16 16 0 0 None
0x28 16 tc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 2 1 Ncon
0x29 16 tc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 4 1 Ncon
0x2a 16 tc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 2 1 Ncon
0x2b 16 tc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 4 1 Ncon
0x2c 16 dc 0 16 0 r . . 5 6 5 0 4 16 0 16 16 16 16 0 0 None
0x2d 16 dc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 0 0 None
0x2e 16 dc 0 16 0 r . . 5 6 5 0 4 24 8 16 16 16 16 0 0 None
0x2f 16 dc 0 16 0 r y . 5 6 5 0 4 0 0 16 16 16 16 0 0 None
0x30 16 dc 0 16 0 r . . 5 6 5 0 4 0 0 16 16 16 16 0 0 None
0x31 16 dc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 2 1 Ncon
0x32 16 dc 0 16 0 r y . 5 6 5 0 4 16 0 16 16 16 16 4 1 Ncon
0x33 16 dc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 2 1 Ncon
0x34 16 dc 0 16 0 r y . 5 6 5 0 4 24 8 16 16 16 16 4 1 Ncon
|
/proc/driver/nvidia/agp/status:
| Code: |
Status: Enabled
Driver: NVIDIA
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled
|
parts of xorg.conf:
| Code: |
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "IntelliMouse" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Module"
Load "record"
Load "extmod"
Load "dbe"
# Load "dri"
Load "glx"
Load "xtrap"
Load "freetype"
Load "type1"
EndSection
Section "Monitor"
#DisplaySize 400 300 # mm
Identifier "Monitor0"
VendorName "SNY"
ModelName "CPD-G500"
HorizSync 30.0 - 121.0
VertRefresh 48.0 - 160.0
Option "DPMS"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # <i>
#Option "FlatPanel" # [<bool>]
#Option "FPDither" # [<bool>]
#Option "CrtcNumber" # <i>
#Option "FPScale" # [<bool>]
#Option "FPTweak" # <i>
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV20 [GeForce3]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
|
lol well that actually ended up being all of it except for two sections....
and thatnks for the help.[/code] |
|
| Back to top |
|
|
frostschutz
Advocate
Joined: 22 Feb 2005
Posts: 2977
Location: Germany
|
| Posted: Fri Sep 30, 2005 12:21 am Post subject: |
|
|
| tsinghoi wrote: | | I had some SuperKaramba themes running at the same time. it worked fine after i closed superkaramba... |
I have no idea what SuperKaramba is so I won't comment on that.
In general, when you have processes running in the background that consume too much CPU power, you should have them running at a proper nice level (lower priority), see 'nice' command.
| tsinghoi wrote: | | but it thought what the nvidia drivers did was use the proccessing power of the video card rather than the computer... |
Not true for programs like glxgears which try to get as much power out of the machine as possible. If you watch using 'top' in a console, you'll notice that glxgears consumes an awful lot of CPU.
And of course, there is no 3D graphics application that can live with 0% CPU, although the graphics card does take some work off it's shoulders it's not like the CPU doesn't have to do anything...
| tsinghoi wrote: | | frostschutz: im not sure if this info is of anymore use... but here it is anyways: |
configuration looks okay to me. of course, it's hard to tell just by glancing at it  but next thing I would try is running SuperKaramba (if that's some CPU eating process or whatever) using nice. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
