From: Alexander Stohr <AlexanderS@ati.com> - 2003-10-25 15:19:37
i think that was meant to go to the list.
Sent: Friday, October 24, 2003 02:28
To: Alexander Stohr
Subject: Re: [Dri-users] startx fails on n mod 2==1 on Radeon 9200
> > I had some
> > problems with the Athlon prefetch bug on the via kt600 which
> > stopped me building xfree on the machine.
> Via KT600 does not impact gcc, not that i know about.
No, but it seems as if the KT600 triggers the Athlon prefetch bug
(which has been fixed by 2.6.0-test8). I even tried an old duron and it
segfaulted in this mainboard. Exchanged everything ! Memory, Processor,
Power-supply, Mainboard, Harddisk even the CPU-Cooler. Then 2.6.0-test8
came to the rescue and no more segfaulting! Just for the record if
someone is as lucky as i am with buying hardware.
> Strange thing, maybe CVS is broken at present.
> There was a different person which complained
> about XFree86 in XF86 CVS having restart problems.
No, it is persistent over different versions of the dri drivers.
I first tried older deb dri packages, everything worked fine exept this
> Only use with DRM from DRI CVS - else you risk any sort of
> CVS provides the developer version in the first row, so take care.
Ok, so is suspect i have to compile drm as a module and replace the
older drm. Does the cvs version support the 2.6.0-test kernels?
2.4.23-pre7 segfaults also :(
> > The important part of the /etc/X11/XF6Config-4
> > Section "Device"
> > Identifier "Radeon 9200 64 MB"
> > Driver "radeon"
> > Option "AGPMode" "4"
> > Option "AGPSize" "64"
> > Option "EnablePageFlip" "1"
> > Option "CloneDisplay" "0"
> > Option "DDCMode" "1"
> > ChipID 0x04966 # <-
> > yes my chip still not detected :(
I just thought this could be a problem to should try an diffent ChipID.
But i can test it again on monday. Probably with 0x5963?
> R9200SE "Yd" - hmm, i cant check DRI sources,
> but should work as any other from the R200 family.
> The drivers you used dont expose it in the supported listing.
yes, i think that is why i cant remove ChipID from the config.
Thanks for the quick answer