Re: R300 DRI report
Vladimir Dergachev wrote: > You could also try FlightGear as far as games go. Yep, this had been proven to trigger even the obscurest bug during the emergence of the r200 driver ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
I'm planning to do some benchmarks when ATI update their driver to work with the new xorg release. Any sugestions for some benckmarks that I can run? I'll post the results to the mailing list if people are interested? glxgears is the easy one :) You could also try FlightGear as far as games go. There is also some general OpenGL benchmarking suite (forgot the name), it might be relatively easy to setup. Thanks Sander PS: Is this the correct list to be asking these kind of thing? The r300 website has no refference to a forum or other mailing list then this one. Yep, this is the right mailing list. best Vladimir Dergachev --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On 13/07/05, Lorenzo Colitti <[EMAIL PROTECTED]> wrote: > Aapo Tahkola wrote: > >>atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > >> > >>Changed this for atlantis and it gave me 23fps instead of 3, thanks. > > > > I get 120 fps with color tiling on pretty much same hw as you and 1280x1024 > > resolution. > > Youll need to use xorg cvs and ColorTiling option to enable it. > > Yep, color tiling is a big win here. When I turned it on, Well, it causing a lot of coruption with color tilling for me. My background is scewd as is my mouse pointer, buttons in gnome 2.10 dissapear and only reapear when i move my mouse over it. > > ./atlantis -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > > (not fulscreen) went from <10 FPS to ~200 FPS. I also get >1000 FPS in > glxgears while before I used to get ~500. This is on a rage mobility > 9600 M10 (RV350) on a Pentium M 1.4 GHz. > > >>Blocktube will not go above 25fps, even with delay is 0. Only with > >>-wireframe it will go to 32fps. > > For reference, I get ~26 FPS with wireframe and ~19 without (not full > screen). With no HW acceleration I get 7 FPS. > > > It seems that something is wrong here as increasing/decreasing window > > size doesnt affect framerates at all. My guess so far would be that > > the command buffer gets too fed up and causes this bottleneck. > > Why should increasing window size affect framerates? I thought that as > far as the graphics chip was concerned, a triangle was just a triangle > irrespective of size, and we're not hitting fill rate limits here... or > is there something I'm missing? > > > Cheers, > Lorenzo > I'll try my Fedora4 AMD64 test partition and build xc and Mesa from cvs. A'll report back if this makes any difference. I now have no closed source binary drivers running on my system (fglrx was the last one), thanks Regards Sander --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On Wed, 13 Jul 2005 17:22:36 +0300
Aapo Tahkola <[EMAIL PROTECTED]> wrote:
> Also, r300s state management is not currently very "efficient" as can be seen
> from oprofiled reports... :)
Measured this and state traffic seems to go from 10 to 60 MB per second
depending on application.
Tnl programs give even higher rates in some cases.
Index: r300_cmdbuf.c
===
RCS file: /cvsroot/r300/r300_driver/r300/r300_cmdbuf.c,v
retrieving revision 1.44
diff -u -b -B -u -r1.44 r300_cmdbuf.c
--- r300_cmdbuf.c 27 Jun 2005 15:56:14 - 1.44
+++ r300_cmdbuf.c 14 Jul 2005 05:58:40 -
@@ -54,6 +54,7 @@
// Set this to 1 for extremely verbose debugging of command buffers
#define DEBUG_CMDBUF 0
+#include
/**
@@ -100,6 +101,28 @@
fprintf(stderr, "Syncing in %s (from %s)\n\n", __FUNCTION__,
caller);
radeonWaitForIdleLocked(&r300->radeon);
}
+ {
+ static struct timeval t;
+ struct timeval temp;
+ unsigned long msec;
+ static unsigned long bytes = 0;
+
+ bytes += cmd.bufsz;
+
+ gettimeofday(&temp, NULL);
+ msec = (temp.tv_sec - t.tv_sec) * 100 + temp.tv_usec -
t.tv_usec;
+ if(msec > 100){
+ float f = msec/100.0;
+ f = bytes / f;
+
+ fprintf(stderr, "%.02f\n", f/1024.0/1024.0);
+ t = temp;
+ bytes = 0;
+ }
+
+ }
--
Aapo Tahkola
---
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On Wed, 13 Jul 2005 13:27:31 +0200 Lorenzo Colitti <[EMAIL PROTECTED]> wrote: > Aapo Tahkola wrote: > >>atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > >> > >>Changed this for atlantis and it gave me 23fps instead of 3, thanks. > > > > I get 120 fps with color tiling on pretty much same hw as you and 1280x1024 > > resolution. > > Youll need to use xorg cvs and ColorTiling option to enable it. > > Yep, color tiling is a big win here. When I turned it on, > > ./atlantis -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > > (not fulscreen) went from <10 FPS to ~200 FPS. I also get >1000 FPS in > glxgears while before I used to get ~500. This is on a rage mobility > 9600 M10 (RV350) on a Pentium M 1.4 GHz. > > >>Blocktube will not go above 25fps, even with delay is 0. Only with > >>-wireframe it will go to 32fps. > > For reference, I get ~26 FPS with wireframe and ~19 without (not full > screen). With no HW acceleration I get 7 FPS. > > > It seems that something is wrong here as increasing/decreasing window > > size doesnt affect framerates at all. My guess so far would be that > > the command buffer gets too fed up and causes this bottleneck. > > Why should increasing window size affect framerates? I thought that as > far as the graphics chip was concerned, a triangle was just a triangle > irrespective of size, and we're not hitting fill rate limits here... or > is there something I'm missing? AFAIK, hardware is usually done in a such way that pretty much everything is proportional to the master frequency. That said, less pixels should mean that it takes less clocks to get the job done. Also, r300s state management is not currently very "efficient" as can be seen from oprofiled reports... :) -- Aapo Tahkola --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
Aapo Tahkola wrote: atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps Changed this for atlantis and it gave me 23fps instead of 3, thanks. I get 120 fps with color tiling on pretty much same hw as you and 1280x1024 resolution. Youll need to use xorg cvs and ColorTiling option to enable it. Yep, color tiling is a big win here. When I turned it on, ./atlantis -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps (not fulscreen) went from <10 FPS to ~200 FPS. I also get >1000 FPS in glxgears while before I used to get ~500. This is on a rage mobility 9600 M10 (RV350) on a Pentium M 1.4 GHz. Blocktube will not go above 25fps, even with delay is 0. Only with -wireframe it will go to 32fps. For reference, I get ~26 FPS with wireframe and ~19 without (not full screen). With no HW acceleration I get 7 FPS. It seems that something is wrong here as increasing/decreasing window size doesnt affect framerates at all. My guess so far would be that the command buffer gets too fed up and causes this bottleneck. Why should increasing window size affect framerates? I thought that as far as the graphics chip was concerned, a triangle was just a triangle irrespective of size, and we're not hitting fill rate limits here... or is there something I'm missing? Cheers, Lorenzo --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On Tue, 12 Jul 2005 21:33:16 +0200 Sander Sweers <[EMAIL PROTECTED]> wrote: > On 12/07/05, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-07-12 at 13:06 +0200, Sander Sweers wrote: > > > > > > Well xscreensaver is horrible to do any tests with, I never get above > > > the 25 fps :( > > > > Which hack(s) are you trying, and are you passing -delay 0? > > atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > > Changed this for atlantis and it gave me 23fps instead of 3, thanks. I get 120 fps with color tiling on pretty much same hw as you and 1280x1024 resolution. Youll need to use xorg cvs and ColorTiling option to enable it. > Blocktube will not go above 25fps, even with delay is 0. Only with > -wireframe it will go to 32fps. It seems that something is wrong here as increasing/decreasing window size doesnt affect framerates at all. My guess so far would be that the command buffer gets too fed up and causes this bottleneck. > Are there other hacks I can use? (-no-fog usually does not give more > than 1 extra fps). Fog is not yet supported. -- Aapo Tahkola --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
Hi, Just for your reference, I have a laptop with PentiumM 1.7GHz, ATI radeon mobility 9700, 1280x800 screen, SUSE 9.3, r300 driver with Dynamic clock enabled. xscreensaver shows around 77 fps with atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps BTW, I tried gentoo longtime ago and found out that it doesn't offer much improvement and many cases it runs actually slower than standard precompiled distribution such as Suse. Toan On Tuesday 12 July 2005 12:33, Sander Sweers wrote: > On 12/07/05, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-07-12 at 13:06 +0200, Sander Sweers wrote: > > > Well xscreensaver is horrible to do any tests with, I never get above > > > the 25 fps :( > > > > Which hack(s) are you trying, and are you passing -delay 0? > > atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > > Changed this for atlantis and it gave me 23fps instead of 3, thanks. > Removing -gradient gives another 8fps extra. > > The below will give me 31fps but is horrible to look at. > atlantis -root -delay 0 -size 5350 -count 3 -no-texture -wireframe -fps > > Blocktube will not go above 25fps, even with delay is 0. Only with > -wireframe it will go to 32fps. > > blocktube -root -delay 0 -fps > > Are there other hacks I can use? (-no-fog usually does not give more > than 1 extra fps). > > I'm running this on a 64bit gentoo box, could this cause bad > xscreensaver performance? > > Thanks > Sander > > > -- > > 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 the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On 12/07/05, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Tue, 2005-07-12 at 13:06 +0200, Sander Sweers wrote: > > > > Well xscreensaver is horrible to do any tests with, I never get above > > the 25 fps :( > > Which hack(s) are you trying, and are you passing -delay 0? atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps Changed this for atlantis and it gave me 23fps instead of 3, thanks. Removing -gradient gives another 8fps extra. The below will give me 31fps but is horrible to look at. atlantis -root -delay 0 -size 5350 -count 3 -no-texture -wireframe -fps Blocktube will not go above 25fps, even with delay is 0. Only with -wireframe it will go to 32fps. blocktube -root -delay 0 -fps Are there other hacks I can use? (-no-fog usually does not give more than 1 extra fps). I'm running this on a 64bit gentoo box, could this cause bad xscreensaver performance? Thanks Sander > > > -- > Earthling Michel Dänzer | Debian (powerpc), X and DRI developer > Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer > > -- After a time, you may find that "having" is not so pleasing a thing, after all, as "wanting." It is not logical, but it is often true. Spock, "Amok Time" stardate 3372.7 --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On Tue, 2005-07-12 at 13:06 +0200, Sander Sweers wrote: > > Well xscreensaver is horrible to do any tests with, I never get above > the 25 fps :( Which hack(s) are you trying, and are you passing -delay 0? -- 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 the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On 11/07/05, Sander Sweers <[EMAIL PROTECTED]> wrote: > On 11/07/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote: > > > > > > On Mon, 11 Jul 2005, Sander Sweers wrote: > > > > > Hi, > > > > > > I have been trying the r300 driver with kernel 2.6.12 and xorg > > > 6.8.99.8 and i have to say I'm impressed :) > > > > > > I have been playing with xscreensaver and am getting +/- 16 fps with a > > > cpu (amd64 3200) load of 50%. I am running gentoo 2005.0/multilib. > > > > > > I have an asus 9600se/td and it is a r300 but not know, reporting it as > > > asked. > > > > > > Unknown device ID 4151, please report. Assuming plain R300. > > > IRQ's not enabled, falling back to busy waits: 15 2 0 > > > > this is coming from r300_driver/r300/radeon_screen.c - could check whether > > using RADEON_CHIP_RV350 works any better for you ? > > > > thank you ! > > > > Vladimir Dergachev > > > > Yes this gives a 5 to 10 extra fps compared to the standard r300. > Still +/- 50% on the cpu though. lspci -vn: > Well xscreensaver is horrible to do any tests with, I never get above the 25 fps :( I now have compiled chromium bse and this is running smooth. No visible artifacts and the fps never dips below 30 with gfx detail set to max running 1024x786 :) Also cube is running well, also no visible artifacts as far as I can tell. The lowest fps I'm getting is +/- 20 (outdoor with a lot of buildings in view). Indoor it runs smoothly with 40-60 fps. I'm planning to do some benchmarks when ATI update their driver to work with the new xorg release. Any sugestions for some benckmarks that I can run? I'll post the results to the mailing list if people are interested? Thanks Sander PS: Is this the correct list to be asking these kind of thing? The r300 website has no refference to a forum or other mailing list then this one. > :01:00.0 Class 0300: 1002:4151 > Subsystem: 1043:c004 > Flags: bus master, 66Mhz, medium devsel, latency 32 > Memory at d000 (32-bit, prefetchable) [size=256M] > I/O ports at e000 [size=256] > Memory at fbe0 (32-bit, non-prefetchable) [size=64K] > Expansion ROM at fbd0 [disabled] [size=128K] > Capabilities: [58] AGP version 3.0 > Capabilities: [50] Power Management version 2 > > Now I'm off compiling some games to test some more :-) > > Thanks > Sander > > > > > > > Below is what dmesg reports: > > > > > > [drm] Initialized drm 1.0.0 20040925 > > > PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device > > > :01:00.0 > > > mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 > > > [drm] Initialized radeon 1.15.0 20050208 on minor 0: ATI > > > Technologies Inc RV350 AQ [Radeon 9600] > > > [drm] Used old pci detect: framebuffer loaded > > > > > > And some warning while is was playing with xscreensaver: > > > > > > *WARN_ONCE* > > > File r300_state.c function r300Enable line 456 > > > TODO - double side stencil ! > > > *** > > > No ctx->FragmentProgram._Current!! > > > > > > *WARN_ONCE* > > > File r300_render.c function r300_get_num_verts line 192 > > > user error: 33 is not a valid number of vertices for primitive QS ! > > > *** > > > > > > *WARN_ONCE* > > > File r300_render.c function r300_get_num_verts line 187 > > > user error: Need more than 1 vertices to draw primitive TS ! > > > *** > > > > > > r300_check_render: fallback:ctx->Point.SmoothFlag (over and over again). > > > > > > If you need me to provide more info or try something let me know. > > > > > > Keep up the good work :) > > > > > > Thanks > > > Sander > > > > > > > > > --- > > > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > > > happening > > > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > > > core and dual graphics technology at this free one hour event hosted by > > > HP, > > > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > > > -- > > > ___ > > > Dri-devel mailing list > > > Dri-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > > > > > > -- > After a time, you may find that "having" is not so pleasing a thing, > after all, as "wanting." It is not logical, but it is often true. > > Spock, "Amok Time" > stardate 3372.7 > --- This SF.Net email is sponsored by the 'Do More With Dual!' web
Re: R300 DRI report
On 11/07/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote: > > > On Mon, 11 Jul 2005, Sander Sweers wrote: > > > Hi, > > > > I have been trying the r300 driver with kernel 2.6.12 and xorg > > 6.8.99.8 and i have to say I'm impressed :) > > > > I have been playing with xscreensaver and am getting +/- 16 fps with a > > cpu (amd64 3200) load of 50%. I am running gentoo 2005.0/multilib. > > > > I have an asus 9600se/td and it is a r300 but not know, reporting it as > > asked. > > > > Unknown device ID 4151, please report. Assuming plain R300. > > IRQ's not enabled, falling back to busy waits: 15 2 0 > > this is coming from r300_driver/r300/radeon_screen.c - could check whether > using RADEON_CHIP_RV350 works any better for you ? > > thank you ! > > Vladimir Dergachev > Yes this gives a 5 to 10 extra fps compared to the standard r300. Still +/- 50% on the cpu though. lspci -vn: :01:00.0 Class 0300: 1002:4151 Subsystem: 1043:c004 Flags: bus master, 66Mhz, medium devsel, latency 32 Memory at d000 (32-bit, prefetchable) [size=256M] I/O ports at e000 [size=256] Memory at fbe0 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fbd0 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Capabilities: [50] Power Management version 2 Now I'm off compiling some games to test some more :-) Thanks Sander > > > > Below is what dmesg reports: > > > > [drm] Initialized drm 1.0.0 20040925 > > PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device > > :01:00.0 > > mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 > > [drm] Initialized radeon 1.15.0 20050208 on minor 0: ATI > > Technologies Inc RV350 AQ [Radeon 9600] > > [drm] Used old pci detect: framebuffer loaded > > > > And some warning while is was playing with xscreensaver: > > > > *WARN_ONCE* > > File r300_state.c function r300Enable line 456 > > TODO - double side stencil ! > > *** > > No ctx->FragmentProgram._Current!! > > > > *WARN_ONCE* > > File r300_render.c function r300_get_num_verts line 192 > > user error: 33 is not a valid number of vertices for primitive QS ! > > *** > > > > *WARN_ONCE* > > File r300_render.c function r300_get_num_verts line 187 > > user error: Need more than 1 vertices to draw primitive TS ! > > *** > > > > r300_check_render: fallback:ctx->Point.SmoothFlag (over and over again). > > > > If you need me to provide more info or try something let me know. > > > > Keep up the good work :) > > > > Thanks > > Sander > > > > > > --- > > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > > core and dual graphics technology at this free one hour event hosted by HP, > > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > > -- > > ___ > > Dri-devel mailing list > > Dri-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > -- After a time, you may find that "having" is not so pleasing a thing, after all, as "wanting." It is not logical, but it is often true. Spock, "Amok Time" stardate 3372.7 --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 DRI report
On Mon, 11 Jul 2005, Sander Sweers wrote: Hi, I have been trying the r300 driver with kernel 2.6.12 and xorg 6.8.99.8 and i have to say I'm impressed :) I have been playing with xscreensaver and am getting +/- 16 fps with a cpu (amd64 3200) load of 50%. I am running gentoo 2005.0/multilib. I have an asus 9600se/td and it is a r300 but not know, reporting it as asked. Unknown device ID 4151, please report. Assuming plain R300. IRQ's not enabled, falling back to busy waits: 15 2 0 this is coming from r300_driver/r300/radeon_screen.c - could check whether using RADEON_CHIP_RV350 works any better for you ? thank you ! Vladimir Dergachev Below is what dmesg reports: [drm] Initialized drm 1.0.0 20040925 PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :01:00.0 mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 [drm] Initialized radeon 1.15.0 20050208 on minor 0: ATI Technologies Inc RV350 AQ [Radeon 9600] [drm] Used old pci detect: framebuffer loaded And some warning while is was playing with xscreensaver: *WARN_ONCE* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *** No ctx->FragmentProgram._Current!! *WARN_ONCE* File r300_render.c function r300_get_num_verts line 192 user error: 33 is not a valid number of vertices for primitive QS ! *** *WARN_ONCE* File r300_render.c function r300_get_num_verts line 187 user error: Need more than 1 vertices to draw primitive TS ! *** r300_check_render: fallback:ctx->Point.SmoothFlag (over and over again). If you need me to provide more info or try something let me know. Keep up the good work :) Thanks Sander --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
