Jump to content
funtoo forums
  • 0
linuxbigot

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

Question

12 answers to this question

Recommended Posts

  • 0

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.

Share this post


Link to post
Share on other sites
  • 0
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

 

 

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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: 

Share this post


Link to post
Share on other sites
  • 0

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:

 

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

So called ivybridge processors come in different shapes and sizes. And your cpu does not seem to support aes or avx. Thus the stage3 you used is not the correct one, as it uses avx:

https://www.funtoo.org/Intel64-ivybridge

I would start with a generic stage3 first:

https://www.funtoo.org/Generic_64

and then use the tool cpuid2cpuflags to find the supported cpu flags and then recompile the system with the supported cpu flags set.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...