I worked through an installation while booted from install-amd64-minimal-20130110.iso and reading, in links, by about the eighth hour, this page: http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=10 While I did emerge grub I tried to follow the docs, which appear to be for legacy grub, with which I am familiar. However, afaict, grub2 is what was emerged and I did not have the correct instruction set to complete the bootloader installation. grub2 is too new to me. It seems to me there is a bug in that the referenced handbook does not instruct about grub2. Thanks.
You must have installed the testing version of grub, since grub:2 is not stable yet.
(In reply to comment #1) > You must have installed the testing version of grub, since grub:2 is not > stable yet. Since 10 years ago, maybe, I've not installed Gentoo and the protocols are not familiar. I followed the handbook and made some choices that, probably, led to testing grub being installed, but which is not evident to me. Following the handbook in links on one vt and making configurations in another, I made certain of the suggested installations and edits, including the following: # mirrorselect -i -o >> /mnt/gentoo/etc/portage/make.conf # mkdir /usr/portage # emerge-webrsync # emerge --sync # emerge portage # eselect news list # eselect news read # emerge genkernel # genkernel --menuconfig all <-- as /boot is reiserfs but already included, so no edits made # emerge grub localhost / # cat etc/fstab [..] # <fs> <mountpoint> <type> <opts> <dump/pass> # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda1 /boot reiserfs noatime,notail 0 2 /dev/sda6 / reiserfs noatime 0 1 /dev/sda5 none swap sw 0 0 /dev/sda7 /home reiserfs noatime 0 2 /dev/cdrom /mnt/cdrom auto noauto,ro,user 0 0 /dev/fd0 /mnt/floppy auto noauto 0 0 localhost / # cat etc/portage/make.conf # These settings were set by the catalyst build script that automatically # built this stage. # Please consult /usr/share/portage/config/make.conf.example for a more # detailed example. CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer" CXXFLAGS="${CFLAGS}" # WARNING: Changing your CHOST is not something that should be done lightly. # Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing. CHOST="x86_64-pc-linux-gnu" # These are the USE flags that were used in addition to what is provided by the # profile used for building. USE="bindist mmx sse sse2 sse3 ssse3" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" MAKEOPTS="-j3" AUTOCLEAN="yes" PORTAGE_ELOG_CLASSES="log warn error" ACCEPT_KEYWORDS="~amd64" GENTOO_MIRRORS="ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/" localhost / # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz [..] Well, that is about what I can think I did that is relevant. Thanks.
(In reply to comment #2) > (In reply to comment #1) > > You must have installed the testing version of grub, since grub:2 is not > > stable yet. > > I followed the handbook and made some choices that, probably, > led to testing grub being installed, but which is not evident to me. > ACCEPT_KEYWORDS="~amd64" This is the reason. If you don't want grub:2, then either mask it and downgrade to grub:0, or start over with stable keywords.
I see, now, the implications of "~amd64" Thanks.
