public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
Date: Thu, 05 May 2016 09:53:23 +0100	[thread overview]
Message-ID: <2012303.QlJmnTNPrp@peak> (raw)
In-Reply-To: <5tdlz0G+MAFz6wRigFofx1@vEFKyqnGQidjFgt8glmD4>

On Thursday 05 May 2016 08:58:06 Helmut Jarausch wrote:
> Hi,
> I had this just yesterday. The libraries of the SystemRescueCD are not
> 64 bits.
> 
> So, you have to proceed as follows.
> 
> Boot RescueCD with the alternative 64 bit kernel (and select the option
> to load all files into memory)
> 
> mkdir /oroot
> 
> ... mount the partition where you installed Gentoo on /oroot
> 
> mount --bind /proc /oroot/proc
> mount --rbind /dev /oroot/dev
> 
> chroot /oroot /bin/bash
> env-update
> source /etc/profile
> 
> ... and now you are in business
> 
> e.g.
> 
> cd /usr/src/linux-????
> 
> make menuconfig   or oldconfig
> make -j8
> make install
> make modules modules_install
> 
> Don't forget to install grub while you are in this chroot environment.
> 
> Then, exit from the chroot environment and reboot.

None of which will work unless the OP's booted his CD in UEFI mode to start 
with. That means, if his system is like mine, having the CD inserted before 
starting, prodding <DEL> or whatever until the BIOS screen comes up, then 
picking the optical drive in UEFI mode, then booting that.

Then the option to load all files into RAM is not available.

Also, grub is a total failure on this box: it just isn't detected. So I use 
gummiboot instead. It's also far, far easier to manage if you have more than 
one kernel to choose from, and it saves you having to learn all that 
baroquery. Frankly, I'm glad to see the back of grub-2.

-- 
Rgds
Peter



  reply	other threads:[~2016-05-05  8:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 13:58 [gentoo-user] CPU you selected does not support x86-64 instruction set John Blinka
2016-05-04 15:31 ` Michael Mol
2016-05-04 16:08   ` John Blinka
2016-05-04 16:36     ` Ron Farrer
2016-05-04 22:52       ` John Blinka
2016-05-04 22:51     ` Neil Bothwick
2016-05-04 22:58       ` John Blinka
2016-05-05  6:58 ` Helmut Jarausch
2016-05-05  8:53   ` Peter Humphrey [this message]
2016-05-05  8:57     ` Neil Bothwick
2016-05-05 15:08       ` John Blinka
2016-05-05 19:58         ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15  1:21 thelma
2020-12-15  4:38 ` J. Roeleveld
2020-12-15  5:44   ` thelma
2020-12-15  6:17 ` thelma
2020-12-15  6:33   ` thelma
2020-12-15  6:47     ` bobwxc
2020-12-15  6:50   ` J. Roeleveld
2020-12-15  6:59     ` thelma
2020-12-15  7:08       ` bobwxc
2020-12-15  7:50         ` J. Roeleveld
2020-12-15  9:51           ` Michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2012303.QlJmnTNPrp@peak \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox