[Clfs-support] [Fwd: CLFS stops booting after mounting root]

[Andreas Hofer]

In the meantime I tried the following: I copied a statically linked sash 
(shell) binary to the disk and started the thing with init=/bin/sash, 
which works. I can use sash and all its builtin functions. But: If I 
then start an arbitrary binary generated during the CLFS build (for 
example "/bin/ls /") it stops with a message like "pid 734: killed by 
signal 4" which means that the CPU encountered an illegal instruction. 
Since my CPU has a 486SX cor without FPU this can only mean one of the 
following:
	1. The instruction is for 586 or newer
	2. It is a floating point instruction
I can only say that I followed the book (Version SVN-0.0.1-20070715-x86) 
literally. Specifically, in chapter 5.3. "Build Variables" I set:
	export CLFS_TARGET="i486-pc-linux-gnu"
I assumed this should suffice to generate 486 code, but I am not sure 
about floating point.?

Should I define a special CFLAGS for my CPU like CFLAGS"-msoft-float"? 
Any other idea?

Andreas

-------- Original-Nachricht --------
Betreff: CLFS stops booting after mounting root
Datum: Mon, 10 Dec 2007 09:49:19 +0100
Von: Andreas Hofer <Andreas.Hofer at dsa-ac.de>
Organisation: DSA - Daten- und Systemtechnik Aachen GmbH
An: clfs-support at lists.cross-lfs.org

Good morning folks,

my shiny new CLFS disk (Version SVN-20071203-x86) doesn't start up as
expected. The kernel's last words are:

VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 140k freed

... and then: silence, no error message, no nothing.

My target is a Vortex86SX (486 instruction set without FPU) and my host
is a Core2Duo notebook. The funny thing is that I already managed to
build the embedded version of CLFS (VersionSVN-0.0.1-20070715-x86) and
run it successfully on the target.

I then tried to boot the "normal" CLFS build with the kernel from the
embedded version, but same result. Also booting with "init=/bin/sh"
doesn't give me a shell.

Last reason I could think of is that the binaries use floating point
instructions but then I would expect some sort of error message.

Anybody can help? I'm stuck.

Andreas