public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] CPU you selected does not support x86-64 instruction set
@ 2016-05-04 13:58 John Blinka
  2016-05-04 15:31 ` Michael Mol
  2016-05-05  6:58 ` Helmut Jarausch
  0 siblings, 2 replies; 24+ messages in thread
From: John Blinka @ 2016-05-04 13:58 UTC (permalink / raw
  To: gentoo-user

[-- 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 --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-04 13:58 [gentoo-user] " John Blinka
@ 2016-05-04 15:31 ` Michael Mol
  2016-05-04 16:08   ` John Blinka
  2016-05-05  6:58 ` Helmut Jarausch
  1 sibling, 1 reply; 24+ messages in thread
From: Michael Mol @ 2016-05-04 15:31 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]

On Wednesday, May 04, 2016 09:58:37 AM John Blinka wrote:
> 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!

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.

-- 
:wq

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  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:51     ` Neil Bothwick
  0 siblings, 2 replies; 24+ messages in thread
From: John Blinka @ 2016-05-04 16:08 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1781 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  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
  1 sibling, 1 reply; 24+ messages in thread
From: Ron Farrer @ 2016-05-04 16:36 UTC (permalink / raw
  To: gentoo-user

On Wed, May 4, 2016 at 9:08 AM, John Blinka <john.blinka@gmail.com> 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.

Generally, 'uname -m' should report x86_64 for 64-bit (amd64) and i686
for 32-bit (x86). While it is possible to have a 64-bit kernel and
32-bit userland, the reverse is not possible. So another check can be
'file /sbin/init' which will report as something along the lines of
"/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, stripped"

Regards,
Ron


^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-04 16:08   ` John Blinka
  2016-05-04 16:36     ` Ron Farrer
@ 2016-05-04 22:51     ` Neil Bothwick
  2016-05-04 22:58       ` John Blinka
  1 sibling, 1 reply; 24+ messages in thread
From: Neil Bothwick @ 2016-05-04 22:51 UTC (permalink / raw
  To: gentoo-user

[-- 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 --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-04 16:36     ` Ron Farrer
@ 2016-05-04 22:52       ` John Blinka
  0 siblings, 0 replies; 24+ messages in thread
From: John Blinka @ 2016-05-04 22:52 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

On Wed, May 4, 2016 at 12:36 PM, Ron Farrer <canutethegreat@gmail.com>
wrote:

>
> Generally, 'uname -m' should report x86_64 for 64-bit (amd64) and i686
> for 32-bit (x86).


uname -m did give x86_64, but...


> ... another check can be 'file /sbin/init' which will report as something
> along the lines of
> "/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
> GNU/Linux 2.6.32, stripped"
>

file /sbin/init gave ELF 32-bit LSB...

So I guess my syrescuecd is 32 bits.

Using the amd64 handbook did the trick with the kernel.  Now onto learning
about uefi.  Thanks for your help!

John

[-- Attachment #2: Type: text/html, Size: 1262 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-04 22:51     ` Neil Bothwick
@ 2016-05-04 22:58       ` John Blinka
  0 siblings, 0 replies; 24+ messages in thread
From: John Blinka @ 2016-05-04 22:58 UTC (permalink / raw
  To: gentoo-user

[-- 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 --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-04 13:58 [gentoo-user] " John Blinka
  2016-05-04 15:31 ` Michael Mol
@ 2016-05-05  6:58 ` Helmut Jarausch
  2016-05-05  8:53   ` Peter Humphrey
  1 sibling, 1 reply; 24+ messages in thread
From: Helmut Jarausch @ 2016-05-05  6:58 UTC (permalink / raw
  To: gentoo-user

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.

Good luck



^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-05  6:58 ` Helmut Jarausch
@ 2016-05-05  8:53   ` Peter Humphrey
  2016-05-05  8:57     ` Neil Bothwick
  0 siblings, 1 reply; 24+ messages in thread
From: Peter Humphrey @ 2016-05-05  8:53 UTC (permalink / raw
  To: gentoo-user

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



^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-05  8:53   ` Peter Humphrey
@ 2016-05-05  8:57     ` Neil Bothwick
  2016-05-05 15:08       ` John Blinka
  0 siblings, 1 reply; 24+ messages in thread
From: Neil Bothwick @ 2016-05-05  8:57 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 663 bytes --]

On Thu, 05 May 2016 09:53:23 +0100, Peter Humphrey wrote:

> 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.

I'd go so far to say that the main reason to use UEFI is to be free of
GRUB. gummiboot/bootctl is so much nicer, even if it is now part of
systemd's plans for World domination ;-)


-- 
Neil Bothwick

Women live longer than men because they have so many clothes that they
wouldn't be caught dead in.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-05  8:57     ` Neil Bothwick
@ 2016-05-05 15:08       ` John Blinka
  2016-05-05 19:58         ` Neil Bothwick
  0 siblings, 1 reply; 24+ messages in thread
From: John Blinka @ 2016-05-05 15:08 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 164 bytes --]

Appreciate all the commentary on sysrescuecd/uefi/booting.  You anticipated
my needs - almost at that point in the install.  I will definitely try
gummiboot.

John

[-- Attachment #2: Type: text/html, Size: 267 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2016-05-05 15:08       ` John Blinka
@ 2016-05-05 19:58         ` Neil Bothwick
  0 siblings, 0 replies; 24+ messages in thread
From: Neil Bothwick @ 2016-05-05 19:58 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

On Thu, 5 May 2016 11:08:16 -0400, John Blinka wrote:

> Appreciate all the commentary on sysrescuecd/uefi/booting.  You
> anticipated my needs - almost at that point in the install.  I will
> definitely try gummiboot.

Note that if you use systemd you don't need gummiboot. Just set the
gnuefi USE flag and you'll get bootctl, which is the same code.


-- 
Neil Bothwick

Power corrupts - absolute power is even more fun.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* [gentoo-user] CPU you selected does not support x86-64 instruction set
@ 2020-12-15  1:21 thelma
  2020-12-15  4:38 ` J. Roeleveld
                   ` (2 more replies)
  0 siblings, 3 replies; 24+ messages in thread
From: thelma @ 2020-12-15  1:21 UTC (permalink / raw
  To: Gentoo mailing list


By mistake on new installation I untar wrong: stage-3  x86_64 instead of
i686

during kernel compiling I got:
cc1: error: CPU you selected does not support x86-64 instruction set

Is it possible to untar new stage-3 (i686) over current one, or I need
to delete all the folders?


^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  1:21 [gentoo-user] CPU you selected does not support x86-64 instruction set thelma
@ 2020-12-15  4:38 ` J. Roeleveld
  2020-12-15  5:44   ` thelma
  2020-12-15  6:17 ` thelma
  2020-12-15  6:58 ` [gentoo-user] " Nikos Chantziaras
  2 siblings, 1 reply; 24+ messages in thread
From: J. Roeleveld @ 2020-12-15  4:38 UTC (permalink / raw
  To: gentoo-user

On 15 December 2020 02:21:22 CET, thelma@sys-concept.com wrote:
>
>By mistake on new installation I untar wrong: stage-3  x86_64 instead
>of
>i686
>
>during kernel compiling I got:
>cc1: error: CPU you selected does not support x86-64 instruction set
>
>Is it possible to untar new stage-3 (i686) over current one, or I need
>to delete all the folders?

To avoid any leftover files causing issues, I would start over.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  4:38 ` J. Roeleveld
@ 2020-12-15  5:44   ` thelma
  0 siblings, 0 replies; 24+ messages in thread
From: thelma @ 2020-12-15  5:44 UTC (permalink / raw
  To: gentoo-user

On 12/14/2020 09:38 PM, J. Roeleveld wrote:
> On 15 December 2020 02:21:22 CET, thelma@sys-concept.com wrote:
>>
>> By mistake on new installation I untar wrong: stage-3  x86_64 instead
>> of
>> i686
>>
>> during kernel compiling I got:
>> cc1: error: CPU you selected does not support x86-64 instruction set
>>
>> Is it possible to untar new stage-3 (i686) over current one, or I need
>> to delete all the folders?
> 
> To avoid any leftover files causing issues, I would start over.
> 
> --
> Joost

You are correct, it is easier to start over.




^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  1:21 [gentoo-user] CPU you selected does not support x86-64 instruction set thelma
  2020-12-15  4:38 ` J. Roeleveld
@ 2020-12-15  6:17 ` thelma
  2020-12-15  6:33   ` thelma
  2020-12-15  6:50   ` J. Roeleveld
  2020-12-15  6:58 ` [gentoo-user] " Nikos Chantziaras
  2 siblings, 2 replies; 24+ messages in thread
From: thelma @ 2020-12-15  6:17 UTC (permalink / raw
  To: Gentoo mailing list

On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
> 
> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
> i686
> 
> during kernel compiling I got:
> cc1: error: CPU you selected does not support x86-64 instruction set
> 
> Is it possible to untar new stage-3 (i686) over current one, or I need
> to delete all the folders?

After selecting stage-3 (i686) I still get the same error message when
trying to compile kernel:

CC      scripts/mod/empty.o
cc1: error: CPU you selected does not support x86-64 instruction set
make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
make: *** [Makefile:1137: prepare0] Error 2

The CPU I have:
AMD FX(tm)-8150 Eight-Core Processor

make.conf
COMMON_FLAGS="-march=native -O2 -pipe"
#COMMON_FLAGS="-O2 -march=i686 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
CPU_FLAGS_X86="mmx mmxext sse sse2 sse3"



^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  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
  1 sibling, 1 reply; 24+ messages in thread
From: thelma @ 2020-12-15  6:33 UTC (permalink / raw
  To: Gentoo mailing list

On 12/14/2020 11:17 PM, thelma@sys-concept.com wrote:
> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
>>
>> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
>> i686
>>
>> during kernel compiling I got:
>> cc1: error: CPU you selected does not support x86-64 instruction set
>>
>> Is it possible to untar new stage-3 (i686) over current one, or I need
>> to delete all the folders?
> 
> After selecting stage-3 (i686) I still get the same error message when
> trying to compile kernel:
> 
> CC      scripts/mod/empty.o
> cc1: error: CPU you selected does not support x86-64 instruction set
> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
> make: *** [Makefile:1137: prepare0] Error 2
> 
> The CPU I have:
> AMD FX(tm)-8150 Eight-Core Processor
> 
> make.conf
> COMMON_FLAGS="-march=native -O2 -pipe"
> #COMMON_FLAGS="-O2 -march=i686 -pipe"
> CFLAGS="${COMMON_FLAGS}"
> CXXFLAGS="${COMMON_FLAGS}"
> FCFLAGS="${COMMON_FLAGS}"
> FFLAGS="${COMMON_FLAGS}"
> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3"

SOLVED:
One need to disable "64-bit kernel" in the root of the menuconfig.


^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  6:33   ` thelma
@ 2020-12-15  6:47     ` bobwxc
  0 siblings, 0 replies; 24+ messages in thread
From: bobwxc @ 2020-12-15  6:47 UTC (permalink / raw
  To: gentoo-user


[-- Attachment #1.1.1: Type: text/plain, Size: 1335 bytes --]

在 2020/12/15 下午2:33, thelma@sys-concept.com 写道:
> On 12/14/2020 11:17 PM, thelma@sys-concept.com wrote:
>> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
>>> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
>>> i686
>>>
>>> during kernel compiling I got:
>>> cc1: error: CPU you selected does not support x86-64 instruction set
>>>
>>> Is it possible to untar new stage-3 (i686) over current one, or I need
>>> to delete all the folders?
>> After selecting stage-3 (i686) I still get the same error message when
>> trying to compile kernel:
>>
>> CC      scripts/mod/empty.o
>> cc1: error: CPU you selected does not support x86-64 instruction set
>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
>> make: *** [Makefile:1137: prepare0] Error 2
>>
>> The CPU I have:
>> AMD FX(tm)-8150 Eight-Core Processor
>>
>> make.conf
>> COMMON_FLAGS="-march=native -O2 -pipe"
>> #COMMON_FLAGS="-O2 -march=i686 -pipe"
>> CFLAGS="${COMMON_FLAGS}"
>> CXXFLAGS="${COMMON_FLAGS}"
>> FCFLAGS="${COMMON_FLAGS}"
>> FFLAGS="${COMMON_FLAGS}"
>> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3"
> SOLVED:
> One need to disable "64-bit kernel" in the root of the menuconfig.

AMD FX-8150 should support x86-64 according to the it data, very confused.

-- 
bobwxc


[-- Attachment #1.1.2: Type: text/html, Size: 2244 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  6:17 ` thelma
  2020-12-15  6:33   ` thelma
@ 2020-12-15  6:50   ` J. Roeleveld
  2020-12-15  6:59     ` thelma
  1 sibling, 1 reply; 24+ messages in thread
From: J. Roeleveld @ 2020-12-15  6:50 UTC (permalink / raw
  To: gentoo-user

On Tuesday, December 15, 2020 7:17:57 AM CET thelma@sys-concept.com wrote:
> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
> > By mistake on new installation I untar wrong: stage-3  x86_64 instead of
> > i686
> > 
> > during kernel compiling I got:
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > 
> > Is it possible to untar new stage-3 (i686) over current one, or I need
> > to delete all the folders?
> 
> After selecting stage-3 (i686) I still get the same error message when
> trying to compile kernel:
> 
> CC      scripts/mod/empty.o
> cc1: error: CPU you selected does not support x86-64 instruction set
> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
> make: *** [Makefile:1137: prepare0] Error 2
> 
> The CPU I have:
> AMD FX(tm)-8150 Eight-Core Processor

Isn't this a 64-bit CPU?
If you boot using a 64bit live-image (the gentoo-admin ISO as an example), you 
should be able to actually use 64bit.

--
Joost




^ permalink raw reply	[flat|nested] 24+ messages in thread

* [gentoo-user] Re: CPU you selected does not support x86-64 instruction set
  2020-12-15  1:21 [gentoo-user] CPU you selected does not support x86-64 instruction set thelma
  2020-12-15  4:38 ` J. Roeleveld
  2020-12-15  6:17 ` thelma
@ 2020-12-15  6:58 ` Nikos Chantziaras
  2 siblings, 0 replies; 24+ messages in thread
From: Nikos Chantziaras @ 2020-12-15  6:58 UTC (permalink / raw
  To: gentoo-user

On 15/12/2020 03:21, thelma@sys-concept.com wrote:
> 
> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
> i686
> 
> during kernel compiling I got:
> cc1: error: CPU you selected does not support x86-64 instruction set
> 
> Is it possible to untar new stage-3 (i686) over current one, or I need
> to delete all the folders?

Your problem is somewhere else. Your CPU is 64-bit, as are all desktop 
CPUs made in the last 15 years.



^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  6:50   ` J. Roeleveld
@ 2020-12-15  6:59     ` thelma
  2020-12-15  7:08       ` bobwxc
  0 siblings, 1 reply; 24+ messages in thread
From: thelma @ 2020-12-15  6:59 UTC (permalink / raw
  To: gentoo-user

On 12/14/2020 11:50 PM, J. Roeleveld wrote:
> On Tuesday, December 15, 2020 7:17:57 AM CET thelma@sys-concept.com wrote:
>> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
>>> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
>>> i686
>>>
>>> during kernel compiling I got:
>>> cc1: error: CPU you selected does not support x86-64 instruction set
>>>
>>> Is it possible to untar new stage-3 (i686) over current one, or I need
>>> to delete all the folders?
>>
>> After selecting stage-3 (i686) I still get the same error message when
>> trying to compile kernel:
>>
>> CC      scripts/mod/empty.o
>> cc1: error: CPU you selected does not support x86-64 instruction set
>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
>> make: *** [Makefile:1137: prepare0] Error 2
>>
>> The CPU I have:
>> AMD FX(tm)-8150 Eight-Core Processor
> 
> Isn't this a 64-bit CPU?
> If you boot using a 64bit live-image (the gentoo-admin ISO as an example), you 
> should be able to actually use 64bit.
> 
> --
> Joost

I'm confused as well, setting from make.conf on this CPU with previous
kernel was:
CHOST="x86_64-pc-linux-gnu"



^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  6:59     ` thelma
@ 2020-12-15  7:08       ` bobwxc
  2020-12-15  7:50         ` J. Roeleveld
  0 siblings, 1 reply; 24+ messages in thread
From: bobwxc @ 2020-12-15  7:08 UTC (permalink / raw
  To: gentoo-user


[-- Attachment #1.1: Type: text/plain, Size: 1511 bytes --]

在 2020/12/15 下午2:59, thelma@sys-concept.com 写道:
> On 12/14/2020 11:50 PM, J. Roeleveld wrote:
>> On Tuesday, December 15, 2020 7:17:57 AM CET thelma@sys-concept.com wrote:
>>> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
>>>> By mistake on new installation I untar wrong: stage-3  x86_64 instead of
>>>> i686
>>>>
>>>> during kernel compiling I got:
>>>> cc1: error: CPU you selected does not support x86-64 instruction set
>>>>
>>>> Is it possible to untar new stage-3 (i686) over current one, or I need
>>>> to delete all the folders?
>>> After selecting stage-3 (i686) I still get the same error message when
>>> trying to compile kernel:
>>>
>>> CC      scripts/mod/empty.o
>>> cc1: error: CPU you selected does not support x86-64 instruction set
>>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
>>> make: *** [Makefile:1137: prepare0] Error 2
>>>
>>> The CPU I have:
>>> AMD FX(tm)-8150 Eight-Core Processor
>> Isn't this a 64-bit CPU?
>> If you boot using a 64bit live-image (the gentoo-admin ISO as an example), you
>> should be able to actually use 64bit.
>>
>> --
>> Joost
> I'm confused as well, setting from make.conf on this CPU with previous
> kernel was:
> CHOST="x86_64-pc-linux-gnu"
>
As Joost says, maybe you can try boot from a 64bit install image to test 
that.

If you can, you may re-install your system to use 64bit.

Only a little chance that your cpu has some problem with x64 module.

-- 
bobwxc



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  7:08       ` bobwxc
@ 2020-12-15  7:50         ` J. Roeleveld
  2020-12-15  9:51           ` Michael
  0 siblings, 1 reply; 24+ messages in thread
From: J. Roeleveld @ 2020-12-15  7:50 UTC (permalink / raw
  To: gentoo-user

On Tuesday, December 15, 2020 8:08:46 AM CET bobwxc wrote:
> 在 2020/12/15 下午2:59, thelma@sys-concept.com 写道:
> > On 12/14/2020 11:50 PM, J. Roeleveld wrote:
> >> On Tuesday, December 15, 2020 7:17:57 AM CET thelma@sys-concept.com 
wrote:
> >>> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
> >>>> By mistake on new installation I untar wrong: stage-3  x86_64 instead
> >>>> of
> >>>> i686
> >>>> 
> >>>> during kernel compiling I got:
> >>>> cc1: error: CPU you selected does not support x86-64 instruction set
> >>>> 
> >>>> Is it possible to untar new stage-3 (i686) over current one, or I need
> >>>> to delete all the folders?
> >>> 
> >>> After selecting stage-3 (i686) I still get the same error message when
> >>> trying to compile kernel:
> >>> 
> >>> CC      scripts/mod/empty.o
> >>> cc1: error: CPU you selected does not support x86-64 instruction set
> >>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
> >>> make: *** [Makefile:1137: prepare0] Error 2
> >>> 
> >>> The CPU I have:
> >>> AMD FX(tm)-8150 Eight-Core Processor
> >> 
> >> Isn't this a 64-bit CPU?
> >> If you boot using a 64bit live-image (the gentoo-admin ISO as an
> >> example), you should be able to actually use 64bit.
> >> 
> >> --
> >> Joost
> > 
> > I'm confused as well, setting from make.conf on this CPU with previous
> > kernel was:
> > CHOST="x86_64-pc-linux-gnu"
> 
> As Joost says, maybe you can try boot from a 64bit install image to test
> that.
> 
> If you can, you may re-install your system to use 64bit.
> 
> Only a little chance that your cpu has some problem with x64 module.

I did a fresh install last weekend and using the 64-bit version from:
https://www.gentoo.org/downloads/

actually worked.

I copied it to a USB-stick using dd:
# dd if=...path...to....iso  of=/dev/<whatever your usb-stick is> 

Took a little bit (as USB-stick is old...)

--
Joost






^ permalink raw reply	[flat|nested] 24+ messages in thread

* Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
  2020-12-15  7:50         ` J. Roeleveld
@ 2020-12-15  9:51           ` Michael
  0 siblings, 0 replies; 24+ messages in thread
From: Michael @ 2020-12-15  9:51 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]

On Tuesday, 15 December 2020 07:50:00 GMT J. Roeleveld wrote:
> On Tuesday, December 15, 2020 8:08:46 AM CET bobwxc wrote:
> > 在 2020/12/15 下午2:59, thelma@sys-concept.com 写道:
> > > On 12/14/2020 11:50 PM, J. Roeleveld wrote:
> > >> On Tuesday, December 15, 2020 7:17:57 AM CET thelma@sys-concept.com
> 
> wrote:
> > >>> On 12/14/2020 06:21 PM, thelma@sys-concept.com wrote:
> > >>>> By mistake on new installation I untar wrong: stage-3  x86_64 instead
> > >>>> of
> > >>>> i686
> > >>>> 
> > >>>> during kernel compiling I got:
> > >>>> cc1: error: CPU you selected does not support x86-64 instruction set
> > >>>> 
> > >>>> Is it possible to untar new stage-3 (i686) over current one, or I
> > >>>> need
> > >>>> to delete all the folders?
> > >>> 
> > >>> After selecting stage-3 (i686) I still get the same error message when
> > >>> trying to compile kernel:
> > >>> 
> > >>> CC      scripts/mod/empty.o
> > >>> cc1: error: CPU you selected does not support x86-64 instruction set
> > >>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
> > >>> make: *** [Makefile:1137: prepare0] Error 2
> > >>> 
> > >>> The CPU I have:
> > >>> AMD FX(tm)-8150 Eight-Core Processor
> > >> 
> > >> Isn't this a 64-bit CPU?
> > >> If you boot using a 64bit live-image (the gentoo-admin ISO as an
> > >> example), you should be able to actually use 64bit.
> > >> 
> > >> --
> > >> Joost
> > > 
> > > I'm confused as well, setting from make.conf on this CPU with previous
> > > kernel was:
> > > CHOST="x86_64-pc-linux-gnu"
> > 
> > As Joost says, maybe you can try boot from a 64bit install image to test
> > that.
> > 
> > If you can, you may re-install your system to use 64bit.
> > 
> > Only a little chance that your cpu has some problem with x64 module.
> 
> I did a fresh install last weekend and using the 64-bit version from:
> https://www.gentoo.org/downloads/
> 
> actually worked.
> 
> I copied it to a USB-stick using dd:
> # dd if=...path...to....iso  of=/dev/<whatever your usb-stick is>
> 
> Took a little bit (as USB-stick is old...)
> 
> --
> Joost

The CPU is 64-bit and as has already been suggested using a 64-bit LiveCD/USB 
to boot with and install will work fine.  For requisite CFLAGS in /etc/
portage/make.conf, take a look here:

https://wiki.gentoo.org/wiki/Safe_CFLAGS

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 24+ messages in thread

end of thread, other threads:[~2020-12-15  9:52 UTC | newest]

Thread overview: 24+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-12-15  1:21 [gentoo-user] CPU you selected does not support x86-64 instruction set 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
2020-12-15  6:58 ` [gentoo-user] " Nikos Chantziaras
  -- strict thread matches above, loose matches on Subject: below --
2016-05-04 13:58 [gentoo-user] " 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
2016-05-05  8:57     ` Neil Bothwick
2016-05-05 15:08       ` John Blinka
2016-05-05 19:58         ` Neil Bothwick

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox