On Monday 13 March 2006 15:09, Jim <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] Mobo/proc combination': > On 164593240 "Boyd Stephen Smith Jr." <[EMAIL PROTECTED]> wrote: > > Better memory architecture and microcode, larger caches, etc.; you > > might even get a Hz bump; in the near future, you'll get hw > > virtualization. There are lot of reasons to choose a modern processor > > than just the 64-bit mode. That said, there's very little reason to > > have less than 1G of RAM these days, and at that point you are > > well-served to put (at least) your kernel in 64-bit mode. > > Is there a how-to on going 64-bit with Gentoo? Anything special to do > with/for the kernel to go 64-bit?
If you are in a 32-bit userland you have to cross-compile the kernel, which is pretty easy. (And been covered recently.) # Get a cross-compiler: emerge -u crossdev crossdev -s1 -t x86_64 # Clean, configure, and compile your new kernel. cd /usr/src/linux # Or whereever you have your kernel sources make mrproper # To completely clean the existing kernel zcat /proc/config.gz > .config # Start with running config make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- menuconfig # Make sure and include support for IA32 binaries. make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- -j2 # Tune jobs # Install modules emerge -u module-rebuild # For below make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- modules_install module-rebuild -X rebuild # out-of-kernel modules, like nvidia # Install the kernel mount /boot # If needed make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- install # Or manually umount /boot # As above # Using lilo? I don't, but if you are, you'll probably need do to # something else, too. # Reboot shutdown -r now -t 5 (Bo Anderson (IIRC) on this list has validated most of this proceedure, so he should be able to help you with any gotchas along the way.) If you are using a 64-bit kernel but still running a 32-bit userland and want to move to a 64-bit userland you'll need to: 1) Fix your make.profile link 2) Update your CHOST, CFLAGS, CXXFLAGS, and ACCEPT_KEYWORDS in make.conf 3) Rebuild system (which will include your toolchain) emerge -e system 4) Switch to the new gcc using gcc-config 5) Rebuild world (which will also do system again. :/) emerge -e world (I haven't validated this, but it *shouldn't* break your system. If you are using LVM and have a little extra space, it might just be better to do a chroot install, then boot into it and remove your old install [don't remove /home!]) -- "If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability." -- Gentoo Developer Ciaran McCreesh -- gentoo-user@gentoo.org mailing list
