> Alan,
> When you finished make zImage, did you rerun lilo (if you need to)?
> Did you move the new zImage to root? And did you run the rdev -R /zImage
> -1 (or whatever your kernel is called)?
>
> I had this happen to me a couple times when I would get in a hurry after
> the make zImage finished, and reboot without doing one of the above steps.
>
> namely, I would copy the new zImage to root, but forget to run lilo.
I know I did not, because :
1/ my zImages are in /boot
2/ My standard kernel is summoned as "linux" in LILO
3/ When I install a new kernel, it's /boot/zImage-x.y.zz so that I do not
overwrite an existing one, and it forces me to rerun lilo so that it
understands the tag "new"...
In this case, "new" was recognized and caused an error, while "linux"
loaded 1.3.80 with no problem.
I'll try a new build this weekend...
Christophe Dupre Universite de Montreal
Internet: duprec@jsp.umontreal.ca Qc, Canada
Montreal, Qc, Canada
"Nous ne sommes pas libres de ne pas etre libres, nous sommes obliges de
l'etre" - Fernando Savater
-- Geek Code 2.1 --
GCS d-- H+ s:++ g+ !p au-* a19 w+ v+ C++(+++) UIL++>+++ P+>++ L++
3- E---- N++ K W- M- V-- Y+ t++ 5++ !j R+ G- tv b++
D+ e+ u** h->++ f+ r++ n---(----) y+
#include <disclaimer.h>