Unmapped RAM-write-access, 02036288

Subject: Unmapped RAM-write-access, 02036288
From: Paul F D Krohn (krohn@sirius.com)
Date: Mon Mar 06 2000 - 20:51:46 MST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Marco Reichwald: "Re: Failure with MOL networking and ethertap"
• Previous message: Robert Garnett: "Re: Failure with MOL networking and ethertap"
• Next in thread: Jason E. Stewart: "Re: Unmapped RAM-write-access, 02036288"

and so on, counting in hex.

this is on: yellow dog linux 1.1 with my own 2.2.14 kernel. when i run
startmol, is says it has successfully patched the running kernel.

so i have 2 questions:

1) is there a patch against a 2.2.14 source tree available? patching the
running kernel seems difficult and dangersous, much rather have it
compiled in.

2) has anyone had experience with this error message? at the same time,
i get a X window of the size i have specified in /etc/molrc. my
resolution is 1152x870@75Hz, same as in MacOS.

tia

• Next message: Marco Reichwald: "Re: Failure with MOL networking and ethertap"
• Previous message: Robert Garnett: "Re: Failure with MOL networking and ethertap"
• Next in thread: Jason E. Stewart: "Re: Unmapped RAM-write-access, 02036288"

This archive was generated by hypermail 2a24 : Sun Apr 02 2000 - 21:06:29 MDT