According to Shawn Campbell: While burning my CPU.
>
>
> Well I might get a flame for this one, but here it goes.
I cant see why, you have asked questions which even i had problems with
"once upon a time".
>
> The other night I started my upgrade from RH 2.0.36-0.7 to 2.2.0 and I never
> did get it to run. I had done mv my linux dir to a backup dir, my rm so
Just a minute, you have a redhat system, the policy of redhat is along the
linux installation guide lines that is, the directory "linux" is a symbolic
link, so you would simply do;
cd /usr/src
rm linux
mkdir linux-2.2.0
ln -s linux-2.2.0 linux
tar xzf linux-2.2.0.tar.gz
cd linux
make config etc etc..
> certain files were only symlinks to the kernel. I had done my make config,
No, "certain directorys" are symlinks to the "kernel source tree".
> make dep, make clean, make modules, and make modules_install. I noticed I
> had 2 errors coming out of my make zImage, plus it said zImage too large try
> bzImage, and I had opted for any features to be in the image. Any ways after
If you got "errors" then you did not get a sucsessfull kernel compile, and
you could not have gotten a zImage if you got the message, "zImage too
large", you need to use "make bzImage" OR compile more options as "modules"
that will not only reduce the kernel size but will save you memory as well
into the bargin.
> getting a small piece of advise from someone in my local LUG group I was
> told the first thing I was missing, the most important piece after copying
> my zImage to /boot.
>
> So the next day I edited my /etc/lilo.conf file to point to
> image=/boot/vlinuz-2.2.0. and ran /sbin/lilo. Now when I boot up my PC
> after it starts to uncompress my kernel it stops at
>
> Kernel panic : kernel compiled for pentium + requires TSC
>
> In swapper task - not syncing
>
> I have tried it as both a 386, and a 586 in my make config step both with
> the same results. Is there some file I am forgetting to remove each time I
> try the process over? I am running on a cyrix (unfortunately) 166 w/ 64Megs
> of memory. I hopefully figured that as of 2.2.0 I would not have to run my
> system in a 386 config (I think) even though it says i586 at the top of the
> screen after boot up.
If you compile a new kernel and copy it to the place stated in
/etc/lilo.conf then you MUST rerun lilo.
I have absolutly no experianve with cryix stuff, however there is some
documentation, read /usr/src/linux/Documentation/Configure.help, 2 places
to look, grep for CONFIG_ALPHA_AVANTI it has a mention about 166 CPU's, you
possably dont have an alpha board but its worth reading, then grep for,
Processor type or
CONFIG_M386
If you persist in having problems drop us another line.
>
> Any help would be greatly appreciated...
>
> Sincerely,
>
> Jrsimon
>
> Remember Linux Rocks - Everything else is just a toy
>
--
Regards Richard.
[EMAIL PROTECTED]
