[Bug 1280] Lock up w/ r200, TCL, GL apps
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=1280 --- Additional Comments From [EMAIL PROTECTED] 2005-12-14 18:10 --- I can still reproduce this as of 7.0rc3 and kernel 2.6.14. -- 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 5339] New: Radeon Mobility 7500: LCD looks like running in wrong scan rate when running 3D applications
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=5339 Summary: Radeon Mobility 7500: LCD looks like running in wrong scan rate when running 3D applications 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] I am runing the DRI snapshot on a IBM T42 with Radeon Mobility 7500 graphic card. The distribution is Kubuntu 5.10. When I run a 3D application, such as glxgears, quake3 demo or planetpenguin-racer, after a shor time, the screen looks like running in a wrong refreshing rate. I am not sure whether it is really running in a wrong refreshing rate. It seems that somes of the horizontal lines are not scanning from the 'zero point', causing the screen display 'shaking'. I use driconf to set to 'Always synchronize with vertical refresh'. This reduces the 'noise' but did not fully solve the problem. When I used Kubuntu 5.04 with the dri snapshot, everything works fine. But aftergrading to 5.10, the dri never works properly. Here is the modules section in my xorg.conf: Section "Module" Load"dri" SubSection "extmod" Option "omit xfree86-dga" EndSubSection Load"GLcore" Load"i2c" Load"bitmap" Load"ddc" Load"dbe" Load"extmod" Load"freetype" Load"glx" # Load"/usr/X11R6/lib/modules/extensions/libglx.a" Load"int10" Load"type1" Load"vbe" Load"radeon" Load"xtrap" Load"drm" SubSection "Extensions" Option "RENDER" "Enable" EndSubSection EndSection Here is the section for the card: Section "Device" Identifier "Radeon Mobility M7 LW" Driver "radeon" VendorName "ATI Technologies Inc." BoardName "Radeon Mobility M7 LW" BusID "PCI:1:0:0" Option "AGPMode" "4" Option "AGPFastWrite" "true" # Option "AGPSize" "64" # default: 8 # Option "RingSize" "8" # Option "BufferSize" "2" Option "EnablePageFlip" "true" # Option "EnableDepthMoves" "true" Option "RenderAccel" "true" Option "UseInternalAGPGART""no" # Option "backingstore" "true" Option "AllowGLXWithComposite" "true" EndSection The output of glxinfo: Disabling HW TCL support 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 version: 1.2 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_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20051013 AGP 4x x86/MMX/SSE2 NO-TCL OpenGL version string: 1.3 Mesa 6.5 OpenGL extensions: 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_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_logic_op, 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_fog_coord, 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_specu
Re: R300 RENDER Support
On 12/13/05, Ben Gamari <[EMAIL PROTECTED]> wrote: > Hi All, > > I am a college student looking for a bit of a project to tackle over > winter break (having no car really sucks) with quite a bit of > programming experience. While I have never worked with driver > development, I have a good working knowledge of graphics hardware and > architecture. My laptop having a Radeon Mobility X300, I have an > interest in advancing X300 support, in particular the RENDER extension > (3D I suspect is a little over my head). Are there any roadblocks in the > way of moving forward with RENDER support in the DRI drivers? Or perhaps > more importantly, is a relative graphics novice such as myself capable > of X300 RENDER development? If so, where is a good place to start? I If you have a decent understanding of render and how xorg drivers are organized you should be ok. the other drivers with exa and render support are a good model of comparison. > understand that there are no specs for the X300 (at least on the 3D > side, is the 2D engine documented?), so does most work come from reverse 2D specs used to be available via NDA from ATI, but I doubt you'll have much luck getting them. that said, you really don't need them as the radeon driver is well documented and pretty clear. All radeons up through the r4xx models have the same basic display engine (even rage128 for that matter). > engineering the ATI binary driver? What tools can be used in tracing the > operation of the driver? Does it entail just tracing the instruction > flow with a disassembler? I look forward to hopefully working with you > guys in the future (exams end next Thursday :( ) Thanks for your time, there should be enough information in the r300 mesa 3d driver to implement exa render accel. basically just look at how it's done for r100 and r200 and fill in a new section for r300. Alex > > - Ben Gamari > --- 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
[Bug 5098] i915 DRM needs to be ported to FreeBSD
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=5098 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-12-14 12:01 --- i915 DRM has been committed to -current and merged to RELENG_6. -- 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
R300 RENDER Support
Hi All, I am a college student looking for a bit of a project to tackle over winter break (having no car really sucks) with quite a bit of programming experience. While I have never worked with driver development, I have a good working knowledge of graphics hardware and architecture. My laptop having a Radeon Mobility X300, I have an interest in advancing X300 support, in particular the RENDER extension (3D I suspect is a little over my head). Are there any roadblocks in the way of moving forward with RENDER support in the DRI drivers? Or perhaps more importantly, is a relative graphics novice such as myself capable of X300 RENDER development? If so, where is a good place to start? I understand that there are no specs for the X300 (at least on the 3D side, is the 2D engine documented?), so does most work come from reverse engineering the ATI binary driver? What tools can be used in tracing the operation of the driver? Does it entail just tracing the instruction flow with a disassembler? I look forward to hopefully working with you guys in the future (exams end next Thursday :( ) Thanks for your time, - Ben Gamari --- 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: r300 + NWN
> On a quick glance (though I'm not familiar with that driver), it looks to me > like introducing texture rectangle caused mipmaps to be disabled for > compressed textures. oops, my bad.. I've checked in the fix.. thanks, 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
Re: r300 + NWN
Roland Scheidegger wrote: Adam K Kirchhoff wrote: I've narrowed down this problem to something that changed in Mesa between the 5th of December and the 11th, when I first noticed this problem. I have a system at work with a 9800. I started up NWN (after first initializing the card with the fglrx driver, of course), and the textures looked just fine (though the fog problem still existed). The drivers were built from CVS on the 5th. I upgraded it to what's currently in CVS, started up NWN, and had the same texture problem. On a quick glance (though I'm not familiar with that driver), it looks to me like introducing texture rectangle caused mipmaps to be disabled for compressed textures. Roland Your patch seems to have solved the texture problem with NWN. Thanks! Adam --- 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: r300 + NWN
Roland Scheidegger wrote: Adam K Kirchhoff wrote: I've narrowed down this problem to something that changed in Mesa between the 5th of December and the 11th, when I first noticed this problem. I have a system at work with a 9800. I started up NWN (after first initializing the card with the fglrx driver, of course), and the textures looked just fine (though the fog problem still existed). The drivers were built from CVS on the 5th. I upgraded it to what's currently in CVS, started up NWN, and had the same texture problem. On a quick glance (though I'm not familiar with that driver), it looks to me like introducing texture rectangle caused mipmaps to be disabled for compressed textures. Roland I'll give it a shot over lunch, hopefully. Adam --- 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: r300 + NWN
Adam K Kirchhoff wrote:
I've narrowed down this problem to something that changed in Mesa
between the 5th of December and the 11th, when I first noticed this
problem. I have a system at work with a 9800. I started up NWN (after
first initializing the card with the fglrx driver, of course), and the
textures looked just fine (though the fog problem still existed). The
drivers were built from CVS on the 5th. I upgraded it to what's
currently in CVS, started up NWN, and had the same texture problem.
On a quick glance (though I'm not familiar with that driver), it looks
to me like introducing texture rectangle caused mipmaps to be disabled
for compressed textures.
Roland
Index: r300_texstate.c
===
RCS file: /cvs/mesa/Mesa/src/mesa/drivers/dri/r300/r300_texstate.c,v
retrieving revision 1.35
diff -u -r1.35 r300_texstate.c
--- r300_texstate.c 5 Dec 2005 09:30:58 - 1.35
+++ r300_texstate.c 13 Dec 2005 14:33:29 -
@@ -370,9 +370,11 @@
* requires 64-byte aligned pitches, and we may/may not need the
* blitter. NPOT only!
*/
- if (baseImage->IsCompressed)
+ if (baseImage->IsCompressed) {
t->pitch =
(tObj->Image[0][t->base.firstLevel]->Width + 63) & ~(63);
+ t->size |=
((log2Width>log2Height)?log2Width:log2Height)pitch = ((tObj->Image[0][t->base.firstLevel]->Width *
Re: r300 + NWN
Roland Scheidegger wrote: Stephane Marchesin wrote: Philipp Klaus Krause wrote: Adam K Kirchhoff schrieb: I'm sure this confirms what are already known issues with the r300 driver, but felt it'd be worth posting anyway. There's definitely something bizarre going on with textures. They're much crisper with the fglrx driver. To me it looks like the fglrx driver does linear filtering, while r300 does nearest filtering. It could be the mipmap selection offset that fglrx applies to textures. There's a setting for this reg on r200 (see the R200_EMIT_PP_TRI_PERF_CNTL reg), it probably applies to r300 too. That setting doesn't affect mipmap selection - just how the transition area from one to another mipmap looks like. You'd only get banding as the worst thing possible. Looks like nearest filtering to me too, and/or no mipmaps (so yes mipmap selection offset (LOD setting?) could be an issue there but if so it would be ways off). No idea what's wrong with the inventory there - some issue with transparent textures? Strange that not the whole inventory gets affected exactly the same way though. Roland Hello all. I've narrowed down this problem to something that changed in Mesa between the 5th of December and the 11th, when I first noticed this problem. I have a system at work with a 9800. I started up NWN (after first initializing the card with the fglrx driver, of course), and the textures looked just fine (though the fog problem still existed). The drivers were built from CVS on the 5th. I upgraded it to what's currently in CVS, started up NWN, and had the same texture problem. Adam --- 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: 'Direct Rendering Disabled' on an R100 chip ...
On Tue, 2005-12-13 at 22:20 +1100, Daniel Kasak wrote: > > I'm putting together a PC for my brother, and my old Radeon 7200 isn't > being accelerated any more. > The X log simply says 'Direct Rendering Disabled', without saying why. [...] > (II) LoadModule: "glx" > (WW) Warning, couldn't open module glx > (II) UnloadModule: "glx" > (EE) Failed to load module "glx" (module does not exist, 0) The glx module is required for 3D acceleration. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- 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
'Direct Rendering Disabled' on an R100 chip ...
Greetings. I'm putting together a PC for my brother, and my old Radeon 7200 isn't being accelerated any more. The X log simply says 'Direct Rendering Disabled', without saying why. I've got an agp module loaded for the motherboard: Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected SiS 735 chipset agpgart: AGP aperture is 64M @ 0xd000 and the radeon module: [drm] Initialized drm 1.0.0 20040925 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :01:00.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5 [drm] Initialized radeon 1.17.0 20050311 on minor 0: All loaded modules: Module Size Used by radeon106944 0 drm72404 1 radeon uhci_hcd 32976 0 ehci_hcd 32392 0 parport_pc 36228 0 parport38472 1 parport_pc 8250_pnp8640 0 8250 22500 1 8250_pnp serial_core22016 1 8250 floppy 61764 0 pcspkr 3616 0 usbhid 30528 0 snd_intel8x0 32668 0 snd_ac97_codec 91168 1 snd_intel8x0 snd_ac97_bus2176 1 snd_ac97_codec snd_pcm91656 2 snd_intel8x0,snd_ac97_codec snd_timer 25156 1 snd_pcm snd53604 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 10016 1 snd snd_page_alloc 10632 2 snd_intel8x0,snd_pcm ohci_hcd 21572 0 sis_agp 8644 1 agpgart34184 2 drm,sis_agp usbcore 121600 5 uhci_hcd,ehci_hcd,usbhid,ohci_hcd 8139too26752 0 The x log ( created by root ): This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation CVS repository. See http://wiki.x.org/wiki/CvsPage for CVS access instructions. X Window System Version 6.99.99.903 (7.0.0 RC 3) Release Date: 02 December 2005 X Protocol Version 11, Revision 0, Release 6.99.99.903 Build Operating System:Linux 2.6.14-nitro2 i686 Current Operating System: Linux blastophagous 2.6.14-nitro2 #1 PREEMPT Tue Dec 6 04:39:57 EST 2005 i686 Build Date: 07 December 2005 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 14 08:36:13 2005 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi". Entry deleted from font path. (Run 'mkfontdir' on "/usr/share/fonts/75dpi"). (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi". Entry deleted from font path. (Run 'mkfontdir' on "/usr/share/fonts/100dpi"). (**) FontPath set to "/usr/share/fonts/misc,/usr/share/fonts/TTF,/usr/share/fonts/Type1" (**) RgbPath set to "/usr/share/X11/rgb" (**) ModulePath set to "/usr/lib/xorg/modules" (**) Extension "Composite" is enabled (**) Extension "RENDER" is enabled (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.99.99.903, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.99.99.903, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0735 card , rev 01 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 1039,0018 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:02:1: chip 1039,0016 card , rev 00 class 0c,05,00 hdr 00 (II) PCI: 00:02:2: chip 1039,7001 card 1019,0a14 rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:02:3: chip 1039,7001 card 1019,0a14 rev 07 class 0c,03,10 hdr 00 (
