env -i HOME=/root TERM=$TERM chroot . bash -l zsh: illegal hardware instruction...

[linuxbigot]

Well ... my enthusiasm came up here!

root@sysresccd /mnt/funtoo % env -i HOME=/root TERM=$TERM chroot . bash -l
zsh: illegal hardware instruction  env -i HOME=/root TERM=$TERM chroot . bash -l

http://www.funtoo.org/Funtoo_Linux_Installation#Chroot_into_Funtoo

 

:angry:

 

 

[pytony]

You might try to chroot into a 64bit system while you are in a 32bit system.

 

Or you try to chroot into an environment that does not have the correct instruction set. Are you sure you selected the correct arch/subarch stage3? If in doubt (and if you are on an intel or AMD 64bit machine), choose generic_64 arch.

[linuxbigot]

root@sysresccd /root % cd /mnt/funtoo
root@sysresccd /mnt/funtoo % wget http://build.funtoo.org/funtoo-current/x86-64bit/intel64-sandybridge/2015-05-29/stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz
--2015-05-29 08:45:58--  http://build.funtoo.org/funtoo-current/x86-64bit/intel64-sandybridge/2015-05-29/stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz
Resolving build.funtoo.org... 
Connecting to build.funtoo.org|0... connected.
HTTP request sent, awaiting response... 200 OK
Length: 297947212 (284M) [application/octet-stream]
Saving to: 'stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz'

stage3-intel64-sand 100%[=====================>] 284.14M   237KB/s   in 23m 51ss

2015-05-29 09:09:50 (203 KB/s) - 'stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz' saved [297947212/297947212]

root@sysresccd /mnt/funtoo % tar xpf stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz

 root@sysresccd /mnt/funtoo % cd /mnt/funtoo

root@sysresccd /mnt/funtoo % cd /mnt/funtoo

root@sysresccd /mnt/funtoo % mount -t proc none proc

root@sysresccd /mnt/funtoo % mount --rbind /sys sys

root@sysresccd /mnt/funtoo % mount --rbind /dev dev

root@sysresccd /mnt/funtoo % cp /etc/resolv.conf etc

root@sysresccd /mnt/funtoo % env -i HOME=/root TERM=$TERM chroot . bash -l

zsh: illegal hardware instruction  env -i HOME=/root TERM=$TERM chroot . bash -l

l

 

 

[linuxbigot]

You might try to chroot into a 64bit system while you are in a 32bit system.

 

Or you try to chroot into an environment that does not have the correct instruction set. Are you sure you selected the correct arch/subarch stage3? If in doubt (and if you are on an intel or AMD 64bit machine), choose generic_64 arch.

 

 

http://forums.funtoo.org/topic/521-btrfs-install/?p=2734

[pytony]

1. does `arch` return "x86_64"

2. Are you 100% sure you have sandybridge-compatible CPU?

 

PS: I don't know about BtrFS, the only thing I can tell you to check is above. You can also get around in [iRC](irc://irc.freenode.net/funtoo) to get some help. :)

[linuxbigot]

 lscpu

Architecture:          x86_64

CPU op-mode(s):        32-bit, 64-bit

Byte Order:            Little Endian

CPU(s):                2

On-line CPU(s) list:   0,1

Thread(s) per core:    1

Core(s) per socket:    2

Socket(s):             1

NUMA node(s):          1

Vendor ID:             GenuineIntel

CPU family:            6

Model:                 42

Model name:            Intel(R) Celeron(R) CPU B820 @ 1.70GHz

Stepping:              7

CPU MHz:               1187.808

CPU max MHz:           1700.0000

CPU min MHz:           800.0000

BogoMIPS:              3392.11

Virtualization:        VT-x

L1d cache:             32K

L1i cache:             32K

L2 cache:              256K

L3 cache:              2048K

NUMA node0 CPU(s):     0,1

[pytony]

Then if your sysresccd version is not a 32bit one, I don't know sorry.

[linuxbigot]

Maybe Funtoo is not too FUN to install !!!

tar xpf stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz
tar: ./usr/local/lib: Cannot create symlink to ?lib64?: File exists
tar: ./usr/lib: Cannot create symlink to ?lib64?: File exists
tar: ./lib: Cannot create symlink to ?lib64?: File exists
tar: Exiting with failure status due to previous errors

this time 'TRYING' to install with xfs...

 

:angry:  :angry:  :angry: 

[pytony]

Depends on what you call "fun". Many people have fun facing issues, trying, understanding why it fails and manage to go further. =)

[fabiomen10]

Same here in a second installation!! After successfully installed generic_64 at first try.

[palica]

couple of things here:

• you are booting the 32bit version of sysresccd and downloading and installing a 64bit version of funtoo - this will not work.
• you are downloading stage3 that ismore than 3 years old - this might not be such a good idea

• On 29.5.2015 at 4:12 PM, linuxbigot said:

  stage3-intel64-sandybridge-funtoo-current-2015-05-29.tar.xz

   

• are you extracting to the newly created filesystem? as it looks like you are trying to extract it to root of the sysresccd

If you want more help I would recommend reading this article:

 

[fabiomen10]

I'm having the same problem but in an instance totally updated.

Some of the commands I have used.

root@sysresccd /mnt/funtoo % lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0 469.9M  1 loop /livemnt/squashfs
sda      8:0    0  14.9G  0 disk
├─sda1   8:1    0   500M  0 part /mnt/funtoo/boot
├─sda2   8:2    0     4G  0 part [SWAP]
└─sda3   8:3    0  10.4G  0 part /mnt/funtoo
sdb      8:16   1   7.3G  0 disk
└─sdb1   8:17   1   7.3G  0 part /livemnt/boot

root@sysresccd /mnt/funtoo % uname -a
Linux sysresccd 4.14.32-std522-amd64 #2 SMP Sat Mar 31 20:05:28 UTC 2018 x86_64 Intel(R) Celeron(R) CPU 1007U @ 1.50GHz GenuineIntel GNU/Linux

root@sysresccd /mnt/funtoo % gcc -march=native -Q --help=target | grep march
  -march=                               ivybridge

root@sysresccd /mnt/funtoo % tar xpf stage3-intel64-ivybridge-funtoo-current-2018-08-26.tar.xz
root@sysresccd /mnt/funtoo % cp /etc/resolv.conf /mnt/funtoo/etc/
root@sysresccd /mnt/funtoo % mount -t proc none proc
root@sysresccd /mnt/funtoo % mount --rbind /sys sys
root@sysresccd /mnt/funtoo % mount --rbind /dev dev
root@sysresccd /mnt/funtoo % env -i HOME=/root TERM=$TERM /bin/chroot . bash -l
zsh: illegal hardware instruction  env -i HOME=/root TERM=$TERM /bin/chroot . bash -l

If anyone can help me. I will be many grateful.