During a reinstallation of Gentoo, I get "Illegal instruction" while trying to do "chroot /mnt/gentoo /bin/bash" as described in installation procedure in the manual. I am using stage3-i686-20110809.tar.bz2 (md5sum match verified). The hardware is a VIA Nehemiah CPU, which is a full i686 CPU. (flags : fpu vme de pse tsc msr cx8 apic sep mtrr pge cmov pat mmx fxsr sse up rng rng_en ace ace_en) The hardware has run Gentoo i686 before without issues. The previous installation was a 2008.0 profile, but I have not been able to determine what stage3-file was used. I posted it as a questions on forums (http://forums.gentoo.org/viewtopic.php?p=6798356) and was suggested to post it as a bug here due to a suspicion of a stage3 build with odd USE or CFLAGS. Reproducible: Always Steps to Reproduce: 1. Perform installation as per instructions in manual (up to the following step) 2. Run: chroot /mnt/gentoo /bin/bash Actual Results: Command returns: Illegal instruction Returns to original shell. Expected Results: Command should return a chrooted bash shell. I will keep my hardware ready for test, if this is needed.
@toolchain: Can you please confirm the correct arch for this processor?
sounds like a dupe of Bug 336020
Marking as duplicate per Mike's comment. *** This bug has been marked as a duplicate of bug 336020 ***
I vote this is not a duplicate - the tinderbox tbz2s[1] and possibly the stages should be rebuilt to fix this, which is an issue for another team to resolve. epia ~ # chroot stage3-i686-20111025/ /bin/bash Illegal instruction Nothing fixed there. [1] http://tinderbox.dev.gentoo.org/default-linux/x86/sys-libs/glibc-2.12.2.tbz2 was last updated before [2] was entered, which I haven't been able to use as a fix. [2] https://bugs.gentoo.org/show_bug.cgi?id=336020#c53
(In reply to comment #4) > epia ~ # chroot stage3-i686-20111025/ /bin/bash > Illegal instruction > > Nothing fixed there. Of course, because bug 336020 is not resolved. Where do you expect the stages to pull a fix from if it isn't in the tree??
*** This bug has been marked as a duplicate of bug 336020 ***
