That's right only when I try to chroot during the installation of gentoo
do I get this error and more importantly only when I'm trying to install
the 2.6.x kernel.

Installing the 2.4.26 kernel is no problem however the
boot leaves me without a cdrom1 I read tha 2.6.x is better at handling a
cdrom1 on a USB port Therefore I'm tring to install a 2.6 kernel WHY ? ?
Will l < somebody > please respond and give me some idea what's giving me
this error please note that I have made every effort to make sure that the
CHOST is correct as according to:
http://www/viaarena.com/Default.aspx...5&ArticleID=61 please note
that I've burned newer gentoo LiveCD's using various machines to make sure
it is not a bad CD

craig enlightened us with:
> That's right only when I try to chroot during the installation of
> gentoo do I get this error and more importantly only when I'm trying
> to install the 2.6.x kernel.

What error? Please copy and paste the full command you're using, and
the full error message. Don't just describe it in the subject.

> Installing the 2.4.26 kernel is no problem however the boot leaves
> me without a cdrom1 I read tha 2.6.x is better at handling a cdrom1
> on a USB port Therefore I'm tring to install a 2.6 kernel WHY ? ?

2.6 is the future, 2.4 is old.

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?

> What error? Please copy and paste the full command you're using, and
> the full error message. Don't just describe it in the subject.

Code Listing 4: chroot into the new enviornment

#chroot /mnt/gentoo /bin/bash
illegal instruction

that's the command
that's the error

Some have suggested that it's the CHOST setting in the make.conf
The one's I've used successfully are posted at:
htt://www/viarena.com/Default.aspx?PageID=5&ArticleID=61
They are the same settings I used when I've installed a 2.4.26 kernel.

craig enlightened us with:
> #chroot /mnt/gentoo /bin/bash
> illegal instruction

Do this and paste the output:

file `which chroot`

> Some have suggested that it's the CHOST setting in the make.conf

Well, since you're using stage3, it could also be that you downloaded
the wrong stage3 tarball.

You can also use a stage1 and just compile everything yourself.

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?

So anyway, it was like, 14:56 CEST Oct 26 2004, you know? Oh, and, yeah,
craig was all like, "Dude,

>> What error? Please copy and paste the full command you're using,
>> and the full error message. Don't just describe it in the subject.
>
> Code Listing 4: chroot into the new enviornment
>
> #chroot /mnt/gentoo /bin/bash
> illegal instruction

Are you sure you unpacked the correct stage for your hardware? The
CHOST setting is completely irrelevant if you can't even get bash to
start in the chrooted environment, since at that point you haven't
even compiled anything.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
15:12:27 up 2 days, 2:36, 3 users, load average: 0.01, 0.02, 0.00
Linux 2.6.9 x86_64 GNU/Linux Registered Linux user #261729

> Are you sure you unpacked the correct stage for your hardware?
It's all comes on one liveCD for the x86 processor
"install-x86-universal-2004.2.iso"

>The
> CHOST setting is completely irrelevant if you can't even get bash to
> start in the chrooted environment, since at that point you haven't even
> compiled anything.

this is what I've been thinking...

On Tue, 26 Oct 2004 15:05:55 +0200, Sybren Stuvel wrote:

> craig enlightened us with:
>> #chroot /mnt/gentoo /bin/bash
>> illegal instruction
>
> Do this and paste the output:

>
> file `which chroot`

this is a command? < which chroot > I'll give it try but I have to pull
the wires out of this computer and plug them into the troubled machine
to test this.. I'll get back to you on this point
> Some have suggested
that it's the CHOST setting in the make.conf
>
> Well, since you're using stage3, it could also be that you downloaded
> the wrong stage3 tarball.
>
its the tar that comes on the x86.iso
> You can also use a stage1 and just compile everything yourself.

That's something I haven't tried yet. I might do this... but I need to get
all the info on this machine.. its a EPIA C3 Ezra M10000 etc.
but it's worth a try to see if I can get over this chroot bump
>
> Sybren

#which chroot
/bin/chroot

On Tue, 26 Oct 2004 07:56:05 -0500, craig wrote:

>> What error? Please copy and paste the full command you're using, and
>> the full error message. Don't just describe it in the subject.
>
> Code Listing 4: chroot into the new enviornment
>
> #chroot /mnt/gentoo /bin/bash
> illegal instruction
>
> that's the command
> that's the error

This is always the result of a binary not compatible with your
sub-architecture.

Could you show us the content of /proc/cpuinfo?

The universal-x86 CD has 5 stages. Which one did you use?

/mnt/loop/stages/stage1-x86-2004.2.tar.bz2
/mnt/loop/stages/stage2-i686-2004.2.tar.bz2
/mnt/loop/stages/stage2-x86-2004.2.tar.bz2
/mnt/loop/stages/stage3-i686-2004.2.tar.bz2
/mnt/loop/stages/stage3-x86-2004.2.tar.bz2

My guess is you used stage3-i686-2004.2.tar.bz2 instead of the x86

FYI, only C3 Nehemiah can run i686 code, well I think they can, but Ezra
cannot do any better than Pentium-mmx

Some info from my own C3-800 /proc/cpuinfo
cpu family : 6
model : 7
model name : VIA Ezra
stepping : 8
cpu MHz : 800.264
flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow

cmov is missing from flags, hence not i686

Useful info from emerge --info
System uname: 2.6.8 i686 VIA Ezra
Gentoo Base System version 1.4.16
distcc[24116] (dcc_trace_version) distcc 2.18 i586-pc-linux-gnu; built Oct 14 2004 17:41:26 [enabled]
CFLAGS="-march=pentium-mmx -Os -pipe -fomit-frame-pointer"
CHOST="i586-pc-linux-gnu"


Hth

> This is always the result of a binary not compatible with your
> sub-architecture.

> Could you show us the content of /proc/cpuinfo?
permission denied
> The universal-x86 CD has 5 stages. Which one did you use?
>
> /mnt/loop/stages/stage1-x86-2004.2.tar.bz2
> /mnt/loop/stages/stage2-i686-2004.2.tar.bz2
> /mnt/loop/stages/stage2-x86-2004.2.tar.bz2
> /mnt/loop/stages/stage3-i686-2004.2.tar.bz2
> /mnt/loop/stages/stage3-x86-2004.2.tar.bz2
>
> My guess is you used stage3-i686-2004.2.tar.bz2 instead of the x86

that is correct

> FYI, only C3 Nehemiah can run i686 code, well I think they can, but Ezra
> cannot do any better than Pentium-mmx

so then your saying I can "not" install a 2.6 kernel? because I'm sure
I've read it being done an on non Nehemiah processors like the Ezra. Mines
a 999.x Mhz and read I believe that those with 800 MHz Ezra's have
installed the 2.6.x kernel. Maybe I'm misunderstand your point.

The state3-i686-2004.2 is the one with the 2.6.2 oh unless you are saying
that .... I wonder.. I bet the x86 has the 2.6 too ah that must be my
error
> Some info from my own C3-800 /proc/cpuinfo cpu family : 6 model
> : 7
> model name : VIA Ezra
> stepping : 8
> cpu MHz : 800.264
> flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow
>
> cmov is missing from flags, hence not i686
>
> Useful info from emerge --info
> System uname: 2.6.8 i686 VIA Ezra
> Gentoo Base System version 1.4.16
> distcc[24116] (dcc_trace_version) distcc 2.18 i586-pc-linux-gnu; built
> Oct 14 2004 17:41:26 [enabled] CFLAGS="-march=pentium-mmx -Os -pipe
> -fomit-frame-pointer" CHOST="i586-pc-linux-gnu"
>
>
> Hth

thanks everyone ... I'll be back