From: John Blinka <john.blinka@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
Date: Wed, 4 May 2016 18:58:55 -0400 [thread overview]
Message-ID: <CAC_tCmoqZF6uHg_VhN=-aA-kfwGF7bY=C3qGroThRwMQmODryQ@mail.gmail.com> (raw)
In-Reply-To: <20160504235108.7fb4dbe9@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
On Wed, May 4, 2016 at 6:51 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
>
> SystemRescueCd has boot menu options for picking the kernel, just pick
> either rescue64 or altker64.
>
I did try that at least once, but I think I compensated for doing the right
thing at that point with making mistakes elsewhere. I'll give it another
try now that I have a 64 bit kernel compiled on the target machine. I'll
need that to get the uefi environment I need to accomplish uefi booting.
Appreciate your reminding me!
John
[-- Attachment #2: Type: text/html, Size: 961 bytes --]
next prev parent reply other threads:[~2016-05-04 22:59 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 [this message]
2016-05-05 6:58 ` Helmut Jarausch
2016-05-05 8:53 ` Peter Humphrey
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='CAC_tCmoqZF6uHg_VhN=-aA-kfwGF7bY=C3qGroThRwMQmODryQ@mail.gmail.com' \
--to=john.blinka@gmail.com \
--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