Subject: Re: Booter: "Failed to read kernel image header" on custom kernel
To: Reinier Jonker <rjgjonker@xs4all.nl>
From: Space Case <wormey@eskimo.com>
List: port-mac68k
Date: 03/28/2002 15:51:10
On Mar 28,  5:42pm, Reinier Jonker wrote:
>I've built a custom based on yesterday's -current sources. Unfortunatel, 
>the booter does not accept this kernel as valid. This does not only 
>happen with 2.0.1a1, but also with 2.0.0a10 and 2.0.0a7, always with 
>"Failed to read kernel image header" (or something similar). That leads 
>to the conclusion my kernel is probably faulty :-)

I'm curious -- what do you get when you run `file` on the new kernel?
Also, try a kernel from my latest snapshot and see if it works.

~Steve


-- 
Steve Allen - wormey@eskimo.com   http://www.eskimo.com/~wormey/   ICQ 6709819

Faith is the quality that enables you to eat blackberry jam on a picnic
without looking to see whether the seeds move.

Contrary to popular belief, Unix is user friendly.  
It just happens to be selective about who it makes friends with.
	-Kyle Hearn  <kyle@intex.net>

You couldn't even prove the White House staff sane beyond a reasonable
doubt.
		-- Ed Meese, on the Hinckley verdict