konjo42 wrote:I have installed the system again via the text installation program. everything seemed fine until i restarted, the same thing occured.

( sarcastic smile )
I hope someone is reading this, i feel like writing a message in a bottle.
If you are using the GTK or CLI automated installer, I would recommend that you don't. They are horribly buggy.
A few things:
The symlink in boot (ie /boot/boot/) is normal. It is there so that putting "kernel /boot/<kernel>" into grub.conf can work whether or not you are using a /boot partition.
Your grub.conf looks okay. Normally, you would link it to /boot/grub/menu.lst, because that's where grub looks for its configuration. Otherwise, it won't find it. However, this should have already been done for you by the installer (I think).
What I would recommend you do in order to get your current installation working is: chroot into your Gentoo installation from a liveCD. Then, emerge grub (if it isn't already) and install it yourself. To chroot (these commands taken from the handbook):
Code: Select all
mount /dev/sdb3 /mnt/gentoo
mount -t proc none /mnt/gentoo/proc
mount -o bind /dev /mnt/gentoo/dev
chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile
So, now you are chrooted in, look at
this chapter in the handbook for details on installing grub. You should probably skip the section about framebuffers (unless your kernel is configured to use one). Additionally, when it shows the two grub.conf files, you should use the genkernel one (modify it to suit your needs, obviously).