Re: ATI AIW Radeon 9800 Pro - LockUp
On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > On 1/5/06, Jon <[EMAIL PROTECTED]> wrote: > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > than computer locks) GLXGears runs fine and for a long time, no > > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > module and the r300 DRI module. > > Is their anything I can test or do? > > -- Thanks > > I have been trying to track down the issue during last few month. > No success so far, maybe i am not a good hunter ;). Anyway could > you test to first run an xserver with fglrx (no need for the drm module) > and then run a server with r300 and see if you still have lockup > (you shouldn't) thus i know you probably face the same lockup as > i do. Have you tried checking what's going on with the card memory map ? (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? There is definitely a bug or two lurking around when we have CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those lockups). Ben. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: ATI AIW Radeon 9800 Pro - LockUp
On 1/5/06, Jon <[EMAIL PROTECTED]> wrote: > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > game video, locks computer solid) and Xmoto (lasts for a few seconds > than computer locks) GLXGears runs fine and for a long time, no > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > module and the r300 DRI module. > Is their anything I can test or do? > -- Thanks I have been trying to track down the issue during last few month. No success so far, maybe i am not a good hunter ;). Anyway could you test to first run an xserver with fglrx (no need for the drm module) and then run a server with r300 and see if you still have lockup (you shouldn't) thus i know you probably face the same lockup as i do. best, Jerome Glisse --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: ATI AIW Radeon 9800 Pro - LockUp
On Wednesday 04 January 2006 10:05 pm, khaqq wrote: > On Thu, 5 Jan 2006 04:51:31 + > > Aapo Tahkola <[EMAIL PROTECTED]> wrote: > > On Wed, 04 Jan 2006 21:07:41 -0400 > > > > Jon <[EMAIL PROTECTED]> wrote: > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of > > > freezing with r300 DRI module. I tried Quake3 (wont get past > > > beginning of opening game video, locks computer solid) and > > > Xmoto (lasts for a few seconds than computer locks) GLXGears > > > runs fine and for a long time, no freezing. (10755 frames in > > > 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 Stable, I just > > > built from cvs at freedesktop.org Mesa3D ,DRM kernel module and > > > the r300 DRI module. > > > Is their anything I can test or do? > > > > This is a known problem with r9500, r9700 and r9800 cards. > > You can initialize the card with official drivers. > > No other fix beyond that exist nor is being planned on. > > Unless I am missing something, I believe there are no > "official drivers" for FreeBSD from ATI at this point. Someone is working with ATI on it and just posted something last week to the FreeBSD current mailling list. A search should turn up something. -- Anish Mistry pgp2TWHmHt9lp.pgp Description: PGP signature
Re: ATI AIW Radeon 9800 Pro - LockUp
On Thu, 5 Jan 2006 04:51:31 + Aapo Tahkola <[EMAIL PROTECTED]> wrote: > On Wed, 04 Jan 2006 21:07:41 -0400 > Jon <[EMAIL PROTECTED]> wrote: > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > than computer locks) GLXGears runs fine and for a long time, no > > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > module and the r300 DRI module. > > Is their anything I can test or do? > > This is a known problem with r9500, r9700 and r9800 cards. > You can initialize the card with official drivers. > No other fix beyond that exist nor is being planned on. Unless I am missing something, I believe there are no "official drivers" for FreeBSD from ATI at this point. khaqq --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: ATI AIW Radeon 9800 Pro - LockUp
On Wed, 04 Jan 2006 21:07:41 -0400 Jon <[EMAIL PROTECTED]> wrote: > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > game video, locks computer solid) and Xmoto (lasts for a few seconds > than computer locks) GLXGears runs fine and for a long time, no > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > module and the r300 DRI module. > Is their anything I can test or do? This is a known problem with r9500, r9700 and r9800 cards. You can initialize the card with official drivers. No other fix beyond that exist nor is being planned on. -- Aapo Tahkola --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
ATI AIW Radeon 9800 Pro - LockUp
I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing with r300 DRI module. I tried Quake3 (wont get past beginning of opening game video, locks computer solid) and Xmoto (lasts for a few seconds than computer locks) GLXGears runs fine and for a long time, no freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel module and the r300 DRI module. Is their anything I can test or do? -- Thanks dmesg drm0: port 0xc000-0xc0ff mem 0xd800-0xdfff,0xe802-0xe802 irq 9 at device 0.0 on pci1 info: [drm] AGP at 0xd000 128MB info: [drm] Initialized radeon 1.21.0 20051229 info: [drm] Loading R300 Microcode --- glxinfo No ctx->FragmentProgram._Current!! 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_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R300 20040924 AGP 1x x86/MMX/SSE2 TCL OpenGL version string: 1.3 Mesa 6.5 OpenGL extensions: GL_ARB_fragment_program, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 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_crossbar, 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_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_histogram, GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program, GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod 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 -- 0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2d 24 dc 0 32 0 r . .
Re: persistant problems with drm + mga
On Wed, 2006-01-04 at 23:09 +, Dave Airlie wrote: > > > > > >>Dave Airlie: Can we get those DRM changes pushed into 2.6.15 or is it > > >>too late for that? > > > > > > 2.6.15 has been released yesterday. > > > > D'oh! > > > > Dave Airlie: Can we get those DRM changes pushed into 2.6.15.1 or are > > the changes too big for that? > > > Way too big... they do a lot of things, they are in the .16 queue already, > > It's bad that we regressed with the older setups, I thought I'd fixed all > those problems with 2.6.14, it certainly worked with my MGA card here when > I released it... Is it possible to make a patch to add to the DRM module for kernels 2.6.14 and 2.6.15 to solve the MGA problems until 2.4.16 is released? This could be usable for e.g. the Debian people to add this patch when building the stock kernels. Or is Option "OldDmaInit" "true" the only way out? > Dave. > -- Svante Signell <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
> > > >>Dave Airlie: Can we get those DRM changes pushed into 2.6.15 or is it > >>too late for that? > > > > 2.6.15 has been released yesterday. > > D'oh! > > Dave Airlie: Can we get those DRM changes pushed into 2.6.15.1 or are > the changes too big for that? Way too big... they do a lot of things, they are in the .16 queue already, It's bad that we regressed with the older setups, I thought I'd fixed all those problems with 2.6.14, it certainly worked with my MGA card here when I released it... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5506] RADEON complains about wrong CRT2Position "RightOf"
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5506 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|NEW |RESOLVED Component|General |Driver/Radeon Product|DRI |xorg Resolution||FIXED Version|DRI CVS |unspecified --- Additional Comments From [EMAIL PROTECTED] 2006-01-05 07:19 --- this was fixed a while ago in xorg cvs. please try a newer version. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5506] New: RADEON complains about wrong CRT2Position "RightOf"
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5506 Summary: RADEON complains about wrong CRT2Position "RightOf" Product: DRI Version: DRI CVS Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] Xorg.0.log shows this warning: (WW) RADEON(0): "RightOf" is not a valid parameter for Option "CRT2Position" (II) RADEON(0): Valid parameters are "RightOf", "LeftOf", "Above", "Below", or "Clone" (II) RADEON(0): Except for "Clone", the parameter may be followed by an integer. i think rightof == rightof, but whatever! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
On Tuesday 03 Jan 2006 18:02, Ian Romanick wrote: > David Mulcahy wrote: > > I have been experiencing problems getting drm to work again with my > > matrox g4oo card. The problem started around this post. > > > > http://sourceforge.net/mailarchive/forum.php?thread_id=8163981&forum_id=7 > >177 > > > > Now although That particular problem has stopped I still cannot get drm > > working again. I have a current kernel 2.6.14 and a new xorg "X Protocol > > Version 11, Revision 0, Release 6.9" but still no drm. > > > > This appears in the xlog > > > > (**) Option "dpms" > > (**) MGA(0): DPMS enabled > > (II) MGA(0): Using overlay video > > (II) MGA(0): X context handle = 0x1 > > (II) MGA(0): [drm] installed DRM signal handler > > (II) MGA(0): [DRI] installation complete > > (EE) MGA(0): [drm] Failed to map DMA buffers list > > (II) MGA(0): [drm] removed 1 reserved context for kernel > > (II) MGA(0): [drm] unmapping 8192 bytes of SAREA 0xe0a27000 at 0xb6192000 > > (WW) MGA(0): Direct rendering disabled > > (==) RandR enabled > > There were some issues with the AGP interaction in the MGA DRM > introduced last August. I believe that I fixed them around the > beginning of November. I'm not sure if all of those changes found their > way into 2.6.14. Is there anything "interesting" in /var/log/messages? > > See also: https://bugs.freedesktop.org/show_bug.cgi?id=4797 > > There are two things that you could try. First, try updating your DRM > to current CVS. Second, try adding 'Option "OldDmaInit" "true"' to the > card's device section in your xorg.conf. Right after upgrading to kernel 2.6.15-rc5 things are getting better. This is with 'Option "OldDmaInit" "true"' in my xconf file. (**) MGA(0): DPMS enabled (II) MGA(0): Using overlay video (II) MGA(0): X context handle = 0x1 (II) MGA(0): [drm] installed DRM signal handler (II) MGA(0): [DRI] installation complete (II) MGA(0): [drm] Mapped 128 DMA buffers (II) MGA(0): [drm] dma control initialized, using IRQ 7 (II) MGA(0): Direct rendering enabled and this is from glxgears 1210 frames in 5.0 seconds = 241.964 FPS 1206 frames in 5.0 seconds = 241.097 FPS 1206 frames in 5.0 seconds = 241.014 FPS 1207 frames in 5.0 seconds = 241.209 FPS 1207 frames in 5.0 seconds = 241.253 FPS 1206 frames in 5.0 seconds = 241.181 FPS However the cogs turning when glxgears are running are VERY slow a lot slower than I am used to and the 241FPS is slightly down on 311FPs that I used to get (but why are the cogs moving so slowly as if direct rendering is turned off). Remove 'Option "OldDmaInit" "true"' and drm is disabled again. Dave --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp Klaus Krause wrote: > Ian Romanick schrieb: > >>Dave Airlie: Can we get those DRM changes pushed into 2.6.15 or is it >>too late for that? > > 2.6.15 has been released yesterday. D'oh! Dave Airlie: Can we get those DRM changes pushed into 2.6.15.1 or are the changes too big for that? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDu/HOX1gOwKyEAw8RAnTtAJ9GPcZStIw5FetmcZcn3YdEBXrOQACfcqzo 2+e1VdhbNRoZ+V/t504Q1jM= =i47w -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
Ian Romanick schrieb: > Dave Airlie: Can we get those DRM changes pushed into 2.6.15 or is it > too late for that? 2.6.15 has been released yesterday. Philipp --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Mulcahy wrote: > On Tuesday 03 Jan 2006 18:02, Ian Romanick wrote: >>David Mulcahy wrote: >> >>There were some issues with the AGP interaction in the MGA DRM >>introduced last August. I believe that I fixed them around the >>beginning of November. I'm not sure if all of those changes found their >>way into 2.6.14. Is there anything "interesting" in /var/log/messages? >> >>See also: https://bugs.freedesktop.org/show_bug.cgi?id=4797 >> >>There are two things that you could try. First, try updating your DRM >>to current CVS. Second, try adding 'Option "OldDmaInit" "true"' to the >>card's device section in your xorg.conf. > > Right after upgrading to kernel 2.6.15-rc5 things are getting better. Okay. That means that this is the same as bug #4797. Since this is a kernel problem, it isn't fixed by Xorg 7.0. Dave Airlie: Can we get those DRM changes pushed into 2.6.15 or is it too late for that? > However the cogs turning when glxgears are running are VERY slow a lot slower > than I am used to and the 241FPS is slightly down on 311FPs that I used to > get (but why are the cogs moving so slowly as if direct rendering is turned > off). Around the middle of last year I changed the way the MGA DRM waits for commands to complete. The new method makes gears run a little slower, but it doesn't seem to impact real applications (e.g., Quake3 or viewperf). Gears is not a good benchmark. > Remove 'Option "OldDmaInit" "true"' and drm is disabled again. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDu+/yX1gOwKyEAw8RAs8RAKCeGRE75S7HwJJAIqX4hNqyjz0rHACfadlp OAJGtNiGWr7JeuJCK4C8yfk= =HvoB -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
On Tue, 2006-01-03 at 23:51 +0100, Svante Signell wrote: > On Tue, 2006-01-03 at 13:34 +, David Mulcahy wrote: > > Hello all > > > > I have been experiencing problems getting drm to work again with my matrox > > g4oo card. ... > > I have had this problem for some time now, both with xorg 6.9.0pre > releases and 6.9.0 with kernels 2.6.14 and 2.6.15-rc4, ... > Kernel 2.6.11 is OK with xorg 6.9.0, ... Setting OldDmaInit to true in xorg.conf solved the direct rendering problems, at least with kernel 2.6.15rc7. Have not tried 2.6.14 yet. Thanks, -- Svante Signell <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: persistant problems with drm + mga
On Tuesday 03 Jan 2006 18:02, Ian Romanick wrote: > David Mulcahy wrote: > > I have been experiencing problems getting drm to work again with my > > matrox g4oo card. The problem started around this post. > > > > http://sourceforge.net/mailarchive/forum.php?thread_id=8163981&forum_id=7 > >177 > > > > Now although That particular problem has stopped I still cannot get drm > > working again. I have a current kernel 2.6.14 and a new xorg "X Protocol > > Version 11, Revision 0, Release 6.9" but still no drm. > > > > This appears in the xlog > > > > (**) Option "dpms" > > (**) MGA(0): DPMS enabled > > (II) MGA(0): Using overlay video > > (II) MGA(0): X context handle = 0x1 > > (II) MGA(0): [drm] installed DRM signal handler > > (II) MGA(0): [DRI] installation complete > > (EE) MGA(0): [drm] Failed to map DMA buffers list > > (II) MGA(0): [drm] removed 1 reserved context for kernel > > (II) MGA(0): [drm] unmapping 8192 bytes of SAREA 0xe0a27000 at 0xb6192000 > > (WW) MGA(0): Direct rendering disabled > > (==) RandR enabled > > There were some issues with the AGP interaction in the MGA DRM > introduced last August. I believe that I fixed them around the > beginning of November. I'm not sure if all of those changes found their > way into 2.6.14. Is there anything "interesting" in /var/log/messages? Nothing interesting in the logs - all looks normal. > > See also: https://bugs.freedesktop.org/show_bug.cgi?id=4797 > Yes I did see this but I thought it would be fixed in the next X release. > There are two things that you could try. First, try updating your DRM > to current CVS. Second, try adding 'Option "OldDmaInit" "true"' to the > card's device section in your xorg.conf. Tried upgrading to binary snapshot of common and mga dated 20122005 and still it doesnt work, noteven with the olddmainit option. Getting late here now if you need any info let me know and i will try my best. Dave ps my g400 is an agp. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
