Hello,
a few comments on this topic:
You can simply emerge grub - as far as I know, grub is always build as
32bit-application! The kernel will change, while he is booting to the
64bit modus. This is how I have done it:
* sys-boot/grub
Installed versions: Version: 0.97-r3
Date: 15:03:53 01/16/07
USE: -custom-cflags -netboot -static
You may see, I haven't enabled any use-flag. (Note, the processor does
not start in 64bit modus, the application has to put it into this mode.
This is done by the kernel.)
Is there any reason, why you need partion magic - I needed only cfdisk
and that only once, when I created the different partitions. I also have
a Windows XP installed. Everthings works fine. After update I do the
following:
#grub
root (hd1,0) #Because linux doesn't really care, everything is on the
#second drive. Windows has it's own drive, hd0, which help
#to assure, that Windows is always installed on c - the
#windows installation always thought, that my ext2 boot
#partition is c, when Linux and Windows where installed on
#the same drive.
setup (hd0) #bios will still look on hd0 for MBR, so grub-MBR-piece
#goes there.
quit #and new grub will be used.
I'm only curious, you wrote about 64bit grub and 32bit grub - I hope you
didn't install sys-boot/grub and sys-boot/grub-static at the same time.
This would be a bad idea in my eyes. I hope, portage prevents someone
from doing this. If you had installed both, that may be the source of
your problem.
Jean-Marc
--
[email protected] mailing list
