From: F. <j_r...@ya...> - 2002-07-05 11:06:32
|
Keith Whitwell confirmed the readiness of the r200-0-1-branch for testing and for binary snapshots. You can get the first binary snapshot from http://dri.sourceforge.net/snapshots/bleeding-edge/ (the r200-* file). Please report any problem with the driver to dri...@li... . Don't forget to read README.r200 existing on the same dir. José Fonseca |
From: Stefan L. <hoi...@gm...> - 2002-07-05 12:56:02
|
Jos=E9 Fonseca wrote: > Keith Whitwell confirmed the readiness of the r200-0-1-branch for > testing and for binary snapshots. > > You can get the first binary snapshot from > http://dri.sourceforge.net/snapshots/bleeding-edge/ > (the r200-* file). Please report any problem with the driver to > dri...@li... . > Hi! I just (briefly) tested these drivers. I must say that I'm surprised in a very positive way! They work quite well, considering the early development state. I tested them with the following: glxgears: ~ 1650 fps quite good, keeping in mind that the driver are probably not optimised yet, firegl-driver give me something like 2200 fps q3a: worked ok (didn't see any problems with the menu, as described in the readme-file), but my keyboard stopped responding after playing for about 5-10 minutes i haven't done a benchmark with q3a: running a selfmade demo gives me about 130 fps with firegl-drivers, and about 80 fps with r200-branch at the same settings rtcw (single player): working, but quite slow (performance isn't really great with firegl-drivers neither...), crashed after about 10 mins some details about my system: XF86 4.2.0, dri-trunk from about 2 months ago, binary r200 modules copied on top of it (i probably should do a new co and recompile everythi= ng) Athlon XP 1800+, Epox 8KHA+-board (KT266A), 256 MB DDR-Ram, FIC Radeon 8500LE (clocked at 250/250), my box is running debian unstable with 2.4.19-pre10 on more comment: xv seems to be broken, it only gives me a black overlay window with mplayer. are there plans to merge with gatos some time? Well anyway, thanks for the very promising drivers, and keep up the good work! Regards Stefan |
From: Keith W. <ke...@tu...> - 2002-07-05 13:09:12
|
Stefan Lange wrote: > Jos=E9 Fonseca wrote: > > Keith Whitwell confirmed the readiness of the r200-0-1-branch for > > testing and for binary snapshots. > > > > You can get the first binary snapshot from > > http://dri.sourceforge.net/snapshots/bleeding-edge/ > > (the r200-* file). Please report any problem with the driver to > > dri...@li... . > > >=20 > Hi! I just (briefly) tested these drivers. I must say that I'm surprise= d > in a very positive way! They work quite well, considering the early > development state. >=20 > I tested them with the following: >=20 > glxgears: ~ 1650 fps > quite good, keeping in mind that the driver are probably not optimised > yet, firegl-driver give me something like 2200 fps I've just commited a small optimization that gears benefits from. It may= be=20 quite close now... > q3a: worked ok (didn't see any problems with the menu, as described in > the readme-file), but my keyboard stopped responding after playing for > about 5-10 minutes > i haven't done a benchmark with q3a: running a selfmade demo gives me > about 130 fps with firegl-drivers, and about 80 fps with r200-branch at > the same settings A large part of this difference is presumably due to HyperZ - something t= hat=20 we can't implement in an open driver. > rtcw (single player): working, but quite slow (performance isn't really > great with firegl-drivers neither...), crashed after about 10 mins Yes, I haven't had the opportunity to do any long runs of these demos. I= t's=20 a bit disappointing that they lockup, though. Keith |
From: Stefan L. <hoi...@gm...> - 2002-07-05 15:55:02
|
Hi! I just checked out and compiled the r200-0-1-branch: >> glxgears: ~ 1650 fps > > I've just commited a small optimization that gears benefits from. It > may be quite close now... its about 1720 now ;-) [...] > > A large part of this difference is presumably due to HyperZ - something > that we can't implement in an open driver. what is hyper-z? a proprietary texture-compression function of the r200? well, as you expected, performance is exactly the same after the checkout as before > >> rtcw (single player): working, but quite slow (performance isn't really >> great with firegl-drivers neither...), crashed after about 10 mins > > > Yes, I haven't had the opportunity to do any long runs of these demos. > It's a bit disappointing that they lockup, though. > I'm also still experiencing crashes with q3a and wolf, after some minutes of playing. Is there anything I can do to help to track down the reason (i have to warn you though: i don't have any programming or debugging experience)? oh yeah, one other thing: in the other mail I reported that xv is broken: it works fine now for me, so I somehow messed it up before. sorry about that > Keith > > > > > |
From: Michel <mi...@da...> - 2002-07-05 21:47:49
|
On Fri, 2002-07-05 at 14:55, Stefan Lange wrote: >=20 > on more comment: xv seems to be broken, it only gives me a black overlay > window with mplayer. are there plans to merge with gatos some time? http://www.keithp.com/~keithp/download/radeon_video.diff makes Xv work with all Radeon chips. http://www.keithp.com/~keithp/download/radeon_xv-2002-03-29-19.diff fixes the color key problems. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
From: Stefan L. <hoi...@gm...> - 2002-07-08 08:23:08
|
Michel D=E4nzer wrote: > On Fri, 2002-07-05 at 14:55, Stefan Lange wrote: >=20 >>on more comment: xv seems to be broken, it only gives me a black overla= y >>window with mplayer. are there plans to merge with gatos some time? >=20 >=20 > http://www.keithp.com/~keithp/download/radeon_video.diff makes Xv work > with all Radeon chips. > http://www.keithp.com/~keithp/download/radeon_xv-2002-03-29-19.diff > fixes the color key problems. >=20 >=20 Thanks for the links. Unfortunately Xv still doesn't work for me. But=20 that might be because of my insufficient knowledge of how to correctly=20 apply a patch. I did the following: -updated cvs -cd'ed to xc/programs/Xserver/hw/xfree86/drivers/ati - and then did a patch -p0 < /path/to/patchfiles/radeon_video.diff (same=20 for the other diff) is that the right way of doing it? regards Stefan |
From: Michel <mi...@da...> - 2002-07-08 10:14:43
|
On Mon, 2002-07-08 at 10:22, Stefan Lange wrote: > Michel D=E4nzer wrote: > > On Fri, 2002-07-05 at 14:55, Stefan Lange wrote: > >=20 > >>on more comment: xv seems to be broken, it only gives me a black overla= y > >>window with mplayer. are there plans to merge with gatos some time? > >=20 > >=20 > > http://www.keithp.com/~keithp/download/radeon_video.diff makes Xv work > > with all Radeon chips. > > http://www.keithp.com/~keithp/download/radeon_xv-2002-03-29-19.diff > > fixes the color key problems. > >=20 > >=20 >=20 > Thanks for the links. Unfortunately Xv still doesn't work for me. But=20 > that might be because of my insufficient knowledge of how to correctly=20 > apply a patch. I did the following: > -updated cvs > -cd'ed to xc/programs/Xserver/hw/xfree86/drivers/ati > - and then did a patch -p0 < /path/to/patchfiles/radeon_video.diff (same=20 > for the other diff) >=20 > is that the right way of doing it? Yes. Keith said he successfully tested it on a 8500, maybe it depends on the other patch. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
From: Stefan L. <hoi...@gm...> - 2002-07-08 17:08:30
|
[...] > > Yes. Keith said he successfully tested it on a 8500, maybe it depends on > the other patch. > > OK, i had another look into my problem: I noticed that only radeon_xv-2002-03-29-19.diff applies cleanly on the r200 branch. the other patch gives me errors. So I first tried to edit the hunks that had failed manually, but the result wouldn't compile (not very surprisingly...) after that i tried to just apply the first patch (the one that applies without problems), recompiled everything, et voila: XV is working! thanks for helping me out again regards Stefan |
From: Oliver F. <ki...@gm...> - 2002-07-06 15:36:44
|
On Friday 05 July 2002 13:04, José Fonseca wrote: > Keith Whitwell confirmed the readiness of the r200-0-1-branch for > testing and for binary snapshots. Just tested this driver on a system with original ATI 8500 card. With the binary snaphots and with the r200 branch compiled myself the system crashes immediately when X is started. With DRI disabled X comes up and runs without problems. I don't really know how to get more information from X. There are no syslog entries and nothing in XFree.0.log. I started X via remote ssh to see X's output, but it stops after printing the first few lines so there is nothing useful there as well. That's all informtation I can give unfortunately. Summary: it crashes. ;) -- Oliver Feiler <kiza@(gmx.net|lionking.org|claws-and-paws.com)> http://www.lionking.org/~kiza/ <-- homepage PGP-key ID 0x561D4FD2 --> /pgpkey.shtml |
From: Oliver F. <ki...@gm...> - 2002-07-06 15:42:25
|
On Saturday 06 July 2002 17:36, Oliver Feiler wrote: > On Friday 05 July 2002 13:04, José Fonseca wrote: > > Keith Whitwell confirmed the readiness of the r200-0-1-branch for > > testing and for binary snapshots. > > Just tested this driver on a system with original ATI 8500 card. > > With the binary snaphots and with the r200 branch compiled myself the > system crashes immediately when X is started. With DRI disabled X comes up > and runs without problems. > > I don't really know how to get more information from X. There are no syslog > entries and nothing in XFree.0.log. I started X via remote ssh to see X's > output, but it stops after printing the first few lines so there is nothing > useful there as well. That's all informtation I can give unfortunately. > > Summary: it crashes. ;) Erm, maybe I should add: the system is a VIA KT333 board, Athlon XP 1800. Kernel is 2.4.19-rc1 with agpgart compiled in. The ATI firegl drivers worked, btw. -- Oliver Feiler <kiza@(gmx.net|lionking.org|claws-and-paws.com)> http://www.lionking.org/~kiza/ <-- homepage PGP-key ID 0x561D4FD2 --> /pgpkey.shtml |
From: Jens O. <je...@tu...> - 2002-07-06 19:49:29
Attachments:
debug.patch
|
Oliver Feiler wrote: > On Saturday 06 July 2002 17:36, Oliver Feiler wrote: >=20 >>On Friday 05 July 2002 13:04, Jos=E9 Fonseca wrote: >> >>>Keith Whitwell confirmed the readiness of the r200-0-1-branch for >>>testing and for binary snapshots. >>> >>Just tested this driver on a system with original ATI 8500 card. >> >>With the binary snaphots and with the r200 branch compiled myself the >>system crashes immediately when X is started. With DRI disabled X comes= up >>and runs without problems. Oliver, If you have the room for a fully debuggable X Server, try adding this=20 patch before you build the X Server. Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. If you can case the crash like that, post the backtrace to the list. Regards, Jens --=20 /\ Jens Owen / \/\ _ je...@tu... / \ \ \ Steamboat Springs, Colorado |
From: Keith W. <ke...@tu...> - 2002-07-06 21:11:41
|
Jens Owen wrote: > Oliver Feiler wrote: >=20 >> On Saturday 06 July 2002 17:36, Oliver Feiler wrote: >> >>> On Friday 05 July 2002 13:04, Jos=E9 Fonseca wrote: >>> >>>> Keith Whitwell confirmed the readiness of the r200-0-1-branch for >>>> testing and for binary snapshots. >>>> >>> Just tested this driver on a system with original ATI 8500 card. >>> >>> With the binary snaphots and with the r200 branch compiled myself the >>> system crashes immediately when X is started. With DRI disabled X=20 >>> comes up >>> and runs without problems. >> >=20 >=20 > Oliver, >=20 > If you have the room for a fully debuggable X Server, try adding this=20 > patch before you build the X Server. >=20 > Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. >=20 > If you can case the crash like that, post the backtrace to the list. >=20 > Regards, > Jens This works if it is a crash, but not if it is a lockup where the system=20 freezes overall -- I don't know which Oliver is experiencing... Keith |
From: Oliver F. <ki...@gm...> - 2002-07-06 21:21:58
|
On Saturday 06 July 2002 23:11, Keith Whitwell wrote: > Jens Owen wrote: > > Oliver Feiler wrote: > >> On Saturday 06 July 2002 17:36, Oliver Feiler wrote: > >>> On Friday 05 July 2002 13:04, José Fonseca wrote: > >>>> Keith Whitwell confirmed the readiness of the r200-0-1-branch for > >>>> testing and for binary snapshots. > >>> > >>> Just tested this driver on a system with original ATI 8500 card. > >>> > >>> With the binary snaphots and with the r200 branch compiled myself the > >>> system crashes immediately when X is started. With DRI disabled X > >>> comes up > >>> and runs without problems. > > > > Oliver, > > > > If you have the room for a fully debuggable X Server, try adding this > > patch before you build the X Server. > > > > Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. > > > > If you can case the crash like that, post the backtrace to the list. > > > > Regards, > > Jens > > This works if it is a crash, but not if it is a lockup where the system > freezes overall -- I don't know which Oliver is experiencing... I will try that later (or tomorrow) when I have access to that computer again. Unfortunately it's not mine. :) All I can say about this crash now is that the system just locks up. The screen goes black and that's it. I cannot ping the system anymore. I will still try what Jens suggested, maybe I can get some useful information. Bye -- Oliver Feiler <kiza@(gmx.net|lionking.org|claws-and-paws.com)> http://www.lionking.org/~kiza/ <-- homepage PGP-key ID 0x561D4FD2 --> /pgpkey.shtml |
From: Jens O. <je...@tu...> - 2002-07-06 21:35:11
|
Oliver Feiler wrote: > On Saturday 06 July 2002 23:11, Keith Whitwell wrote: >=20 >>Jens Owen wrote: >> >>>Oliver Feiler wrote: >>> >>>>On Saturday 06 July 2002 17:36, Oliver Feiler wrote: >>>> >>>>>On Friday 05 July 2002 13:04, Jos=E9 Fonseca wrote: >>>>> >>>>>>Keith Whitwell confirmed the readiness of the r200-0-1-branch for >>>>>>testing and for binary snapshots. >>>>>> >>>>>Just tested this driver on a system with original ATI 8500 card. >>>>> >>>>>With the binary snaphots and with the r200 branch compiled myself th= e >>>>>system crashes immediately when X is started. With DRI disabled X >>>>>comes up >>>>>and runs without problems. >>>>> >>>Oliver, >>> >>>If you have the room for a fully debuggable X Server, try adding this >>>patch before you build the X Server. >>> >>>Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. >>> >>>If you can case the crash like that, post the backtrace to the list. >>> >>>Regards, >>>Jens >>> >>This works if it is a crash, but not if it is a lockup where the system= >>freezes overall -- I don't know which Oliver is experiencing... >> >=20 > I will try that later (or tomorrow) when I have access to that computer= again.=20 > Unfortunately it's not mine. :) >=20 > All I can say about this crash now is that the system just locks up. Th= e=20 > screen goes black and that's it. I cannot ping the system anymore. I wi= ll=20 > still try what Jens suggested, maybe I can get some useful information.= As Keith said, this won't help much if your system is hanging. You can=20 carefully crawl up to the edge of the cliff, but you don't know where=20 the edge is :-) Each time you fall, you need to reboot and possibly=20 fsck depending on your file system. Perhaps it's better for you to wait until the driver is more stable. --=20 /\ Jens Owen / \/\ _ je...@tu... / \ \ \ Steamboat Springs, Colorado |
From: Keith W. <ke...@tu...> - 2002-07-06 21:31:15
|
Oliver Feiler wrote: > On Saturday 06 July 2002 17:36, Oliver Feiler wrote: >=20 >>On Friday 05 July 2002 13:04, Jos=E9 Fonseca wrote: >> >>>Keith Whitwell confirmed the readiness of the r200-0-1-branch for >>>testing and for binary snapshots. >>> >>Just tested this driver on a system with original ATI 8500 card. >> >>With the binary snaphots and with the r200 branch compiled myself the >>system crashes immediately when X is started. With DRI disabled X comes= up >>and runs without problems. >> >>I don't really know how to get more information from X. There are no sy= slog >>entries and nothing in XFree.0.log. I started X via remote ssh to see X= 's >>output, but it stops after printing the first few lines so there is not= hing >>useful there as well. That's all informtation I can give unfortunately. >> >>Summary: it crashes. ;) >> >=20 > Erm, maybe I should add: the system is a VIA KT333 board, Athlon XP 180= 0.=20 > Kernel is 2.4.19-rc1 with agpgart compiled in. >=20 > The ATI firegl drivers worked, btw. >=20 >=20 I think you've got to look at things like agp mode, fast writes, etc. Th= e=20 8500 has the same 2d component as the 7500, so it's suprising to get a cr= ash=20 so early. What version of XFree did you install on top of? Keith |
From: Oliver F. <ki...@gm...> - 2002-07-07 13:33:13
|
On Saturday 06 July 2002 21:49, Jens Owen wrote: > Oliver Feiler wrote: > > On Saturday 06 July 2002 17:36, Oliver Feiler wrote: > >>On Friday 05 July 2002 13:04, José Fonseca wrote: > >>>Keith Whitwell confirmed the readiness of the r200-0-1-branch for > >>>testing and for binary snapshots. > >> > >>Just tested this driver on a system with original ATI 8500 card. > >> > >>With the binary snaphots and with the r200 branch compiled myself the > >>system crashes immediately when X is started. With DRI disabled X comes > >> up and runs without problems. > > Oliver, > > If you have the room for a fully debuggable X Server, try adding this > patch before you build the X Server. > > Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. > > If you can case the crash like that, post the backtrace to the list. This is as far as it gets: (gdb) run Starting program: /home/kiza/work/r200-branch/xc/xc/programs/Xserver/XFree86 XFree86 Version 4.2.0 (DRI trunk) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19-rc1 i686 [ELF] 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/XFree86.0.log", Time: Sun Jul 7 15:09:13 2002 (==) Using config file: "/etc/X11/XF86Config" And here the system locks up. So it looks like the crash is happening very early or the complete output didn't make it over the network. I installed on top of the 4.2.0 release. Anything else I could try? Otherwise I think I'll just wait a bit until the driver is a bit older, since the owner of the computer where I'm testing it isn't exactly happy if I crash the system regularly. ;) If the DRI module is not loaded in XF86Config X comes up without problems. So there shouldn't really be a problem? Bye -- Oliver Feiler <kiza@(gmx.net|lionking.org|claws-and-paws.com)> http://www.lionking.org/~kiza/ <-- homepage PGP-key ID 0x561D4FD2 --> /pgpkey.shtml |
From: Michel <mi...@da...> - 2002-07-07 14:19:22
|
On Sun, 2002-07-07 at 15:33, Oliver Feiler wrote: > On Saturday 06 July 2002 21:49, Jens Owen wrote: > > Oliver Feiler wrote: > > > On Saturday 06 July 2002 17:36, Oliver Feiler wrote: > > >>On Friday 05 July 2002 13:04, Jos=E9 Fonseca wrote: > > >>>Keith Whitwell confirmed the readiness of the r200-0-1-branch for > > >>>testing and for binary snapshots. > > >> > > >>Just tested this driver on a system with original ATI 8500 card. > > >> > > >>With the binary snaphots and with the r200 branch compiled myself the > > >>system crashes immediately when X is started. With DRI disabled X com= es > > >> up and runs without problems. > > > > Oliver, > > > > If you have the room for a fully debuggable X Server, try adding this > > patch before you build the X Server. > > > > Then login remotely and run gdb xc/programs/Xserver/XFree86 as root. > > > > If you can case the crash like that, post the backtrace to the list. >=20 > This is as far as it gets: >=20 > (gdb) run > Starting program: /home/kiza/work/r200-branch/xc/xc/programs/Xserver/XFre= e86=20 >=20 > XFree86 Version 4.2.0 (DRI trunk) / X Window System > (protocol Version 11, revision 0, vendor release 6600) > Release Date: 18 January 2002 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version before > reporting problems. (See http://www.XFree86.Org/) > Build Operating System: Linux 2.4.19-rc1 i686 [ELF]=20 > Markers: (--) probed, (**) from config file, (=3D=3D) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (=3D=3D) Log file: "/var/log/XFree86.0.log", Time: Sun Jul 7 15:09:13 20= 02 > (=3D=3D) Using config file: "/etc/X11/XF86Config" >=20 > And here the system locks up. So it looks like the crash is happening ver= y=20 > early or the complete output didn't make it over the network. The server output is very non-verbose by default since 4.2.0, use the -verbose command line option to increase the level of verbosity. Not that it will likely give much more useful information... --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |