Nick Rout wrote:
On Wed, 2004-10-20 at 18:39, Steve Holdoway wrote:
Michael JasonSmith wrote:
On Wed, 2004-10-20 at 17:47, Dale Anderson wrote:
Being that you didnt give any info re what exactly you did to upgrade
the kernel on the formentioned OS it is rather hard for anyone to give
advise in correcting the issue .
I wasn't really looking for advice :) I was venting and it is now
corrected! However, you make a good point. The upgrade path consisted of
tar xfj…
make menuconfig
…
make modules
make modules_install
make bzImage
make install
A prior incantation used "make pkg-rpm" but that caused more problems
that it was worth by removing my old kernel so I had not backup!
(Stupid… operating system.)
no, no, no! That's for a 2.4.x kernel.
For 2.6.x,
1. copy the .config across from the working kernel source
2. make menuconfig
3. make
well of course the two of you are doing the same thing, so "no no no!"
is hardly correct.
in 2.6 make help tells you a lot.
especially that make all makes bzImage, modules and vmlinuz
no parameter makes all
so modules_install is needed in either case
no. Not with fedora core 2, or debian. Slackware, being minimalist,
requires that you manually copy the bzImage yourself. The only other
distro I use is White Box, which is 2.4. make install gives me a good
feeling, but I really don't think it's necessary.
Steve
install uses the script or program in ~/bin/installkernel or
/sbin/installkernel. I personally prefer to install the bzImage by hand.
BTW... you don't use nVidia drivers, do you? I tried the 2.6.9-pre4
kernel with version 6111, and it wouldn't build.
Steve
