From: Kevin Ruland <kruland@su...> - 2005-05-13 01:19:08
I think I've got something wierd going on here. I get these dmesg when
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: X passes broken AGP2 flags (1f000207) in AGP3 mode. Fixed.
agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000204
tmp:ff001e0b fell back to:- cmd:1f000200 tmp:ff001e0b]
agpgart: Bridge couldn't do AGP x4.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
I have a gentoo 2005.0 system running a 2.6.11 kernel. I have compiled
agp and via-agp into the kernel. The chipset is properly detected as a
PM800 on boot. I have built the drm linux kernel modules from dri-cvs.
I have the gentoo xorg-x11 ebuild installed for most of the X stuff.
I am using the unichrome-pro-snapshot via X module.
When I remove LoadModule dri those messages above are not generated.
Also those messages are generated on server startup, long before I run
anything like glxgears, or xine.