Edit: Unfortunately, the images originally included in this post are gone, because of hosting problems in late 2009. My apologies.
This is the part where I eat my own words. I didn’t think it possible, but it works. The Geode is an i586, and logic says that a system tuned to the 686 — which regularly resisted all efforts to run or even boot on K6-series machines for me — seems quite happy to plunk along on my XO-1. See for yourself.
The method was identical to the Crux version I had been using for a few weeks — basically importing the OLPC kernel, modules, firmware, etc., straight into the Arch installation. It still seems a bit barbaric to me, and as an Arch fan it’s less than satisfactory since it undercuts a lot of what Arch is about. But it works.
I stuck with the same GTK1.2-ish setup I had with Crux (Dillo, XMMS, Xfe, xterm and the like), and performance is about the same.
I still want to get a proper, pure, non-OLPC-reliant system into place, but this is satisfactory for now. I get all the frills and benefits of Arch without having to recompile every little fragment of software that is implied. That gets a little old on a 430Mhz system. 😉
Motho ke motho ka botho 
That looks like windows! 🙂
Which video package are you using? The Ubuntu guide suggests xserver-xorg-video-amd, but that’s not present in Arch yet, is it?
By the way, you might want so substitute xterm with rxvt-unicode. Compiled from source, with unneeded functions disabled and using its server+client model, it will use less resources. But that’s just a tip.
P.S. I’m curious, since am using fbdev right now, and ‘geode’ from freedesktop.org doesn’t work with Xorg ATM.
I believe it was the AMD driver, but I can’t be sure because I tore that system apart a few months ago. That driver is in Arch, though, so I’m fairly certain that’s the one I used.
Pingback: Farewell, OLPC XO-1 « Motho ke motho ka botho