I got 1.4rc1, everything went great up to the point I had to deal with X. Using a Matrox G400 card, resolutions and modes are setup just fine. However, whenever I move the mouse around, open or close a window, change wallpaper, whatever, it goes up to 100% usage. ( X server ). This applies to KDE and Gnome. Fluxbox does it a lot better but it still gives sudden peaks in X server CPU usage. I even got the old working XF86Config file I kept from my previous distro, even got a binary version of XFree86 instead of the one I compiled in Gentoo, to no avail. Perhaps there is some issue with all X apps compiled using the default Gentoo cflags / with gcc3. I 've tried almost everything possible, and because of the fact I never had those problems in previous distros and that I used the old XF86Config file, I think it classifieds as a bug.
Try xfree-4.2.1 and let me know ?
Reducing the depth to 16bpp resulted in a functional/tolerable environment. It still goes way higher than it should /expected( moving the mouse around gets it 20% cpu usage ). I will try 4.2.1 and see how it goes, though.
And ?
Is there a way to profile where the time is being spent? My system works just dandy with a similar config. Have you tried changing to a different video card? that would determine if it's hardware or a driver issue. Also, check if your kernel has DRI and AGPGART built in and the xfree86config file has it enabled (and enabled for users). check if DRI is working with "glxinfo | grep rendering" in an xterm while logged in non-superuser. another thing I can think of is if your programs are using OpenGL for something and your machine is forced to do rendering in software. Also, anything that CONSTANTLY moves or has giant pixmaps will slow X down a lot, is your background a giant JPEG or something?
When I've had troubles with X taking up all the resources it's been due to wrong settings in the /etc/hosts file, what I did to fix it was to set my hostname after the loopback address (127.0.0.1). This might not solve your problem but you can try anyway.
Mark, updates to this bug?
closing bug report. re-open if persists.
