Re: [PATCH] 2.0.35: updated Jumbo -4 patch

Andreas U. Trottmann (andreas.trottmann@werft22.com)
Mon, 20 Jul 1998 13:54:24 +0200


On Mon, Jul 19, 1998 at 06:22:14AM +0200, Andrew Derrick Balsa wrote:

> I have moved up check_bugs in /init/main.c, this may be triggering the problem.

That could really be the explanation, since ...

> Could you please try the following, it should solve the problem:
>
> - the Jumbo patch must have left a /init/main.c.orig file. Copy it back to
> main.c, and do a "make zImage" again (that should be pretty fast). Install the
> new kernel and reboot.

... this new kernel boots (and seems to work) fine on the iP and the
Tillamook that caused the problems before. It doesn't seem to break
anything as well, since a so-patched kernel still runs fine on the Cyrix
6x86L. I also tested it on a i486SX where everything seems to work fine as
well.

The iP and the Tillamook get their clock frequency detected (in the case
of the iP, /proc/cpuinfo says 120.00 +- 0.01 MHz, which is totally correct,
whereas the Tillamook is detected to run at 265267154 Hz = 265.26 +- 0.01
MHz... did they cheat me when they sold me a Tillamook 266? :-) )

The 6x86L and the i486SX don't display the clock frequency, but I think
this is caused because they don't have (correctly working) TSCs.

So, thanks a lot for the work you put into this and for your fast response!

-- 
Andreas Trottmann <andreas.trottmann@werft22.com>

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html