LFS 2.4 - Hang on 1st reboot
kazunobu.kuriyama at nifty.com
Tue Sep 19 11:30:30 PDT 2000
Richard Bland wrote:
> I set the CFLAGS and CXXFLAGS for -march=i486 and -mcpu=i486 in the
> .profile, so it _should_ have compiled to that platform, unless the
> Makefile over-rode.
> I've tried passing init=/bin/bash and even init=/bin/ls from lilo, but
> it just stops.
> -----Original Message-----
> From: Hendrik Volker Brunn [mailto:hvb at gmx.net]
> Sent: Tuesday, September 19, 2000 9:40 AM
> To: lfs-discuss at linuxfromscratch.org
> Subject: Re: LFS 2.4 - Hang on 1st reboot
> On Tue, Sep 19, 2000 at 12:16:42PM -0400, Gerard Beekmans wrote:
> > > On the build machine (i686), the new LFS HDD boots fine.
> > > On the target machine (i486), the new LFS HDD hangs as below.
> > Is your kernel compiled for i486? Run kernel config script and make
> sure you
> > select the proper CPU.
> The kernel boots so it is i486 - but perhaps init was compiled for
> Linux, of course, cannot use such excuses because under Linux -
> "if something is possible in principle, then it is already
> implemented or somebody is working on it".
This comment may be helpful for you, which is taken from
xc/config/cf/xf86site.def in the X Window
* The default optimisation flags for GCC 2.x. -fno-strength-reduce is
* here to work around a bug in -O2 for GCC 2.x on i386 platforms.
* If you are using a version that doesn't have this bug, you can
* uncomment the following line, and remove '-fno-strength-reduce'
* If you are building binaries for a 486, it may be beneficial to add
#define DefaultGcc2i386Opt -O2 -fno-strength-reduce
This suggests that -mcpu=i486 or -march=i486 or both should be replaced
More information about the lfs-dev