[ale] kernel compile won't boot

[Fulton Green]

That's not weird, just a bad combo of certain versions of kernel/gcc/bintools
on your target machine. Is the "compile works" machine also Mandrake, but
just a different version? Or something completely different? Maybe in the
docs supplied in the kernel source tarball, but definitely on kernelnotes.org,
is a list of minimal versions of software needed for a successful compile.
That said, I've been using egcs (the default Red Hat compiler) in lieu of
the legacy gcc for my compiles.

kernelnotes.org) is a list of *minimal* versions of various software you
On Wed, Aug 16, 2000 at 08:16:32AM -0400, Wandered Inn wrote:
> Okay, here's the wierd part.  I compiled the same exact kernel (copied
> the config file over) on another machine.  Took the created kernel and
> put it on the machine that would not boot.  It now boots.  I'm good to
> go, but I'd really like to figure out what was the problem with the
> other kernel.  I recompiled it on the target machine and still had the
> same problem.
> 
> Wandered Inn wrote:
> > 
> > I've just recompiled a kernel for a machine using lilo.  I've seen
> > problems with the boot loader before, such as getting portions of
> > 'LILO.'  This problem is different and I've never seen it.  The kernel
> > begins to boot, I see:
> > 
> > linux.............
> > 
> > But then the machine locks up.  It won't go any further.  Well, it
> > doesn't actually lock up, the keyboard caps lock key will toggle the
> > caps lock led.  Still it justs sits.  This machine is running Manrake
> > 7.1, original kernel was 2.2.15.  I've attempted to upgrade to 2.2.16.
> > 
> > Anyone seen this behavior?  I can't find any docs reflecting this
> > particular issue.
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.