From: Neil Bothwick <neil@digimed.co.uk>
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 23:51:08 +0100 [thread overview]
Message-ID: <20160504235108.7fb4dbe9@digimed.co.uk> (raw)
In-Reply-To: <CAC_tCmpepu5HX95hq5n9VOErVpRknDtS6r==A9MKVEaMYYFrXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Wed, 4 May 2016 12:08:22 -0400, John Blinka wrote:
> I had read similar thoughts about booting into a 64 bit environment
> before posting and had gone to some effort to figure out whether the
> sysrescuecd kernel was, in fact, 64 bit. Its /proc/config.gz seemed to
> indicate 64 bit, as did uname -a. But I really don't know if there is
> a definitive way of determining whether a running kernel is 64 or 32
> bit.
SystemRescueCd has boot menu options for picking the kernel, just pick
either rescue64 or altker64.
--
Neil Bothwick
OK Scotty, NOW! Detonate and energize! I mean.......
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-05-04 22:51 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 [this message]
2016-05-04 22:58 ` John Blinka
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=20160504235108.7fb4dbe9@digimed.co.uk \
--to=neil@digimed.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