I have the same problem.
Look at this picture
Any solution found ?
Hyp: I've been able to replicate your problem (exactly), however the solution isn't what I'd call wonderful.
Since I've been digging into the LiveCD's themselves, and re-forming it to suit a different set of demands, I've been able to learn quite a bit.
The bottom line is that the LiveCD's kernel configuration is what I would call 'messed up'. The entire point of the Gentoo LiveCD is to allow a user to install the OS; so it makes sense to attempt to avoid 'features' that while interesting for use on a desktop, don't necessarily make sense when you're installing the OS for the first time. In this case, the LiveCD's kernel was compiled with options that can (and does) break on certain hardware sets.
So, I actually modified a LiveCD 2005.1 CD, but used a different kernel than comes with the official LiveCD, using more sane options. (This was the only necessary difference).
Obviously, this isn't a great 'general' solution. I'm dissapointed that the Gentoo people were so careless with their kernel config on this LiveCD.
A decent solution that will work is to use the LiveCD 2005.0 (minimal) to boot. Then use the 2005.1 base image and/or stage tarballs, sync up portage and start building. The minimal CD is actually quite version-neutral; you just need it to partition/format the hard disk drives, and unpack the current 'base' gentoo image. Then you chroot into that -- once you've chrooted, it doesn't matter that you booted from a different LiveCD than Gentoo's -- the 2005.0 part isn't visible within the chroot. Which means you won't get a 'polluted' install in any way, shape, or form.
For an example of how neutral the Gentoo LiveCD can be: You can actually install SuSE with a Gentoo LiveCD; it takes a bit of work, and a complete lack of sanity, but it can be done. (Why you'd want to is another matter...)