maxim wexler wrote: > well, it built the .94 version, the one I already > have. All the while interspersing yellow-flagged > warnings about upgrading to a version that uses > tool-chain functions. Is that the one I need? How do I > tell it to build the .96? I've run merge --sync a > couple of times for many hours. According to $ls -l > /usr/portage/sys-boot/files was updated but only w/ > grub-0.95-20040823. So why didn't it build .95?
I assume you meant the directory "ls -l /usr/portage/sys-boot/grub"? Well, the 0.95-20040823 ebuild is masked ~x86 (testing). But you should also have 0.96, 0.96-r1, and 0.96-r2, and 0.96-r1 is marked stable. Do you get a different result if you do: ACCEPT_KEYWORDS=~x86 emerge --buildpkgonly --pretend grub Is /etc/make.profile correct? It should be symbolic link to ../usr/portage/profiles/default-linux/x86/2005.0 > BTW, the suggestion to mv -v ../e2fs_stage1_5 got me > to a console with the lone word GRUB in one corner > then nothing. That is very, very good news!! That means the stage2 loaded, but it didn't find your config file. Booting should work. Try the following at that grub prompt (the one you get from booting): Try 1 (should bring up the boot menu): grub> configfile (hd0,3)/grub/grub.conf Try 2 (locate the config file, use that if found. Replace X,X with the numbers reported by find): grub> find /grub/grub.conf grub> (hdX,X)/grub/grub.conf Try 3 (booting without a menu, use the actual name of your kernel file instead of vmlinuz) grub> kernel (hd0,3)/vmlinuz grub> boot Let me know how it goes! -Richard -- [email protected] mailing list
