Guys,
last night I installed the latest (3.2) from Schneider. The kernel module compiled and loads just fine. X starts just fine. When I open a terminal to run glxinfo or fgl_gears I get an error message ... something like

Error: DDX error, recieved 502 was expecting 524
libGL: InitDriver failed

has anyone seen this before?

I have the kt400 chipset but here is the output for cat /proc/pci

[root@localhost root]# cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge (rev 0).
Master Capable. Latency=8.
Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (rev 0).
Master Capable. No bursts. Min Gnt=12.
Bus 0, device 11, function 0:
Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 1).
IRQ 10.
Master Capable. Latency=32.
Prefetchable 32 bit memory at 0xeb002000 [0xeb002fff].
Bus 0, device 16, function 0:
USB Controller: VIA Technologies, Inc. USB (rev 128).
IRQ 11.
Master Capable. Latency=32.
I/O at 0xa000 [0xa01f].
Bus 0, device 16, function 1:
USB Controller: VIA Technologies, Inc. USB (#2) (rev 128).
IRQ 5.
Master Capable. Latency=32.
I/O at 0xa400 [0xa41f].
Bus 0, device 16, function 2:
USB Controller: VIA Technologies, Inc. USB (#3) (rev 128).
IRQ 12.
Master Capable. Latency=32.
I/O at 0xa800 [0xa81f].
Bus 0, device 16, function 3:
USB Controller: VIA Technologies, Inc. USB 2.0 (rev 130).
IRQ 10.
Master Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xeb000000 [0xeb0000ff].
Bus 0, device 17, function 0:
ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge (rev 0).
Bus 0, device 17, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 6). Master Capable. Latency=32.
I/O at 0xac00 [0xac0f].
Bus 0, device 17, function 5:
Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 80).
IRQ 12.
I/O at 0xb000 [0xb0ff].
Bus 0, device 18, function 0:
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 116).
IRQ 11.
Master Capable. Latency=32. Min Gnt=3.Max Lat=8.
I/O at 0xb400 [0xb4ff].
Non-prefetchable 32 bit memory at 0xeb001000 [0xeb0010ff].
Bus 1, device 0, function 0:
VGA compatible controller: PCI device 1002:4e48 (ATI Technologies Inc) (rev
0).
IRQ 11.
Master Capable. Latency=255. Min Gnt=8.
Prefetchable 32 bit memory at 0xd8000000 [0xdfffffff].
I/O at 0x9000 [0x90ff].
Non-prefetchable 32 bit memory at 0xe9000000 [0xe900ffff].
Bus 1, device 0, function 1:
Display controller: PCI device 1002:4e68 (ATI Technologies Inc) (rev 0).
Master Capable. Latency=32. Min Gnt=8.
Prefetchable 32 bit memory at 0xe0000000 [0xe7ffffff].
Non-prefetchable 32 bit memory at 0xe9010000 [0xe901ffff].

Where should I try to run fglrxgears at? When I try it I get command not found. Thanks for help so far. I have to be close.

KoS, fglrxgears should be located in /usr/X11R6/bin. (although I think it may be called fgl_gears). to find out what all is in there just do an 'ls /usr/X11R6/bin/fgl*'. Another thing to try would be 'glxinfo | grep -i direct'. This will tell you if DRI is turned on or not.

just a quick question ... after the install did you execute /usr/X11R6/bin/fglrxconfig to create a new X config file?

jpbarto, I did find fgl_glxgears, thanks. I get between 150 - 170 fps. When I run the glxinfo it says "Direct Rendering: Yes". I also created a new X config file after I ran fglrxconfig. Any other ideas where to look or what to do?

so direct rendering says yes? you should be good to go then. however the numbers from fgl_glxgears don't look good. what about just plain ol' glxgears? (also in /usr/X11R6/bin). And you're getting these slow runtimes use the X config that was produced by running fglrxconfig?

we might have to look at the log file /var/log/XFree86.0.log

With glxgears I get about 4000 fps. I ran the fglrxconfig and told it to save. Am I supposed to do something else to use the new file? If I am supposed to I haven't. Guess that means I'm a total noob. What do you want me to look for in the log file? Thanks again for the help.

KoS ... you're golden. glxgears is output at 4000? you're running full throttle. Congratulations. Your AGP card is up and running.

Sweet thanks for the help then. What is the fgl_glxgears test for? Also when I open the display window it has a box for hardware 3D but it is greyed out and I can't check it. Does that matter? Also does this mean I can finaly run WineX?

Yes you can run WineX ... as for the fgl_glxgears (not really too sure) ... however glxinfo and glxgears are reporting the rendering is on and your FPS are just fine so go off and have a field day (Quake III, Half Life, ... ahh the possibilities).

By editing the agpgart_be.c file in the fglrx/build_mod directory to have agp_kt400 instead of agp_generic for the KT400 (around line 5846) this resolves the issue. Change the file, manually compile the module and load it. Works like a charm on my KT400 running 8x

I've looked for agp_generic around line 5846 and have none. The lowest line I have agp_generic on is 5454. What else is it supposed to be around or with?

read up in the thread back a couple of pages, everything you need to know is in there. You want to go into you're agpgart_be.c and look for your chipset ID and change the line from via_genericsetup to via_kt400setup but double check that with the thread.

Sorry KoS, wrong string. Look for this one: via_generic_setup and change it to via_kt400_setup

I found it at line 5847 but have seen it referred to as 5846. It should be under the ID of your chipset, not at home right now or I'd give you the header of that value too. Just look at line 5847 though for via_generic_setup and change it to say kt400. Not quite sure why ATI decided to have the KT400 chipset run generic instead of the built in kt400. Guess we'll never know. Seems like they could just rebuild the RPM with the right build environment parameters for the chipset and ship it correctly to avoid all these people with problems. Not sure why they haven't yet.

ATI passes most setups to via_generic_setup so that the chipset can be properly detected. Many KT400 chipsets can also run in 4x AGP mode and as such would require a different setup routine. So via_generic_setup detects the chipset and then sends control over to the proper setup routine (via_kt400_Setup) ... only trouble is ATI messed it up somehow and can't properly detect 8x chipsets thus ... we're stuck here editing our drivers.

What should i changed it to if my chipset was

Chipset North Bridge: NVIDIA® nForce2 SPP(Ultra400)
South Bridge: NVIDIA® nForce2 MCP-T

and the product link was at
http://usa.asus.com/prog/spec.asp?m=...eluxe&langs=09