From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-171151-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 29F68138222
for <garchives@archives.gentoo.org>; Wed, 4 May 2016 16:09:02 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 92EFF21C179;
Wed, 4 May 2016 16:08:45 +0000 (UTC)
Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id B97F021C100
for <gentoo-user@lists.gentoo.org>; Wed, 4 May 2016 16:08:43 +0000 (UTC)
Received: by mail-wm0-f48.google.com with SMTP id g17so102856183wme.1
for <gentoo-user@lists.gentoo.org>; Wed, 04 May 2016 09:08:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=xt0rxQWnCBxYiPCxkmmxsxDJaf124nMFJryxNtBObIs=;
b=avbb63IEKVVfRWAGD8Rkj0puZOSkPPJdKbjRBKtla8gTT9BO2zV8ulOcuWq8tR5Kns
KIcZZuh/lQW4q4EMkgjY/Tm5MvlTJ1IGxEvluaWIK1p1l5XEc8uVzHkbsB7INRudJ+vj
HqJOPEaudTw4QqPgAYw+uMpik4bR1NNhDMUrvN+L23TIKigfN2o4hHVHHaKTBwc0fYOz
U+nJa71DXd9702X6YUzbRQjh0lN9cY6hTV0HYQUeeUpANSzM7RBlUdi0HmAtxucU2EBJ
a9hYTsnWwaplmPSIlQ0vxUWlWReDwqnxfx+ufkUlcGDpksQoFyWC6tn9UGwiCmjmQTK1
VZeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=xt0rxQWnCBxYiPCxkmmxsxDJaf124nMFJryxNtBObIs=;
b=beOk7+mrA/EP1xe563rHULdvlbkLPBeLFmOKDPIasa880EOrBimGZYdTzdx9nBluQi
eNLxf4oQIv65Fn+wKw4qc3vEaHy/jST8ppYexEtWz3nKvqSyXVItsOoxmCk/R6EOkTBd
5wRL8V9476bV42djiXnrLHo0+q7Cq6Bmzj2gagz6mX6Oao2fiAUkYLHFCDcKc9mTA1iP
3jTLOlqbsOMqNhXx3VmaOPVp0zsGkpu3tXLd2aMFVAgqqXGkGL+oNu5XBTGNxEnXV4nB
1J9Ct2+/iJWK9xhlfnEABEoPZM5IaRr2CPaG1QTubVrxH7ztB1dOm3Lo4l67WdgoozFe
aThA==
X-Gm-Message-State: AOPr4FU+HehGqgkpLIT+cWmYjXtGQ4n4+PW/s/pmi37gCcFl1/F83BUzVkCrKacEPP7EubHf4hbU/RuJ0tlGXw==
X-Received: by 10.194.189.231 with SMTP id gl7mr10070018wjc.129.1462378122394;
Wed, 04 May 2016 09:08:42 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.28.232.204 with HTTP; Wed, 4 May 2016 09:08:22 -0700 (PDT)
In-Reply-To: <3508588.A2Wzk4mQlR@serenity>
References: <CAC_tCmp5yV_9B+A20O+sk6QNs=Ey=31GKehwn93HDv1-wgJPbw@mail.gmail.com>
<3508588.A2Wzk4mQlR@serenity>
From: John Blinka <john.blinka@gmail.com>
Date: Wed, 4 May 2016 12:08:22 -0400
Message-ID: <CAC_tCmpepu5HX95hq5n9VOErVpRknDtS6r==A9MKVEaMYYFrXQ@mail.gmail.com>
Subject: Re: [gentoo-user] CPU you selected does not support x86-64
instruction set
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=047d7bb046c0834287053206703e
X-Archives-Salt: d2b8e6d4-15ce-49cf-84bf-aa0bb6499e11
X-Archives-Hash: 442569c206ca2d597d27715658802e45
--047d7bb046c0834287053206703e
Content-Type: text/plain; charset=UTF-8
On Wed, May 4, 2016 at 11:31 AM, Michael Mol <mikemol@gmail.com> wrote:
>
> You should use the AMD64 handbook, not the x86 handbook, if you're trying
> to
> install on x86_64 hardware.
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64
>
> More importantly, you should be booted into a 64-bit environment. That
> means
> using a 64-bit live image for your initial boot, and using an amd64 stage3.
>
> EFI has similar requirements; you'll need to be booted via EFI in the first
> place in order to set up the bootloader properly; your firmware won't make
> the
> necessary hardware calls available to register your bootloader if you're
> not
> booted in EFI mode.
>
> HTH
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.
I was booted via EFI, so that part of my installation process was correct.
I never thought to look in the AMD64 handbook. Thanks for the suggestion -
will give it a try.
John
--047d7bb046c0834287053206703e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 4, 2016 at 11:31 AM, Michael Mol <span dir=3D"ltr"><<a h=
ref=3D"mailto:mikemol@gmail.com" target=3D"_blank">mikemol@gmail.com</a>>=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><di=
v class=3D"h5">
<br>
</div></div>You should use the AMD64 handbook, not the x86 handbook, if you=
're trying to<br>
install on x86_64 hardware.<br>
<br>
<a href=3D"https://wiki.gentoo.org/wiki/Handbook:AMD64" rel=3D"noreferrer" =
target=3D"_blank">https://wiki.gentoo.org/wiki/Handbook:AMD64</a><br>
<br>
More importantly, you should be booted into a 64-bit environment. That mean=
s<br>
using a 64-bit live image for your initial boot, and using an amd64 stage3.=
<br>
<br>
EFI has similar requirements; you'll need to be booted via EFI in the f=
irst<br>
place in order to set up the bootloader properly; your firmware won't m=
ake the<br>
necessary hardware calls available to register your bootloader if you'r=
e not<br>
booted in EFI mode.<br>
<br>
HTH</blockquote><div><br></div><div>I had read similar thoughts about booti=
ng 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.=C2=A0 Its /=
proc/config.gz seemed to indicate 64 bit, as did uname -a.=C2=A0 But I real=
ly don't know if there is a definitive way of determining whether a run=
ning kernel is 64 or 32 bit.<br><br></div><div>I was booted via EFI, so tha=
t part of my installation process was correct.<br><br></div><div>I never th=
ought to look in the AMD64 handbook.=C2=A0 Thanks for the suggestion - will=
give it a try.<br><br></div><div>John <br></div></div><br></div></div>
--047d7bb046c0834287053206703e--