Patch from Hui Yu and Michel Daenzer: http://penguinppc.org/~daenzer/DRI/radeon-agp8x.diff At some point we should just commit this patch or a variation on it. too many users get bitten by having 8x agp set up by the bios, but only 4x in the radeon driver. I seriously doubt it'll break anything. Unfortunately my mobo only does 4x or I'd test 8x support. if it causees problems it can always be reverted, or better yet, fixed. Thoughts?
this patch doesn't seem to cause any regressions on my hardware, but I don't have an 8x motherboard to test on. Committed to HEAD.
AFAIR Hui didn't consider the patch ready for inclusion... What do you mean by 'get bitten', anyway? I thought you could achieve AGP even without this patch via Option "AGPMode" "2"?
(In reply to comment #2) > AFAIR Hui didn't consider the patch ready for inclusion... What do you mean by > 'get bitten', anyway? I thought you could achieve AGP even without this patch > via Option "AGPMode" "2"? well, I can back it out if think it shouldn't be included. I hadn't heard that Hui didn't think it was ready for inclusion. All comments I ever saw seemed to indicate it was ok. By 'get bitten' I mean that I've gotten many reports of users having problems if they have agp mode set to 8x or auto in the bios. I'm not sure how much of it is related to agp vs. the driver itself. forcing 4x in the bios usually fixed the problems. While I realize it may not really provide much performance-wise, it'd be nice to formally support 8x mode. If you or anyone else feels this patch would cause a problem or experiences any problems let me know and I can back it out. Part of the problem is that no one tests the patches and most things don't shake out until they hit the trunk.
You don't seemed to have commited the whole patch at the moment or did you revert it? the radeon_dri.c portion doesn't seem to be there....
(In reply to comment #4) > You don't seemed to have commited the whole patch at the moment or did you > revert it? > > the radeon_dri.c portion doesn't seem to be there.... > > Argh! Sorry... fixed now.
I just try my Radeon 9200SE AGP 8X with cvs and with Mesa of some minutes ago. I compile Mesa and install radeon dri with : cd Mesa make linux-dri-x86 cd Mesa/lib/ cp radeon_dri.so /usr/X11R6/lib/modules/dri/radeon_dri.so Option "AGPMode" "4" works Option "AGPMode" "8" screen go tottaly crazy on start up btw can't enable # Option "EnablePageFlip" "true" # Option "AGPFastWrite" "true" because hangs the computer. that all for today :)
(In reply to comment #6) > I just try my Radeon 9200SE AGP 8X with cvs and with Mesa of some minutes ago. > I compile Mesa and install radeon dri with : > cd Mesa > make linux-dri-x86 > cd Mesa/lib/ > cp radeon_dri.so /usr/X11R6/lib/modules/dri/radeon_dri.so > > Option "AGPMode" "4" works > Option "AGPMode" "8" screen go tottaly crazy on start up > > btw can't enable > # Option "EnablePageFlip" "true" > # Option "AGPFastWrite" "true" > because hangs the computer. > > that all for today :) Do you have a 8x capable motherboard? could you post any agp or drm messages from the kernel log when you start X with 8 set?
Created attachment 1546 [details] /var/log/Xorg.0.log (In reply to comment #7) yes is AGP 4x/8x
I went to bios and have AGP setting on auto or 4x or 8x , I try to force 8x but some results. after some more tests Option "AGPFastWrite" "true" hangs my computer and Option "EnablePageFlip" "true" can be enabled but don't see much different unless some little better performance sometimes, I will keep it on :).
Tested on i865 motherboard with Radeon 9200 8x and kernel reports: agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode played ut2004 no problems.
dmesg | grep -i agp Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected VIA PT800 chipset agpgart: Maximum main memory to use for agp memory: 439M agpgart: AGP aperture is 128M @ 0xe0000000 agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode 4x works , 8x no
Trying describe the problem with 8x, looks like bad refresh rate with monitor. I try lower modes and lower depths with no luck. Modes "1024x768" "800x600" "640x480" Depth 16
AGPFastWrite hard froze my system, as does AGP 8x, here is a summary of what I got working with X.Org 6.8.2 RC3 RPMs for SuSE 9.2 http://lists.suse.com/archive/suse-xfree86/2005-Jan/0106.html My motherboard is ASUS A7N8X, here is what dmesg|grep agp said: agpgart: X passes broken AGP3 flags (1f00420f). Fixed agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode agpgart: Putting AGP V3 device at 0000:03:00.0 into 8x mode
(In reply to comment #13) > AGPFastWrite hard froze my system, as does AGP 8x, here > is a summary of what I got working with > X.Org 6.8.2 RC3 RPMs for SuSE 9.2 > did you apply this patch to the rpms? 6.8.x doesn't have this patch. > > http://lists.suse.com/archive/suse-xfree86/2005-Jan/0106.html > > My motherboard is ASUS A7N8X, here is what dmesg|grep agp said: > > agpgart: X passes broken AGP3 flags (1f00420f). Fixed > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode > agpgart: Putting AGP V3 device at 0000:03:00.0 into 8x mode fastwrites locks up many systems that's why it's disabled by default. as I said before did you patch the rpms? if X and agpgart disagree about the agp mode, that may cause problems.
The patch has been committed, and remaining issues are likely agp driver issues and not xorg, so closing this.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.