Re: kernel has null dereference during boot

[hendrik@topoi.pooq.com]

On Tue, Dec 13, 2005 at 09:05:16PM -0500, Marty wrote:

> After thinking more about your problem I suspect that your new kernel has 
> the wrong processor selected, maybe not the one you think it has.  This 
> will cause a kernel oops early in a boot cycle.  As an experiment, you 
> could try the lowest common denomenator processor option (386 or whatever).

  One of them *was* 2.4.18-1-386.  It failed.
  2.4.18.1-686?? was tried too.  It failed on my old-fashioned classic Pentium,
  of course.  Just stopped dead.

-- hendrik