Open-Source ATI 6.8.0 Driver Released

[phoronix]

Phoronix: Open-Source ATI 6.8.0 Driver Released

It's been a long time in the making, but the xf86-video-ati driver has finally reached version 6.8.0! The major improvements in this new version include the drivers now all using libpciaccess, restructuring of the ATI wrapper, Radeon support for the R500/600 series using the AtomBIOS, initial Render acceleration support for the R300/400 series, improve BIOS/driver interaction, and many other changes. More information can be found in the Xorg release announcement...

http://www.phoronix.com/vr.php?view=NjMzOQ

[sergus]

Did somebody try this driver with Xpress 200m?

[Porter]

Wow! So is this the driver to use over fglrx on an R520 (X1400) that is used for video? Does Xv work properly?

[mo0n_sniper]

I am also interested in the state of the infamous Xpress 200m with this new driver?

[Michael]

Wow! So is this the driver to use over fglrx on an R520 (X1400) that is used for video? Does Xv work properly?

No, the xf86-video-ati 6.8.0 driver only supports 2D accel for the R500 series. There is no 3D or X-Video support at this time.

[Porter]

No, the xf86-video-ati 6.8.0 driver only supports 2D accel for the R500 series. There is no 3D or X-Video support at this time.

Bummer. Will it at least allow basic video playback scaled to fullscreen on an R500+ without terrible pixelation? I could care less what method it uses to draw to the screen, as long as it works.

[Michael]

Bummer. Will it at least allow basic video playback scaled to fullscreen on an R500+ without terrible pixelation? I could care less what method it uses to draw to the screen, as long as it works.

If using X11 in mplayer, yes, but I haven't tried it myself (with either Radeon or RadeonHD) so I cannot comment on its quality, but will be second-rate compared to fglrx with X-Video / TexturedVideo.

[Porter]

If using X11 in mplayer, yes, but I haven't tried it myself (with either Radeon or RadeonHD) so I cannot comment on its quality, but will be second-rate compared to fglrx with X-Video / TexturedVideo.
True on X11 vs. working Xv accel, but fglrx doesn't support Xv video rendering on the R5xx right now, or perhaps it's broken. That's with TexturedVideo turned on in xorg.conf, and VideoOverlay turned off.

See also: http://www.phoronix.com/forums/showthread.php?t=7876

[Pseus]

I'm excited about the work on Render accel. Though it's still pretty basic, I hope to see more getting added in the future. Go Xorg devs :)

[koolmanoncampus]

If using X11 in mplayer, yes, but I haven't tried it myself (with either Radeon or RadeonHD) so I cannot comment on its quality, but will be second-rate compared to fglrx with X-Video / TexturedVideo.


I find using "mplayer -vo x11 -zoom videofile" using a non-fglrx driver works fine assuming you have a decent machine...

Like fglrx has resulted in horrible diagonal tearing for the past year, so I was glad to get rid of that. It was terrible to watch anything; and resulted in an unusable setup.

[kirù]

When I had an ATI card this driver was good because with the 9600 you could see videos, you could see compiz (just see because the fps was not so great in scrollings even if it was better than fglrx scrolling) and generally you could work... but it had an issue: games performances were not always so good as fglrx. If you don't play games (some emulator excluded :) ) this driver is the best choice.

[givemesugarr]

I am also interested in the state of the infamous Xpress 200m with this new driver?

i'm on the live git branch of xf86-video-ati and the driver works quite well. though, there's no render working on this board; even if forced it is disabled at startup. the vt switch seems still broken and opengl still doesn't work but you have hw accel for divx5 some divx6 and xvid movies. this is quite good since neither fglrx has this yet.
xv works well and fast, exa is still a little buggy and slow and with some artifacts, but it could get better in no time.

[Kano]

You dream too much, there was never divx acc available, not even with win!

[val-gaav]

the vt switch seems still broken and opengl still doesn't work
the vt switch means ctrl+alt+f1 into text mode right ?

I'm facing this on rs690 though right now I'm running only the radeon driver 6.8.0 from sid ... Mesa and drm are old versions but I planned to upgrade them (compile from git) and see if it helps ...
I guess it will not help?

[Porter]

but you have hw accel for divx5 some divx6 and xvid movies. this is quite good since neither fglrx has this yet.
xv works well and fast, exa is still a little buggy and slow and with some artifacts, but it could get better in no time.

Huh? What card are you using? Xv supported?

This seems to contradict everything said so far.

[legume]

I can get some hw accel with fglrx on an AGP X1600 pro by using

mplayer -vo gl:yuv=4:lscale=1

[givemesugarr]

You dream too much, there was never divx acc available, not even with win!

not with windows or fglrx driver but with radeon is there. i can assure you.
when playing divx-5 movies with xine and radeon i get the processor at 10% of the lower speed (800mhz) and a top thermal temp of 58° C.
when running the same movie on windows or fglrx i get the processor at 35% of middle speed (1600Mhz) and a thermal temp of 69°C.

when playing other sort of movies i don't get this behaviour except some xvid ones (probably coded for divx-5 compatibility). this has only one explanation:
hw decoding capabilities.
i got the confirmation on the xorg mailing list or on one of the radeon devs blog of the presence of hw decoding in the radeon driver. i have to find out the confirmation, but right now i'm in a hurry cause i got my favorite soccer team playing a game this evening in champions league so i'll post the link to this confirmation when i find it in the next days.

Huh? What card are you using? Xv supported?

This seems to contradict everything said so far.

xpress 200m 5975 model.
i get xv overlay, xv movie accel, font antialiasing, buggy opengl, dri forced to on, but unsupported by default and no render. i use the git versions of:
libdrm, x11-drm-rework, xf86-video-ati, xorg-server, mesa, evdev, kdb, mouse and xcb. i have them compiled with xcb enabled and i have xinerama disabled. as movie player i use xine+kaffeine+external ffmpeg from svn. i have kaffeine and xine compiled with xcb and without xinerama. i use kde without any gnome package, with exception of gtk+ and some other needed packages for pidgin and pan. i'm on gentoo 2.6.23-r8 (the 24 branch is buggy with networkmanager and madwifi) with system on the amd64 branch while the other packages are from the unstable branch.
there's no compiz support, but damage, compositing and aiglx work well. glxgears shows about 900fps and i've allowed the mapping ot mtrr registers. without it the xorg seems a little buggy.

the vt switch is ctrl+atl+fx where x is the number of the virtual termina. normally the vt from 1 to 6 are console logins while the 7 to 11 are xorg ones. unfortunately the vt switch problem in radeon with some boards is well known and the devs are working on it.
dinamic clocks option works very well to keep the system cool and the battery high (i got about 10% more battery time on radeon when compared to fgrlx + powerplay).

the last good fglrx driver for this board is the december one; the january one doesn't start for the glx problem while the feb one is very angry with xorg-1.4 from git and is very slow and has a lot of artifacts even if it has rendering (100-150 fps on rendering). fglrx has opengl overlay and opengl acceleration work, while the radeon one is still faulty: for example i get a lot of problem running stellarium or google-earth. for that reason i have to run these programs with fglrx.

[DoDoENT]

All right! That's just too much for a newbie like me. I have ATI Mobility Radeon X1600. Will this driver work with it in the manner of running compiz, playing videos and games at some normal speed?

[Porter]

xpress 200m 5975 model.
Ah, so an R300 core.

[givemesugarr]

All right! That's just too much for a newbie like me. I have ATI Mobility Radeon X1600. Will this driver work with it in the manner of running compiz, playing videos and games at some normal speed?

guess you'll have to try it out. without trying you cannot know. the board should be supported but maybe advanced features like compiz or high-level opengl acceleration may still not be at a high level. for videos and normal use (web browsing, listen to music, reading documents and so on) it should be satisfying. for games i don't know if there really are games that run pretty well with either fglrx or radeon.

Ah, so an R300 core.

r300 chipset architecture integrated into motherboard without vertex shaders and without dedicated memory (it's quite a bad board itself). it is similar to the rs690 as core arch so one should benefit from the other's specs and the same goes for driver implementation.

[bridgman]

There is no open source 3d or video acceleration for X1600 yet. We're working hard to change that.

[Svartalf]

r300 chipset architecture integrated into motherboard without vertex shaders and without dedicated memory (it's quite a bad board itself).

Well... Not ALL iterations of the Xpress 200M GPU were UMA only. I know, my previous laptop from HP was one with "Sideport" memory, which was 128Mb of dedicated VRAM of the traditional type combined with either UMA or using UMA only. I could never get any of the modern fglrx drivers to work with anything other than UMA only mode with it, so, with all the other drawbacks, it got relegated to be my mother's computer, since it was more than serviceable under XP.

What I want to know is what possessed ATI to make such stinkers in the first place- when they had the lead with the R200 mobility parts and they DID have T&L hardware? (No, I don't expect an answer...I just expect better from you guys going forward... :D)

[agd5f]

Well... Not ALL iterations of the Xpress 200M GPU were UMA only. I know, my previous laptop from HP was one with "Sideport" memory, which was 128Mb of dedicated VRAM of the traditional type combined with either UMA or using UMA only. I could never get any of the modern fglrx drivers to work with anything other than UMA only mode with it, so, with all the other drawbacks, it got relegated to be my mother's computer, since it was more than serviceable under XP.

What I want to know is what possessed ATI to make such stinkers in the first place- when they had the lead with the R200 mobility parts and they DID have T&L hardware? (No, I don't expect an answer...I just expect better from you guys going forward... :D)

As much as we dislike them, something like 70% of computers sold have IGP graphics on them. When graphics are more or less free when you buy the chipset, it make a compelling argument if you are an OEM :)

[airlied]

What I want to know is what possessed ATI to make such stinkers in the first place- when they had the lead with the R200 mobility parts and they DID have T&L hardware? (No, I don't expect an answer...I just expect better from you guys going forward... :D)

It's call transistor count... fitting a TCL or Vertex processor onto an integrated chipset device requires lots of transitors. Also for that market segment they mostly don't expect tcl/vertex shaders because Intel didn't do it either.

Now that shaders are unified they will probably just put less of them on future integrated chipsets and you can do TCL with some of the threads. again what Intel have done with 965.

[Svartalf]

As much as we dislike them, something like 70% of computers sold have IGP graphics on them. When graphics are more or less free when you buy the chipset, it make a compelling argument if you are an OEM :)

Won't argue the compelling argument there- I've had to deal with some of the board vendors (ECS...) directly in the past when one of my other business ventures was doing embedded Linux for Internet Appliances. The only REAL complaint would be that the cuts to get the transistor counts down were...iffy...at best in the case of ATI's chips. The reality is that they managed to HAVE TCL support in the previous lineup of chips, even if it wasn't Vertex shader based, in spite of that argument.

Right now, it's water under the bridge, really. :D

[Svartalf]

It's call transistor count... fitting a TCL or Vertex processor onto an integrated chipset device requires lots of transitors. Also for that market segment they mostly don't expect tcl/vertex shaders because Intel didn't do it either.

Heh... The problem with that thinking is that they managed to HAVE TCL in the previous series without this issue coming up. That's just...frustrating.

As for the market segment, they're the ones that actually MADE it (In laptops, that is...) in the first place with the Radeon Mobility lineup. Why slack off to what the competitor can manage when you're already vastly better than they are in the first place?


Now that shaders are unified they will probably just put less of them on future integrated chipsets and you can do TCL with some of the threads. again what Intel have done with 965.

Heh... Like I said... Just DO better... ;)

[airlied]

Heh... The problem with that thinking is that they managed to HAVE TCL in the previous series without this issue coming up. That's just...frustrating.

As for the market segment, they're the ones that actually MADE it (In laptops, that is...) in the first place with the Radeon Mobility lineup. Why slack off to what the competitor can manage when you're already vastly better than they are in the first place?



Heh... Like I said... Just DO better... ;)

None of ATI integrated chipsets have ever had TCL support for my knowledge, Mesa always disabled TCL on all the ATI integrated chipsets. So transistor count is still the problem, you have more space on a dedicated GPU die than on an integrated one.

Dave.

[Svartalf]

None of ATI integrated chipsets have ever had TCL support for my knowledge, Mesa always disabled TCL on all the ATI integrated chipsets. So transistor count is still the problem, you have more space on a dedicated GPU die than on an integrated one.

Dave.

Heh... I offer this as evidence and it comes from the horse's mouth as it were:

http://ati.amd.com/products/comparisons/mobilitycomparison.html

The 7500 and 9000 mobility parts offered the Charisma Engine (TCL) and the 9000 provides Shader Model 1.4 support.

What happens if you use driconf to override the settings on the configuration? It's not signalling any warnings on start up nor is it crashing when I force it to use hardware TCL support on the laptop I've done this to. :D

[agd5f]

Heh... I offer this as evidence and it comes from the horse's mouth as it were:

http://ati.amd.com/products/comparisons/mobilitycomparison.html

The 7500 and 9000 mobility parts offered the Charisma Engine (TCL) and the 9000 provides Shader Model 1.4 support.

What happens if you use driconf to override the settings on the configuration? It's not signalling any warnings on start up nor is it crashing when I force it to use hardware TCL support on the laptop I've done this to. :D

Those are discrete parts. They have fully functionality. The IGP parts are different.

IGP chips:
ATI Radeon™ X1200 series
ATI Radeon™ XPRESS series
ATI Radeon™ 9100 IGP
ATI Radeon™ 9000 IGP
ATI Radeon™ 7000 IGP
ATI Radeon™ 340M IGP
ATI Radeon™ 320M IGP

[Svartalf]

Ah... That sort of explains things a bit, then.

Looking at a more in-depth comparison of the varying parts, the IGP parts not only were crippled in TCL, but also crippled in the fragment shader department as well. <*sigh*> That just makes for "fun" in trying to support stuff for titles and applications. Ugh...

I'll drop the gripes about that aspect of things- but it still goes back to the "why ever have done it" that I really
asked at the beginning of this aside. It's frustrating to have something claim to be 3D but end up being pretty much
like the Savage of this era of chips in hand- more of a decellerator than an accelerator... >:-) :D

[Fluxid]

Xpress 200m 5955, Gentoo 2.6.24-r2:
I couldn't get into GNOME and Xfce. In few configurations GDM even couldn't start. Switching to different vt hanged my laptop and i had to reboot.
I can't even say that xv or 3d accel worked.

For first time log said that loading kernel module failed, but GDM and Xfce started. It was unusable anyway - rendering single GTK button took one second. I had to wait for menu to render, scrolling console didn't refresh content. Compositing was off. I could switch to vt.

After compiling module, i couldn't get GDM to work - X just showed characteristic pattern, and nothing happened. Switching to different vt crashed.

Switching off AIGLX, RENDER, DAMAGE, acceleration in device section didn't help.

Actually fglrx works, and i'm happy with it, even if 3D is slow, there is no randr support and so on. It's better than nothing :)

[givemesugarr]

Xpress 200m 5955, Gentoo 2.6.24-r2:
I couldn't get into GNOME and Xfce. In few configurations GDM even couldn't start. Switching to different vt hanged my laptop and i had to reboot.
I can't even say that xv or 3d accel worked.

For first time log said that loading kernel module failed, but GDM and Xfce started. It was unusable anyway - rendering single GTK button took one second. I had to wait for menu to render, scrolling console didn't refresh content. Compositing was off. I could switch to vt.

After compiling module, i couldn't get GDM to work - X just showed characteristic pattern, and nothing happened. Switching to different vt crashed.

Switching off AIGLX, RENDER, DAMAGE, acceleration in device section didn't help.

Actually fglrx works, and i'm happy with it, even if 3D is slow, there is no randr support and so on. It's better than nothing :)

well, your problem is fglrx being loaded at startup by udev.
you'd have to mark it blacklisted or to have it removed manually with modprobe -r fglrx or rmmod fglrx
before trying to use radeon, or dri won't load and the driver would be unusable. also you'll have to do an eselect opengl set xorg-x11 to set opengl to radeon before trying to use it. after that you should be able to use the driver well.
also keep in mind that 5955 is different from my 5975 but it should still work with xf86-video-ati. just use the ebuilds form the x11 overlay or you won't have it working well. also to use it you have to switch to unstable xorg-server 1.4, which will slow down your fglrx experience.

[rvdboom]

I've a Slackware-current laptop, running a self-compiled ATI 6.8.0 driver on a Xserver 1.4 and Mesa 7.0.2.
The chip is an Xpress 200M 5955, kernel is 2.6.24.3. The driver is configured to use EXA and PageFlip.
My results are the following :
- 3D Acceleration seems to work (about 1100 in glxgears compared to the 500-600 I get when no acceleration is available). DRI is loaded (r300).
- XV works fine.
- 2D works well. Overall image quality (font antialiasing, XV, etc) is very good in my opinion.
- Issues I had before with detection of my LCD display seem gone.

But..

- Starting KDE4 with OpenGL composite hangs X. I haven't tested yet Render composite. Notice that composite works with the latest (as of february) fglrx driver, so I don't think it might be a bug in KDE4's kwin. AIGLX seems loaded and OK (according to Xorg.0.log), though, so I suppose it's just a matter of time.

[mar_rud]

The chip is an Xpress 200M 5955
...
- 3D Acceleration seems to work (about 1100 in glxgears compared to the 500-600 I get when no acceleration is available). DRI is loaded (r300).
I have also 200M (HP nx6125 laptop) and 3d only works in glxgears. In any game (i.e. scorched3d or ManiaDrive) I have just random bunch of triangles. Maybe it needs some special configuration?

In plus, with latest radeon driver I'm able to control lcd brightness again without need to switch to console. Except 3d in applications this driver is fine for me. However for now I switched to fglrx 8.40.4, last best ati driver I used. Any later version has strange visual effects in 3d (visible lightening difference between neighbor triangles) and slowdown in my application (displaying cloud of 3d points).

PS. I don't use/need compiz/fusion/eyecandy/whatever.

[djdoo]

Oh guys those ./configure scripts are really hell!!

I installed the latest DRM, latest MESA from gitweb, with the correct PREFIXes for a 64 bit system and not the default /usr/local/lib but /usr/lib64!!

I understood this problem after 2 installation attemps with no result...

Then I installed the ati driver. In order to be installed correctly(at least I think so) I typed this:
./configure --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib64 --enable-FEATURE=DRI --with-xorg-module-dir=/usr/lib64/xorg/modules

The driver is running I can use EXA and 3D but I have 2 basic problems!
NO DRI and NO other resolution than 1152x864!:(

Any help would be really appreciated cause it's the first time I try to use the xf86-video-ati driver and I want to make a nice how-to for our friends in Compiz-Fusion forum and RS690 mailing-list;)

Here's my glxinfo text:
djdoo@dhcppc0:~> glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 7.1
server glx extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address,
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
client glx vendor string: Brian Paul
client glx version string: 1.4 Mesa 7.1
client glx extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address,
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
GLX extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address,
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
OpenGL vendor string: Brian Paul
OpenGL renderer string: Mesa X11
OpenGL version string: 2.1 Mesa 7.1
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program,
GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader,
GL_ARB_half_float_pixel, GL_ARB_imaging, GL_ARB_multisample,
GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object,
GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shader_objects,
GL_ARB_shading_language_100, GL_ARB_shading_language_120, GL_ARB_shadow,
GL_ARB_shadow_ambient, 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_non_power_of_two,
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_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
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_depth_bounds_test, GL_EXT_draw_range_elements,
GL_EXT_framebuffer_object, GL_EXT_framebuffer_blit, GL_EXT_fog_coord,
GL_EXT_gpu_program_parameters, GL_EXT_histogram, GL_EXT_multi_draw_arrays,
GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels,
GL_EXT_paletted_texture, GL_EXT_pixel_buffer_object,
GL_EXT_point_parameters, GL_EXT_polygon_offset, 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_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_lod_bias, GL_EXT_texture_mirror_clamp,
GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB,
GL_EXT_timer_query, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_APPLE_vertex_array_object, GL_ATI_blend_equation_separate,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_ATI_fragment_shader, GL_ATI_separate_stencil,
GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip,
GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate,
GL_MESA_pack_invert, GL_MESA_program_debug, GL_MESA_resize_buffers,
GL_MESA_texture_array, GL_MESA_ycbcr_texture, GL_MESA_window_pos,
GL_NV_blend_square, GL_NV_fragment_program, GL_NV_light_max_exponent,
GL_NV_point_sprite, GL_NV_texture_rectangle, GL_NV_texgen_reflection,
GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_OES_read_format,
GL_SGI_color_matrix, GL_SGI_color_table, GL_SGI_texture_color_table,
GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture,
GL_SGIX_shadow, GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays
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 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x25 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x29 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x7c 32 tc 0 32 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None

My Xorg.0.log:

http://pastebin.ca/922791

And my xorg.conf too:
# /.../
# SaX generated X11 config file
# Created on: 2007-10-25T23:38:15+0300.
#
# Version: 8.1
# Contact: Marcus Schaefer <sax@suse.de>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
#
# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
#

Section "ServerLayout"
Identifier "Layout[all]"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
Option "Clone" "off"
Option "Xinerama" "off"
Option "AIGLX" "on"
EndSection

Section "Files"
InputDevices "/dev/gpmdata"
InputDevices "/dev/input/mice"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/URW"
FontPath "/usr/share/fonts/Speedo"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/uni:unscaled"
FontPath "/opt/kde3/share/fonts"
EndSection

Section "Module"
Load "dbe"
Load "type1"
Load "freetype"
Load "extmod"
Load "GLcore"
Load "glx"
Load "dri"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "on"
EndSection

Section "InputDevice"
Identifier "Keyboard[0]"
Driver "kbd"
Option "Protocol" "Standard"
Option "XkbLayout" "us,gr"
Option "XkbModel" "samsung4500"
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
Option "XkbRules" "xfree86"
Option "XkbVariant" "basic,extended"
EndSection

Section "InputDevice"
Identifier "Mouse[1]"
Driver "mouse"
Option "Buttons" "5"
Option "Device" "/dev/input/mice"
Option "Name" "Creative USB Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection

Section "Modes"
Identifier "Modes[0]"
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection

Section "Monitor"

# created by KGamma
Identifier "aticonfig-Monitor[0]"
Gamma 1.1 0.95 1.2
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "ati"
# Option "VideoOverlay" "off"
Option "TexturedVideo" "on"
Option "AccelMethod" "exa"
# Option "Textured2D" "on"
# Option "TexturedXrender" "on"
# Option "UseFastTLS" "1"
Option "BackingStore" "off"
# Option "MaxGARTSize" "256"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768_85"
EndSubSection
EndSection

Section "DRI"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
Option "RENDER" "Enable"
Option "DAMAGE" "Enable"
Option "Composite" "Enable"
EndSection

Thanks in advance..

Jim

[dungeon]

Maybe i'm wrong, but i think that for RS690 there is no DRI driver in Mesa.

[sid350]

how can I enable DRI for my x200m? Option "DRI" "true" just freezes the graphics - i can hear sounds of booting system, but I can see only still picture with corrupted squares and parts of wallpaper. Without DRI option all works good

[agd5f]

how can I enable DRI for my x200m? Option "DRI" "true" just freezes the graphics - i can hear sounds of booting system, but I can see only still picture with corrupted squares and parts of wallpaper. Without DRI option all works good

DRI support is still experimental on XPRESS and RS690 chips. We are working on it, but it's still not stable on all chips yet.

[djdoo]

DRI support is still experimental on XPRESS and RS690 chips. We are working on it, but it's still not stable on all chips yet.

You mean that there is no way to use it right now even if experimental?

I d like to use it just for testing and provide some feedback...

Also please tell me if I did something wrong in the installation procedure...

I compiled mesa by typing:
make linux-dri-x86-64
Just because I didn't mention it in the previous post;)

[agd5f]

You mean that there is no way to use it right now even if experimental?


Sure. If you have a recent enough mesa, just add:
Option "DRI" "TRUE"
to the device section of your xorg config.


I d like to use it just for testing and provide some feedback...

Also please tell me if I did something wrong in the installation procedure...

I compiled mesa by typing:
make linux-dri-x86-64
Just because I didn't mention it in the previous post;)

That should be fine. Thanks for testing!

[djdoo]

@agd5f:
I have to install first the very latest drm and mesa and after that the driver??

Also I must uninstall fglrx (/usr/share/ati/fglrx-uninstall.sh) for the driver to work??

Ok for mesa my command was good... But for drm and driver is this ok??
./configure --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib64

And last why I cannot change resolutions and I always get 1152x840 whereas I set at xorg.conf 1024x768??

Please answer me these questions and I will test everything again!!:)

CPU:AMD Athlon 64 4800+, VGA:ATi X1250, openSUSE 10,3 64bit and Xorg 7.2->xserver 1.3...

Thanks

Jim

[agd5f]

@agd5f:
I have to install first the very latest drm and mesa and after that the driver??


Depends how old the mesa and drm from your distro are. if you are using a fairly recent distro you should be fine. There hasn't been alot of changes in the drm or mesa WRT your chip.


Also I must uninstall fglrx (/usr/share/ati/fglrx-uninstall.sh) for the driver to work??


Yes. You need to remove fglrx and it's associated libraries.


Ok for mesa my command was good... But for drm and driver is this ok??


Looks fine.



And last why I cannot change resolutions and I always get 1152x840 whereas I set at xorg.conf 1024x768??


I'm not sure. I'd need to see your log and config. Generally you'll want to use xrandr to change modes.

Alex

[djdoo]

@Alex:

Em... you mean that the uninstall command for fglrx isn't enough??
Who are the associated libraries??

[agd5f]

@Alex:

Em... you mean that the uninstall command for fglrx isn't enough??
Who are the associated libraries??

It should be enough. fglrx provides it's own version of libGL.

[djdoo]

ok then!

opensuse provides Mesa 7.0.1 packages and lidrm 2.3.0..
I already installed the latest git DRM...

I cannot compile latest git Mesa I get this error:
lxext.c:784: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘interface_methods’
glxext.c: In function ‘CallCreateNewScreen’:
glxext.c:949: error: ‘interface_methods’ undeclared (first use in this function)
glxext.c:949: error: (Each undeclared identifier is reported only once
glxext.c:949: error: for each function it appears in.)
glxext.c:950: warning: passing argument 9 of ‘createNewScreen’ makes pointer from integer without a cast
glxext.c:950: error: too many arguments to function ‘createNewScreen’
make[3]: *** [glxext.o] Error 1
make[3]: Leaving directory `/home/djdoo/mesa/src/glx/x11'
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory `/home/djdoo/mesa/src'
make[1]: *** [default] Error 1
make[1]: Leaving directory `/home/djdoo/mesa'

[djdoo]

If you set Option DRI "TRUE" which DRI module should be loaded then??

Cause I get this in the log:
LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules//extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI

Any ideas? Alex?

[agd5f]

If you set Option DRI "TRUE" which DRI module should be loaded then??

Cause I get this in the log:


Any ideas? Alex?

You don't have to load a module. The driver will take care of the dri setup. you should see this line in your log if it was successful:

(II) RADEON(0): Direct rendering enabled

[djdoo]

@Alex:
I installed now Xorg 7.3 latest build from suse packages, installed Mesa and libdrm also from packages which where created from yesterday's git and devel packages too, in order not to make any compilation-configure mistakes...

I installed the 6.8.0 driver from git(cause X contained 6.6.3 version).
Works but I still get this in the log: :(
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.

I cannot understand why... I do the procedure very carefully, added the Option "DRI" "TRUE" as you told me but still no DRI even to test it!!

No luck here... :(

[agd5f]

I cannot understand why... I do the procedure very carefully, added the Option "DRI" "TRUE" as you told me but still no DRI even to test it!!


there's some problem with the drm. I can't say what without seeing your log.

[djdoo]

@Alex:
Xorg.0.log? ok here it is!

http://pastebin.ca/924467

Please take a look...

[djdoo]

The dri device is not initialized at /dev/dri

Does this has to do with something wrong at modprobe.conf??

Just guessing...

[djdoo]

djdoo@dhcppc0:~> dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810

Is this good?? I mean the version...

[agd5f]

@Alex:
Xorg.0.log? ok here it is!

http://pastebin.ca/924467

Please take a look...

your drm is too old. You need the drm from drm git. I thought you had an rs400, not an rs690.

[djdoo]

Oh there are alot of drms at freedesktop.org git!!

Which one should I take??

[djdoo]

@Alex:
OK I uninstalled the libdrm suse packages and grabbed drm from here:
git clone git://anongit.freedesktop.org/mesa/drm

Configured it like that:
./configure --prefix=/usr --libdir=/usr/lib64

Installed them (output sais /usr/lib64 which is correct) and I get this again:
djdoo@dhcppc0:~> dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810

Xorg.0.log is the same and of course I still don't get DRI...:(

A question, did anyone manage to get DRI from ati OSS driver for an RS690 chip and a 64bit OS??

[djdoo]

@Alex:
I finally did it!!

I just compiled the drm modules and added them in the kernel replacing the old ones at /lib/modules/my kernel/kernel/drivers/char/drm
I read this at a guide at dri.project.
Rebooted and I had DRI!

I get Textured Video (very good quality) but with diagonial tearing like it was with fglrx and opengl video!! How can it be??

Also Xorg.0.log is reporting DRI enabled but glxinfo sais Direct Rendering: No
Why? Is this normal??

BTW my new succeded Xorg.0.log:

http://www.pastebin.org/22074

3D is much slower than it was with fglrx, but EXA and Textured Video work well in general terms.

[agd5f]

I get Textured Video (very good quality) but with diagonial tearing like it was with fglrx and opengl video!! How can it be??


We still haven't shaken all the bugs out of the textured video in IGP chips.


Also Xorg.0.log is reporting DRI enabled but glxinfo sais Direct Rendering: No
Why? Is this normal??


Probably an issue with the 3D driver. you might have old fglrx remnants floating around or your 3D driver is installed in the wrong place.

Try this:

LIBGL_DEBUG=verbose glxinfo

and see what error you get.

[djdoo]

@Alex:
It shows me the same output as glxinfo does.
Doesn't mention any errors...

EDIT: Ignore this one, obsolete! Look at the next post! Cause I think here the driver was using fglrx's libGL and libglut! That's why wasn't mentioning RS690 experimental!

[djdoo]

@Alex:
I think you were right about fglrx's remnants...

Searching my /usr/lib64 I found 2 files there libGL.so.1.5.070100 and libglut.so.3.8.0!
Those 2 were not created by the mesa src I got from git and not linked to anything instead the mesa git provided libGL.so.1.2 which had only 2MB size whereas the 1.5 one had 16.4MB!! And libglut.so.3.7.1 which has 873KB size instead of 273KB of 3.8.0 one.

Well after removed those 2 files glxinfo changed dramatically and now LIBGL=verbose glxinfo gives me this:
djdoo@dhcppc0:~> LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib64/dri/r300_dri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:05.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:01:05.0
Warning, RS690 detected, 3D support is incomplete.
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x26
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2a
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2e
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x30
libGL warning: 3D driver claims to not support visual 0x31
libGL warning: 3D driver claims to not support visual 0x32
Error: couldn't find RGB GLX visual

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 y . 0 8 8 8 0 24 8 0 0 0 0 0 0 None
0x24 24 tc 0 32 0 r y . 0 8 8 8 0 24 0 0 0 0 0 0 0 None
0x25 24 tc 0 32 0 r y . 0 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x26 24 tc 0 32 0 r y . 0 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x27 24 tc 0 32 0 r . . 0 8 8 8 0 24 8 0 0 0 0 0 0 None
0x28 24 tc 0 32 0 r . . 0 8 8 8 0 24 0 0 0 0 0 0 0 None
0x29 24 tc 0 32 0 r . . 0 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x2a 24 tc 0 32 0 r . . 0 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x2b 24 dc 0 32 0 r y . 0 8 8 8 0 24 8 0 0 0 0 0 0 None
0x2c 24 dc 0 32 0 r y . 0 8 8 8 0 24 0 0 0 0 0 0 0 None
0x2d 24 dc 0 32 0 r y . 0 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x2e 24 dc 0 32 0 r y . 0 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x2f 24 dc 0 32 0 r . . 0 8 8 8 0 24 8 0 0 0 0 0 0 None
0x30 24 dc 0 32 0 r . . 0 8 8 8 0 24 0 0 0 0 0 0 0 None
0x31 24 dc 0 32 0 r . . 0 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x32 24 dc 0 32 0 r . . 0 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x84 32 tc 0 32 0 r . . 0 8 8 8 0 0 0 0 0 0 0 0 0 Ncon


Now it's a more logical output but it doesn't reports the mesa info and instead gives this:
Error: couldn't find RGB GLX visual
Why??

BTW Xorg.0.log is very good and reports DRI and rest stuff OK and enabled! Except AIGLX which is reverted to software... but this is known isn't it?

glxgears isn't working and sais glxgears: Error: couldn't get an RGB, Double-buffered visual

But I think I am finally reaching the end now!!:)

[mal13]

I'm interested to try this one. I have ati 2400 pcie card and i've used fglrx drivers but got tired w/ problems on kubuntu 7.10. I get blan/ck screen when i either logout or switchuser or shutdown. 2 users and it's awful always to push reset button (keyboard is frozen) when need to change user. Also ctrl+alt+bckspce gets blank screen. So is this problem appearing only in fglrx in k/x/ubuntu?
Mesa driver works quite well... logout=ok, switchuser=colors gets messed up, shutdown=ok.

[NaterGator]

I'm trying to get this to work on gentoo and compiled the most recent DRM module, placed and loaded them, compiled the 6.8.0 driver, but I can't tell a difference.

Xorg doesn't acknowledge the TexturedVideo option in my conf (or the radeon driver doesn't?) and EXA causes my system to hard freeze. I can't even REISUB recover it :(

I'm going to build mesa from git too and see if that helps, but I'm stumped.

[agd5f]

Xorg doesn't acknowledge the TexturedVideo option in my conf (or the radeon driver doesn't?) and EXA causes my system to hard freeze. I can't even REISUB recover it :(

I'm going to build mesa from git too and see if that helps, but I'm stumped.

6.8.0 did not include support for textured video. you'll need xf86-video-ati from git.

[NaterGator]

Thanks. Is there any reason for me to manually replace mesa with an update from git? I just did a make linux-dir-x86-64 and it compiled mesa for me, but the libraries are much bigger than my current ones. I suspect that's partially due to me compiling in debug info and partially because there have been updates.

I'm going to compiled new drivers from git now and test 'em out. Thanks again!

[agd5f]

Thanks. Is there any reason for me to manually replace mesa with an update from git? I just did a make linux-dir-x86-64 and it compiled mesa for me, but the libraries are much bigger than my current ones. I suspect that's partially due to me compiling in debug info and partially because there have been updates.

For textured video and render all you need is an updated xf86-video-ati.

[mal13]

I installed radeonhd... hopefully. It was quite exhausting as i had to install lots of other tools, dev stuff etc to get installation run through.
I'm not so familiar w/ commands so how do i see if it's ok or not, fglrxinfo doesn't work and glxinfo gives long er list but it mentions mesa there.
On xorg.conf there's radeonhd written.

[djdoo]

@Alex:
Em... you didn't answer me my friend..:(

Why I always get this error:
Error: couldn't find RGB GLX visual

Xorg.0.log sais glx OK module loaded, DRI instrallation OK, EXA works, Textured VIdeo very good quality-low CPU(except the diagonial tearing at fast motion).

Do you need my new Xorg.0.log and xorg.conf files??
Just tell me to pastebin them!

Thanks in advance
Jim

[NaterGator]

No dice. Just finished compiling and installing the driver. My Xorg.0.log confirms textured video is started, and xvinfo shows the pseudo adapter, but when I run:
mplayer -vo xv:port=74 content/TV\ Shows/Top\ Gear/Top\ Gear\ -\ \[10x10\]\ -\ 2007.12.23.avi

I get an mplayer window which freezes an image of whatever it appeared over and a whole lot of "X11 error: BadAlloc (insufficient resources for operation)?,?% 1 0 " on the console.

[NaterGator]

Jim what do you see when you run lsmod? It sounds like you've still got linger fglrx issues.

[djdoo]

This problem happens when I install Mesa from git. If I use the Mesa provided by suse packages I get another error saying unknown chip 0x791e and also it sais no fbtables or something.

I tried a hybrid situation where I installed only the dri modules at /usr/lib64/dri and used the libGL provided by suse latest Mesa packeges.
Then I see Mesa information and the rest extensions at glxinfo by again unknown chip and no DRI!

I am very comfused with Mesa stuff... :s

[djdoo]

Here it is lsmod:
djdoo@dhcppc0:~> lsmod
Module Size Used by
iptable_filter 20224 0
ip_tables 40024 1 iptable_filter
ip6_tables 33736 0
x_tables 38920 2 ip_tables,ip6_tables
radeon 145808 2
drm 205480 3 radeon
af_packet 42248 2
rfcomm 62240 0
l2cap 43776 9 rfcomm
bluetooth 83588 4 rfcomm,l2cap
snd_pcm_oss 70144 0
snd_mixer_oss 35712 1 snd_pcm_oss
snd_seq_midi 27648 0
snd_emu10k1_synth 26112 0
snd_emux_synth 59648 1 snd_emu10k1_synth
snd_seq_virmidi 24960 1 snd_emux_synth
snd_seq_midi_event 25600 2 snd_seq_midi,snd_seq_virmidi
snd_seq_midi_emul 24192 1 snd_emux_synth
f71882fg 30088 0
snd_seq 82928 5 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_se q_midi_event,snd_seq_midi_emul
cpufreq_conservative 26248 0
cpufreq_userspace 24068 0
cpufreq_powersave 18816 0
powernow_k8 32656 1
binfmt_misc 30220 1
nls_iso8859_1 22144 1
nls_cp437 23936 1
vfat 31232 1
fat 75568 1 vfat
fuse 71856 3
loop 37636 0
dm_mod 88168 0
snd_emu10k1 174224 3 snd_emu10k1_synth
snd_rawmidi 46720 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
firmware_class 28032 1 snd_emu10k1
snd_hda_intel 411048 1
snd_ac97_codec 140360 1 snd_emu10k1
ac97_bus 19456 1 snd_ac97_codec
snd_seq_device 26516 6 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_ seq,snd_emu10k1,snd_rawmidi
snd_pcm 116360 5 snd_pcm_oss,snd_emu10k1,snd_hda_intel,snd_ac97_cod ec
snd_util_mem 22784 2 snd_emux_synth,snd_emu10k1
snd_timer 44168 3 snd_seq,snd_emu10k1,snd_pcm
rndis_host 24576 0
snd_page_alloc 28688 3 snd_emu10k1,snd_hda_intel,snd_pcm
cdc_ether 23808 1 rndis_host
usbnet 38792 2 rndis_host,cdc_ether
ohci1394 51124 0
snd_hwdep 28424 3 snd_emux_synth,snd_emu10k1,snd_hda_intel
emu10k1_gp 21120 0
snd 91512 22 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_emu10k1 _synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi _emul,snd_seq,snd_emu10k1,snd_rawmidi,snd_hda_inte l,snd_ac97_codec,snd_seq_device,snd_pcm,snd_util_m em,snd_timer,snd_hwdep
ieee1394 122200 1 ohci1394
shpchp 53404 0
i2c_piix4 26252 0
gameport 33936 2 emu10k1_gp
rtc_cmos 25912 0
sr_mod 35236 0
i2c_core 44160 1 i2c_piix4
pci_hotplug 50096 1 shpchp
k8temp 23040 0
mii 23040 1 usbnet
rtc_core 40716 1 rtc_cmos
cdrom 53544 1 sr_mod
soundcore 26000 1 snd
serio_raw 24836 0
hwmon 20488 2 f71882fg,k8temp
rtc_lib 20224 1 rtc_core
button 27168 0
sg 56240 0
floppy 82056 0
usbhid 64848 0
hid 56080 1 usbhid
ff_memless 23048 1 usbhid
ehci_hcd 54540 0
ohci_hcd 42244 0
usbcore 184480 7 rndis_host,cdc_ether,usbnet,usbhid,ehci_hcd,ohci_h cd
sd_mod 47616 7
edd 27784 0
ext3 170384 2
mbcache 27136 1 ext3
jbd 82240 1 ext3
fan 22920 0
pata_atiixp 26112 0
ahci 48644 5
libata 189856 2 pata_atiixp,ahci
scsi_mod 193960 4 sr_mod,sg,sd_mod,libata
thermal 38688 0
processor 68040 2 powernow_k8,thermal

[djdoo]

@NaterGator:

I use Xine with XV driver and all it's frontends (kaffeine, Totem) and quality is very good with Textured Video!

Maybe you should add this under Extensions Section at your xorg.conf:
Option "XVideo" "Enable"

And this under DRI Section:
Mode 0666