Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Feb 95 9:44:57 MST
From: (Terry Lambert)
To: (Paul Evans)
Subject:   Re: I goofed. ;)
Message-ID:  <>
In-Reply-To: <> from "Paul Evans" at Feb 8, 95 00:31:48 am

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> Remember me-- the person who couldn't compile his kernel, well I did
> and I cp'ed to /

Did you save an old copy of the kernel in kernel.old or something?

You should be able to type this at the boot prompt, which will save you
some hassle reinstalling an older kernel.

> but, when I boot it crashes, after it loads the kernel and jumps
> to it, it freezes the machine.

What did you add to the kernel above and beyond GENERIC to make it go from
'huge' to 'monster'?  This is what I would suspect first.

Also if you have twiddled the config file without doing a make clean
in the build directory, it could be inconsistant.  You must also do
a make depend before the build, and probably a make clean unless someone
has snuck in and fixed the dependencies.

> Is there a common cause to this problem? (and solution?)

It might be possible for a kernel to be too big to load.  I doubt this.
Probably what you have is a destructive probe causing you problems.

> I will boot off the Install disk and mount my root partition to replace
> (rename) the monster kernel I created with the huge one from the install,
> I think this is the easiest way? (me hopes)

You should be able to type the name of the backup you made of the old
kernel at the boot prompt to boot it instead (see above).  You could also
boot /kernel -c instead, which would let you start dyking out various
drivers until you found the problem (and the boot worked).  This is
probably the fastest way to see what's going wrong.

					Terry Lambert
Any opinions in this posting are my own and not those of my present
or previous employers.

Want to link to this message? Use this URL: <>