From: Ronan Cunniffe (rcunniff at domain wilde.cs.tcd.ie)
Date: Tue 02 Oct 2001 - 18:45:50 IST
On Tue, 2 Oct 2001, Dave Airlie wrote:
> this means it found your kernel .. so ignore all lilo stuff.. it fails
> before init boot you have either set the wrong root device it should print
> someat and tell you, forgot to add ELF binary support modularised it or
> someat ...
> or did something like compile it for i686 on i586 or so on ..
Wrong root device will give you a kernel panic (with a clear message)
before init is run
Wrong processor family will cause the kernel to halt practically on line
1. IIRC you never even get the message "Linux X.X.X booting...." But the
proc family is (almost?) the first thing checked, and you get told (again
with a clear message) what the problem is.
My guess is that init is expecting X (a la 2.2.X) and getting Y from
2.4.X and going down in flames. It's just occurred to me that while init
will have been modified countless times, there must still be some really,
*really* old DNA in there. Anybody know more about this? (I mean
actually *know* as distinct from a 30 second google result.)
Solution: either reread the last oh, two years worth? of kernel developer
traffic to work out what needs updating, or acquire a full distro built
around kernel 2.4.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:12:27 GMT