From: John Blinka <john.blinka@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] CPU you selected does not support x86-64 instruction set
Date: Wed, 4 May 2016 09:58:37 -0400 [thread overview]
Message-ID: <CAC_tCmp5yV_9B+A20O+sk6QNs=Ey=31GKehwn93HDv1-wgJPbw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
Hello, Gentooers:
I have a new Dell 17 5759 with core i5-6200U skylake cpu on which I'm
trying to dual boot windows 10 and gentoo. All the rest of my gentoo
hardware is much older, so this new laptop introduces 2 technologies new to
me: uefi and 64 bit kernels.
I installed gentoo using the x86 handbook and a recent sysrescuecd usb
drive. The install was unremarkable except for trying to build a 64 bit
kernel. No matter what I do, the kernel build fails very early with the
message:
kernel/bounds.c:1:0 error: CPU you selected does not support x86-64
instruction set.
Looking at bounds.c does not enlighten me.
I've tried specifying a 64 bit kernel in various ways:
setting CONFIG_64BIT=y and CONFIG_X86_64=y via make menuconfig,
make defconfig, which claims it uses an x86_64_defconfig, and sets the 2
configuration variables above to "y",
and genkernel, which says it's getting arch-specific config.sh from
/usr/share/genkernel/arch/x86_64/config.sh, which also sets the 2 variables
above to "y".
So, a 64 bit sysrescuecd kernel does run on this box, and its /proc/cpuinfo
tells me that it does indeed have a core i5-6200U cpu which, per Google,
does support the x86-64 instruction set. I believe I've told the kernel
make system that I want a 64 bit kernel and that the cpu I want to run it
on supports the x86-64 instruction set. Not trusting my kernel config
knowledge, I've tried letting clean kernel installations produce a 64 bit
kernel configuration for me via make defconfig and genkernel, both of which
appear to be attempting 64 bit configurations. All of these attempts fail
the same way. I've tried all of this on gentoo-sources-4.4.6 and
-4.1.15-r1.
Any help would be greatly appreciated. Thanks!
John Blinka
[-- Attachment #2: Type: text/html, Size: 2063 bytes --]
next reply other threads:[~2016-05-04 13:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:58 John Blinka [this message]
2016-05-04 15:31 ` [gentoo-user] CPU you selected does not support x86-64 instruction set 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
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_tCmp5yV_9B+A20O+sk6QNs=Ey=31GKehwn93HDv1-wgJPbw@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